Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

SIP incoming call Match with H323 Dialpeer, Why?

Hi everyone,

I'm working with a Cisco 3945 (CUBE) and I have realized that a SIP incoming call is matching a H323 Dialpeer. Could a SIP call match a H323 Dialpeer?

dial-peer voice 2 voip
incoming called-number .
voice-class codec 1
dtmf-relay h245-alphanumeric rtp-nte
no vad

Debug:

*Nov 13 08:02:12.622: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Calling Number=8095445000, Called Number=, Voice-Interface=0x0,

   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

   Peer Info Type=DIALPEER_INFO_SPEECH

*Nov 13 08:02:12.622: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Result=NO_MATCH(-1) After All Match Rules Attempt

*Nov 13 08:02:12.622: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1

*Nov 13 08:02:12.622: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Calling Number=8095445000, Called Number=, Voice-Interface=0x0,

   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

   Peer Info Type=DIALPEER_INFO_SPEECH

*Nov 13 08:02:12.622: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:

   Result=NO_MATCH(-1) After All Match Rules Attempt

*Nov 13 08:02:12.622: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1

*Nov 13 08:02:12.622: //-1/BCBDC6278B46/DPM/dpAssociateIncomingPeerCore:

   Calling Number=8095445000, Called Number=5449, Voice-Interface=0x0,

   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

   Peer Info Type=DIALPEER_INFO_SPEECH

*Nov 13 08:02:12.622: //-1/BCBDC6278B46/DPM/dpAssociateIncomingPeerCore:

   Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=2

*Nov 13 08:02:12.622: //-1/BCBDC6278B46/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0

*Nov 13 08:02:12.622: //-1/BCBDC6278B46/DPM/dpMatchPeersCore:

   Calling Number=, Called Number=5449, Peer Info Type=DIALPEER_INFO_SPEECH

*Nov 13 08:02:12.622: //-1/BCBDC6278B46/DPM/dpMatchPeersCore:

   Match Rule=DP_MATCH_DEST; Called Number=5449

*Nov 13 08:02:12.622: //-1/BCBDC6278B46/DPM/dpMatchPeersCore:

   Result=Success(0) after DP_MATCH_DEST

*Nov 13 08:02:12.622: //-1/BCBDC6278B46/DPM/dpMatchSafModulePlugin:

   dialstring=5449, saf_enabled=0, saf_dndb_lookup=1, dp_result=0

*Nov 13 08:02:12.622: //-1/BCBDC6278B46/DPM/dpMatchPeersMoreArg:

   Result=SUCCESS(0)

   List of Matched Outgoing Dial-peer(s):

     1: Dial-peer Tag=11

     2: Dial-peer Tag=12

     3: Dial-peer Tag=31 *Nov 13 08:02:12.622: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=8095445000, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
*Nov 13 08:02:12.622: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=NO_MATCH(-1) After All Match Rules Attempt
*Nov 13 08:02:12.622: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1
*Nov 13 08:02:12.622: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Calling Number=8095445000, Called Number=, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
*Nov 13 08:02:12.622: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
   Result=NO_MATCH(-1) After All Match Rules Attempt
*Nov 13 08:02:12.622: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1
*Nov 13 08:02:12.622: //-1/BCBDC6278B46/DPM/dpAssociateIncomingPeerCore:
   Calling Number=8095445000, Called Number=5449, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
*Nov 13 08:02:12.622: //-1/BCBDC6278B46/DPM/dpAssociateIncomingPeerCore:
   Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=2
*Nov 13 08:02:12.622: //-1/BCBDC6278B46/DPM/dpMatchSafModulePlugin:
   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
*Nov 13 08:02:12.622: //-1/BCBDC6278B46/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=5449, Peer Info Type=DIALPEER_INFO_SPEECH
*Nov 13 08:02:12.622: //-1/BCBDC6278B46/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=5449
*Nov 13 08:02:12.622: //-1/BCBDC6278B46/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
*Nov 13 08:02:12.622: //-1/BCBDC6278B46/DPM/dpMatchSafModulePlugin:
   dialstring=5449, saf_enabled=0, saf_dndb_lookup=1, dp_result=0
*Nov 13 08:02:12.622: //-1/BCBDC6278B46/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=11
     2: Dial-peer Tag=12
     3: Dial-peer Tag=31

Please remember to rate useful posts clicking on the stars below.
Favor calificar todos las respuestas útiles dando click en las estrellas de mas abajo.
___________________________________________
LinkedIn Profile: do.linkedin.com/in/leosalcie       

