Help with CUBE Voice dial peers

[David Harrell]

I'm beginning the process of migrating from a PRI service to SIP service, and I'm was hoping someone could help me with a dial-peer issue. I feel like I am missing something simple, but I cannot place it. I've using the same translation rules on the router, but I have removed the old dial-peers and added the dial-peers below. The router IP is 10.6.102.50 for LAN, and 192.168.255.5 for the ITSP facing interface. The ITSP IP is 192.168.255.6. 10.6.102.20 is the nearest CM to this location.

voice service voip
ip address trusted list
ipv4 10.6.102.20
ipv4 10.2.100.22
ipv4 10.2.100.20
ipv4 192.168.255.6
mode border-element
allow-connections sip to sip
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
sip
early-offer forced
midcall-signaling passthru
!
voice class codec 3
codec preference 1 g729r8
codec preference 2 g711ulaw
codec preference 3 g711alaw
!
!
!
!
!
!
voice translation-rule 1
rule 1 /^.*\(....\)/ /\1/
!
voice translation-rule 2
rule 1 /^423\(.*\)/ /9\1/
rule 2 /^.*/ /9&/ type subscriber subscriber
rule 3 /^.*/ /91&/ type national national
rule 4 /^.*/ /9&/ type unknown unknown
!
voice translation-rule 3
rule 1 /^.*/ /4239752732/
!
!
voice translation-profile INCOMING
translate calling 2
translate called 1
!
voice translation-profile OUTGOING
translate calling 3
!

dial-peer voice 1000 voip
description **Inbound LAN Side dial-peer**
session protocol sipv2
incoming called-number 9T
dtmf-relay rtp-nte
codec g711ulaw
no vad
!
dial-peer voice 1002 voip
description **Inbound WAN Side dial-peer**
translation-profile incoming INCOMING
session protocol sipv2
incoming called-number .T
dtmf-relay rtp-nte
codec g711ulaw
no vad
!
dial-peer voice 1001 voip
description **Outbound LAN Side dial-peer**
translation-profile outgoing OUTGOING
destination-pattern [2-9].........
session protocol sipv2
session target ipv4:10.6.102.20
dtmf-relay rtp-nte
codec g711ulaw
no vad
!
dial-peer voice 1003 voip
description **Outbound WAN Side Peer**
translation-profile outgoing OUTGOING
destination-pattern 9[2-9].........
session protocol sipv2
session target ipv4:192.168.255.6
dtmf-relay rtp-nte
codec g711ulaw

The calling number is 4232027058 and the called DN is 4237223739, DN 3739 is configured and assigned to a phone. Here's the output of a begun voice dialpeer default command:

003553: Jun 29 09:52:05: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=4237223739, Called Number=4237223739, Peer Info Type=DIALPEER_INFO_SPEECH
003554: Jun 29 09:52:05: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=4237223739
003555: Jun 29 09:52:05: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
003556: Jun 29 09:52:05: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=4237223739, saf_enabled=1, saf_dndb_lookup=1, dp_result=0
003557: Jun 29 09:52:05: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=1001
003558: Jun 29 09:52:05: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=4232027058, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
003559: Jun 29 09:52:05: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=1001
003560: Jun 29 09:52:05: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
003561: Jun 29 09:52:05: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Calling Number=4232027058, Called Number=, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
003562: Jun 29 09:52:05: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=1001
003563: Jun 29 09:52:05: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
003564: Jun 29 09:52:05: //-1/F8538BDBA0B4/DPM/dpAssociateIncomingPeerCore:
Calling Number=4232027058, Called Number=4237223739, Voice-Interface=0x0,
Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
Peer Info Type=DIALPEER_INFO_SPEECH
003565: Jun 29 09:52:05: //-1/F8538BDBA0B4/DPM/dpAssociateIncomingPeerCore:
Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=1002
003566: Jun 29 09:52:05: //-1/F8538BDBA0B4/DPM/dpMatchSafModulePlugin:
dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
003567: Jun 29 09:52:05: //-1/xxxxxxxxxxxx/DPM/dpGetSIPUriProvisionBmp:
Tag=1002
003568: Jun 29 09:52:05: //-1/xxxxxxxxxxxx/DPM/dpGetSIPUriProvisionBmp:
Result=0 Bitmap=0x0
003569: Jun 29 09:52:05: //-1/F8538BDBA0B4/DPM/dpMatchPeersCore:
Calling Number=, Called Number=3739, Peer Info Type=DIALPEER_INFO_SPEECH
003570: Jun 29 09:52:05: //-1/F8538BDBA0B4/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=3739
003571: Jun 29 09:52:05: //-1/F8538BDBA0B4/DPM/dpMatchPeersCore:
No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1)
003572: Jun 29 09:52:05: //-1/F8538BDBA0B4/DPM/dpMatchSafModulePlugin:
dialstring=3739, saf_enabled=0, saf_dndb_lookup=1, dp_result=-1
003573: Jun 29 09:52:05: //-1/F8538BDBA0B4/DPM/dpMatchPeersMoreArg:
Result=NO_MATCH(-1)

