Interop or coexistence issues when a user calls Office Communications Server 2007 R2 Attendant to try to join a meeting that is hosted on a Microsoft Communication Server 2010 pool

Article ID: 981219 - View products that this article applies to.
Expand all | Collapse all

SUMMARY


Beta Information
This article discusses a beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this beta product. For information about how to obtain support for a beta release, see the documentation that is included with the beta product files, or check the Web location where you downloaded the release.


Users encounter interop or coexistence issues when they contact Microsoft Office Communications Server 2007 R2 Attendant to try to join a meeting that is hosted on a Microsoft Communication Server 2010 pool.
  • When an Office Communications Server 2007 R2 Attendant user tries to join a conference that is hosted on a Communication Server 2010 pool, the user may hear Office Communications Server 2007 R2 Attendant play an error prompt when they enter the lobby. Then, the user is disconnected.
  • When an Office Communications Server 2007 R2 Attendant user tries to join a conference that is hosted on a Communication Server 2010 pool, the user may hear Office Communications Server 2007 R2 Attendant play an error prompt when the conference is locked. Then, the user is disconnected.
  • By default, the out-of-the-box settings of a Communication Server 2010 online meeting require all users who dial in through Office Communications Server 2007 R2 Attendant to enter a telephone number and a PIN code. However, this does not occur if callers dial in through Communication Server 2010 Attendant.
Back to the top | Give Feedback
In Communication Server 2010, a new concept called the lobby was introduced. This concept is represented by the conference Focus returning the onHold value. However, Office Communications Server 2007 R2 Attendant does not understand this new concept. Therefore, Office Communications Server 2007 R2 Attendant reacts to the unknown response by disconnecting the caller after it plays an error prompt.
Back to the top | Give Feedback

RESOLUTION

To fix these problems, install the update for Office Communications Server 2007 R2 that is dated April 2010.
980370
(http://support.microsoft.com/kb/980370/ )
Description of the cumulative update for Office Communications Server 2007 R2, Conferencing Attendant: April 2010

The update for Office Communications Server 2007 R2 that is dated April 2010 introduces a new behavior called interpool transfer to Office Communications Server 2007 R2 Attendant. This behavior works as follows. Office Communications Server 2007 R2 Attendant detects that the conference ID entered by the caller corresponds to a conference hosted on a Communication Server 2010 pool. Then, Office Communications Server 2007 R2 Attendant transfers the call to the Communications Server 2010 Attendant in the pool where the conference is being hosted. However, Office Communications Server 2007 R2 Attendant only transfers the call if the pool in which the conference is being hosted is newer than Office Communications Server 2007 R2 Attendant.

If you cannot install the Office Communications Server 2007 R2 CU5 package that is described in the "Resolution" section, use the combination of the following items that best suits your organization:
  • To prevent Office Communications Server 2007 R2 Attendant from contacting the lobby for Communications Server 2010 meetings, change the meeting policy so that default meetings are anonymous, instead of open meetings.
  • To prevent Office Communications Server 2007 R2 Attendant from contacting the lobby for Communications Server 2010 meetings, advise users to enable the PSTN users bypass the lobby check box when they customize an online meeting.
  • To prevent Office Communications Server 2007 R2 Attendant from hitting locked Communications Server 2010 meetings, advise users not to lock meetings.
  • If you can do this, advise users to always call the access number that is shown in the meeting invite. This should increase the possibility that users will call Communications Server 2010 Attendant to join meetings hosted on a Communications Server 2010 pool.

Note You must only follow these steps if you cannot install the update for Office Communications Server 2007 R2 that is dated April 2010.
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

Properties

Article ID: 981219 - Last Review: October 6, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft Office Communications Server 2007 R2 Standard Edition
  • Microsoft Office Communications Server 2007 R2 Enterprise Edition
Keywords: 
kbhotfixserver kbsurveynew kbfix kbexpertiseinter kbautohotfix atdownload KB981219
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top