Moved to Hosted and have a small issue

[Nicholas Butler]

the issue Im having is if I change a name on a phone or on any BLF"s, it wont update.. Ive even waited 2 weeks.. Ive had to factory reset the phones in order for it to get the proper button BLFs. is ther some way to get it to push the changes?

Im using a SBC and T48s yealink phones.

 

[Kevin@voxtelesys]

Does that same thing happen with the T48 provisioned via STUN? I think the SBC's have a limitation on their BLF's depending on what you have for your SBC.

 

[JohnS_3CX]

Hi Nicholas,

This sounds like the phone is not automatically provisioning itself as expected.

Normally when you perform such changes, you need to go to the 3CX phones tab, select the affected phones and press the reprovision button. Assuming the phones are not behind a restrictive firewall, they should attempt to reprovision themselves within a few moments.

 

[JohnS_3CX]

Does that same thing happen with the T48 provisioned via STUN? I think the SBC's have a limitation on their BLF's depending on what you have for your SBC.

I don't think this is related to what Nicholas is saying, his labels are not updating which is not something related to the SBC.

 

[Nicholas Butler]

I tried to reprovision and that doesn't work.. only factory reset

 

[JohnS_3CX]

Kindly read the below and provide us more info on your deployment so we may better understand the case

https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[Nicholas Butler]

• 3CX Version, 16.0 Update 7 (Build 1078) Annual Latest
• Server OS, Raspberry Pi SBC
• Is the 3CX Server Hosted and where? 3CX Hosted
• IP Phone Make/Model/Firmware: Yealink T48S 66.85.0.5 Latest
• Provisioning Method: Local / VPN / STUN / SBC SBC
• Trunk Provider or Gateway Make/Model Wiretap Telecom
• Has the Firewall Checker passed: YES / NO YES
• Are custom Phone Templates being used: YES / NO NO

 

[JohnS_3CX]

Thanks Nicholas. So since you have moved to hosted here is what I suspect:

1. You moved to hosted, but your old server is still running the phone might be trying to reach the old server for provisioning. Ensure there is no 2nd PBX running and causing confusion

2. Your phone provisions when factory reset, but once it is provisioned it gets a provisioning link that doesn't point to your PBX, hence any reprovisioning attempt will fail. Ensure you have followed the guide to provision the phone is SBC mode https://www.3cx.com/sip-phones/yealink-t4-series/

3. If none of the above turn out to be the issue, then I would highly recommend to ask your 3CX Partner to take a look because it will probably be something that is not so straightforward to detect. In case you don't already have a partner, you can look here https://www.3cx.com/ordering/find-reseller/

 

[Nicholas Butler]

the old server is long since been repurposed. but the SBC is using the same internal IP address of the original 3cx pbx. But a good point is that all the phones weren't reprovisioned after the move to the 3cx cloud service. with that, im thinking that they ALL need to be reprovisioned from factory to get that code from the SBC fresh..

 

[JohnS_3CX]

This is an important detail Nicholas, they will indeed have the wrong provisioning now.

Factory reset, and reprovision them as per our guide please and let us know how it went