Changing called number based upon calling number

[iptuser55]

I  need to present different number to the original number.   I know I can do this by external mask but is there another neater way? 

DN 5551234

Calls 911

Outbound need to show  2221000 to 911 instead of 5551234

DN 5551234

Calls a normal number say 6104545

Outbound to show 5551234 to 6101234

I don't want to use different route patterns or lots of partitions

Also we  use RLG as well, so my idea is to  use a single route pattern 911, then use calling transformation to capture the different calling DN and then change the calling DN based upon that number 

[R0g22]

If you are using a CUBE and/or a SIP trunk to your GW, it is much easier to it there rather than on UCM IMO.

[iptuser55]

Thanks for the reply

The DN's making call will from different sites and the modified number will different per site

Site A 

Dn555xxxx

Make a normal call then their ddi is sent

Make a 911 then the sited.  number ie 2221000

Site B 

DN 444xxxx

Make a normal call then their ddi is sent

Make a 911 then  the sites number 6121800

Cube Config

change the sites  911 to say 555911 in cucm then route to cube and set up a dial peer  of destination pattern 555911 then send Site A 2221000

Same with site B  change outbound to 444911  dial peer destination 444911 send out site B 6121800

I guess this can or is there a better way in cube or better to do it in cucm  ? 

[Jinto Alakkal]

Hi You can do it in this way

create voice translation rules and place them on the Emergency numbers dial peer, if you are using standard local route groups for emergency dialing this is the way to go so that you don't have to create any additional partitions or patterns for example

Voice translation profile

=======================

Voice translation-profile Emergency
translate calling 400

Voice translation rule

===================

Voice translation-rule 400
rule 1 /555....$/ /2221000/
rule 2 /444....$/ /6128100/

Dial peer

========

Destination-pattern 9911
forward-digits 3
translation-profile outgoing Emergency

[iptuser55]

We have a centralised PSTN cube set so the GW approach works though we also have standalone GWs as well so we can replicate the same setup with GW.

I worked for a company where we did the following

SiteA site code 444

Route Pattern 9.911 PT_911_SITEA

Device CSS contains pt_911_SITEA

TP 9.911

Translate to say *9.911

Route Pattern *9.911

Use Device Pool calling transformation 

Calling Transformation PT_SITEA

 444XXXX-PT_SITEA

transform to 2123331000

If my memory is correct- has anyone used this method- pro`s and con`s

thanks

[Jinto Alakkal]

Device pool level transformation will affect all calls for the devices using that device pool, or you have to create 911 route patterns for each site and add the calling party transformation mask from the route pattern level, the problem with this approach you will have multiple 911 patterns in different partitions. Not sure in your config why you have a route pattern and translation pattern with same 9.911

[iptuser55]

The multiple route pattern are

User dials 9.911 -these are example digits

Which is a TP for siteA

TP translates this to *9911

Route pattern *9911

This is set to use the calling  transformation of the device pool and a css of

css-siteA-XForm

Pt-911

We assign all logged DN's of site A to pt-911 eg logged out devices 444xxxx 

Where the calling DN matches then change the outgoing CLI if site A

If the DN doesn't match then don't change outgoing cli

This is from memory. It looks like the cube approach us better but is there a better way using xform patterns 

[Maren Mahoney]

If you are talking specifically about altering callerID for emergency (911) calls, and you are using CUCM 11.0 or later, have you looked at implementing the native Emergency Call Handler available in that version?

The upshot is that you can assign ELINs on a per-Device Pool basis. And Device Mobility will allow roaming users to pick up the ELIN on their roaming device pool.

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200452-Usage-of-Native-Emergency-Call-Routing-F.html