[asterisk-dev] BLF configuration suggestions

Olivier oza.4h07 at gmail.com
Mon Feb 17 04:30:45 CST 2020


Hello,

>From recent experiences with Proneprov and Resource List Subscriptions, I
would like to gather comments on the following enhancements.

These include the following items:
1. Tools for list edition
2. Support of Classical List
3. Phoneprov function to iterate over List items
4. List items labels

1. Tools for list edition
As mentioned in [1], a common use case is "a small office where an Asterisk
server acts as a PBX for 20 people, each with a SIP desk phone. Each of
those 20 phones subscribes to the state of the others in the office".
A natural way to implement this use case would be to define:
- a single common list for all desk phone
- 20 specific list for each phone, each simply removing one entry for the
common list.

If I'm not mistaken, there is currently no way to simply remove one entry
from an existing list.
Having such tool would be convenient.


2. Support of Classical List
Though several SIP phones do support RFC4662 Resource List Subscriptions,
some do not.
What about adding a new 'legacy' eventype in PJSIP resource_list entries ?
This 'legacy' value could be used a simple way to toggle off Resource List
Subscriptions NOTIFY/SUBSCRIBE dialogs
when a list is attached to a phone that do not support RFC4662, the
alternative being to remove or comment out
the whole resource_list entry.


3. Phoneprov function to iterate over List items
Combined with above 'eventype=legacy' feature, a new Phoneprov
PP_EACH_ITEM_LIST() dialplan function would be helpful
to let a sysadmin define within pjsip.conf, BLF configuration for both
RFC4662 supporting and non-RFC4662 supporting phones.
A single unified workflow seems valuable to me.


4. List items labels
Many desk phones have an LCD beside BLF.
If I'm not mistaken, RFC4662 do not allow to associate a label with a List
entry.
What about adding a label to current list_item implementation such as with
list_item="Foo<123>" or anything better than that ?
This label would not be used with RFC4662 Resource List Subscriptions but
could be used with Classical List as defined above.


Comments would be very appreciated.

[1] https://wiki.asterisk.org/wiki/pages/viewpage.action?pageId=30278158

Best regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20200217/66647511/attachment.html>


More information about the asterisk-dev mailing list