- Joined
- Sep 13, 2021
- Messages
- 10
- Reaction score
- 2
Hello,
This is our first setup of 3CX with SBC:
3CX Server on one site, required ports In/Out opened and firewall check all passed. local phones connected directly to main 3CX server does not auto-provision because of multicast issues we are having with an old Alcatel core switch but if we use the manual URL in our Yealink T31P it is provisioning just fine, so we have no problem keeping it this way.
On another site, we have SBC which is connected normally in the main 3CX server, SBC is having full internet access without any restrictions.
Now when we connect a new Yealink phone in the SBC site it shows as "New" in the Phones list but if we assign extension nothing happens. Also tested adding the manual URL in phone as we do in the main site also nothing happens.
One workaround that worked for us is to allow internet access to the Yealink phone, then the phone is provisioned normally and works just fine in both ways, complete auto-provision and Assign Ext. or with manual URL.
After the previsioning, the phone keeps working even if we disable the internet access of Yealink phone and even if we reboot the phone with internet disabled. I assume from that point it is working with SBC as its SIP proxy. But if we change any setting in the User settings (Management Console) like BLF and re-prevision the phone nothing happens, unless we again allow internet access on yealink and re-provision.
During our troubleshooting, I used the network Diagnostics page in 3CX to ping the FQDN of our 3CX server, it is able to resolve through our local DNS but cannot pint without internet, which is the expected behavior.
When we allow internet to Yealink our firewall shows connections from Yealink to our FQDN and public IP of 3CX server on port 5001.
If we are using the manual URL which contains the FQDN I assume that it actually requires internet connection, otherwise how it will reach the mentioned FQDN to get the config file?
I was under the assumption that phones behind SBC uses SBC for any communication required. In a normal configuration, does the phone behind 3CX requires connection to the main 3CX for provisioning? or are we having any misconfiguration?
3CX Server 18.0.237
SBC 18.0.30
Yealink T31P with latest firmware from 3CX site 124.86.0.35
This is our first setup of 3CX with SBC:
3CX Server on one site, required ports In/Out opened and firewall check all passed. local phones connected directly to main 3CX server does not auto-provision because of multicast issues we are having with an old Alcatel core switch but if we use the manual URL in our Yealink T31P it is provisioning just fine, so we have no problem keeping it this way.
On another site, we have SBC which is connected normally in the main 3CX server, SBC is having full internet access without any restrictions.
Now when we connect a new Yealink phone in the SBC site it shows as "New" in the Phones list but if we assign extension nothing happens. Also tested adding the manual URL in phone as we do in the main site also nothing happens.
One workaround that worked for us is to allow internet access to the Yealink phone, then the phone is provisioned normally and works just fine in both ways, complete auto-provision and Assign Ext. or with manual URL.
After the previsioning, the phone keeps working even if we disable the internet access of Yealink phone and even if we reboot the phone with internet disabled. I assume from that point it is working with SBC as its SIP proxy. But if we change any setting in the User settings (Management Console) like BLF and re-prevision the phone nothing happens, unless we again allow internet access on yealink and re-provision.
During our troubleshooting, I used the network Diagnostics page in 3CX to ping the FQDN of our 3CX server, it is able to resolve through our local DNS but cannot pint without internet, which is the expected behavior.
When we allow internet to Yealink our firewall shows connections from Yealink to our FQDN and public IP of 3CX server on port 5001.
If we are using the manual URL which contains the FQDN I assume that it actually requires internet connection, otherwise how it will reach the mentioned FQDN to get the config file?
I was under the assumption that phones behind SBC uses SBC for any communication required. In a normal configuration, does the phone behind 3CX requires connection to the main 3CX for provisioning? or are we having any misconfiguration?
3CX Server 18.0.237
SBC 18.0.30
Yealink T31P with latest firmware from 3CX site 124.86.0.35