Yealink Forums

Full Version: "On the Phone" or "User Busy" status display into caller phone LCD
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Hi,

I'm wondered if this feature is already implemented, but I haven't found an answer, so I'll asking here.

Suppose the following scenario:

Involved Users:
201
202
203

Call flow:
- all users have Call Waiting enabled.
- 201 call 202
- 202 answer to 201
- when 201 is on the phone with 202, 203 call 201
- 201 hear the background call waiting tone, and into yealink display can see the call coming from 203
- 203 hear the ringing tone, but it can't figure out that 201 is already on the phone
- 201 can't answer to 203 because the call with 202 is very important
- 203 after some time giveup the comunication thinking that 201 is not in office

the question is:

Exist a way to show a message into 203 LCD that 201 is already occupied into another conversation?

I seen this features into 3com phones connected to 3com PBX, and that phones display "On the Phone" message status into caller LCD.

I'm trying to accomplish that feature using T26 phones connected to Asterisk 1.8.15 PBX.
Of course using the BLF keys is not the solution.

Thank you very much for the support.

Best Regards
Hi Ugo,
Sorry currently we don't have such feature.
But i think BLF is a solution, on the DSS key of extension 203, you can set a BLF to monitor 201, when 201 is in a call, the BLF light will in red, so 203 can know he is in a call, when the light turns to green, 203 can dial to 201.
Do you think so?
(06-10-2013 02:27 PM)Yealink Support Wrote: [ -> ]Hi Ugo,
Sorry currently we don't have such feature.
But i think BLF is a solution, on the DSS key of extension 203, you can set a BLF to monitor 201, when 201 is in a call, the BLF light will in red, so 203 can know he is in a call, when the light turns to green, 203 can dial to 201.
Do you think so?

Hi!

Thank you very much for the answer!

I already use the BLF features in the Receptionist stations with T28 and T32 (using EXP38 and EXP39) phones, but if I have, for example 100 extensions with call waiting enabled, and I call anyone from a phone like a T22, how can I undestarnd that the called phone is already busy in another conversation? I need this features enabled for all extension in my corporation, not only in the receptionist phones.

For example, can I configure one of the three Line Keys of T22 to blink if the called number (whatever is it) is already busy?
Like configuring an action http url when I call a number, and based on returncode of http request (the web app accept as argument the called number, and return if it's already on the phone), Turn ON or OFF a Line key (this is only an idea).

Let's me known.

Best regards!
I'll second that... It would be great to see that the handset is already in use.
What happens if multiple handsets share an extension? Would this still show up as extension in use?
Would the phone system be responsible or the phone?
Support any more info on this... Not lots of people have lots of blfs to use... Ie : t22 or t32, t41, t 42
It would be a great feature!
I wonder if we could also have a different tone to let the caller know the callee is busy.
I'm also looking for this function. It is very important as we are limited in the amount of BLFs available to indicate status of extensions. We have 50+ extensions and some of our phones have 15 BLFs. I've noticed that this thread has been created in may of 2013 and is yet to be resolved or implemented (I think). Is there a way to see what is being developed and when the anticipated delivery is?
This would be a nice feature. An alternative would be a special "busy tone" that could be sent by the phone, like it used to be in the old days. Or are those already possible and I missed them? You could sent a busy tone even if the other person is hearing the call waiting tone and could pickup the phone.
Has anyone found a solution to this issue. I am using a T23G and a T29G
Yes Please!!! I have been asking for this forever! Our dinosaur Norstar system had this feature..
Pages: 1 2
Reference URL's