[cisco-voip] CCM 3.3 MGCP Gateway dial delay

[Scott Ingram]

Found the issue.  I was having  DSP issues ->  idle channels would not
take a call so it would keep hunting to one answered.  I moved PRI to
another controller and it went  away.

 

________________________________

From: Jeff Anderson [mailto:janderson at enventis.com] 
Sent: Wednesday, May 17, 2006 2:48 PM
To: Brian Henry; Voll, Scott; Scott Ingram; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] CCM 3.3 MGCP Gateway dial delay

 

You don't. I didn't catch the MGCP part in the title. Either way those
same concepts can be applied directly to the route patterns in CCM.

 

Jeff Anderson

 

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Brian Henry
Sent: Wednesday, May 17, 2006 1:40 PM
To: Voll, Scott; Scott Ingram; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CCM 3.3 MGCP Gateway dial delay

 

Why do you need all those Dial-Peers with MGCP?

 

If you post the config minus company info we could better understand.

 

CCM 3.3(?) VGW IOS (?)  Device Loads (?)

 

Brian

 

________________________________

From: cisco-voip-bounces at puck.nether.net on behalf of Voll, Scott
Sent: Wed 5/17/2006 2:26 PM
To: Scott Ingram; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CCM 3.3 MGCP Gateway dial delay

Any new route patterns that would cause a interdigit timeout?  You could
use DNA or Route report.  

 

Scott

 

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Scott Ingram
Sent: Wednesday, May 17, 2006 7:14 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] CCM 3.3 MGCP Gateway dial delay

 

I have started to experience an issue with outside dial patterns.  When
a user hits 9 they hear the outside dial tone then + 10 digit number
there is a 20 Sec delay before  call  rings destination.  I have done
some traces and the call set up and handling seems to be correct.  I
have also watched the ISDN debugs and I'm  not finding any errors.  Any
Ideas?

IMPORTANT NOTICE:
 
This message is intended only for the use of the individual or entity to
which it is addressed and may contain information that is privileged,
confidential and exempt from disclosure under applicable law.  If you
have received this message in error, you are hereby notified that we do
not consent to any reading, dissemination, distribution or copying of
this message.  If you have received this communication in error, please
notify the sender immediately and destroy the transmitted information.
 

IMPORTANT NOTICE:

This message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law.  If you have received this message in error, you are hereby notified that we do not consent to any reading, dissemination, distribution or copying of this message.  If you have received this communication in error, please notify the sender immediately and destroy the transmitted information.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060517/4b0f3852/attachment-0001.html