BLF changed into Custom Speed Dial

[m.nussbaumer]

Hello,

i have 16.0.9 Enterprise.

when i set an Extension to BLF, some Extensions will be converted into "Custom speed dials" after saving the Provisioning tab.
The settings of all Extensions are the same...

 

[ChrisC_3CX]

This will happen if that extension gets deleted. Is there any chance these extensions did in fact get deleted and then recreated?

 

[m.nussbaumer]

This Extension hasn't been deleted!
Its stil activ and i can call this extensions...

 

[ChrisC_3CX]

Is this something that happens regularly or did it only affect one specific extension and specific BLF?

Is there anyway you can replicate this issue? Once the issue is replicated, does setting the Custom Speed dial back to BLF actually save?

Please also provide the relevant info mentioned here: https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[m.nussbaumer]

Hello,

yes i can change back to BLF and after some time it changes to Custom Speed dial (C.S.d)..
and everytime the same extensions... i have about 90 extensens on one 3cx System... 4-6 are changing to C.S.d.

• 3CX Version, Enterprise Annual 16.0.9
• Server OS, Debian 9 /
• Is the 3CX Server on Premise (VMware)
• IP Phone Make/Model/Firmware Grandstream GXP2160 1.0.11.16
• Provisioning Method: Local
• Trunk Provider AZISTA
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

 

[ChrisC_3CX]

Well that is very strange, do these extensions have anything in common? You say these 4-6 change to CSD everytime. Do they change on every extension? For instance, lets say you have 80 extensions with BLF keys set to these 4-6 extensions. Do the BLF of these 4-6 extensions change to CSD on all 80 extensions?

• Are you using O365 Integration at all to sync users, etc?
• Is there any other 3rd party software installed on the machine hosting 3CX that may be interfering?
• Do you have any scheduled restore tasks on this 3CX Instance?
• In the screenshot you sent, the label for the first name got set to the extension number, does that always happen?

 

[m.nussbaumer]

yes they changed all to CSD for those Extensions
- o365 no
- no only 3CX with all defaults
- no scheduled tasks
- yes, first name is extension...

 

[ChrisC_3CX]

At this point I think a more in-depth investigation is in order as I am unable to replicate the issue you are describing on my end.

I would highly recommend contacting one of our 3CX Partners to get them to help you with troubleshooting this issue and hopefully reaching a resolution.

In the meantime I can only suggest that you try deleting and recreating the 4-6 affected extensions in hopes that the issue is related to their current configuration. You could of course test with 1 to begin with and move on with the rest if it resolves the issue.