We have purchased some Sangoma phones with an eye to using them in conjunction with OpenVPN as a way to get around various ISPs that seem to block SIP, or at least make it a pain to get configured (Looking at you, Comcast!).
Anyhow, the default “Server Range” for OpenVPN is 10.8.0.0/24, and this conflicts with one of our remote office’s subnets, so we changed it to 10.80.0.0/24. No big deal. VPN is established, proper addresses are given out, and everything seems great, but the phones won’t register.
A little more digging revealed that Endpoint Manager is still setting the “SIP Destination Address” to “10.8.0.1:5060”, even after we have rebuilt the phone configs. We can work around this by editing the template, but it seems that Endpoint Manager ought to see the new Server Range and update the address in the provisioning files. Are we doing something wrong, or is Endpoint Manager not picking up on the change we have made?
I haven’t set up an environment like that before, but we might get a better idea of what could be going on if you let us know what you have for the following:
-In the Endpoint Manager template used for the phones. What is “SIP Destination Address” set to? I know you said it’s “10.8.0.1:5060” in the config files, but what’s it set to on this page? ex. Internal, External, Custom.
-EndPoint Manager Global Settings, what do you have for the Internal and External Address?
-Settings->Asterisk SIP Settings, in the General SIP Settings tab, what do you have for External Address, and what entries do you have, if any for Local Networks?
The “SIP Destination Address” was set to “Internal”. That was when the conf file was written out as “10.8.0.1:5060”. We worked around the problem by setting it to custom and using “10.80.0.1”.
The Endpoint Global internal address is set to the server’s internal LAN address, and the external address is set to the external address of the machine.
Our localnet settings in SIP settings are 10.0.0.0/8 and 192.168.1.0/24, 192.168.2.0/24 and 192.168.3.0/24.