Yealink Forums

Full Version: BLF audio alert (ring)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Chaps,
when the current BLF audio setting came out i was delighted.
features.pickup.blf_audio_enable = 1
features.pickup.blf_visual_enable = 1
features.blf.ring_type =

But horrified to discover its a global setting for the phone - so all BLF keys assigned to cause the phone to ring in response to a call on any of the monitored extensions.

This makes it almost unusable.

Example 1- a PA supports 5 managers and wants to closely monitor calls to their phones. But the PA has 20 other users monitored on BLF where the old low level audio alert or no audio alert was adequate.

Example 2 - A receptionist answers most inbound calls but if she's not answering the call overflows to a call group of 5 people, each of whom have other BLFs populated .
The current result is the group will be audio alerted for all calls making the feature too disruptive.

Whats needed is the ability to select the Audio alert/ring setting to be made at BLF level not phone level. The setting could just be ring type under the Type 16 key.

Chris
(06-17-2017 09:04 AM)Chris Barron Wrote: [ -> ]Chaps,
when the current BLF audio setting came out i was delighted.
features.pickup.blf_audio_enable = 1
features.pickup.blf_visual_enable = 1
features.blf.ring_type =

But horrified to discover its a global setting for the phone - so all BLF keys assigned to cause the phone to ring in response to a call on any of the monitored extensions.

This makes it almost unusable.

Example 1- a PA supports 5 managers and wants to closely monitor calls to their phones. But the PA has 20 other users monitored on BLF where the old low level audio alert or no audio alert was adequate.

Example 2 - A receptionist answers most inbound calls but if she's not answering the call overflows to a call group of 5 people, each of whom have other BLFs populated .
The current result is the group will be audio alerted for all calls making the feature too disruptive.

Whats needed is the ability to select the Audio alert/ring setting to be made at BLF level not phone level. The setting could just be ring type under the Type 16 key.

Chris

Hi Chris,

Thanks for the feedback, we will send a feature request to our Product team and ask them to optimize this behavior, by the way, may I know how many Yealink phones do you have in total? What kinds of models are they?

Regards,
Yealink_Support
Hi Travis,

The number of phones is 5K, mainly t46 but T41 and T48 also - I'm happy to do without on any of the smaller models. My 5k installed base comes from two estates / reseller channels - My new channel has been running for six months and we have 2.5K users.

There is also another Killer App that we would derive from this blf ring feature:-

The nortel/avaya product set has a feature called MADN - multi appearance directory number. We would use the differentiated ring on blf to emulate this feature. E.g We allocate the main ddi to the receptionists phone - each phone to ring in response to those calls would have a blf for the receptionists extension with ring set. This removes the burden of creating ring groups and queues to ring each phone.

I am aware that T4x has mca and bridge line appearance but we cant deploy that on our current version server.
(06-22-2017 11:45 AM)Chris Barron Wrote: [ -> ]Hi Travis,

The number of phones is 5K, mainly t46 but T41 and T48 also - I'm happy to do without on any of the smaller models. My 5k installed base comes from two estates / reseller channels - My new channel has been running for six months and we have 2.5K users.

There is also another Killer App that we would derive from this blf ring feature:-

The nortel/avaya product set has a feature called MADN - multi appearance directory number. We would use the differentiated ring on blf to emulate this feature. E.g We allocate the main ddi to the receptionists phone - each phone to ring in response to those calls would have a blf for the receptionists extension with ring set. This removes the burden of creating ring groups and queues to ring each phone.

I am aware that T4x has mca and bridge line appearance but we cant deploy that on our current version server.

Hi Chris,

I will send a feature request to our Product team.
If any update, I will let you know.

Regards,
Travis
(06-17-2017 09:04 AM)Chris Barron Wrote: [ -> ]Chaps,
when the current BLF audio setting came out i was delighted.
features.pickup.blf_audio_enable = 1
features.pickup.blf_visual_enable = 1
features.blf.ring_type =

But horrified to discover its a global setting for the phone - so all BLF keys assigned to cause the phone to ring in response to a call on any of the monitored extensions.

This makes it almost unusable.

Example 1- a PA supports 5 managers and wants to closely monitor calls to their phones. But the PA has 20 other users monitored on BLF where the old low level audio alert or no audio alert was adequate.

Example 2 - A receptionist answers most inbound calls but if she's not answering the call overflows to a call group of 5 people, each of whom have other BLFs populated .
The current result is the group will be audio alerted for all calls making the feature too disruptive.

Whats needed is the ability to select the Audio alert/ring setting to be made at BLF level not phone level. The setting could just be ring type under the Type 16 key.

Chris
+1 from me.
Instead of a Ring Group ringing a group of phones, you could have a BLF on each of the phones that rings which you use to pick up the call. I have a number of customers who would like this.

Mike
Reference URL's