Extension Module grayed out for an extension

[kanchan.verma]

I’m facing an issue where a customer’s extension module is grayed out, even though it has been configured under the user extension in 3CX.

The extension module includes the following button configurations:
• BLF
• Speed dials
• Change status
• Shared parking buttons

All settings appear to be correctly assigned on the user extension; however, the module remains unavailable/grayed out on the phone.

Could you please advise what might be causing this behavior and if there are any additional settings, limitations, or checks required?

 

[TheodorosG_3CX]

What is the ip phone and expansion module model/firmware?

 

[kanchan.verma]

phone is GXP2170 and it got local IP as 192.X.X.X instead of public IP.
Also it shows up as local phone in 3CX.

 

[NikosT_3CX]

@kanchan.verma ensure that the phone is on the firmware 3cx recommends as a first step.
Also from your screenshot I can see BLFs on the Expansion module. What are these for ?
They are not the ones setup on the PBX side ?


https://www.3cx.com/docs/phone-firmwares/

​

Grandstream 2170 IP Phone

Grandstream GXP-2170 FW: Maintenance release

Firmware here : Download

​

 

[kanchan.verma]

it is on right firmware 1.0.11.74 , the one u see on expansion module are the one we added in 3cx but on cx end it shows grayed out and not working

 

[Alphabetic]

is this read any good for you?

Solved Thread 'BLF Keys greyed out.'

Aug 24, 2023

I did a new install of 3cx linux based, 18.0 Update 8(Build 917). It is the current version that does not have the local IP for provisioning anymore, you have to use the FDQN. I have all the BLF configured for each extension and they show up on the grand stream 2170's but they are greyed out. If I make a change to a BLF and re provision the phone it makes the change they just stay grey out. Just cant figure out why they are greyed out.

• bustech
• blf buttons
• Replies: 17
• Forum: Other

 

[NikolasA_3CX]

Is this Phone local to the PBX or remote? If its remote do you have an SBC?

 

[kanchan.verma]

It points to the 3CX cloud PBX (my3cx.ca), not a local PBX or an installed SBC.
• Your remote phone will provision directly from the 3CX cloud.
• 3CX cloud handles the remote registration and NAT traversal automatically — so in this case, an SBC isn’t required.

 

[NikolasA_3CX]

If the phone is remote to the PBX, the supported way is to use an SBC.

 

[kanchan.verma]

The phone is remote — it’s located at the customer site outside our internal network. However, it connects to our 3CX cloud PBX directly via the provisioning URL, so a separate SBC is not required.

 

[Charles_3CX]

Please note that you must have a 3cx SBC on site with the phones to provision them to a 3cx system in the cloud. This is mandatory; there are no exceptions for remote phones other than using a Site-to-Site VPN so phones communicate with the 3cx via the VPN to its local IP. What you have right now is not supported and will cause issues.