Yealink T48G will not provision

[that1guy]

Greetings,

I have a T48G that needs to be setup as a remote extension. I have an SBC in place and have confirmed I can connect back to the PBX. When running the AutoProvision from the web UI, I get the configuration message displaying for about a minute. Once "operation complete", the phone does not provision. I have disabled trusted certs and I am using firmware 35.81.0.60.

In the PBX, I see the T48G as a new phone. I select "assign ext" and assign it. I grab the provisioning url and copypasta into the phone web ui. I have tried using host name and IP of the PBX, but no luck. Also tried https and http, but still no cigar.

Any assistance will be greatly appreciated.

3cx v15.

 

[teldata1]

Are you able to manually register the extension to the PBX? As a test that you have full connectivity

SIP Server will be the public hostname or IP of the 3CX, and enable outbound proxy and insert the IP of the SBC in that field.

 

[Gregory Marciano]

Hi,

I have the same issue, with a Yealink T46G, Firmware up to date, 3CX V15.5. Like mentionned by teldata1, I could manually register the extension to the PBX, but it never automatically provisions.
I also connected a Snom D745 which directly auto-provisioned and worked perfectly. That means for me that the firewall and SBC config are good.
So it seems the issue is with Yealink devices.
Does anyone have any idea where the problem can come from?

Thx for help!

 

[that1guy]

I was able to get the phone to provision. Seems like there was an issue with the Sonicwall we have in place. I also believe there is an external factor at play. This phone is a remote extension and I notice it continues to drop from the network. Thinking thats where my problem may lie.

 

[Saqqara]

Do you have the correct firmware / patch for the sonic wall

https://www.3cx.com/blog/voip-howto/sonicwall-firewall-configuration/

 

[that1guy]

Yes, thank you. I have visited that page many times to double and triple check settings.

 

[Gregory Marciano]

Hi,
Just for information, we solved the problem with our Yealink t46g phone. We had to set the parameter "Only Accept Trusted Certificates" to "disabled" in the config page of the phone (menu Security>Trusted Certificates) as we working with our own FQDN.

Now it's working perfectly.