Polycom VVX 501 BLF not displaying as built for users in 3CX admin panel

[Callinectes]

We have a system that is not properly provisioning the BLFs that have been set up for the users/phones; they are using Polycom VVX 501s with the recommended firmware. When reprovisioning sometimes the updates take on some of the BLFs but not on others - it has been very inconsistent.

 

[OlegR_3CX]

Does it mean if you reprovision the phone again/reboot etc, the settings will be there? This can be something specific to the phone and not related to the 3CX System, as it's not necessary that the 3CX System did not send the file, is maybe the OS of the phone is not applying it properly etc.

 

[Callinectes]

This is at a customer premises so it is hard to get exact information, but I can tell you that after we recently updated the names on a couple of extensions and then reprovisioned the phones (by using the Reprovision feature of the web admin control panel on the Phones page) the resulting update to the phone was not correct. For example, we updated one extension (x102) with a new name and the resulting phone display after reprovision shows the old name for the extension (x102) but replaced the next extension BLF (which should have been x103) with the new name for the extension (x102) and the next extension (which should have been x103) is completely missing from the display even though it is set properly in the BLF fields in the control panel. This information was sent to us in pictures so it has been verified.

 

[SweetAction]

This is at a customer premises so it is hard to get exact information, but I can tell you that after we recently updated the names on a couple of extensions and then reprovisioned the phones (by using the Reprovision feature of the web admin control panel on the Phones page) the resulting update to the phone was not correct. For example, we updated one extension (x102) with a new name and the resulting phone display after reprovision shows the old name for the extension (x102) but replaced the next extension BLF (which should have been x103) with the new name for the extension (x102) and the next extension (which should have been x103) is completely missing from the display even though it is set properly in the BLF fields in the control panel. This information was sent to us in pictures so it has been verified.

Polycoms need a reboot to apply BLF changes, etc.
Can you confirm that the phone is rebooted? If the phone is in use when you send reprovision, it won't do anything.

 

[Callinectes]

Polycoms need a reboot to apply BLF changes, etc.
Can you confirm that the phone is rebooted? If the phone is in use when you send reprovision, it won't do anything.

When you press the Reprovision button in the admin web control panel (Phones tab) it initiates a phone reboot, so the answer to your question is yes the phones are rebooting to pull their new provisioning data.

 

[SweetAction]

When you press the Reprovision button in the admin web control panel (Phones tab) it initiates a phone reboot, so the answer to your question is yes the phones are rebooting to pull their new provisioning data.

In case it wasn't clear...
I am aware that it needs a reboot and the reprovision button will trigger it. I'm asking if you confirmed the phone actually rebooted. There are a few situations where you can hit reprovision and the phone will not actually reboot.

 

[Callinectes]

In case it wasn't clear...
I am aware that it needs a reboot and the reprovision button will trigger it. I'm asking if you confirmed the phone actually rebooted. There are a few situations where you can hit reprovision and the phone will not actually reboot.

Ah, I see. Yes, the phones did reboot. They even changed but not correctly as mentioned in my reply to Oleg earlier today.

 

[SweetAction]

Ah, I see. Yes, the phones did reboot. They even changed but not correctly as mentioned in my reply to Oleg earlier today.

If you download the xml file manually (provlink/mac-cfg.xml I think, could be wrong) - does the XML have the correct settings? Need to nail down if it's a config file generation issue or a phone issue.

Another way - if you factory a phone and reprovision it - does it show correctly the new BLFs, etc?

 

[Callinectes]

So we looked at the CFG files generated and they were correct, at least at the time we generated them. We then initiated another reprovision - this time of each phone separately instead of at the same time (doubtful this had any effect). The event log showed that the config files were generated and delivered to each phone and the customer confirmed that this time the phones did update properly. Very odd situation but it is now resolved.