cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
821
Views
0
Helpful
1
Replies

Duplicate debug lines on inbound dial-peer matching

jomar050485
Level 1
Level 1

I'm trying to understand to understand why is it that when I send a call to the gateway with no inbound dial-peer defined, do I get the following output:

*Mar 1 00:08:07.843: //-1/3E47BFC58004/DPM/dpAssociateIncomingPeerCore:
Calling Number=, Called Number=2106558996, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Mar 1 00:08:07.843: //-1/3E47BFC58004/DPM/dpAssociateIncomingPeerCore:
Result=NO_MATCH(-1) After All Match Rules Attempt

*Mar 1 00:08:07.851: //-1/3E47BFC58004/DPM/dpAssociateIncomingPeerCore:
Calling Number=, Called Number=2106558996, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Mar 1 00:08:07.851: //-1/3E47BFC58004/DPM/dpAssociateIncomingPeerCore:
Result=NO_MATCH(-1) After All Match Rules Attempt

*Mar 1 00:08:07.895: //-1/3E47BFC58004/DPM/dpMatchPeersCore:
Calling Number=, Called Number=2106558996, Peer Info Type=DIALPEER_INFO_SPEECH

*Mar 1 00:08:07.895: //-1/3E47BFC58004/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=2106558996

*Mar 1 00:08:07.895: //-1/3E47BFC58004/DPM/dpMatchPeersCore:
No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1)

*Mar 1 00:08:07.899: //-1/3E47BFC58004/DPM/dpMatchPeersMoreArg:
Result=NO_MATCH(-1)


I produced this call with a "csim start" command from another router. I don't understand why I get the result of "Result=NO_MATCH(-1) After All Match Rules Attempt" twice.


When I create a simple inbound dial-peer:

gateway(config)# dial-peer voice 2 voip
gateway(config-dial-peer)# incoming called-number .

I get the following debug:

*Mar 1 00:09:36.079: //-1/72E1EEF88006/DPM/dpAssociateIncomingPeerCore:
Calling Number=, Called Number=2106558996, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Mar 1 00:09:36.079: //-1/72E1EEF88006/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=2

*Mar 1 00:09:36.087: //-1/72E1EEF88006/DPM/dpAssociateIncomingPeerCore:
Calling Number=, Called Number=2106558996, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Mar 1 00:09:36.087: //-1/72E1EEF88006/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=2

*Mar 1 00:09:36.107: //-1/72E1EEF88006/DPM/dpMatchPeersCore:
Calling Number=, Called Number=2106558996, Peer Info Type=DIALPEER_INFO_SPEECH

*Mar 1 00:09:36.107: //-1/72E1EEF88006/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=2106558996

*Mar 1 00:09:36.111: //-1/72E1EEF88006/DPM/dpMatchPeersCore:
No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1)

*Mar 1 00:09:36.111: //-1/72E1EEF88006/DPM/dpMatchPeersMoreArg:
Result=NO_MATCH(-1)

I get two debug lines indicated a match just like I got two debugs lines indicated a match failure. What is the reason behind this? Why does it try to match twice if in the case of the first example, it found a match why did it try again and in the second case, it already failed the first time why did it try to match again. Anyone know?

*edit for clarity

1 Reply 1

jomar050485
Level 1
Level 1

bump