Solved Yealink T46U not provisioning

[cuber]

Hello,

I am using the 3CX SMB Free edition Version 20.0 Update 5 (Build 551) and have been attempting to provision a remote employees Yealink T46U which is classed as a router phone.
We first plugged everything in and attempted to provision the phone via Direct Connection on 3CX however we got the warning from the SIP Server as seen in the image below.


From what I found on the forum, this was related to an incorrect firmware version. We then deleted the phone from 3CX, factory reset the phone and updated the firmware.

After this, we attempted to provision the phone once again via Direct Connection several times, however it seems as if it did not create a provisioning file, all it did was "RPS request for Yealink (MAC:##########) IP Phone of ######, Ruby delivered successfully", as seen here:


Could anyone provide any insight as to why the phone is no longer creating a provisioning file after the firmware update?

Thanks

 

[fortech]

Hi, just sanity check question - did you already review carefully the document from 3cx regarding deployment for this phone, ie,
docs at URL > https://www.3cx.com/sip-phones/yealink-t4-series/

You mention as part-way through you steps-taken, that you did firmware update - is it correct that the phone now is definitely running latest 3cx firmware (ie, as per download from > https://www.3cx.com/docs/phone-firmwares/ it looks like the t46u has firmware release - version - 108.87.0.16 as latest current?)

just figured I would ask to see / etc.

Tim

 

[cuber]

Hey Tim,

Thanks for replying.

We attempted once again the following day, 24 hours after the first attempt and auto provision functioned as it should almost instantly.

Seems as if we were placed on a 24hr ban after the first RPS request which failed due to the incorrect firmware installed by the looks of it.

Thanks for replying!

 

[fortech]

Hey Tim,

Thanks for replying.

We attempted once again the following day, 24 hours after the first attempt and auto provision functioned as it should almost instantly.

Seems as if we were placed on a 24hr ban after the first RPS request which failed due to the incorrect firmware installed by the looks of it.

Thanks for replying!

Ah, lovely, that is great news. Glad to hear it is all sorted! I agree, auto-provision is super fast when it works smoothly
Tim