Busy Lamp Field (BLF)
Busy Lamp Field Blf
Reputed and Administration as a watcher, will monitor the 'real time' status of a directory number or SIP URI, a BLF presence entity, from watcher device, when you configure BLF Presence in Cisco Unified Communications Manager an interested party. SIP URI makes up a call destination configured with an user@host format, such as xten3@CompB.
BLF presence entity with the subsequent options. Call lists and directories display the BLF status for existing entries. Besides, BLF presence entity displays as a speed dial on the watcher device, when you configure BLF/SpeedDial buttons.
Yes, that's right! For BLF presence supported phones that are running SIP, you may configure directory numbers or SIP URIs as BLF/SpeedDial buttons. Considering the above said. For BLF presence supported phones that were probably running SCCP, you will mostly configure directory numbers as BLF/SpeedDial buttons. You configure BLF/SpeedDial buttons for a phone or user device profile. The BLF value does not have to be on cluster. For data on Busy Lamp Field status icons that display on phone, see Cisco Unified IP Phone documentation that supports our phone. For instance, see Cisco Unified IP Phone documentation that supports our phone and this version of Cisco Unified Communications Manager, in order to identify whether the phone supports LF presence.
Watchers send BLF presence requests to Cisco Unified Communications Manager, with an intention to view a LF status presence entity. 'realtime' status icons display on the watcher device to indicate whether BLF presence entity is usually on the phone, not on status unknown, the phone or on, after administrators configure BLF presence features. Now let me tell you something. Extension mobility users could use BLF presence features on phones with extension mobility support.
Now pay attention please. BLF presence group authorization ensures that solely authorized watchers could access BLF presence status for a destination. BLF presence group authorization does not apply to BLF/Speed Dials, cause the administrator ensures that the watcher has been authorized to monitor the destination when a BLF/Speed Dial was always configured. For phones that have probably been running SIP, BLF presence group authorization does not apply to any directory number or SIP URI that is usually configured as a BLF/Speed Dial that appears in a call list.Sounds familiar? administrators must configure the scheme to accept BLF presence requests from the external trunk or application, with an intention to allow LF presence requests from outside the cluster. Of course you will assign BLF presence groups to trunks and applications outside the cluster to invoke BLF presence group authorization. The SUBSCRIBE Calling Search Space determines how Cisco Unified Communications Manager routes BLF presence requests that come from trunk or the phone. The SUBSCRIBE Calling Search Space that has usually been connected with an end user gets used for extension mobility calls.
|© 2002-2019||Follow us @providerslist|