No auto-provisioning when BLFs are set in Extensions?

Status
Not open for further replies.

tss956

New User
Joined
Feb 13, 2018
Messages
19
Reaction score
7
Working on this interesting problem right now.

When I set each extension's BLFs, I can pull up a provisioning template via the web browser: https://[realFQDN].3cx.us/provisioning/38t[edited]qq9/cfg[MAC] if I set the BLF keys to line, or speed dial. BUT if I set them to BLF, I can't get the provisioning template anymore and consequently, the phones don't get provisioned properly.

Phones are GXP-2170 with a custom template. I can set hardcode BLF directly in the custom template and it works fine.

Are there logs kept to show why 3CX won't generate the configuration file if BLF is selected?

Thanks.
 
Last edited:
Setting BLF keys in the console, only works with 3cx standard templates and not custom ones.

To test, configure one phone to use 3cx template

Check this post out, as it has info on where (number) to start the BLF keys https://www.3cx.com/community/threa...p3-and-new-templates-blf-problems-help.54284/
Setting BLF keys in the console, only works with 3cx standard templates and not custom ones.

To test, configure one phone to use 3cx template

Check this post out, as it has info on where (number) to start the BLF keys https://www.3cx.com/community/threa...p3-and-new-templates-blf-problems-help.54284/

Yes, I've read that post, thank you!

Customizing the VPK (virtual multipurpose keys) in the console actually works with custom templates also.

For example, for Grandstream, I can set speed dial, shared parking extensions, line keys, etc...everything except a busy lamp field light using the custom template. If I select BLF instead of shared parking, speed dial, etc...a custom provisioning file stops being generated/served by 3CX. I can't even figure out why it won't generate the provisioning file on the fly.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,884
Messages
589,542
Members
164,741
Latest member
Carsonix