[cisco-voip] Dial Peer Matching

Tue Apr 3 23:11:23 EDT 2007

You want to try to order the dial-peers correctly, and try not to put extra commands on the MGCP created dial-peers that ccm-manager config push may remove on you someday. I also put "application mgcpapp" or "service mgcpapp" (depending
on IOS version) on all the pots dial-peers, except peers for PRI ports
(there  is a bug where PRI calls may fail after awhile if the command is on a PRI peer), and that
solves this problem on MGCP gateways where all the ports are MGCP.  The mgcpapp isn't technically needed on the other peers, and I've had TAC say do it both ways when working funky MGCP issues in earlier IOS versions. From experience, I noticed if application/service mgcpapp isn't under a pots dial-peer for an analog port controlled by MGCP that someday when you least want a problem, an inbound call will start using the pots dial-peer for the inbound call leg and incoming calls fail because it is hitting a H.323 dial-peer and not able to go anywhere. 

HTH, Erick

----- Original Message ----
From: STEVEN CASPER <SCASPER at mtb.com>
To: cisco-voip at puck.nether.net; jason.aarons at us.didata.com
Sent: Tuesday, April 3, 2007 9:04:54 PM
Subject: Re: [cisco-voip] Dial Peer Matching

Yes they do.

Weststannapolis00r01#sh mgcp endpoint
aaln/S0/SU2/0 at Weststannapolis00r01
aaln/S0/SU2/1 at Weststannapolis00r01
aaln/S0/SU2/2 at Weststannapolis00r01
aaln/S0/SU2/3 at Weststannapolis00r01
aaln/S0/SU3/0 at Weststannapolis00r01
aaln/S0/SU3/3 at Weststannapolis00r01     

>>> "Jason Aarons (US)" <jason.aarons at us.didata.com> 04/03/07 9:56 PM
>>>
Does "show mgcp endpoint" reflect your FXO ports are controlled by
MGCP?

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net 
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of STEVEN CASPER
Sent: Tuesday, April 03, 2007 9:42 PM
To: STEVEN CASPER; cisco-voip at puck.nether.net 
Subject: Re: [cisco-voip] Dial Peer Matching

 Installed a site tonight with analog FXO trunks controlled via MGCP.
Outbound calls worked fine but inbound did not. Looking at a debug of
the dial peers I could see that the inbound calls were matching the
dial
peers that were built for SRST. These were in front of the MGCP dial
peers in the router config.

 Removed  the SRST dial peers and inbound worked fine. Added them back
in and inbound still works ok Now they are after the MGCP dial peers
in
the config. Are dial peers searched on a hierarchical basis? I would
have thought that because the FXO ports were controlled by MGCP the
dial
peers configured for SRST would not have been used.

Thanks!

Steve Casper
Voice Technologies
M&T Bank
(410) 347-6026

************************************
This email may contain privileged and/or confidential information that
is intended solely for the use of the addressee.  If you are not the
intended recipient or entity, you are strictly prohibited from
disclosing, copying, distributing or using any of the information
contained in the transmission.  If you received this communication in
error, please contact the sender immediately and destroy the material
in
its entirety, whether electronic or hard copy.  This communication may
contain nonpublic personal information about consumers subject to the
restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act.
You may not directly or indirectly reuse or disclose such information
for any purpose other than to provide the services for which you are
receiving the information.
There are risks associated with the use of electronic transmission. 
The
sender of this information does not control the method of transmittal
or
service providers and assumes no duty or obligation for the security,
receipt, or third party interception of this transmission.
************************************

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

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.

************************************
This email may contain privileged and/or confidential information that is intended solely for the use of the addressee.  If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission.  If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy.  This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act.  You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.
There are risks associated with the use of electronic transmission.  The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.
************************************

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

____________________________________________________________________________________
It's here! Your new message!  
Get new email alerts with the free Yahoo! Toolbar.
http://tools.search.yahoo.com/toolbar/features/mail/