Yealink T48S Stuck on Registering.

Status
Not open for further replies.

Delmir

Customer
Basic Certified
Joined
Mar 4, 2020
Messages
3
Reaction score
0
Having an Issue with Yealink T48S getting stuck on registering when trying to auto provision.( Using STUN)
I manually enter in the provisioning URL and it will get majority of the settings such as contact Speed dial keys, but not register the account it seems to get stuck and does not fail it continuously says "registering". If i do not put this URL in it will not pull down any configuration.

Phones have been factory reset, updated and still not working. Have registered with the same accounts on a yealink T53 which worked. Have also tried to provision the phones on another working 3CX instance and this did not work either.

i can manually put the account details in and this will allow the account to work but it does not give them access to the contact and preconfigured keys.


Any ideas would be helpful. I am leaning towards a phone issue and have raised a ticket with Yealink, any ideas on some items to check would be appreciated.

1606365899438.png

Cheers,
 
Last edited:
Information to provide when requesting help | 3CX - Software Based VoIP IP PBX / PABX

Was the T53 behind the same firewall? Did you do all the port forwarding on the phone side (unique SIP and RTP ports) for the phone?

I manually enter in the provisioning URL and it will get majority of the settings such as contact Speed dial keys, but not register the account it seems to get stuck and does not fail it continuously says "registering". If i do not put this URL in it will not pull down any configuration.

Don't confuse provisioning with registering. It's getting ALL of the settings, not the majority of the settings. It's just not registering. Make sure the box 'Disallow use outside of LAN' is unchecked for the extension. I assume it is since you said it worked on a T53 but just in case. You can also try going into the phone after it provisions and try changing it from UDP to TCP. If that solves it then I would blame SIP ALG on the firewall.
 
  • Like
Reactions: Evolute IT
No Port forwarding or anything unique kept everything basically default exact same scenario for the T53. Did Untick the box Disallow use outside of LAN.
Changing it to TCP allowed it to register for a short period of time i tried to dial out, heard nothing and then it went to register fail. Trying to repeat it and i cannot. Think this is a SIP ALG issue?
There is a separate phone system set up and working correctly on this network, plans are to migrate them across.


  • 3CX Version Standard Annual 16.0.655
  • Server OS, Debian 9
  • Is the 3CX Server Hosted and where? We host it in a datacentre
  • IP Phone Make/Model/Firmware Yealink T48S, Latest Firmware
  • Provisioning Method: Local / VPN / STUN / SBC Stun
  • Trunk Provider or Gateway Make/Model: Audiocodes Trunk
  • Has the Firewall Checker passed: YES
  • Are custom Phone Templates being used: NO
 
Last edited:
If there isn't a VPN to that data center then your next step should be to setup a SBC. That is the preferred way for multiple phones behind a single NAT device and will say you a LOT of time. Then you won't have to worry about port forwarding or SIP ALG or anything else.
 
You put me on to the right path, i went and changed it to be using SIP TLS by passing all the SIP ALG settings and this seems to have resolved the issue. I now need to figure out how to get the provisioning to send out TLS as the transport method. Thanks!
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,990
Messages
590,161
Members
164,926
Latest member
tohoken1