[Rajan · Accepted solution]

Hi David,

Because of incoming called-number .T in the below dialpeer, DP 1002 is selected as the inbound DP.

dial-peer voice 1002 voip
description **Inbound WAN Side dial-peer**
translation-profile incoming INCOMING
session protocol sipv2
incoming called-number .T
dtmf-relay rtp-nte
codec g711ulaw
no vad

Due to the translation profile INCOMING applied in this DP, the called number is converted to 4 digits 3739 and with this it cannot match an outbound DP. you can remove the translation-profile if not needed or if that is needed for incoming calls coming into the system then create another dial-peer to match for inbound DP match for these calls without translating the called number.

HTH

Rajan

Pls rate all useful posts

[Rajan · Accepted solution]

Or if you want the called number to get translated to 4 digits, then edit the below dial-peer to CUCM for 4 digits [2-9]... instead of the current 10 digit pattern.

dial-peer voice 1001 voip
description **Outbound LAN Side dial-peer**
translation-profile outgoing OUTGOING
destination-pattern [2-9].........
session protocol sipv2
session target ipv4:10.6.102.20
dtmf-relay rtp-nte
codec g711ulaw
no vad

[David Harrell]

Yep, that fixed the dial-peer issue.

!
dial-peer voice 1001 voip
description **Outbound LAN Side dial-peer**
destination-pattern [2-9]...
session protocol sipv2
session target ipv4:10.6.102.20
dtmf-relay rtp-nte
codec g711ulaw
no vad
!

Now I am faced with this issue:

Sent:
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.255.6:5060;branch=z9hG4bK-1e29ff-75d40ea2-5d24f98b
From: "WIRELESS CALLER" <sip:4232027058@192.168.255.5:5060;transport=UDP>;tag=4d1060f8-7f000001-13c4-1e29ff-8a23d7cd-1e29ff
To: <sip:4237223739@192.168.255.5:5060>;tag=FA82B94-252F
Date: Thu, 29 Jun 2017 15:53:06 GMT
Call-ID: 4d163300-7f000001-13c4-1e29ff-a1199ca5-1e29ff@192.168.255.5
CSeq: 1 INVITE
Allow-Events: telephone-event
Warning: 399 192.168.255.5 "No matching outgoing dial-peer"
Server: Cisco-SIPGateway/IOS-15.4.3.M1
Reason: Q.850;cause=1
Content-Length: 0

Here's a current debug voice dialpeer default:

003891: Jun 29 12:00:23: //-1/E4A0AFCBA249/DPM/dpAssociateIncomingPeerCore:
   Calling Number=4232027058, Called Number=4237223739, Voice-Interface=0x0,
   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
   Peer Info Type=DIALPEER_INFO_SPEECH
003892: Jun 29 12:00:23: //-1/E4A0AFCBA249/DPM/dpAssociateIncomingPeerCore:
   Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=1002
003893: Jun 29 12:00:23: //-1/E4A0AFCBA249/DPM/dpMatchSafModulePlugin:
   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0
