[cisco-voip] Bussy number - Call Cannot be Completed as Dialed

[Ryan Ratliff]

If your gateway is H.323 you may be able to play with the cause it  
sends back to CM using translation rules.  I don't have the link  
handy and it appears the cisco.com search is down so I'm not sure if  
it's possible.  It probably depends on exactly what they are sending  
you.

-Ryan

On May 29, 2008, at 11:24 AM, Ryan Ratliff wrote:

You can disable Annunciator so that CCM simply plays a reorder tone  
to the caller.  You may get lucky and your users won't know the  
difference between reorder and user-busy tones :)

-Ryan

On May 29, 2008, at 11:21 AM, Mladen Milanovic wrote:

Ryan,
Thanks on your answer. I am sure that we are getting a wrong  
disconnect message from carrier. If I confirm that, is there any way  
that we can change CCM behavior – to react on this message differently ?

Mladen

From: Ryan Ratliff [mailto:rratliff at cisco.com]
Sent: Thursday, May 29, 2008 10:58 AM
To: Mladen Milanovic
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Bussy number - Call Cannot be Completed as  
Dialed

The first place to look is a q931 debug at the voice gateway to see  
what disconnect cause is being sent back to CM.

-Ryan

On May 29, 2008, at 10:45 AM, Mladen Milanovic wrote:

Guys,
I am connected to Centrex DMS 100 via T1 PRI using primary-ni  
signalization. When phone on the Cetrex switch is busy I am getting a  
message from the CCM that Call Cannot Be Completed as Dialed. I am  
using H.323 as a signaling protocol between CCM 6.0(1a) and VGs

Can anyone provide any explanation for this

Thanks
Mladen
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080529/e4268b7c/attachment.html>