Yealink Phone Provisioning Issues

[GEEVEE]

I am in the process of switching from a hosted PBX provider to 3CX. I have spent the last few days reading up on the instructions and installing 3XC. I am stumped at the phone provisioning step. Here is a summary of my setup

1. 3CX installed on Microsoft Azure Cloud
2. 3CX SBC installed on site Windows Server (192.168.1.2)
3. All checks on the 3CX dash board checks normal including firewall checks.
4. SIP provider is Call Centric
5. The system configured a default extension 0000
6. I added two extensions 2000 and 2001.
7. Extension 2001 is associated with a softphone installed on an iPhone. I can make and receive calls from this iPhone. However, the phone does not appear in list of phones. In the list of extensions, the extension shows with the Green Circle.
8. I tried to provision a phone to Extension 2001 (local IP 192.168.1.22). The phone is YealinkT48G. Firmware has been upgraded to the 3CX approved version 35.83.0.55. Tried auto provision using both methods (3CX SBC and Direct SIP (Stun Remote). The Phone talks to the 3CX hosted on the cloud and goes through the initialization process and reboots. However, the registration fails. "No service" message shows on the phone screen. The phone shows the 3CX Logo. Tried the whole process multiple times. The extension shows with a red circle and there are no entries in the Phone Tab of the 3CX Management Console.

I am stumped now. Don't know how to proceed from here. What additional checks can point me to the issue. Additional things that I have done are unchecking the "Disallow use of extension outside the LAN (Remote extensions using Direct SIP or STUN will be blocked) " in the Extensions Tab under options.

Any help is appreciated. if there is anyone who can help troubleshoot this please send me a PM and I am willing to compensate you for time and effort.

GEEVEE

 

[nub]

Give rps a try with at least one of the phones.

 

[cobaltit]

I tried to provision a phone to Extension 2001 (local IP 192.168.1.22). The phone is YealinkT48G. Firmware has been upgraded to the 3CX approved version 35.83.0.55. Tried auto provision using both methods (3CX SBC and Direct SIP (Stun Remote). The Phone talks to the 3CX hosted on the cloud and goes through the initialization process and reboots. However, the registration fails. "No service" message shows on the phone screen. The phone shows the 3CX Logo. Tried the whole process multiple times. The extension shows with a red circle and there are no entries in the Phone Tab of the 3CX Management Console.

Confused by this step. When you say provision and then give the local IP did you try to provision the phone as local? That would fit with your description of the problem. Try deleting the phone from the extension and then factory resetting the phone. If you have a SBC local to the phone it should show up in bold in the phones tab. You should be able to then right-click on it and assign it to extension 2001.

 

[GEEVEE]

I will try that. One question though? My SBC is installed on 192.168.1.2. When I factory reset the Yealink and connect it back to the internal network, how will it know that the SBC is on 192.168.1.2? The option to specify is SBC IP is only available when 3XC SBC option is selected. If I select Local LAN option in the phone provisioning screen, it gives two choices for interface 10.0.0.4 and mydomain.3cx.com? Which is the right choice so that the phone can talk to the SBC and then to the 3CX on the cloud.

GEEVEE

 

[Saqqara]

You connect the phone on the same network as the SBC server. The sbc server sees the new phone and sends the request to the 3cx server.

https://www.3cx.com/sip-phones/yealink-t4-series/

Make sure you have unticked ‘block remote tunnel connections’ under the option tab for each extension.

Check you blacklist, to see if the IP address has been blacklisted.

Check you have enabled inbound ports 443 or 5001 (your 3cx https port) on your firewall as this is used by the provisions url

 

[GEEVEE]

Give rps a try with at least one of the phones.

Tried RPS. No luck. The phone goes through the initialization process, a redirector screen comes on the phone asking for a user ID and password. I enter the Extension number (2000) and the password (instructions tells me to use voicemail pin as the password). The credentials are not rejected. After a few minutes I get the update skipped message and the phones comes up with the user screen still showing no service. There is no record of phone attempting to register in the 3CX log. The phone is not showing in the phone tab. In the extension tab, the extension still shows with a Red dot.

 

[nub]

Tried RPS. No luck. The phone goes through the initialization process, a redirector screen comes on the phone asking for a user ID and password. I enter the Extension number (2000) and the password (instructions tells me to use voicemail pin as the password). The credentials are not rejected. After a few minutes I get the update skipped message and the phones comes up with the user screen still showing no service. There is no record of phone attempting to register in the 3CX log. The phone is not showing in the phone tab. In the extension tab, the extension still shows with a Red dot.

settings > network settings > Select Network Card Interface:
could you have the wrong one here?

 

[GEEVEE]

settings > network settings > Select Network Card Interface:
could you have the wrong one here?

Are you referring to the Settings >network settings on the Yealink Phone or in 3CX Console?

 

[Saqqara]

For rps the network address has to be the fqdn address, and not the local ip of the server.

All the info is in the url I posted earlier

 

[GEEVEE]

For rps the network address has to be the fqdn address, and not the local ip of the server.

All the info is in the url I posted earlier

The FQDN is what I used. Not the local IP of the server.

 

[JohnS_3CX]

You connect the phone on the same network as the SBC server. The sbc server sees the new phone and sends the request to the 3cx server.

https://www.3cx.com/sip-phones/yealink-t4-series/

Make sure you have unticked ‘block remote tunnel connections’ under the option tab for each extension.

Check you blacklist, to see if the IP address has been blacklisted.

Check you have enabled inbound ports 443 or 5001 (your 3cx https port) on your firewall as this is used by the provisions url

Please follow the guide as Saqqara suggested and make sure you have the relevant ports needed open. The SBC will facilitate communication with your PBX but the phones provision via FQDN, meaning that at the phone+SBC site the firewall must allow communication with your provisioning ports.

Confirmation of blocked HTTPS ports can be seen if you provisioned the phone via SBC, the phone never provisions, and yet the FQDN appears in your phone's UI when you check the provisioning URL. This means the SBC did its job but the phone had trouble reaching your FQDN. Same issue would occur via RPS if again your FQDN and port are not reachable by the phone.