Link to home
Start Free TrialLog in
Avatar of amigan_99
amigan_99Flag for United States of America

asked on

AD Integration to UCM 7.1 full phone number

I setup LDAP/Active Directory import to UCM.  The problem I have is that "Telephone Number" in AD ends up in "Telephone Number" field in End User Config in UCM.  So say I have 650-737-2222 in AD - this winds up in UCM.  On the phone if I go to Corporate Directory I search my user ID and it shows the telephony number 650-737-2222.  But if I press Dial - it dials without a "9" so you end up with fast busy.  If I hit EditDial and try to press "9" it puts in a "w" - doesn't even give me the option to put in a 9 to dial out!  Is there any way to get the 9 to work with the Edit Dial?  And ideally I would like the Corporate directory to just have the last four digits of Telephony number.  I may need to just use AD field "IP Phone" and put the extension there.  Any other way to accomplish this integration better?
Avatar of greekstones
greekstones
Flag of United States of America image

that is a very good question

you can configure Directory Lookup dial rule for this. Configuration can be found below

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_1_1/ccmsys/a03adial.html#wp1036745


regards.
Avatar of amigan_99

ASKER

The URL is referring to Attendant Console.  But this should work with Corporate Directory on a standard phone as well?  It looks like I would want to strip the left six digits if yes.  I'll look at this closer when I get to the office.  Thanks!
sorry yes that is same for their corporate directory
So I think we're onto something here with the Directory Lookup Dial Rule.  The thing that's a little unclear is what this applies to.  I want to only affect numbers in Corporate Directory - that is the number in the "Telephony Number" field of the user database.  They're not saying precisely that.  
Directory Number is the four digit extension associated with each device.  I am just wanting to be 110% certain that the only time this Dirctory Lookup Dial Rule would come into play would be when someone hits Directory button/Corporate Directory and tries to dial from there.  I don't have a lab to test this hence the paranoia.  :-)  Thank you.


Directory lookup rules transform caller identification numbers into numbers that can be looked up in the directory. Each rule specifies which numbers to transform based on the beginning digits and length of the number. For example, you can create a directory lookup rule that automatically removes the area code and 2 prefix digits from a 10-digit telephone, which would transform 4085551212 into 51212. If Cisco Unified Communications Manager Attendant Console can match the number with a user in the speed-dial entries of the attendant or in the directory, the attendant console displays the name in the Call Detail window.

Table 39-1 describes the available settings in the Phone Configuration window. For more information about related procedures, see the Related Topics topic.

Table 39-1 Directory Lookup Dial Rule Configuration Settings
Field
      
Description

Name
      

Enter a name for the directory lookup dial rule. The name can contain up to 50 alphanumeric characters and can contain any combination of spaces, periods (.), hyphens (-), and underscore characters (_).

Description
      

Enter a description of the directory lookup dial rule in the Description field or leave blank.

Number Begins With
      

Enter the initial digits of the directory numbers to which you want to apply this directory lookup dial rule. For example, if you enter 972, this dial rule applies to directory numbers that include 9725551212.

Valid values include numeric digits (0 through 9), plus (+), asterisk (*), and pound (#).

Number of Digits
      

Enter the length of the directory numbers to which you want to apply this directory lookup dial rule. For example, if you enter 7, this dial rule applies to directory numbers including 8675309.

Total Digits to be Removed
      

Enter the number of digits that you want Cisco Unified Communications Manager to remove from directory numbers that apply to this dial rule. For example, if you enter 3, Cisco Unified Communications Manager removes 408 from directory numbers that include 4085556666.

Valid values for this field range from 0 to 100. The total digits to be removed cannot be more than the number of digits of the directory numbers that apply to this directory lookup dial rule.

Prefix With Pattern
      

Enter the pattern to prepend to directory numbers that apply to this directory lookup dial rule. Valid values include digits (0 through 9), plus (+), asterisk (*), and pound (#).
Hi amigan_99

I tested this feature for you and it doesn't work . Sorry for this confusion. I always thought that the directory dial rule was for the corporate directory but unfortunatly is ony for CTI application very strange is same as the application dial rule.

however I replicated your solution in my lab and the only way i can see this to work is to create translation pattern as shown below



I created this translation

Translation Pattern 2123945XXX

Partition: None (very important all the devices needs to have access so the none partition will do the job)

Called Party Transform Mask : 5XXX

Calling Search Space: css- Internal  (this calling search space is very important just add the calling search space that has access to internal only not pstn access)


now if i go to the corporate directory and dial 2123945002 the translation will change it to 5002.

I hope that helps








So implementing this translation would take place globally - correct?  So say I was in another office on the same cluster and I manually dial 2123945222 - this call in your example would get translated to 222 correct?  Or is there some way to limit the effect of the translation so that it only executes when someone goes to the Directory/Corporate Directory and selects from there?  Thank you for the clarification.
ASKER CERTIFIED SOLUTION
Avatar of greekstones
greekstones
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thank you very much!
Post-note: Using the translation profile as described worked perfectly.