Solved Hotdesking not working since 18.0.6

Status
Not open for further replies.

nicoonline

SOHO User
Joined
Jul 4, 2019
Messages
54
Reaction score
6
Hello,

Since the last update, i cannot provision a new YLT46 & YLT54 as a hotdesking extension.
I have tried to assign to a user => OK
When creating a hotdesk extension, nothing happens on the phone.

Error in syslog:
Mar 9 19:33:48 btsv[722.722]: ANY <0+emerg > 628.599.622:Built-at :Feb 25 2021,13:51:21,Git:cef120c22eeddfc8d4460175fa29466df8b91bc3
Mar 9 19:33:48 btsv[722.722]: ANY <0+emerg > 628.599.924:ANY =6
Mar 9 19:33:48 GUI [556:556]: WIRE<3+error > 628.604.742:[bt alive][true]
Mar 9 19:33:48 GUI [556:556]: WIRE<3+error > 628.652.896:[bt init][successful]
Mar 9 19:33:49 auto[744.744]: ANY <0+emerg > autoServer log :type=1,time=0,E=3,W=4,N=5,I=6,D=7
Mar 9 19:33:49 auto[744.744]: ANY <0+emerg > ANY =3
Mar 9 19:33:49 auto[744.744]: ANY <0+emerg > autoServer service process starts!
Mar 9 19:33:49 auto[744.744]: ANY <0+emerg > Version :7.3.0.134 for release
Mar 9 19:33:49 auto[744.744]: ANY <0+emerg > Built-at:Mar 3 2021,20:10:33
Mar 9 19:33:49 sys [744.760]: ANY <0+emerg > sys log :type=1,time=0,E=3,W=4,N=5,I=6,D=7
Mar 9 19:33:49 sys [744.760]: ANY <0+emerg > LSYS=6
Mar 9 19:33:49 ATP [744.760]: ANY <0+emerg > ATP log :type=1,time=0,E=3,W=4,N=5,I=6,D=7
Mar 9 19:33:49 ATP [744.760]: ANY <0+emerg > ANY =6
Mar 9 19:33:52 sys [867.867]: ANY <0+emerg > sys log :type=1,time=0,E=3,W=4,N=5,I=6,D=7
Mar 9 19:33:52 sys [867.867]: ANY <0+emerg > LSYS=6
Mar 9 19:33:52 WEB [867:867]: ANY <0+emerg > 632.880.702:WEB log :type=1,time=1,E=3,W=4,N=5,I=6,D=7
Mar 9 19:33:52 WEB [867:867]: ANY <0+emerg > 632.881.584:_log_set ANY =6
Mar 9 19:33:53 ATP [744.761]: ATP <3+error > url with auth parameter fail
Mar 9 19:33:53 ATP [744.761]: ATP <3+error > Get static config url fail
Mar 9 19:33:53 GUI [556:556]: APP <3+error > 633.914.524:from[app_vpPhone] sync[0] msg[395306][0][0] size[4] target[0xc401d620] not found
Mar 9 19:33:56 ATP [744.761]: DURL<3+error > [DCMN]Recode is 403, Request err.
Mar 9 19:33:56 ATP [744.761]: DURL<3+error > [DCMN]download common error, errcode:403, no out.
Mar 9 19:33:57 ATP [744.761]: DURL<3+error > [DCMN]Recode is 403, Request err.
Mar 9 19:33:57 ATP [744.761]: DURL<3+error > [DCMN]download common error, errcode:403, no out.
Mar 9 19:33:59 ATP [744.761]: DURL<3+error > [DCMN]Recode is 403, Request err.
Mar 9 19:33:59 ATP [744.761]: DURL<3+error > [DCMN]download common error, errcode:403, no out.
Mar 9 19:34:00 ATP [744.761]: DURL<3+error > [DCMN]Recode is 403, Request err.
Mar 9 19:34:00 ATP [744.761]: DURL<3+error > [DCMN]download common error, errcode:403, no out.
Mar 9 19:34:02 ATP [744.761]: DURL<3+error > [DCMN]Recode is 403, Request err.
Mar 9 19:34:02 ATP [744.761]: DURL<3+error > [DCMN]download common error, errcode:403, no out.
Mar 9 19:34:04 ATP [744.761]: DURL<3+error > [DCMN]Recode is 403, Request err.
Mar 9 19:34:04 ATP [744.761]: DURL<3+error > [DCMN]download common error, errcode:403, no out.
Mar 9 19:34:05 ATP [744.761]: ATP <3+error > Get redirect error.
Mar 9 19:34:05 ATP [744.761]: ATP <3+error > get RPS url error.
 
Hi Nico,

1. Kindly tell us the full model names

2. the exact firmware version each one is using

3. and whether they are Local or SBC phones
 
1. Yealink T46S & Yealink T54W
2. 18.0.6 Build 908
3. SBC Phones
 
Thanks Nico, can I also have the firmware versions please?
 
sure. 66.86.05 (t46s)
 
OK I tested this and can confirm that provisioning is OK under 18.0.6. So let's see what happened in your case though.


Before starting, you must factory reset the phone. Do not proceed if the factory reset has not been done!

1. Firstly, when you add the phone in the Hotdesking page, ensure that the MAC is 100% correct. If there is a typo then provisioning will fail. Copy the MAC from the Phones page to be sure.

2. Then make sure that the correct SBC is selected:

1678365723858.png

3. Finally, go back to the Phones page, select 1 phone and press "Assign Ext" and it will tell you that this will be assigned to HD0000xx

1678365817453.png

4. Your phone should now provision and reboot. Make sure by the way that the SBC is indeed online, if it is not the provisioning will fail. The management console tells you via which SBC the phone was detected under the IP column in the Phones page:
1678366074859.png

Let me know if you have any issues


Note: The T54W firmware should be 98.86.0.74 (this is the supported and tested version). For T46S it should be 66.86.0.5
 
  • Like
Reactions: Evolute IT
What can we do if everything has been done ?
 
I was hoping you would do one from the beginning (just so we can ensure all checkpoints are done) and then tell me what happens after you select the phone and press Assign Ext. and OK.

Your phone log above did not show any attempts to provision, it's almost like the Assign command did not reach the phone for some reason..
 
OK. i found the issue. :) HD0004 is now provisioned. i will try with HD001
 
Ah very nice! What was it?
 
i didn't click on "Assign Extension" :)
 
Ok no problem, everything should be provisioning fine now :)
 
  • Like
Reactions: JohnS_3CX
Status
Not open for further replies.

Members Online Now

No members online now.

Forum statistics

Threads
111,831
Messages
589,277
Members
164,660
Latest member
RJenkinsROCK