Webclient BLF Disappearing

[bentech]

Hi All,

I have a client that has a Grandstream GXP2140 and that was logging in to their 3CX webclient to updated speed dials and BLFs on their expansion module. I was under the assumption that it was saved on the main 3CX installation then. It was not. The phone reprovisioned from the 3CX main installation and all the BLFs were gone on the expansion module and on the webclient. Is there any way to make the BLFs added on the webclient stay and get added to the extension on the main 3CX installation?

 

[JohnS_3CX]

Hi @bentech

Start by providing all the relevant information as per this post:
https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[TelecomlijnSupport]

Besides all the relevant information it would be good to know if the BLFs did remain visible in the webclient? Are you using the default templates and supported firmware?

 

[bentech]

Here is the information. The BLFs did not remain visible in Webclient. We are using custom templates. The only changes included 4 line keys instead of two so we can get 4 calls at once and custom Weather location as the Auto weather location picks up the wrong location due to the ISP.

• 3CX Version, Standard Annual 16.0.676
• Server OS, Debian
• Is the 3CX Server Hosted and where? Hosted, AWS Lightsail
• IP Phone Make/Model/Firmware Grandstream GXP2140, 1.0.9.135
• Provisioning Method: Local / VPN / STUN / SBC STUN
• Trunk Provider or Gateway Make/Model DIDforSale
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: YES, enable for 4 account line keys on phone first page.

 

[JohnS_3CX]

Hi bentech

Factory reset, and reprovision this device with the 3CX default template to test. Then ask the user to try again and let us know if it provisioned successfully.

When the user makes their changes on the webclient, tell them to restart the phone so it will pick up the changes, or, hit reprovision from your management console. It may take a few seconds after the phone registers before the new BLFs show up.

The phone compatibility with 3CX was probably broken at some level due to the custom template, this test should show us if this is the case. The phone must run with a single account and VPK1 and VPK2 dedicated to the same account (as per manufacturers design and tested templates+firmware for 3CX).