__________________________________________________
Please remember to rate useful posts clicking on the stars below.
LinkedIn Profile: do.linkedin.com/in/leosalcie
1 ACCEPTED SOLUTION

Accepted Solutions

Re: SIP incoming call Match with H323 Dialpeer, Why?

@aokanlawon I guess we both know a voip dialpeer won't match a call coming from the TDM world, and vice versa, a POTS dialpeer will not ever match a call coming from the VOIP world, even if the incoming called-number (or destination-pattern or answer address) would be a potential match. I believe this distinction made leosalcie confused - if voip does not match pots and pots does not match voip, then perhaps voip with SIP should not match voip with H.323. But as I said in my previous post, regardless of the signalling protocol, SIP or H.323, if it's voip, it matches.

G.

8 REPLIES

SIP incoming call Match with H323 Dialpeer, Why?

Hi,

yes, it's either POTS or VOIP (or VOATM etc), regardless of the signalling protocol used.

I noticed this behaviour as well but can't find an explanation at the available documents. I might be looking at the incorrect ones, I must admit.

G.

SIP incoming call Match with H323 Dialpeer, Why?

I have not found any documenation regarding this case. My concern is beacause maybe at the future this scneario will cause trouble so is better to avoid it...

Please remember to rate useful posts clicking on the stars below.
Favor calificar todos las respuestas útiles dando click en las estrellas de mas abajo.
___________________________________________
LinkedIn Profile: do.linkedin.com/in/leosalcie

__________________________________________________
Please remember to rate useful posts clicking on the stars below.
LinkedIn Profile: do.linkedin.com/in/leosalcie
VIP Super Bronze

SIP incoming call Match with H323 Dialpeer, Why?

Leo,

The issue is with the wild card (incoming called number .) I suggest you define specific dial-peer to match your inboound sip calls..eg

dial-peer voice 3 voip

incoming called number 9XXXXXX

session protocol sipv2

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

SIP incoming call Match with H323 Dialpeer, Why?

Hi aokanlawon,

I know why the call is match but why a SIP call is matching a H323 Dialpeer? is this secnario supported?, that's the real question here.

Please remember to rate useful posts clicking on the stars below.
Favor calificar todos las respuestas útiles dando click en las estrellas de mas abajo.
___________________________________________
LinkedIn Profile: do.linkedin.com/in/leosalcie

__________________________________________________
Please remember to rate useful posts clicking on the stars below.
LinkedIn Profile: do.linkedin.com/in/leosalcie
VIP Super Bronze

Re: SIP incoming call Match with H323 Dialpeer, Why?

Leo calls are not matched based on protocols. Calls are matched based on calling and called number. This scneario cound give you issues because what you want is sip signalling going to your CUBE. One key issue you will have is that when you attempt to troiubleshoot and you turn on sip relates debugs, you woundlt see anything for the inbound leg because your inbound leg is not sip, its h323. This could also lead to call failure...

So in summary, Cisco IOS gateways are not looking to match calls to dial-peers based on protocols, rather based on calling and called number

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

Re: SIP incoming call Match with H323 Dialpeer, Why?

@aokanlawon I guess we both know a voip dialpeer won't match a call coming from the TDM world, and vice versa, a POTS dialpeer will not ever match a call coming from the VOIP world, even if the incoming called-number (or destination-pattern or answer address) would be a potential match. I believe this distinction made leosalcie confused - if voip does not match pots and pots does not match voip, then perhaps voip with SIP should not match voip with H.323. But as I said in my previous post, regardless of the signalling protocol, SIP or H.323, if it's voip, it matches.

G.

VIP Super Bronze

SIP incoming call Match with H323 Dialpeer, Why?

Gergely (+5) Good point on the POTS and VOIP comparison. I have never considered becuase I just know like you said that an inboud POTS call wont match a VOIP dial-peer and vice versa.

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

SIP incoming call Match with H323 Dialpeer, Why?

Both have answered my doubt. Thanks (+5)

Regards

Please remember to rate useful posts clicking on the stars below.
Favor calificar todos las respuestas útiles dando click en las estrellas de mas abajo.
___________________________________________
LinkedIn Profile: do.linkedin.com/in/leosalcie

__________________________________________________
Please remember to rate useful posts clicking on the stars below.
LinkedIn Profile: do.linkedin.com/in/leosalcie
247
Views
10
Helpful
8
Replies
CreatePlease to create content