Non-E.164 number format on CUBE

[Yangjp715]

Hi all,

We have global e.164 number deployed on CUCM. I was wondering is there any issue if i use non-e164 numbers on CUBE? The incoming non-e.164 number without +1 will match the e.164 number on CUCM?

Thanks!

[Yangjp715]

Any help would be appreciated.

[Maren Mahoney · Accepted solution]

This is easy to do with digit manipulation. If the number comes in from the service provider in 10-digit format and your dialplan is E164, then use voice translation profiles on the CUBE to globalize the number prior to sending it to CUCM.

Here is one example:

voice translation-rule 1
rule 1 /\([2-9].........\)/  /+1\1/

voice translation-profile globalize
 translate called 1
 translate calling 1

dial-peer voice 1 voip
 description CUCM-facing dial-peer for calls from PSTN to CUCM
 translation-profile outgoing globalize

There are a bunch of resources for learning about and writing voice translation profiles. Here is one from Cisco:  Number Translation using Voice Translation Profiles 

And here is the first of in a series of four that I wrote because my students asked so many questions. The links to the other three parts are in there: Cisco IOS Voice Translations – Part 1: The Basics of Voice Translation Rules 

There is more to the overall dialplan with regards to dial-peers on the CUBE and localization of digits outbound from CUCM, but this will get you started with digit manipulation.

Maren

[Yangjp715]

Thanks Maren. Actually, all services are working fine with the existing configuration for this client. I was just wondering How the incoming calls in 10-digit format by using e164-pattern-map under the sip dial-peer match the desk phones with e.164 number? I checked device pool and the SIP trunk, there is no +1 added under incoming called party.

[Yangjp715]

No related translation-profile configured on the CUBE

[Yangjp715]

Figured out. Thanks