07-20-2017 07:12 PM - edited 03-17-2019 10:50 AM
Hello,
I am in the process of cutting over a customer from 28xx to 43xx gateways. I ran into an issue with outbound dialing in SRST mode to POTS lines. After troubleshooting, I have tracked it down to the way SRST seems to be reading the dial peers. 2 dial peers are listed below. The first dial peer works in SRST mode, the second does not(numbers are obfuscated for privacy) Both dial peers work fine performing a csim start. Originally I was suspecting the issue was caused by the # as the prefix, but I tried both dial peers using a 9 prefix and the results were the same. The symptom is a fast busy as soon as the last number that exists in the dial-peer is dialed. So dialing #1 presents a busy after 1 is pressed. IOS version is 3.16.5s. This configuration worked fine on the 28xx these are replacing. Any help is greatly appreciated.
dial-peer voice 1 pots
destination-pattern #12223334444
forward digits 11
port 0/1/0
dial-peer voice 1 pots
destination-pattern #1..........
forward digits 11
port 0/1/0
Thanks,
Tom
Solved! Go to Solution.
07-21-2017 08:40 AM
Interesting. Bug in this version of IOS? Have you opened a case with TAC?
07-21-2017 06:39 AM
Tom,
SIP or SCCP phones? Turn on "debug voip dialpeer" and post the results. Let's see if the call is hitting the proper dial peer and what digits are being collected.
Brandon
07-21-2017 08:07 AM
Hi Bradon,
Thanks for the response
SCCP phones, 7962 and 6921 phones.
dial-peer debug below. Once it gets to the ... it no longer sees the dial-peer as a match. csim start works fine and sees the dial-peer as a match.
the dial-peer it begins to match is
dial-peer voice 3 voip
destination-pattern #1..........
port 0/1/2
forward-digits 11
*Jul 21 14:20:58.970: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=16019, Called Number=, Voice-Interface=0x7FC7B6543C50,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Jul 21 14:20:58.970: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=20005
*Jul 21 14:20:58.970: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
*Jul 21 14:21:00.621: //-1/A6B6C11E8028/DPM/dpMatchPeersCore:
Calling Number=, Called Number=#, Peer Info Type=DIALPEER_INFO_SPEECH
*Jul 21 14:21:00.621: //-1/A6B6C11E8028/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=#
*Jul 21 14:21:00.621: //-1/A6B6C11E8028/DPM/dpMatchPeersCore:
Result=Partial Matches(1) after DP_MATCH_DEST
*Jul 21 14:21:00.621: //-1/A6B6C11E8028/DPM/dpMatchSafModulePlugin:
dialstring=#, saf_enabled=1, saf_dndb_lookup=0, dp_result=1
*Jul 21 14:21:00.621: //-1/A6B6C11E8028/DPM/dpMatchPeersMoreArg:
Result=MORE_DIGITS_NEEDED(1)
*Jul 21 14:21:00.621: //-1/A6B6C11E8028/DPM/dpMatchPeersCore:
Calling Number=, Called Number=#1, Peer Info Type=DIALPEER_INFO_SPEECH
*Jul 21 14:21:00.621: //-1/A6B6C11E8028/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=#1
*Jul 21 14:21:00.621: //-1/A6B6C11E8028/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
*Jul 21 14:21:00.621: //-1/A6B6C11E8028/DPM/dpMatchSafModulePlugin:
dialstring=#1, saf_enabled=1, saf_dndb_lookup=0, dp_result=0
*Jul 21 14:21:00.621: //-1/A6B6C11E8028/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=3
*Jul 21 14:21:00.622: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=16019, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Jul 21 14:21:00.622: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=NO_MATCH(-1) After All Match Rules Attempt
*Jul 21 14:21:00.622: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1
*Jul 21 14:21:00.622: //-1/A6B6C11E8028/DPM/dpMatchPeersCore:
Calling Number=, Called Number=#1, Peer Info Type=DIALPEER_INFO_SPEECH
*Jul 21 14:21:00.622: //-1/A6B6C11E8028/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=#1
*Jul 21 14:21:00.622: //-1/A6B6C11E8028/DPM/dpMatchPeersCore:
No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1)
*Jul 21 14:21:00.622: //-1/A6B6C11E8028/DPM/dpMatchSafModulePlugin:
dialstring=#1, saf_enabled=0, saf_dndb_lookup=1, dp_result=-1
*Jul 21 14:21:00.622: //-1/A6B6C11E8028/DPM/dpMatchPeersMoreArg:
Result=NO_MATCH(-1)
*Jul 21 14:21:00.622: //-1/A6B6C11E8028/DPM/dpMatchPeersCore:
Calling Number=, Called Number=#1, Peer Info Type=DIALPEER_INFO_SPEECH
*Jul 21 14:21:00.622: //-1/A6B6C11E8028/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=#1
*Jul 21 14:21:00.622: //-1/A6B6C11E8028/DPM/dpMatchPeersCore:
No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1)
*Jul 21 14:21:00.622: //-1/A6B6C11E8028/DPM/dpMatchSafModulePlugin:
dialstring=#1, saf_enabled=0, saf_dndb_lookup=1, dp_result=-1
*Jul 21 14:21:00.622: //-1/A6B6C11E8028/DPM/dpMatchPeersMoreArg:
Result=NO_MATCH(-1)
*Jul 21 14:21:00.622: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=#1, Called Number=#1, Peer Info Type=DIALPEER_INFO_SPEECH
*Jul 21 14:21:00.622: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=#1
*Jul 21 14:21:00.622: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1)
*Jul 21 14:21:00.622: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=#1, saf_enabled=0, saf_dndb_lookup=1, dp_result=-1
*Jul 21 14:21:00.622: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
Result=NO_MATCH(-1)
*Jul 21 14:21:00.622: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Jul 21 14:21:00.622: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=NO_MATCH(-1) After All Match Rules Attempt
*Jul 21 14:21:00.622: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1
*Jul 21 14:21:00.622: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=#1, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
*Jul 21 14:21:00.622: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=NO_MATCH(-1) After All Match Rules Attempt
*Jul 21 14:21:00.622: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=-1
*Jul 21 14:21:00.623: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=, Called Number=#1, Peer Info Type=DIALPEER_INFO_SPEECH
*Jul 21 14:21:00.623: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=#1
*Jul 21 14:21:00.623: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1)
*Jul 21 14:21:00.623: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=#1, saf_enabled=0, saf_dndb_lookup=1, dp_result=-1
*Jul 21 14:21:00.623: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
Result=NO_MATCH(-1)
*Jul 21 14:21:00.623: //-1/A6B6C11E8028/DPM/dpMatchPeersCore:
Calling Number=, Called Number=#1, Peer Info Type=DIALPEER_INFO_SPEECH
*Jul 21 14:21:00.623: //-1/A6B6C11E8028/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=#1
*Jul 21 14:21:00.623: //-1/A6B6C11E8028/DPM/dpMatchPeersCore:
No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1)
*Jul 21 14:21:00.623: //-1/A6B6C11E8028/DPM/dpMatchSafModulePlugin:
dialstring=#1, saf_enabled=1, saf_dndb_lookup=1, dp_result=-1
*Jul 21 14:21:00.623: //-1/A6B6C11E8028/DPM/dpMatchPeersMoreArg:
07-21-2017 08:19 AM
Does the behavior change if you make the destination pattern #1[2-9]..[2-9]......?
07-21-2017 08:31 AM
same exact result. I was messing around with all different variations last night, and the only thing I found is that it only matches an exact match. As get a fast busy as soon as I press 1.
07-21-2017 08:40 AM
Interesting. Bug in this version of IOS? Have you opened a case with TAC?
07-21-2017 09:01 AM
Well it was firmware. I uploaded the 03.16.05.S firmware, but had the incorrect boot system parameter, so it was still booting from 03.16.04b.S. So if anyone else runs into the issue, it is fixed in 03.16.05.S. I'm surprised I could not find a bug, seeing it is fixed in a newer version. Thanks for the assistance.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide