Article ID: 971844 - Last Review: July 31, 2009 - Revision: 1.1

No calling party name appears in Communicator 2007 R2 when a Private Branch Exchange telephone user calls a Communications Server 2007 R2 user

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Expand all | Collapse all

SYMPTOMS

When a Private Branch Exchange (PBX) telephone user calls a Microsoft Office Communications Server (OCS) 2007 R2 user, the calling party name that exists in PBX is stripped at the OCS 2007 R2 Mediation Server stage. Because the PBX telephone user does not exist in Active Directory directory service, no name appears in Microsoft Office Communicator 2007 R2.
Back to the top

CAUSE

This problem occurs because OCS 2007 R2 Mediation Server does not forward the display name information from the Unified Communications (UC) side to the gateway side. Therefore, the Communicator 2007 R2 client does not receive the display name information.
Back to the top

RESOLUTION

To resolve this issue, apply the following updates:
  • 969695  (http://support.microsoft.com/kb/969695/ ) Description of the update for Communicator 2007 R2: July 2009
  • 970679  (http://support.microsoft.com/kb/970679/ ) Description of the update package for Office Communications Server 2007
  • 969821  (http://support.microsoft.com/kb/969821/ ) Description of the update package for Office Communications Server 2007 R2: July, 2009
  • 969835  (http://support.microsoft.com/kb/969835/ ) Description of the update package for Office Communications Server 2007
Back to the top
APPLIES TO
  • Microsoft Office Communicator 2007 R2
Back to the top
Keywords: 
kbqfe kbexpertisebeginner kbsurveynew kbprb KB971844
Back to the top