Is there any thought to support BLF List URI's in future FreePBX versions?

FreePBX Endpoints
1

I notice that BLF List URI’s have been supported in Asterisk for a while now:

I noticed that there was 1 query back in 2017 then tagged in 2021 regarding this but listed as not supported:

The poster said they thought this was a Yealink specific thing - but it’s not.

BLF URI’s are supported by these phones, Yealink, Cisco 3PCC, Cisco Phone OS, Fanvil, Grandstream, and a few other minor player phones (like Flying Voice) as well as some “cloud PBX” like Cisco BroadSoft/BroadWorks (which is OEMed to Vonage, Spectrum Enterprise, Cox Communications, Comcast, Verizon, BT, and AT&T via ClearSpan) as well as Webex, now Cisco Cloud Calling.

It’s obvious why the major cloud PBX providers are encouraging this since it reduces their bandwidth requirements.

I’m just curious if there’s been any discussion on providing configuration support in the FreePBX GUI.

1 Like
2

Interesting you posted this. Something I’ve been dabbling with:

SCR-20251229-tuy
SCR-20251229-tuy2714×974 158 KB

It will make a new conf file pjsip.rls.conf and hooks into the Pjsip conf configuration so pjsip.conf includes the new conf file.

RLS wants the list items in extension@context format except for when the item is another list. I’ve made it so you don’t have to include the default contexts (from-internal or default) when you add/update the list.

For dialog/presence you add something like this

100
101
200@east-office ; this is a custom context
sales_list@rls_list

@rls_list is just a way to flag RLS lists so the final output for the conf would be

list_item = 100@from-internal,101@from-internal,200@east-office,sales_list

For message-summary (MWI) you add something like this

100
101
200

the final output for the conf would be

list_item = 100@default,101@default,200@default

If the week stays slow, I should have a beta for testing this week at some point.

2 Likes