You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create BLF Hints for call forward toggle to a specific extension and for normal behaviour.
when forwarding extension 695 to 1111 with *966951111 shows the forwarding state for this forward to BLF button
when forwarding extension 695 to 2222 with *966952222 shows the forwarding state for this forward to BLF button
Not only when use *96695
The text was updated successfully, but these errors were encountered:
The only way I can think of having hints work this way, is for the pbx admin to specify a list of all the possible forwarding destinations that a user can use, and then creating hints for each of them. This would prevent the user from being able to choose their own forwarding destination that an admin has not previously defined.
This is enough of a change that you're we're talking about creating a whole new feature code module, not merely modification to the existing.
Thanks for the quick reply .
I thought it would be simpler and wouldn't require as much modification.
On classic PBXs this is a common operation.
On Aastra and Mitel workstations with Asterisk and Freepbx it was possible with the XML API and users really appreciated this mode of operation.
FreePBX Version
FreePBX 17
Improvement Description
Create BLF Hints for call forward toggle to a specific extension and for normal behaviour.
when forwarding extension 695 to 1111 with *966951111 shows the forwarding state for this forward to BLF button
when forwarding extension 695 to 2222 with *966952222 shows the forwarding state for this forward to BLF button
Not only when use *96695
The text was updated successfully, but these errors were encountered: