Smart Dial peers

[AbteenZ]

Hello,

I have a scenario with one CUBE, with one SIP trunk coming in and two locations with their CUCM subscribers.

We wanted each location phones to register with that location's subscriber but here is the problem. The CUBE doesn't know where to route the call coming in based on the DNIS and it works based on dial-peer prefrence.

I know I can create a dial-peer per DID and point to the subscriber that hosts the target phone but that's a tedious and error prone job.

Any automatic smart way to do this?

Thanks,

[Andrew West]

If I understand what you want to do right you could do the following: 

1. Create an E.164 pattern map for each location

2. Insert a char before sending off of CUBE for example a #

3. Use Trans patterns on UCM to match that charcter you insert and route where you need to. 

It's late and Im tired so there is probably an easier way to do this which will come to me in the morning.. =)

[Dennis Mink]

Look into deploying ILS between your CUCMs and CUBE, that will make all this more manageable than administring dialpeers

[Andrew West]

Good pickup! 

When I read locations I was thinking "bandwidth" and not 2 seperate UCM clusters. 

Late night thinking is always fun. 

[Ayodeji Okanlawon]

You may be over thinking this. This is much simpler than you think..

Two CUCM subscribers in a single cluster.

Single CUBE

There are multiple ways to achieve this..but this is the easiest

1. Configure dial-peer with the relevant DDI range and use e164 pattern map

voice class e164-pattern-map 1

e164 557...  ..this is for location 1

e164 558... ..this is for location 1

e164 666... this is for location two

2. configure a single dial-peer and reference the e164 pattern-map above

eg dial-peer voice 5 voi

pref 1

destination e614-pattern-map 1

sess targ ipv4:sub1

eg dial-peer voice 6 voi

pref 2

destination e614-pattern-map 1

sess targ ipv4:sub2

[AbteenZ]

What if there is phones registered with each subscriber that share a line? 

[Dennis Mink]

Abtin,

can you confirm this for me, are your two subs part of the same cluster or are they in independent/different clusters?

[AbteenZ]

Yes Sir. They are part of a single cluster.

[Dennis Mink]

In that case, you dont strictly need your dial peers follow where your phones are registered. either sub has knowledge of the other subs registered phones and extensions, and vice versa.  so although your dial peer might point to the sub that the destination phone is not registered on. singnalling will point to the IP address of the phone registered on the other sub. the only way to make this somewhat more optimal is to use dial peer preferences based on patterns that are on sub 1 and sub 2 only. But the question really, what problem are you actually trying to fix by doing that.

thanks

[AbteenZ]

The problem is the dial peer wont route the call to the phone that is registered to the other subscriber that is not the target of the dial peer.

[Jaime Valencia]

Then you have some other problem in your cluster, either you're pointing to a server where the H.323 daemon is not running, or you might have SDL problems in your CUCM cluster.

As Dennis has pointed out, the servers in the CUCM cluster are aware of where the devices are registered, and there is no real need for dial peers to be specific to only DN's in each server.

[AbteenZ]

Well let me describe the Scenario now that I've learned the fact about subscribers knowing about each other's registered phones.

The CUBE recieves the call from the SIP provider through this Dial Peer

dial-peer voice 2582 voip

 description SIPT outbound DP to CUCM Subscriber

 translation-profile outgoing Last10

 destination-pattern ^258[2-9]..[2-9]......$

 session protocol sipv2

 session target ipv4:10.10.10.38

 voice-class codec 1

 dtmf-relay rtp-nte

 no vad

as you can see in the following debug message the provider adds a 258 to the called number.

Sep 27 23:59:26.495: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

ACK sip:2586266266262@172.17.100.250:5060;dtg=caciquetg1 SIP/2.0

Via: SIP/2.0/UDP 12.12.1.1:5060;branch=z9hG4bKl61htu300go19spje4d0.1

CSeq: 585363086 ACK

From: "ABTIN,YAZDANI  "<sip:8182400558@12.12.1.1;user=phone>;tag=SDncu5f01-1139057836-1506556763419-

To: "6266266262 6266266262"<sip:2586266266262@sip.example.com>;tag=F2615622-509

Call-ID: SDncu5f01-b7115ac0c705985107e0e08d2f3a5958-v300g00

Max-Forwards: 68

Content-Length: 0

Which this translation rule takes care of it.

voice translation-rule 10
rule 1 /.*\(..........\)/ /\1/

Since the provider forwards all the digits the previous phone guy has decided to config the DN on the phones like this.

Does this make any difference now? 

Thanks,