It's set to 4 digits on the trunk. That's not the problem here. On Thu, Apr 23, 2009 at 10:14 AM, Rick Grimes <[email protected]>wrote:
> Change your destination-pattern to 4 digits or make sure that significant > digits is set to 4 in your sip trunk. > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Nara Shikamaru > *Sent:* Thursday, April 23, 2009 11:26 AM > *To:* Jiahong - tobeccie Fang > *Cc:* [email protected] > *Subject:* Re: [OSL | CCIE_Voice] v3 lab : SIP trunk/dial peers on HQ > router > > > > James, > > If there are two dial peers that are identical except for the > preference setting, is it normal for the debug to reflect matching on both? > I'm wondering if the problem is occuring before the dial-peer has an > oppurtunity to do anything with the call. Codec and dtmf-relay settings are > relevant, I believe, in the final steps of the call staging set up, no? > > > > When I configured my PSTN switch and had to work out dial peers to > forward traffic to my PSTN phones on another router (FXS ports), traffic > would not be forwarded until the dial peer match was resolved. I will add > the syntax to the dial peers and let you know, just seems unusual based on > my understanding. > > 2009/4/23 Jiahong - tobeccie Fang <[email protected]> > > OK you match the outbound dial-peer properly. You may have problem with > dtmf-relay or codec negotiation. > > Copy/paste your 'voice class codec 1' config. Also add 'dtmf-relay > sip-notify rtp-nte' in both dial-peers > > James F. > > > Message: 1 > > Date: Wed, 22 Apr 2009 22:48:04 -0700 > > From: Nara Shikamaru <[email protected]> > > Subject: [OSL | CCIE_Voice] v3 lab : SIP trunk/dial peers on HQ router > > To: "[email protected]" <[email protected]> > > Message-ID: > > <[email protected]> > > Content-Type: text/plain; charset="iso-8859-1" > > > > > > Hello, > > I am working on inbound calling to the HQ site for HQ (internal ext > > 500X). Calling inbound from PSTN phone, the dial-peer debug traffic shows > > that both redundant dial-peers are being matched (5000 and 5001). > However, > > my impression is that the "preference" syntax should be the deciding > factor > > in which dial peer is used. As far as I can tell the inbound call is not > > being passed to CUCM's SIP trunk. From the dial-peer debug; > > > > *P1-HQ-VG# > > Apr 22 22:37:14: //-1/A018D0158081/DPM/dpAssociateIncomingPeerCore: > > Calling Number=0113432141891, Called Number=2123945002, > > Voice-Interface=0x0, > > Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search > > Type=PEER_TYPE_VOICE, > > Peer Info Type=DIALPEER_INFO_SPEECH > > Apr 22 22:37:14: //-1/A018D0158081/DPM/dpAssociateIncomingPeerCore: > > Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=5000 > > Apr 22 22:37:14: //-1/A018D0158081/DPM/dpAssociateIncomingPeerCore: > > Calling Number=0113432141891, Called Number=2123945002, > > Voice-Interface=0x0, > > Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search > > Type=PEER_TYPE_VOICE, > > Peer Info Type=DIALPEER_INFO_SPEECH > > Apr 22 22:37:14: //-1/A018D0158081/DPM/dpAssociateIncomingPeerCore: > > Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=5000 > > Apr 22 22:37:14: //-1/A018D0158081/DPM/dpMatchPeersCore: > > Calling Number=, Called Number=2123945002, Peer Info > > Type=DIALPEER_INFO_SPEECH > > Apr 22 22:37:14: //-1/A018D0158081/DPM/dpMatchPeersCore: > > Match Rule=DP_MATCH_DEST; Called Number=2123945002 > > Apr 22 22:37:14: //-1/A018D0158081/DPM/dpMatchPeersCore: > > Result=Success(0) after DP_MATCH_DEST > > Apr 22 22:37:14: //-1/A018D0158081/DPM/dpMatchPeersMoreArg: > > Result=SUCCESS(0) > > List of Matched Outgoing Dial-peer(s): > > 1: Dial-peer Tag=5000 > > 2: Dial-peer Tag=5001 > > Apr 22 22:37:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: > > Calling Number=2123945002, Called Number=2123945002, Peer Info > > Type=DIALPEER_INFO_SPEECH > > Apr 22 22:37:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: > > Match Rule=DP_MATCH_DEST; Called Number=2123945002 > > Apr 22 22:37:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: > > Result=Success(0) after DP_MATCH_DEST > > Apr 22 22:37:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg: > > Result=SUCCESS(0) > > List of Matched Outgoing Dial-peer(s): > > 1: Dial-peer Tag=5000 > > 2: Dial-peer Tag=5001 > > Apr 22 22:37:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: > > Calling Number=2123945002, Called Number=2123945002, Peer Info > > Type=DIALPEER_INFO_SPEECH > > Apr 22 22:37:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: > > Match Rule=DP_MATCH_DEST; Called Number=2123945002 > > Apr 22 22:37:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: > > Result=Success(0) after DP_MATCH_DEST > > Apr 22 22:37:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg: > > Result=SUCCESS(0) > > List of Matched Outgoing Dial-peer(s): > > 1: Dial-peer Tag=5000 > > 2: Dial-peer Tag=5001 > > Apr 22 22:37:14: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore: > > Calling Number=2123945002, Called Number=, Voice-Interface=0x0, > > Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search > > Type=PEER_TYPE_VOICE, > > Peer Info Type=DIALPEER_INFO_SPEECH > > Apr 22 22:37:14: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore: > > Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=5000 > > Apr 22 22:37:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: > > Calling Number=, Called Number=2123945002, Peer Info > > Type=DIALPEER_INFO_SPEECH > > Apr 22 22:37:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: > > Match Rule=DP_MATCH_DEST; Called Number=2123945002 > > Apr 22 22:37:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: > > Result=Success(0) after DP_MATCH_DEST > > Apr 22 22:37:14: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg: > > Result=SUCCESS(0) > > List of Matched Outgoing Dial-peer(s): > > 1: Dial-peer Tag=5000 > > 2: Dial-peer Tag=5001 > > Apr 22 22:37:14: //-1/A018D0158081/DPM/dpMatchPeersCore: > > Calling Number=, Called Number=2123945002, Peer Info > > Type=DIALPEER_INFO_SPEECH > > Apr 22 22:37:14: //-1/A018D0158081/DPM/dpMatchPeersCore: > > Match Rule=DP_MATCH_DEST; Called Number=2123945002 > > Apr 22 22:37:14: //-1/A018D0158081/DPM/dpMatchPeersCore: > > Result=Success(0) after DP_MATCH_DEST > > Apr 22 22:37:14: //-1/A018D0158081/DPM/dpMatchPeersMoreArg: > > Result=SUCCESS(0) > > List of Matched Outgoing Dial-peer(s): > > 1: Dial-peer Tag=5000 > > 2: Dial-peer Tag=5001* > > > > > > This is the dial-peer syntax; > > > > *dial-peer voice 5000 voip > > destination-pattern 2123945... > > voice-class codec 1 > > session protocol sipv2 > > session target ipv4:10.1.200.20 > > incoming called-number . > > dtmf-relay rtp-nte > > no vad > > ! > > dial-peer voice 5001 voip > > preference 1 > > destination-pattern 2123945... > > voice-class codec 1 > > session protocol sipv2 > > session target ipv4:10.1.200.24 > > incoming called-number . > > dtmf-relay rtp-nte > > no vad* > > ** > > ** > > Has anyone dealt with this issue before? > > > > > > > > -- > > -Shikamaru > > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: > http://onlinestudylist.com/pipermail/ccie_voice/attachments/20090422/51eaf625/attachment-0001.htm > > > > ------------------------------ > > See all the ways you can stay connected to friends and > family<http://www.microsoft.com/windows/windowslive/default.aspx> > > > > > -- > -Shikamaru > > E-mail Disclaimer: Any views expressed in this message may be those of the > individual sender, if the sender has not specifically stated that he/she is > acting within his/her authority on behalf of or specifically states them to > be the views of CSI Technology Outfitters. The information in this email may > be confidential, and is intended only for the use of or dissemination by the > recipient named above. If the reader of this message is not the intended > recipient, > you are hereby notified that any dissemination, distribution, or copying of > this > communication, or any of its contents, is strictly prohibited. > > If you have received this communication in error, please re-send this > communication > to the sender and delete the original message and any copy of it from your > computer > system. To report any abuse, please forward to [email protected]. > > -- -Shikamaru
