Hi,
I have searched and tried out all sorts of different settings for enabling/changing the way CUCiLync searches the Active Directory (AD) for contact phone numbers.
But no matter what setting I use in the HKEY_CURRENT_USER\Software\Cisco Systems, inc.\ Client Services Framework\AdminData and/or HKEY_CURRENT_USER\Software\Cisco Systems, inc.\ Client Services Framework\Active Directory hive, CUCiLync still uses the default for Work phone number. The default for this is to use telephoneNumber, the value that I wish to use is the ipPhone field.
The registry values that I have tested so far are these.
HKEY_CURRENT_USER\Software\Cisco Systems, inc.\ Client Services Framework\AdminData
- LDAP_AttributeName_businessPhone
- LDAP_AttributeName_primaryPhoneNumberForSearches
- LDAP_AttributeName_otherPhone
All set to ipPhone, and I have also tested to set it to another field in AD that contains the same value as the ipPhone, that is in my case extensionAttribute5.
HKEY_CURRENT_USER\Software\Cisco Systems, inc.\ Client Services Framework\Active Directory
- BusinessPhone
- PreferredNumber
- DisableSecondaryNumberLookups
First two set to ipPhone and the third set to 0, and I have also tested to set it to another field in AD that contains the same value as the ipPhone, that is in my case extensionAttribute5.
The above values comes from these two urls,
The later url have this
Table 3-9 LDAP Registry Subkeys
Subkey Names | Description |
LDAP_AttributeName_primaryPhoneNumberForSearches | Specify the phone number that you use to resolve most LDAP queries. This value must match one of the values specified for the following LDAP keys: •LDAP_AttributeName_businessPhone •LDAP_AttributeName_homePhone •LDAP_AttributeName_mobilePhone •LDAP_AttributeName_otherPhone The values that are valid for the LDAP attribute keys listed above are: •telephoneNumber •homePhone •mobilePhone •otherTelephone •a custom LDAP attribute value, for example, myCustomPhoneNumber The value of the LDAP_AttributeName_primaryPhoneNumberForSearches key must match one of the values in the list above, for example, telephoneNumber. Otherwise, the value of the LDAP_AttributeName_businessPhone key is used. |
The version of CUCiLync is 8.5(3)-4.5.9, that is the latest I can find on the support download page, have also tried with earlier version 8.5.(1).
Does anyone have any suggestions for how to achieve this, if at all possible?
Roger Kallberg
Unfortunatly not. I have a TAC case open, but no real responce have been resieved yet. Last update was that it's at the developers for investigation.
This is the reply we got from TAC.
Regarding to your query, Can you please go through the attached flow diagram (also you can see it in the link given below). I hope it will clarify more on the telephone number display behavior in office communicator.
As per this flow chart presently your setup is working as designed. As per the design, the number should be in E.164 format in order to be available in MOC.
You have AD in your network as a source, so OCS pulls this information from LDAP it is integrated with. As per Microsoft, here you need to add Normalization rules to OCS to normalize the number into the E164 format.
http://technet.microsoft.com/en-us/library/bb964002%28office.12%29.aspx
Phone number display for MOC contact:
- •- OCS will not provide a contacts number unless it is correctly formatted to the E.164 standard.
- •- The Address Book Service on OCS processes the contacts phone number and attempts to normalize it.
- •- If correctly normalized then the number is inserted into the OCS address book.
- •- Communicator will only display this normalized number if it is properly formatted in E.164 (+13125551234).
- •- The E.164 standard defines an international numbering plan for public phone systems.
- •- In the E.164 standard, each number contains a country code, an area code, and a subscriber number.
- •- Each phone user has a globally unique number.
- •- In Cisco UC Integration for Microsoft Office Communicator, phone numbers in E.164 format must begin with a plus character ("+").
I have done some research to your first question. Can you please just go through the blog given below from the Microsoft.
http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=26.
It tells that If the numbers not in E.164 format then the number will not appear in office communicator if LDAP integrated. Can you please check with Microsoft to see their inputs on this.
Since MOC seem to require E.164 we ended up populating that into AD and then take care of internal calls with LCR. That is we translate any "internal" E.164 call to the internal DN.
For example like this, customer have this external DID range +141055567XX and this equals to internal DN range of 10167XX. They use 0 as the outside (external) call prefix. For any call to an internal number formated in any possible external combination we translate that to the internal DN, an example would be internal call to +14105556710 would be translated to 1016710 and so on....
I hope this helps you.
Please remember to rate helpful responses and identify helpful or correct answers.