003894: Jun 29 12:00:23: //-1/xxxxxxxxxxxx/DPM/dpGetSIPUriProvisionBmp:
   Tag=1002
003895: Jun 29 12:00:23: //-1/xxxxxxxxxxxx/DPM/dpGetSIPUriProvisionBmp:
   Result=0 Bitmap=0x0
003896: Jun 29 12:00:23: //-1/E4A0AFCBA249/DPM/dpMatchPeersCore:
   Calling Number=, Called Number=3739, Peer Info Type=DIALPEER_INFO_SPEECH
003897: Jun 29 12:00:23: //-1/E4A0AFCBA249/DPM/dpMatchPeersCore:
   Match Rule=DP_MATCH_DEST; Called Number=3739
003898: Jun 29 12:00:23: //-1/E4A0AFCBA249/DPM/dpMatchPeersCore:
   Result=Success(0) after DP_MATCH_DEST
003899: Jun 29 12:00:23: //-1/E4A0AFCBA249/DPM/dpMatchSafModulePlugin:
   dialstring=3739, saf_enabled=0, saf_dndb_lookup=1, dp_result=0
003900: Jun 29 12:00:23: //-1/E4A0AFCBA249/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=1001

[David Harrell]

Looks like this error above may be related to CSS. Putting the SIP trunk in the same CSS as the phone has resolved the issue.

[David Harrell]

Rajan,

Incoming calls are working fine now. Outgoing calls are failing. Looks like the dial-peers send the outgoing call back to CUCM. I've attempted to cleanup the dial-peers, and reorganize them. Still no luck. Do you see anything below that would cause an outgoing call to 92027058 be redirected back to 10.6.102.20?

dial-peer voice 101 voip
description **Inbound WAN Side dial-peer**
translation-profile incoming INCOMING
session protocol sipv2
incoming called-number .T
dtmf-relay rtp-nte
codec g711ulaw
no vad
!
dial-peer voice 102 voip
description **Outbound WAN Side Peer**
preference 1
destination-pattern 9[2-9].........
session protocol sipv2
session target ipv4:192.168.255.6
dtmf-relay rtp-nte
codec g711ulaw
!
dial-peer voice 201 voip
description **Inbound LAN Side dial-peer**
session protocol sipv2
incoming called-number 9T
dtmf-relay rtp-nte
codec g711ulaw
no vad
!
dial-peer voice 202 voip
description **Outbound LAN Side dial-peer**
destination-pattern [2-9]...
session protocol sipv2
session target ipv4:10.6.102.20
dtmf-relay rtp-nte
codec g711ulaw
no vad
!

[Rajan]

Its because of the dial-peer 101 which has translation applied. This translates all the called number to 4 digits which will cause the system to route it back to CUCM.

You need to fine tune the translations and separate the translations done for inbound and outbound as per the requirement. Can you tell us whether you need any kind of number translation for the outbound call. Also let us know what could be the calling number for all the extensions in order to match and hit a specific DP for inbound matching.

[David Harrell]

Ah, makes sense. After removing that translation pattern on dial-peer 101I now get two matches on outgoing:

011267: Jun 29 14:48:12: //-1/7FD8DA000000/DPM/dpMatchPeersCore:
Calling Number=, Called Number=92027058, Peer Info Type=DIALPEER_INFO_SPEECH
011268: Jun 29 14:48:12: //-1/7FD8DA000000/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=92027058
011269: Jun 29 14:48:12: //-1/7FD8DA000000/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
011270: Jun 29 14:48:12: //-1/7FD8DA000000/DPM/dpMatchSafModulePlugin:
dialstring=92027058, saf_enabled=0, saf_dndb_lookup=1, dp_result=0
011271: Jun 29 14:48:12: //-1/7FD8DA000000/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=102
2: Dial-peer Tag=202

As far as requirements, I need to strip 9 as a prefix from all outgoing calls and be able to make local 7 digit calls, as well as 11 digit long distance calls. Of course, 911 and 9911 need to be matched also.