Asked by:
ABServer and IP Phone telephone number field

Question
-
Will the ABServer parse the IP Phone field of a user for telephone number to display, or will ABServer only parse the telephone number from the general tab, and the other numbers from the telephone numbers tab?
Tuesday, May 19, 2009 9:16 PM
All replies
-
It processess all telephone numbers
Look into the Invalid_AD_Phone_Numbers.txt to view which are not translated correctly
Example
Unmatched number: User: 'SMTP:x' AD Attribute: 'otherTelephone' Number: '6028'
Unmatched number: User: 'SMTP:x' AD Attribute: 'mobile' Number: '06-53542476'
Unmatched number: User: 'SMTP:x' AD Attribute: 'telephoneNumber' Number: '(xx) 318-649630'
- Belgian Unified Communications Community : http://www.pro-exchange.be -Tuesday, May 19, 2009 10:35 PM -
Here's a list of the attributes it gets in R1. I don't believe there are any substantial changes for R2.
Name
msExchHideFromAddressLists
givenName
sn
displayName
title
mailNickname
company
physicalDeliveryOfficeName
msRTCSIP-PrimaryUserAddress
telephoneNumber
homeNumber
otherHomeNumber
mobile
otherMobile
otherTelephone
ipPhone
mail
proxyAddresses
groupType
manager
Mike Stacy | Evangelyze Communications | http://www.evangelyze.net/cs/blogs/mikeWednesday, May 20, 2009 2:52 AMModerator -
I've got IP Phone field populated with a full E164 number, but it does not show in the address book or in the invalid numbers text file. I've regened the UR and resync'd abs but am not able to see the ip phone field. I'm thinking this has to do with level of access, but I've never seen IP phone listed as a field viewable by a level of access. Just home, cell etc.Wednesday, May 20, 2009 12:25 PM
-
The absconfig.exe resource kit tool can add additional number attributes to the OCS Address Book data:
http://social.microsoft.com/forums/en-US/communicationsserveruser/thread/e33de985-550a-49a9-a26d-c6ef1c7a76a4/
Also, Access Levels only apply to numbers added by end-users into their Communicator client's Phones settings. Any telephone fields populated directly in Active Directory will always display for all users, regardless of the Access Level they may be granted by a user. Basicall anything published in AD is concidered 'public' and readable by all authenticated users.
Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCSWednesday, May 20, 2009 1:38 PMModerator -
We decided to populate the E164 numbers off the ADUC users' general tab, 'Other' button and they show up now.
Jeff-
Are you certain that all AD numbers are available publicly? Wouldn't that pretty much eliminate the need for access levels? Very few of our users or customer's users have the know-how to populate and publish their own numbers inside OC. In AD we do have some people configured with home numbers but they do not appear unless you set them to team or personal. Just want to see if we are doing something wrong or if that is the case.
Thanks!
MattWednesday, May 20, 2009 1:57 PM -
Yes that's correct; I've blogged about it in the past: http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=26
And it's documented by Microsoft in the Communicator Quick Reference Card:
http://www.microsoft.com/downloads/details.aspx?familyid=526C7DF3-0965-4597-ABD8-75C4A8515F34&displaylang=en
*If these attributes are defined in Active Directory®, they are visible to all contacts in your company, regardless of Access Level. They are also visible to federated contacts, depending on the assigned Access Level. They are not visible to public instant messaging contacts.
The Access Levels control more than just phone number visibility (e.g. Meeting details)
Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCSWednesday, May 20, 2009 2:46 PMModerator