Yealink W60B - Unable to Access Provisioning file

[monty_frankel_technology]

Hi all,

We have a Yealink W60B that we're having some trouble with. I've taken over management of this system so I don't have the full history. This base station was just working with this system, but was not showing under Voice & Chat, and was instead showing under phones, with the MAC listed as "UNPROVISIONED". There are other W60B base stations in that status that are currently working.

We wanted to reset these properly to ensure they are provisioned correctly, so we took one base station, deleted it under phones, factory reset it, and then tried to re-add it. It adds to 3CX properly. We then followed the instructions and put the provisioning link into the base station and hit auto configure, which never applies.

Looking at the event log, we do see that the system successfully generates a provisioning file. However, looking at the log on the phone, from what I can see the file is not available? Trying to access the link in a browser also times out, but we're able to see / download other provisioning files through the browser.

Any ideas?

We're using 3CX through Lightsail, and do have an SBC on site which is working properly with all other phones and 1 Yealink W70B base station.

EDIT: One note I forgot to add, we did manually update the firmware on the device to the latest 3CX firmware, per the provisioning instructions.

Screenshot of the pbx showing the file generated:



Relevant Log from base station (I think):
2024/10/15 16:50:44.560|0022|Trac| [_3CX.Http] [7]+223.165.104.27 GET https://xxxxxxxxxx.3cx.us:443/provisioning/*** - - -
2024/10/15 16:50:44.560|0022|Trac| [ManagementConsoleJS.Results.ProvisioningActionResult] PRV: file=/provisioning/mzp0gltjv922zl/805ec0XXXXXX.boot
2024/10/15 16:50:44.560|0022|Info| [_3CX.Provisioning.Provisioning] PRV: Requested file is not found in file system
2024/10/15 16:50:44.560|0022|Info| [ManagementConsoleJS.Results.ProvisioningActionResult] PRV: error getting /provisioning/mzp0gltjv922zl/805ec0XXXXXX.boot requested from 223.165.104.27
2024/10/15 16:50:44.560|0022|Trac| [ManagementConsoleJS.Results.ProvisioningActionResult] PRV: expired 1, remains 1
2024/10/15 16:50:44.560|0022|Info| [_3CX.Http] [6]-223.165.104.27 GET https://xxxxxxxxxxx.3cx.us:443/provisioning/*** - 404 - - 0.4819ms

 

[TheodorosG_3CX]

Are you able to reach the FQDN from the base location?

 

[JohnS_3CX]

Hi,

I can confirm that this works on V20 Update 3 using firmware 77.85.0.25, even though this model is end of life.

Your Event Log seems to indicate that the config file was indeed generated.

Trying to access the link in a browser also times out, but we're able to see / download other provisioning files through the browser.

Don't see how that is possible when the log was generated, unless there is some networking issue at play.

 

[monty_frankel_technology]

Are you able to reach the FQDN from the base location?

From what I'm seeing, the W60B does not have the option to ping? There is no diagnostic section under the Network tab like there is on other Yealink models. Am I overlooking something, or is there a way to see in the device log that it can reach it?



For reference I did test from another phone on the same subnet / vlan, and (after enabling ping in Lightsail) it resolves the IP properly and can ping our 3CX instance without issue:

Hi,

I can confirm that this works on V20 Update 3 using firmware 77.85.0.25, even though this model is end of life.

Your Event Log seems to indicate that the config file was indeed generated.



Don't see how that is possible when the log was generated, unless there is some networking issue at play.

So I went back to double check this and did notice something.

At 11:03 AM I hit auto provision on the base station GUI. Looking at the event viewer, I see two entries at that time? The first one says it was generated, but the second says it was not.

I then tried from a web browser at 11:05 AM and only got the message that it could not be generated.



Let me know if I can provide any logs or anything else that would help. Thanks!

 

[ivank]

You may enable Verbose logs, retry "auto provision" that generated these 2 records from above and check 3CXManagementConsole.log. Filter out using PRV tag, there should be some explanation why it failed.

 

[monty_frankel_technology]

I believe I found the event, but I'm having trouble interpreting what I'm seeing. I've replaced the office IP with [Public IP] in the logs:

