Directory Lookup Rule

[rchaseling]

Hi,

I'd just like to confirm something. I'm designing a new UC 11.X deployment and thinking of proposing E164 numbering end to end. Meaning extension numbers in E164 and E164 numbering in directory fields.

My concern is user confusion as they would be used to seeing 4 digit extensions in directories. I have two areas I'd like to convert if possible to soften the blow.... but from my initial testing doesn't look like it works by using Directory Lookup Rules

+ Attendant Console 11.X

+ IP Phone Corporate Directory

I have a rule in place that says any number starting with + and being 12 digits long (which includes the +) strip off the first 8. This does not reflect in the CUACA directory or IP Phone

Is there any way of doing this?

Thanks

[Mohammed al Baqari]

Hi,

Best to do is to review CUCM SRND to check globalization and normalization. You are in the right track at the concept level.

Based on SRND, your routing table should include E164 numbers. However, you need to use translation-patterns to convert users dialing habits to globalized dialing format. Then you need to ensure that you enforce onnet local calling to as you proposing E164 DNs.

Best is to refer to SRND as this is well covered there

[rchaseling]

Thanks for that. I understand what is required to configure the dialplan if I configure E164 end to end.

My question is around visible directories - CUACA and Corporate Directory. UCM will be integrated with AD and if I get the AD team to enter E164 numbering for the telephoneNumber field this is what will be seen in CUACA and Corporate Directory......I was wondering if there was a way that this could be manipulated - I assumed Directory Lookup Rules did this but it doesn't seem to be the case in my testing

Thanks

[Mohammed al Baqari · Accepted solution]

You mean to manipulate the telephoneNumber field when replicated from AD so that enduser will have the manipulated number in his configuration window.

If my understanding is correct, this isn't doable. CUCM will get the fields from AD as they are. You can only manipulate when users dial these numbers (whether directly or from directory) through the use of translation-patterns.

[rchaseling]

Yes this does seem to be the case. Thanks for confirming

[aneesap90]

Hi,

Having the same requirement

User is dialing from jabber in PC. Jabber contact details are like
Work:
Email:
Mobile:
Other:
All filed are filled by taking AD. in the filed "other" user's direct line is given which is start with +966XXXXXXXXX. so when user click on this number call should route.if it is 00966XXXXXXXXX then call we routing by matching the application dial rule, where we can remove 00966 and 9 can be added as prefix to match with route pattern.But AD entry is starts with +966
Any way to customize this? Translation pattern also we cannot start with + right ?

Please suggest