Call Routing from CME through CUCM to PRI

[rajeshpat]

Hi Guys,

Need your help for one of my customer. His phone is registered with CME and in our setup, we also have CUCM which is connected with CUBE (ITSP trunk). CUCM and CME are integrated via SIP trunk. By this setup, we are able to make calls from CME to CUCM and vice-versa. Now the user has a request that he wants to dial 1800XXXXXXX pattern from CME that has to go through CUCM via CUBE as a PSTN call. 

So it is possible to do. If so then can you please let me know how can I achieve this.

Regards,

Raj

[Ratheesh Kumar]

Hi there

How about configuring a dial-peer in CME pointing 1800XXXXXXX to a dummy number in CUCM (say 6161). Create a Route Pattern in CUCM forwarding to 1800XXXXXXX thru your CUBE.

Hope this Helps

Cheers
Rath!

***Please rate helpful posts***

[Jaime Valencia]

First, figure out exactly how they want to dial to know how to configure this.

Then, configure a DP in CME pointing to CUCM as they wish to dial.

In CUCM make sure there is a RP to match what they want to dial.

Make sure the inbound CSS of the SIP trunk to CME can reach the required RP.

If required, do digit manipulation as necessary in your system(s)

[rajeshpat]

Hi Jaime,

I have already created the dial peer and route pattern that should route through CUBE

Dial peer in CME:

dial-peer voice 708 voip
description Outgoing call to SIP trunk
preference 1
destination-pattern 91800.......
session protocol sipv2
session target ipv4:<CUCM_IP>
dtmf-relay sip-notify rtp-nte
codec g711ulaw

Route pattern:

9.1800XXXXXXX --> RL --> RG --> SIP trunk (CUBE).

But the dial peer which I created it not taking. Instead, it is taking the dial peer of destination-pattern 900T.

dial-peer voice 59 pots
trunkgroup PSTN-TRUNK
description **CCA*International**
translation-profile outgoing OUTGOING_TRANSLATION_PROFILE ( rule 1 /^9/ //)
preference 5
destination-pattern 900T
forward-digits all
no sip-register

Please guide me 

Regards,

Raj

[gmgarrian]

Can you get debugs for a failed call?  I'm not seeing how it would hunt to that other dial peer.

debug ccsip message

debug voip ccapi inout

Thanks!

[rajeshpat]

Hi,

Please find the attachment which is debug output (debug voip ccapi inout). Also I have given the details about calling and called number and the dial peer which is getting triggered

Calling number: 104
Called number: 918005532447

dial-peer voice 59 pots
trunkgroup PSTN-TRUNK
description **CCA*International**
translation-profile outgoing OUTGOING_TRANSLATION_PROFILE
preference 5
destination-pattern 900T
forward-digits all
no sip-register

voice translation-profile OUTGOING_TRANSLATION_PROFILE
translate called 1112

voice translation-rule 1112
rule 1 /^9/ //

Regards,

Raj

[gmgarrian]

Can you send the current configuration?

The debugs show only 1 then 8 dialed and then it errors out:  (Digit collect failed).

Should you be dialing a 9 first?

[rajeshpat]

Hi,

Yes, we are dialing as 918005532447 and don't know why it is taken the pattern 900T.  This is the logs which were pulled at the time of testing.

Regards,

Raj

[R0g22]

Share your config.

[rajeshpat]

attaching the config file 

[R0g22]

Are you sure the 900 number was not dialed ? Per the config there is nothing that could translate the DNIS.
Need additional logs to further isolate -

debug voip translation
debug voip dialpeer
debug voice ccapi inout
debug voip application callsetup

[R0g22]

Is your CME and CUBE hosted on the same IOS router ? If yes, not a supported deployment and would not recommend it either (there are exceptions to this though).

If not, just have a dial-peer on this CME point directly to the CUBE. Again, it depends how your network is, how is QoS enforced, what path you want RTP to take etc.