CUBE Destination Dial peer group configuration

[Muthurani Lavanya Paneerselvam]

Introduction

This document covers the procedure for configuring Destination Dial peer groups. 

Dial-peer grouping feature. A group of dial-peers can be made a part of a dial-peer group under a “voice class dpg <tag>”
“destination dpg <tag> will be used to reference a dial-peer group  from an incoming dial-peer
Once an incoming dial-peer is matched. The dial-peers which are a part of the dpg defined under it will be used for outbound dial-peer matches on the particular call.

(config)#voice class dpg <tag>
(config-class)#dial-peer <dial peer tag> preference <preference number>

• Allows grouping of outbound dial-peers based on an incoming dial-peer, reducing existing outbound dial-peer provisioning requirements.
• Eliminates the need to configure extra outbound dial-peers that are sometimes needed as workarounds to achieve desired call routing outcome.

Dial peer group configuration

Step 1: Incoming Dial peer is first matched 

Device(config)# dial-peer voice 100 voip
Device(config-dial-peer)# incoming called-number 1341
Device(config-dial-peer)# destination dpg 10000
Device(config-dial-peer)# description DP Source Boston w/voice class dpg
Device(config-dial-peer)# end
Device(config)# end

Step 2: Now the DPG associated with the Inbound DP is selected  ie dpg 10000 is selected in the above configuration

Grouping outbound dial peers and configuring preferences needed.

Device(config)# voice class dpg 10000
Device(config-class)# dial-peer 1001 preference 1
Device(config-class)# dial-peer 1002 preference 2
Device(config-class)# dial-peer 1003 
Device(config-class)# description voice class DPG for DP Source Boston
Device(config-class)# exit

3. Outbound DP is selected based on the above configuration

Configuring outbound Dial peers
Device(config)# dial-peer voice 1001 voip
Device(config-dial-peer)# destination-pattern 1001
Device(config-dial-peer)# session protocol sipv2
Device(config-dial-peer)# session target ipv4:10.1.1.1
Device(config-dial-peer)# exit

Device(config)# dial-peer voice 1002 voip
Device(config-dial-peer)# destination-pattern 1002
Device(config-dial-peer)# session protocol sipv2
Device(config-dial-peer)# session target ipv4:10.1.1.2
Device(config-dial-peer)# exit

Device(config)# dial-peer voice 1003 voip
Device(config-dial-peer)# destination-pattern 1003
Device(config-dial-peer)# session protocol sipv2
Device(config-dial-peer)# session target ipv4:10.1.1.3
Device(config-dial-peer)# exit

Verify

Show voice class dpg <tag>
Ex. CUBE#show voice class dpg 10000
Voice class dpg: 10000      AdminStatus: Up
 Description:
 Total dial-peer entries: 4
 Peer Tag           Pref
 --------           ----
 1                  0
 2                  0
 104                0
 1000               0
------------------------------------

Troubleshoot

Debug voip dialpeer can be used for debugging to identify the DPG selected and the list of dial-peers under the DPG that match the destination pattern.

*Jul 19 10:15:53.311 IST: //-1/ED647BD1B0F9/DPM/dpMatchPeersCore:
   Outbound Destination DPG Group Request; Destination DPG=21
*Jul 19 10:15:53.311 IST: //-1/ED647BD1B0F9/DPM/dpMatchDestDPGroup:
   Result=0
*Jul 19 10:15:53.311 IST: //-1/ED647BD1B0F9/DPM/dpMatchPeersCore:
   Result=SUCCESS(0) after DestDPGroup
*Jul 19 10:15:53.311 IST: //-1/ED647BD1B0F9/DPM/dpMatchSafModulePlugin:
   dialstring=244510104, saf_enabled=0, saf_dndb_lookup=1, dp_result=0
*Jul 19 10:15:53.311 IST: //-1/ED647BD1B0F9/DPM/dpMatchPeersMoreArg:
   Result=SUCCESS(0)
   List of Matched Outgoing Dial-peer(s):
     1: Dial-peer Tag=104
     2: Dial-peer Tag=1000
     3: Dial-peer Tag=102
     4: Dial-peer Tag=101
     5: Dial-peer Tag=104

[Wilson Samuel]

Hi Muthurani,

Looks like the document got edited and fell short of the complete description. 

Could you please add some more description to it?

Regards

[Yorick Petey]

Hi Muthurani,

Once the outbound DP is selected within a DPG, is the command "destination-pattern" used?

I mean, is there any other matching mechanism processed at the outbound DP level, to confirm this DP can really be used? (like "destination-pattern", or "voice class e164-pattern-map")

This part is not clear in the docs.

Thank you.

[Joshua Warcop]

Yorick,

When an inbound dial-peer is bound to an outbound dial-peer using dpg the destination-pattern is not used for matching. The destination-pattern is still required to be configured.

show dial-peer voice | inc destination - this will show the dpg tag and validity

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/multiple-outbound-dial-peer.html

Thanks!

[nicklng86]

But why?  What are the benefits?  

[j.a.m.e.s]

I can see some value in this for loop prevention, so that if a CUBE is configured with a wildcard (e.g +.T) and a call arrives from an ITSP it can be forced to match a PBX-facing outbound dial-peer. 

However,  ignoring the destination-pattern seems a bit of a stumbling block. Surely one of the reasons to use an SBC is to check the destination-pattern sent by the provider, rather than just offloading that problem to the PBX? I guess you could configure "incoming called e164-pattern-map" on the inbound DP, but most people prefer to do this match on "incoming uri via" as that takes precedence.

The other problem which I foresee is that you might have more than one PBX and want CUBE to route calls to the appropriate far-end based on destination-pattern.

[j.a.m.e.s]

I just found an interesting solution which I was not aware of before I wrote my previous comment. This addresses a situation where:

• You want to match inbound dial-peers based on "incoming uri via xxx" because it's the first choice match criteria
• You want to force the call to a destination dial-peer using "destination dpg XXX" and hence disable an outbound match based on dialed-number
• For security reasons, you still want some destination checking done on the CUBE before handing off the call to the PBX.

I hadn't realized the call-block command could work based on DNIS:

! Block at the ITSP facing incoming dial-peer:
dial-peer voice X
 call-block translation-profile incoming tp-inbound
exit
voice translation-profile tp-inbound
  translate called 1
exit
voice translation-rule 1
 ! Search and Replace valid DDI ranges without modification:
 rule 1 //\(\+XXEnterYourValidDDIRange\)$/ /\1/
 ! reject everything else:
 rule 100 reject /.*/
exit

The above appears to work in CUBE v12, but not in v11 (Denali).