BLF Entry: why are some numbers forbidden/impossible to enter?

[nobody]

When you provision a BLF entry for an IP phone, you can choose from a list of extensions, or you can type in a value. The value however can only be chosen from the number of extensions. Why?
For example I would like to add an IVR to a BLF. That works fine if I manually add that on the Phone, but then it will be overridden every day by autoprovisioning, or I have to make a custom template.
Why does 3CX not trust the admins of the pbx enough to allow any value?

 

[nobody]

Bump.
Allowing any number would be an easy thing to change. I do not see any negativ side effects.

 

[Alphabetic]

Why do you need to have a BLF? BLF is used to tell you if an EXT is busy or not.

Simply create a custom speed dial of your IVR.

 

[nobody]

I will explain:
I need to see if an IVR is currently busy with a call. AFAIK this can only be done using a BLF. If I manually setup this on the phone, it works as needed: If a call goes to the IVR the LED is red, otherwise, greeen.
This AVR is for anonymous calls. Any anonymous call goes automatially to this IVR. The IVR answeres and tells: please press #4to transfer your call to a live person, otherwise, hang up. The IVR also is used if I make a call and the other side puts me on hold. Then I transfer the call to the IVR, so I can hang up and dont have to hear the MOH of the other party.
I hope this is reason enough?

Besides of this, why cant I simply enter any number in the BLF number field, I see no need to verify the number against known extensions.

 

[Alphabetic]

In that case, if you want it your only choice is to make a custom template.

 

[TBWD]

In that case, if you want it your only choice is to make a custom template.

Or login to the phone and add the keys, if you do this you will need to remove the Provisioning Link Both of these methods will work but are not supported by 3cx

 

[nobody]

Yes I know that, but disabling autoprovisioning for an extension is not (my) choice and managing custom templates is a PITA when updates are installed.
So we are again at the beginning of the thread, where I asked why it is not allowed to enter any character string in the BLF provisioning field?
One could argue, that if this is not checked against valid extensions a BLF might not work, but an IVR is an extension as any other, and will work like one.
Also why not simple remove the checking an leave it like entered - this will even improve the situation regarding the trouble with copying BLFs, because currently you can only copy a complete extension to a new one, you cannot copy BLFs from an existing extension to an existing extension - instead we are told to delete the extension and recreate it - which will in turn delete all BLFs the extension has relations to other extension - making it impossible to use the new copy BLF feature at all. If you just could enter a number in the field and this number is just treated as a string it wont be deleted when an extension is deleted.