2024/10/29 14:10:43.421|0046|Trac| [_3CX.Http] [9]+[Public_IP] GET https://grosswelch.3cx.us:443/provisioning/*** - - -
2024/10/29 14:10:43.421|0046|Trac| [ManagementConsoleJS.Results.ProvisioningActionResult] PRV: file=/provisioning/mzp0gltjv922zl/805ec0a0d79f.boot
2024/10/29 14:10:43.422|0046|Info| [_3CX.Provisioning.Provisioning] PRV: Requested file is not found in file system
2024/10/29 14:10:43.422|0046|Info| [ManagementConsoleJS.Results.ProvisioningActionResult] PRV: error getting /provisioning/mzp0gltjv922zl/805ec0a0d79f.boot requested from [Public_IP]
2024/10/29 14:10:43.422|0046|Trac| [ManagementConsoleJS.Results.ProvisioningActionResult] PRV: expired 1, remains 1
2024/10/29 14:10:43.422|0046|Info| [_3CX.Http] [8]-[Public_IP] GET https://grosswelch.3cx.us:443/provisioning/*** - 404 - - 0.5268ms
2024/10/29 14:10:43.808|0046|Trac| [_3CX.Http] [9]+[Public_IP] GET https://grosswelch.3cx.us:443/provisioning/*** - - -
2024/10/29 14:10:43.808|0046|Trac| [ManagementConsoleJS.Results.ProvisioningActionResult] PRV: file=/provisioning/mzp0gltjv922zl/y000000000000.boot
2024/10/29 14:10:43.808|0046|Info| [_3CX.Provisioning.Provisioning] PRV: Requested file is not found in file system
2024/10/29 14:10:43.808|0046|Info| [ManagementConsoleJS.Results.ProvisioningActionResult] PRV: error getting /provisioning/mzp0gltjv922zl/y000000000000.boot requested from [Public_IP]
2024/10/29 14:10:43.808|0046|Info| [_3CX.Http] [8]-[Public_IP] GET https://grosswelch.3cx.us:443/provisioning/*** - 404 - - 0.5138ms
2024/10/29 14:10:44.234|0046|Trac| [_3CX.Http] [9]+[Public_IP] GET https://grosswelch.3cx.us:443/provisioning/*** - - -
2024/10/29 14:10:44.235|0046|Trac| [ManagementConsoleJS.Results.ProvisioningActionResult] PRV: file=/provisioning/mzp0gltjv922zl/y000000000077.cfg
2024/10/29 14:10:44.236|0046|Trac| [_3CX.Provisioning.Provisioning] PRV: Requested file will be generated
2024/10/29 14:10:44.242|0046|Trac| SetProvLinks PROVLINKLOCAL will be secure if possible
2024/10/29 14:10:44.247|0046|Info| [_3CX.Http] [8]-[Public_IP] GET https://grosswelch.3cx.us:443/provisioning/*** - 200 404 application/octet-stream 12.9265ms
2024/10/29 14:10:44.628|0046|Trac| [_3CX.Http] [9]+[Public_IP] GET https://grosswelch.3cx.us:443/provisioning/*** - - -
2024/10/29 14:10:44.628|0046|Trac| [ManagementConsoleJS.Results.ProvisioningActionResult] PRV: file=/provisioning/mzp0gltjv922zl/805ec0a0d79f.cfg
2024/10/29 14:10:44.628|0046|Info| [_3CX.Provisioning.Provisioning] PRV: wrong prov subdir specified
2024/10/29 14:10:44.630|0046|Info| [_3CX.Http] [8]-[Public_IP] GET https://grosswelch.3cx.us:443/provisioning/*** - 404 - - 2.5584ms
2024/10/29 14:10:45.479|0019|Debg| [MyPhone.RefQueue] SBCRUNTIMEDATA.6.Updated is ready

Only things I'm seeing that look like errors are
2024/10/29 14:10:43.422|0046|Info| [_3CX.Provisioning.Provisioning] PRV: Requested file is not found in file system

and

2024/10/29 14:10:44.628|0046|Info| [_3CX.Provisioning.Provisioning] PRV: wrong prov subdir specified

 

[MikkelAnd]

Hi, @monty_frankel_technology

Did you ever find a solution to this? I have some T54W phones stuck exactly like this?
I could do a manuel update, but would much rather have it working as expected

/mikkel

 

[JohnS_3CX]

Hi, @monty_frankel_technology

Did you ever find a solution to this? I have some T54W phones stuck exactly like this?
I could do a manuel update, but would much rather have it working as expected

/mikkel

I'm not sure you have the same issue. Can you start a new post here https://www.3cx.com/community/forums/yealink/ and describe in detail? Maybe it's something we can help with.

Include firmware version, 3CX version, how they are provisioned (Local with 3CX, or SBC?)