09-14-2015 01:31 PM - edited 03-17-2019 04:18 AM
Hello
I'm really confused with a simple config.
Outbound dial-peer doesn't match for call but matches for "csim start" and "sh dialplan".
More detailed explanation.
2851 with E1 PRI that should act as a VoIP gateway for inbound calls from PSTN to the SIP server.
But there are no VoIP legs for inbound E1 calls.
No outbound dial-peers are matched.
The most strange thing is that "sh dialplan number <NUMBER>" and "csim start <NUMBER>"
where <NUMBER> is called number copy-pasted from the output of "deb isdn q931" matches dial-peer while inbound calls from PSTN - Not.
Here is my dial peer.
dial-peer voice 100 voip
description ::: PSTN Calls to InIn -> 10.178.23.12 :::
preference 1
destination-pattern 590....
session protocol sipv2
session target ipv4:10.178.23.12
dtmf-relay rtp-nte
codec g711alaw
no vad
E1 is up; MULTIPLE_FRAME_ESTABLISHED.
With deb isdn q931
I can see that call arrives,
Sep 14 19:56:16.291: ISDN Se1/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x4EB9
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA9838E
Exclusive, Channel 14
Calling Party Number i = 0x0083, 'XXXXX'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x81, '5905430'
Plan:ISDN, Type:Unknown
Sep 14 19:56:16.303: ISDN Se1/0/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0xCEB9
Channel ID i = 0xA9838E
2 Exclusive, Channel 14
Sep 14 19:56:16.303: ISDN Se1/0/0:15 Q931: TX -> CONNECT pd = 8 callref = 0xCEB9
Sep 14 19:56:16.339: ISDN Se1/0/0:15 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x4EB9
Sep 14 19:56:16.343: %ISDN-6-CONNECT: Interface Serial1/0/0:13 is now connected to 0672082933 N/A
Sep 14 19:56:19.587: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0/0:13, changed state to up
Sep 14 19:56:21.095: ISDN Se1/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x4EB9
Cause i = 0x8090 - Normal call clearing
Progress Ind i = 0x8288 - In-band info or appropriate now available
Here is the output for "deb voice dialpeer inout" for the inbound PSTN call.
Sep 14 20:10:41.517: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=XXXXX, Called Number=5905430, Voice-Interface=0x468BF088,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
Sep 14 20:10:41.517: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=NO_MATCH(-1) After All Match Rules Attempt
Sep 14 20:10:41.517: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=0672082933, Called Number=5905430, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_FAX
Sep 14 20:10:41.517: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=NO_MATCH(-1) After All Match Rules Attempt
Sep 14 20:10:41.517: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=XXXXX, Called Number=5905430, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
Sep 14 20:10:41.517: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=NO_MATCH(-1) After All Match Rules Attempt
Sep 14 20:10:41.521: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=XXXXX, Called Number=5905430, Voice-Interface=0x468BF088,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
Sep 14 20:10:41.521: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=NO_MATCH(-1) After All Match Rules Attempt
Sep 14 20:10:41.569: %ISDN-6-CONNECT: Interface Serial1/0/0:14 is now connected to XXXXX N/A
Sep 14 20:10:48.973: %ISDN-6-DISCONNECT: Interface Serial1/0/0:14 disconnected from XXXXX , call lasted 7 seconds
Here is the output for "deb voice dialpeer inout" for the "csim start <NUMBER>".
DM.VG-1#csim start 5905430
csim: called number = 5905430, loop count = 1 ping count = 0
csim err:csim_do_test invalid major major(16) minor(0)
csim: loop = 1, failed = 0
csim: call attempted = 1, setup failed = 0, tone failed = 0
DM.VG-1#
Sep 14 20:12:42.559: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=, Called Number=5905430, Peer Info Type=DIALPEER_INFO_SPEECH
Sep 14 20:12:42.559: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=5905430
Sep 14 20:12:42.559: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
Sep 14 20:12:42.559: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=100
09-14-2015 01:56 PM
Hi
Could you please post the config as well? It is bit difficult to come to a conclusion without the complete Dial-Peer config
Regards
09-14-2015 02:04 PM
Thank you for reply.
Here is the config
isdn switch-type primary-net5
!
voice-card 0
dspfarm
dsp services dspfarm
!
voice-card 1
dspfarm
dsp services dspfarm
!
!
voice call disc-pi-off
!
voice service voip
allow-connections sip to sip
sip
header-passing
interface Serial1/0/0:15
description ::: ISDN Num 7-272 :::
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn timer T301 180000
isdn incoming-voice voice
isdn guard-timer 5000
no cdp enable
dial-peer voice 100 voip
description ::: InIn Inbound -> 10.178.23.12 :::
preference 1
destination-pattern 590....
session protocol sipv2
session target ipv4:10.178.23.12
dtmf-relay rtp-nte
codec g711alaw
no vad
!
dial-peer voice 101 voip
description ::: InIn Inbound -> 10.178.23.13 :::
preference 2
huntstop
destination-pattern 590....
session protocol sipv2
session target ipv4:10.178.23.13
dtmf-relay rtp-nte
codec g711alaw
no vad
sip-ua
retry invite 2
timers trying 150
!
09-14-2015 02:23 PM
Hi,
So if I understand correctly, this is how your topology is:
ISDN ========> 2851 ====SIP Trunk ======>> CCM Cluster
I don't see any POTS Dial-Peer, so any call that lands in from ISDN-PRI is hunting for a dial-peer and tries to match with VoIP dial-peer.
Sep 14 20:10:41.517: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=XXXXX, Called Number=5905430, Voice-Interface=0x468BF088,
Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
Sep 14 20:10:41.517: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=NO_MATCH(-1) After All Match Rules Attempt
And when you do the csim start 5905430
Sep 14 20:12:42.559: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=, Called Number=5905430, Peer Info Type=DIALPEER_INFO_SPEECH
Sep 14 20:12:42.559: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=5905430
Sep 14 20:12:42.559: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
Sep 14 20:12:42.559: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=100
HTH
09-14-2015 10:30 PM
Thank you for reply.
Yes are absolutely right.
The only one note, SIP server is not a Cisco server.
Today, I'll try to replace 2851 box.
09-15-2015 04:30 AM
Hi,
I don't think you need to replace the router. What you need is to apply this config:
dial-peer voice 100 pots
incoming called-number .
port 1/0/0:15
This should fix the problem
09-16-2015 11:29 AM
Thank you for reply. I have solved the issue but in a little bit different way. I remembered about an option direct-inward-dial on inbound dial-peers. So, here is properly working config
dial-peer voice 200 pots
description ::: PSTN Leg Inbound Dial Peer :::
incoming called-number 590....
direct-inward-dial
port 1/0/0:15
!
dial-peer voice 106 voip
description ::: InIn Inbound. PRI 5 -> 10.178.23.12 :::
preference 1
destination-pattern 59054[2-3][0-3,5-9]
session protocol sipv2
session target ipv4:10.178.23.12
session transport tcp
dtmf-relay rtp-nte
codec g711alaw
no vad
!
dial-peer voice 107 voip
description ::: InIn Inbound. PRI 5 -> 10.178.23.13 :::
huntstop
preference 2
destination-pattern 59054[2-3][0-3,5-9]
session protocol sipv2
session target ipv4:10.178.23.13
session transport tcp
dtmf-relay rtp-nte
codec g711alaw
no vad
!
09-14-2015 02:01 PM
Have you tried simply rebooting the ISR??
09-14-2015 02:19 PM
Thank you for reply.
I have rebooted ISR twice.
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