[cisco-voip] Call Manager question

Wed May 26 19:26:00 EDT 2010

It is a trivial feature for some customers. I have ran into this before. It
is not on any roadmap as it just not that important in the scheme of things.
If this was such a critical piece of functionality you or the system
integrator should  have found this out in the discovery phase. The net
result is this is not a fault of Cisco or Call Manager. 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ahmed Elnagar
Sent: Wednesday, May 26, 2010 4:53 PM
To: Ryan Ratliff
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Call Manager question

I don't know what is the great deal about that in order not to have natively
in CUCM.customers are asking for this trivial feature; that they see very
basic with other phone systems like mobile operators who play a different
ringing tone to the calling party and send a notification to the phone that
the other end is on waiting.

Is there a roadmap for this?

 Best Regards;

  Ahmed Elnagar

  Senior Network PS Engineer

  Mob: +2019-0016211

  CCIE#24697 (Voice)

 ccie_voice_large.gifccvp_voice_large.gif

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
Sent: Monday, May 24, 2010 11:39 PM
To: Ahmed Maher
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Call Manager question

You'd have to send it to a 3rd party application that could play the
appropriate in-band recording, and then treat the call as desired.

For phones with only one line, yes that would present a problem.

-Ryan

On May 24, 2010, at 4:08 PM, Ahmed Maher wrote:

Also, what about calls coming from PSTN, No display appear to them J

Best Regards,

   <image001.jpg>

       Ahmed Maher

Networking Team Leader               CONNECT  Professional Services

             Bldg. 1A Maadi Star Towers, Cornish El Maadi,

<image003.jpg><image005.jpg>             Cairo, Egypt

                                                             Phone:  (+202)
25 27 09 30          Ext.: 113

                                                             Fax:
(+202) 25 26 54 85

                                                             Mobile: (+2016)
665 1150

                                                             Email:
<mailto:ahmed.maher at connectps.com> ahmed.maher at connectps.com

                                                             Website:
www.connectps.com <http://www.connectps.com/> 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ahmed Abd EL-Rahman
Sent: Monday, May 24, 2010 10:55 PM
To: Ryan Ratliff
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Call Manager question

This is a great idea as it enables the called user to receive the second
call if he wishes to, but the only constrain for this is it needs a phone
with 2 lines, so the simple phones with only 1 line will not be applicable,
right?

Best Regards

Ahmed Abd EL-Rahman

From: Ryan Ratliff [mailto:rratliff at cisco.com] 
Sent: Monday, May 24, 2010 10:41 PM
To: Ahmed Abd EL-Rahman
Cc: Scott Voll; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Call Manager question

The caller only receives a busy tone if the busy trigger is hit, and no CFB
destination is set.  In this case you would be setting the CFB destination
to another line on the phone, and using that line's alerting name (or
display, whatever setting works) to update the display of the calling phone
to indicate that the user's primary line was busy.

Example:

Joe at 1000 calls Mary at 2000. 

2000 is busy, CFB to *2000.  DN *2000 is line 2 on Mary's phone, with an
Alerting Name (or Display) set to "BUSY - Mary".

Joe's phone will show To: BUSY - Mary (hopefully).

You can word it however you wish, but hopefully you get the what I'm talking
about.  The downside is that Mary's phone would be ringing on a different
line, which could impact ring settings, etc.

-Ryan

On May 24, 2010, at 3:30 PM, Ahmed Abd EL-Rahman wrote:

this means that the busy trigger will be set to 1, and in this case the
caller will get a busy tone which will solve the problem, but this will
prevent the user from receiving a second call which is a needed feature.

Best Regards

Ahmed Abd EL-Rahman

From: Ryan Ratliff [mailto:rratliff at cisco.com] 
Sent: Monday, May 24, 2010 6:16 PM
To: Scott Voll
Cc: Ahmed Abd EL-Rahman; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Call Manager question

You could try forward busy (busy trigger) to a second line with an Alerting
Name set to indicate that the user is busy.  

-Ryan

On May 24, 2010, at 11:03 AM, Scott Voll wrote:

I believe your only option is to set the call busy to 1 then setup the busy
greeting in Unity (or UC).

Scott

On Sun, May 23, 2010 at 12:08 PM, Ahmed Abd EL-Rahman
<Ahmed.Rahman at bmbgroup.com> wrote:

Dear all, I have a question about are there any way to indicate to a calling
user who calls a user phone with a busy trigger set to 2 that this called
user is on another call ? because by default the called user (who is already
on a call) will see another call come into his phone screen BUT the calling
user will have no idea that this user is on another call.

Best Regards

Ahmed Abd EL-Rahman I Senior Network Engineer

CCVP, CCNP, CCNA, CCNA-VOICE, IPTX, UCCX, CRMCS, WLSS

 <http://www.bmbgroup.com/> <image001.jpg>

               Lebanon I Egypt I Algeria I KSA I Libya I Jordan

Al-Ajlan Center Office #1 I Olaya Main Street I P.O Box 17384 I Riyadh,
Saudi Arabia I Tel: +966 1 216 7994 I Fax: +966 1 4620030  I Mobile: +966
507920925 I  <http://www.bmbgroup.com/> www.bmbgroup.com

P     Save a tree. Don't print this e-mail unless it's really necessary

************************************************************
Disclaimer: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited. If you
are not the intended recipient, please contact the sender by reply email and
destroy all copies of the original message. 
************************************************************

__________ Information from ESET Smart Security, version of virus signature
database 5139 (20100523) __________