- Joined
- Nov 17, 2017
- Messages
- 912
- Reaction score
- 586
This particular call box isnt my favorite, but in a pinch they are usefull as they support PoE, but also for bigger pinches, such as when PoE is not available, they have WiFi built in as well, so all you need is power.
These are my findings in setting up a couple of them for a situation where there is no possibility to run networking to the endpoint, but power is available.
The username and extension must be the same, as the device uses the SIP Username as its extension, so for our example, we set the extension and SIP username to 980
The will not accept special characters in the SIP Password, so you need to use only alphanumerics, such as DoOrBeLL for a password
For what they call the proxy url, which is actually the Sip Server, put your 3CX FQDN, without port, so example, xxxxx.az.3cx.us
We also had issues until we enabled Allow Receiving Calls in the Doorbird, when we did this, it suddenly registered properly.
In the SIP Calls section, this is where you specify who to call, put in the extension url, in such case the receptionist is ext 100, you would do, [email protected].3cx.us
After doing this, the doorbird functioned properly as a remote extension to a cloud hosted 3CX server, without any form of VPN in place.
Hope this helps someone, i just had to mess with getting several of them working, and I STRONGLY AGREE. the user interface of their setup app is a PITA.
These are my findings in setting up a couple of them for a situation where there is no possibility to run networking to the endpoint, but power is available.
The username and extension must be the same, as the device uses the SIP Username as its extension, so for our example, we set the extension and SIP username to 980
The will not accept special characters in the SIP Password, so you need to use only alphanumerics, such as DoOrBeLL for a password
For what they call the proxy url, which is actually the Sip Server, put your 3CX FQDN, without port, so example, xxxxx.az.3cx.us
We also had issues until we enabled Allow Receiving Calls in the Doorbird, when we did this, it suddenly registered properly.
In the SIP Calls section, this is where you specify who to call, put in the extension url, in such case the receptionist is ext 100, you would do, [email protected].3cx.us
After doing this, the doorbird functioned properly as a remote extension to a cloud hosted 3CX server, without any form of VPN in place.
Hope this helps someone, i just had to mess with getting several of them working, and I STRONGLY AGREE. the user interface of their setup app is a PITA.
