This is a nice document, but should also include using the BLF "list" URI subscription. It is much easier to provision when monitoring alot of users and is dynamic (i.e. if the Broadsoft BLF changes, the phone changes with it). There is one MAJOR drawback to doing the "list" method though... When the initial NOTIFY is received, the phone fills in all of the users in the list with only blf+cp, not blf+cp+sd. I REALLY wish this would get resolved, as it would make provisioning BLF's that much easier.
That is indeed good news.. I will try out the new s/w ASAP.
In regards to the call pickup, I have found it to work with no issues. Remember it is not doing a "directed" call pickup on the incoming line.. It is doing a "group" call pickup. Assign your BLF user in a Call Pickup Group along with all of the users that the user is monitoring. When an incoming call comes into one of the monitored users, pressing a flashing button causes the phone to dial a "*98" which picks up the incoming call....
Thanks for your answer. The group call pickup would work in most cases. The problem is if there are two calls coming in at the same time it is difficult to know which one you are answering.
I was hoping for directed call pickup support for Broadworks with the syntax "*97#", where # whould resolve to the blinking extension.
Unfortunatly, this is not working . We have a problem with blf on spa504g phone with broadsoft on tcp only.
The spa504g is not learning the Record-Route within our 200 OK (for the first Subscribe). It must set its route set (Route header) to match the list of URIs in the Record-Route header sent in the response.
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
