• Skip to main content
  • Skip to secondary menu
  • Skip to primary sidebar
  • Skip to footer
  • Home
  • Disclaimer & Policy

Elan Shudnow's Blog

MVP Logo
  • Azure
  • Exchange
  • Lync

Phone Numbers not displaying for some Communicator 2007 Users

July 31, 2008 by Elan Shudnow 2 Comments

So in my organization, we’ve had Enterprise Voice with Office Communication Server (OCS) 2007 set up for quite a while and we have been adopting the usage of it more and more as time goes on. So I told someone to call my Mobile Phone number via Communicator 2007 and they said they didn’t see my Mobile Phone number.  I definitely thought this was odd as Active Directory (AD) has me configured for Home Phone, Mobile Phone, and Business Phone.  My Mobile Phone number and my Home Phone number are the same numbers while my  Business Phone number is different.

So it will help to give you a little background on how phone numbers show up to Communicator 2007 clients in relation to how my account is configured in our production AD environment.

In Office Communicator 2007, I am going into the Options > Phones Tab.  You will see that my Work Phone, Mobile Phone, and Home Phone are all greyed out.  This is because OCS 2007 is integrated with AD.  My AD account has Work Phone, Mobile Phone, and Home Phone all set.  As stated earlier, my Mobile Phone and Home Phone are the same while my Work Phone is different.

All Work, Mobile, and Home phone numbers are visible to all contacts in an AD environment if they have either Company, Team, or Personal Access Levels which you can assign to someone by Right-Clicking this individual within your Contacts list.  Because my phone numbers are published in AD, Communicator 2007 does not provide the ability to modify the phone numbers.

For contacts not in your Active Directory environment, you have more flexibility with who sees what phone numbers.  For example, if I am federated with another organization who also has OCS 2007, those contacts are not part of our Active Directory.  Because of that, the same rules in the previous paragraph do not apply.  They do not see my Work, Mobile, and Home numbers if they have either Company, Team, or Personal Access Levels to which I associated with their contact.

Instead, these contacts go by the following Access Levels ONLY if I selected to publish my phone numbers.  As you can see, I have all three of my phone numbers set to be published.  Because of that, all federated contacts can see my phone number information if I give them the proper Access Levels to do so.  By default, all new contacts are provided Work Access Levels which means federated contacts will only be able to see your Work Phone number by default.  Again, remember, if the contact is a part of your AD environment, they will be able to see all your phone numbers if they have either Company, Team, or Personal Access Levels which they will be default.

So what’s the issue?  Well it’s very simple.  If your Mobile Phone number and your Home Phone number are the same as mine are, your Mobile Phone number will not show up to others.  Only your Home Phone number will which I find to be very odd.

So because my Home Phone number and my Mobile Phone number are the same but my Business Phone Number is different, if someone goes to Communicator 2007 to select a phone number to call, they will only see Home Phone number and Business Phone number.

I have verified that this works the same way in a couple of OCS 2007 environments using Communicator 2007 and I don’t see any options to change this behavior.  You would think that all three options would display or that Mobile Phone number would have preference as the display number as Home Phone number.  After all, Communicator 2007 is a business tool.  Would you rather contact someone on their Mobile Phone number or their Home Phone number?  I would say most likely the favored choice would be the former.

Unfortunately, I haven’t seen an option to change this behavior but I have been told my another in my company to which I informed that they have notified the OCS Team.  So hopefully sometime in the future, Microsoft will modify this behavior or provide a method to which the behavior can be changed.

Share this:

  • Click to share on X (Opens in new window) X
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on Reddit (Opens in new window) Reddit

Filed Under: OCS Tagged With: OCS

Reader Interactions

Comments

  1. wayne jackson says

    September 5, 2010 at 7:10 pm

    So we have an OCS implementation exhibiting exactly the same behavior……….is there an answer??

    Reply
    • Elan Shudnow says

      September 12, 2010 at 7:18 am

      The answer is it's by design and that's how it works. If you don't like it, contact your Technical Account Manager and have him file a Design Change Request (DCR) on behalf of your company.

      Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar

  • GitHub
  • LinkedIn
  • RSS
  • YouTube

More to See

Azure AD User Settings

Pre-creating Azure AD App for Azure Migrate

January 24, 2023 By Elan Shudnow

Azure Runbooks Connecting to Exchange Online and Microsoft Graph

July 22, 2022 By Elan Shudnow

Using Python 3.8.0 Azure Runbooks with Python Packages

July 11, 2022 By Elan Shudnow

Preserving UNC Path after Azure Files Migration using DFS-N

April 10, 2022 By Elan Shudnow

Tags

ACR Always Encrypted Ansible Automation Availability Sets Availability Zones Azure Azure Active Directory Azure Application Gateway Azure Files Azure Firewall Azure Key Vault Azure Load Balancer Azure Migrate Azure Monitor Azure Web App CDN Cluster DevOps DFS Docker DPM Event Grid Exchange Exchange 2010 Exchange Online Function App ISA iSCSI Log Analytics Logic App Lync Microsoft Graph OCS Office Personal PowerShell Proximity Placement Groups Runbook SCOM Storage Accounts Symantec Virtual Machines Windows Server 2008 Windows Server 2008 R2

Footer

About Me

Microsoft Cloud Solution Architect focused on Azure IaaS, PaaS, DevOps, Ansible, Terraform, ARM and PowerShell.

Previously a 6x Microsoft MVP in Exchange Server and Lync Server.

My hobbies include watching sports (Baseball, Football and Hockey) as well as Aviation.

Recent

  • GRS Storage and BCDR Considerations
  • Pre-creating Azure AD App for Azure Migrate
  • Azure Runbooks Connecting to Exchange Online and Microsoft Graph
  • Using Python 3.8.0 Azure Runbooks with Python Packages
  • Preserving UNC Path after Azure Files Migration using DFS-N

Search

Tags

ACR Always Encrypted Ansible Automation Availability Sets Availability Zones Azure Azure Active Directory Azure Application Gateway Azure Files Azure Firewall Azure Key Vault Azure Load Balancer Azure Migrate Azure Monitor Azure Web App CDN Cluster DevOps DFS Docker DPM Event Grid Exchange Exchange 2010 Exchange Online Function App ISA iSCSI Log Analytics Logic App Lync Microsoft Graph OCS Office Personal PowerShell Proximity Placement Groups Runbook SCOM Storage Accounts Symantec Virtual Machines Windows Server 2008 Windows Server 2008 R2

Copyright © 2025 · Magazine Pro on Genesis Framework · WordPress · Log in