Microsoft Office Communications Server 2007 R2

Client Technical Reference

Published: June 2009 Updated: October 2009

For the most up-to-date version of the Client Technical Reference documentation and the complete set of the Microsoft Office Communications Server 2007 R2 online server and client documentation, see the Office Communications Server TechNet Library at http://go.microsoft.com/fwlink/?LinkID=132106. Note: In order to find topics that are referenced by this document but not contained within it, search for the topic title in the TechNet library at http://go.microsoft.com/fwlink/? LinkID=132106.

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. 2009 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, ActiveX, Excel, Hyper-V, Internet Explorer, MSN, MSDN, OneNote, Outlook, PowerPoint, RoundTable, SharePoint, SQL Server, Visio, Visual Basic, Visual C++, Visual J#, Visual Studio, Windows, Windows Live, Windows Media, Windows Mobile, Windows NT, Windows PowerShell, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.

Contents
Microsoft Office Communications Server 2007 R2.........................................................................1 Client Technical Reference..........................................................................................................1 Contents..........................................................................................................................................3 Client Technical Reference.............................................................................................................6 Installation Methods........................................................................................................................6 Multiple Client Installation Script (OCInstall.wsf).........................................................................7 Unattended Installation and Microsoft XML Core Services 6.0 (MSXML)....................................7 Installing Communicator by using Group Policy..........................................................................7 Compatibility and Integration...........................................................................................................7 Client Compatibility......................................................................................................................8 Planning for Compatibility.........................................................................................................8 Compatibility among Office Communications Server 2007 R2 Clients ...................................9 Multiple Points of Presence with Previous Client Versions.......................................................9 Interoperability with Previous Client Versions ..........................................................................9 Communicator 2007 R2 Compatibility ..................................................................................10 Microsoft Office...................................................................................................................10 Exchange Server.................................................................................................................11 Windows..............................................................................................................................11 Public Instant Messaging Clients........................................................................................12 Communicator 2007 R2 Integration...........................................................................................12 Planning for Communicator 2007 R2 Integration....................................................................13 Integration and Exchange 2007..............................................................................................14 Exchange 2007 Communication Interfaces............................................................................14 Publishing Free Busy Information...........................................................................................15 Controlling Integration............................................................................................................15 Integration with Office SharePoint Server, Office Word, and Office Excel..............................17 Office SharePoint Server........................................................................................................17 Word and Excel......................................................................................................................17 Common Communicator and Outlook Integration Issues.......................................................18 Client Sign-In, Discovery, and Presence.......................................................................................18 Office Communicator Sign-in and Discovery.............................................................................18 Understanding Client Automatic Configuration and DNS Discovery.......................................19 Communicator Mobile Sign-in and Discovery............................................................................22 Communicator Mobile and NTLM Authentication...................................................................22 Endpoint Registration.............................................................................................................23 Communicator Mobile and Cellular Networks........................................................................24 Connection Management.......................................................................................................25 Common Issues with Sign-in and Discovery..............................................................................26 3

Incorrect User Information......................................................................................................26 Sign-in Failures with Manual Configuration............................................................................27 Sign-in Failures with Automatic Configuration........................................................................27 External Users Unable to Sign In...........................................................................................29 Client Group Policy and Registry Settings....................................................................................30 Office Communications Server 2007 R2 CALs..........................................................................30 Office Communications Server 2007 R2 Standard Edition CAL.............................................30 Office Communications Server 2007 R2 Enterprise Edition CAL...........................................31 Server Settings and Client Behavior..........................................................................................32 In-Band Provisioning..................................................................................................................32 Group Policy for Unified Communications Clients.....................................................................35 How Group Policy Works........................................................................................................35 Adding Administrative Templates............................................................................................36 Communicator 2007 R2 Group Policy....................................................................................37 Communicator 2007 R2 Group Policy Precedence ............................................................37 Communicator 2007 R2 Group Policy Additions ................................................................37 Legacy Communicator Group Policies ...............................................................................38 Changed or Superseded Policies for Communicator 2007 R2............................................41 Obsolete Communicator 2007 R2 Group Policies...............................................................43 Live Meeting Group Policy.....................................................................................................44 Group Chat Group Policies....................................................................................................46 Registry Keys............................................................................................................................48 Live Meeting 2007 Registry Keys...........................................................................................48 Live Meeting Registry Keys that are Shared with Office Communicator................................51 Common Issues with GPO and Registry Settings.....................................................................52 Where to Find the Communicator.adm Template...................................................................52 Users are Always Prompted for Credentials...........................................................................53 Hyperlinks Are Not Working....................................................................................................53 Disabling Video and A/V Conferencing...................................................................................53 Disabling Communicator Calls...............................................................................................54 File Transfer is Not Working...................................................................................................54 Audio, Video, or Desktop Sharing Failures.............................................................................55 Integrating a Third-Party Collaboration Program with Communicator........................................56 Integrating an Internet-Based Collaboration Program with Communicator 2007 R2..............56 Integrating a Server-Based Collaboration Program with Communicator 2007 R2..................59 Communicator 2007 R2 Call Scenarios........................................................................................61 Standalone Communicator (TelephonyMode=1)........................................................................62 Co-existence of Office Communicator and PBX (TelephonyMode=2).......................................63 Dual forking (TelephonyMode=3)...............................................................................................64 Communicator Mobile Call Scenarios...........................................................................................65 Communicator Mobile Topology.................................................................................................65 Single-Number Reach...............................................................................................................66 Topology.................................................................................................................................66 Single-Number Reach Features.............................................................................................67 4

Server Roles...........................................................................................................................67 Incoming Calls...........................................................................................................................68 Diagnosing Microsoft RoundTable................................................................................................68 Diagnosing Microsoft RoundTable..........................................................................................68 Installing the Microsoft RoundTable Management Tool..............................................................69 Using RTManage.exe................................................................................................................69 Configuring the RoundTable Device..........................................................................................71 Common Configuration Tasks....................................................................................................79 Set the Time...........................................................................................................................79 Change the Display Language...............................................................................................79 Change the Time Zone...........................................................................................................80 Getting the Device's Current Configuration............................................................................80 Update the Firmware Images.................................................................................................80 Reset the Device to Factory Settings.....................................................................................81 Reset the Device Password...................................................................................................81 Upload the Diagnostics Logs..................................................................................................82 Interpreting the Diagnostics Logs..............................................................................................82 CE Logging Tasks..................................................................................................................82 Send the CE Log to the Update Service Server.....................................................................82 Interpret the CE Log...............................................................................................................82 Errata in the RoundTable CE log............................................................................................85 Diagnostics Logging...............................................................................................................85 Diagnostics Log Schema........................................................................................................85 Interpreting Diagnostics Logs.................................................................................................86 LoggingType == POST...........................................................................................................86 Logging Type == Health.........................................................................................................88 Logging Type == Image Update.............................................................................................90 Dr. Watson Logs........................................................................................................................91 Diagnosing Live Meeting 2007......................................................................................................91 Diagnosing Communicator Mobile................................................................................................93

Client Technical Reference

Depending on the size and complexity of a Microsoft Office Communications Server 2007 R2 organization, administrators must set, maintain, and manage various standard configurations for computers using the unified communications clients. Client computers at times must be configured for specific purposes ranging from limited to full use. These topics concentrate on common scenarios encountered when managing unified communications clients. Most enterprise networks that deploy Office Communications Server 2007 R2 also deploy Microsoft Office Communicator 2007 R2 and Microsoft Live Meeting 2007 clients to their desktops. Depending on the client access license (CAL) that an organization has purchased, there are varying degrees of client function available to users. The topics in this section outline how to manage the combination of unified communication clients in your organization so that you get the most from each client. In This Document Installation Methods Compatibility and Integration Client Sign-In, Discovery, and Presence Client Group Policy and Registry Settings Communicator 2007 R2 Call Scenarios Communicator Mobile Call Scenarios Diagnosing Microsoft RoundTable Diagnosing Live Meeting 2007 Diagnosing Communicator Mobile

Installation Methods
Depending on their preferred deployment method, IT departments may want to install clients using a logon script, which performs unattended installation of the client when users log on. Logon scripts can be distributed to users through a deployment system such as Active Directory Domain Services Group Policy or Systems Management Server (SMS). This section includes the following topics: Multiple Client Installation Script (OCInstall.wsf) Unattended Installation and Microsoft XML Core Services 6.0 (MSXML) Installing Communicator by using Group Policy

Multiple Client Installation Script (OCInstall.wsf)

The OCInstall.wsf script is an example of a logon script that installs Office Communicator, the Conferencing Add-in for Microsoft Office Outlook, and the Live Meeting client. This script configures users SIP URIs, the help desk URL, and branding. It also configures Outlook integration with Communicator, configures high security mode, and enables tracing for debugging. The OCInstall.wsf script is available in the Microsoft Office Communications Server 2007 R2 Resource Kit.

Unattended Installation and Microsoft XML Core Services 6.0 (MSXML)

Communicator 2007 R2 requires Microsoft XML Core Services 6.0 (MSXML6), which is an optional update through Microsoft Update or Windows Update. If MSXML6 is not installed on the computer, Communicator installation fails. During an attended installation, the user will see an error message that provides a link to the MSXML6 download page. However, during an unattended installation, users will not see this error message and installation will fail. If you plan to deploy Communicator by using an automated method, ensure that MSXML6 is also installed on the client computers. For more information about MSXML6, see Microsoft Knowledge Base article 934268, Description of Microsoft Core XML Services 6.0 Service Pack 1, at http://go.microsoft.com/fwlink/? linkid=147167. The Microsoft Core XML Services 6.0 Service Pack 1 download is available at http://go.microsoft.com/fwlink/?Linkid=144674.

Installing Communicator by using Group Policy

When you use Group Policy Software Installation to deploy Communicator in your organization, you should assign the software installation to the Computer Configuration container instead of the User Configuration container. Publishing from User Configuration results in a per-user installation. However, some Communicator installation files require a per-machine installation, so they will not install. An initialization error will occur the first time that a user runs Communicator. For more information, see the Microsoft Knowledge Base article 947379, Error message when you try to start Communicator 2007: The application failed to initialize properly (0xc0150002), at http://go.microsoft.com/fwlink/?linkid=147165.

Compatibility and Integration

This section covers the following topics: 7

 The ability of Office Communications Server 2007 R2 clients to coexist and interact with each other, and with earlier client versions. Office Communicator 2007 R2 compatibility with different versions of Office Communicator, Office, Exchange Server, Windows, and selected public instant messaging (IM) clients. Office Communicator 2007 R2 integration with Microsoft Office and Microsoft Exchange Server: how it works, and how to troubleshoot common integration issues. This section includes the following topics: Client Compatibility Communicator 2007 R2 Integration

Client Compatibility
This topic discusses the ability of Office Communications Server 2007 R2 clients to coexist and interact with clients from earlier versions of Office Communications Server. There are two types of client compatibility, as follows: Multiple points of presence (MPOP): the ability of a single user to sign in to an Office Communications Server 2007 R2 server with multiple clients Interoperability: the ability to interact with another user who is signed in using a different client type, or an earlier version of the same client This topic also discusses the compatibility of Office Communicator 2007 R2 with various versions of Microsoft Office, Exchange Server, Windows, and with selected public instant messaging clients.

Planning for Compatibility

During migration, users with Office Communicator 2007 installed can sign in to an Office Communications Server 2007 R2 server, and interact with Office Communicator 2007 R2 clients. However, they will not have access to the new Office Communications Server 2007 R2 features. To ensure that your organizations migration to the new Office Communications Server 2007 R2 clients goes smoothly, consult the following topics: Migration overview: Migration from Office Communications Server 2007 documentation and Migration from Live Communications Server 2005 documentation Client migration: Phase 10: Update Client Software in the Migration from Office Communications Server 2007 documentation and Phase 8: Update Client Software in the Migration from Live Communications Server 2005 documentation New features: Office Communicator Enhancements in the New Client Features documentation Note: To coexist and interact with Office Communications Server 2007 R2 clients, earlier client versions must have the most current updates installed. 8

Compatibility among Office Communications Server 2007 R2 Clients

All Office Communications Server 2007 R2 clients can interoperate with other Office Communications Server 2007 R2 clients. Most Office Communications Server 2007 R2 clients also support the multiple points of presence scenario, with the following exceptions: Office Communications Server 2007 R2 Attendant users cannot log on at the same time by using Office Communicator 2007 R2 Phone Edition, the 2007 R2 release of Communicator Mobile for Windows Mobile, and the 2007 R2 release of Microsoft Office Communicator Web Access. 2007 R2 release of Communicator Mobile for Windows Mobile users cannot be signed in on two mobile devices at the same time.

Multiple Points of Presence with Previous Client Versions

The following table describes which client versions are supported when a single user is signed in to an Office Communications Server 2007 R2 server at multiple locations.
Current Client Version Previous Client Versions Supported (with required updates)

Office Communicator 2007 R2

Office Communicator 2007 Office Communicator 2007 R2 Phone Edition 2007 release of Office Communicator Mobile

2007 R2 release of Office Communicator Mobile for Windows Mobile Office Communicator 2007 R2 Phone Edition Office Communications Server 2007 R2 Attendant

Office Communicator 2007 Office Communicator 2007 Phone Edition Office Communicator 2007 Office Communicator 2007

Interoperability with Previous Client Versions

The following table shows which client versions can interact with Communicator 2007 R2 on an Office Communications Server 2007 R2 server. Client Interoperability on Office Communications Server 2007 R2
Current Client Version Previous Client Versions Supported (with required updates)

Office Communicator 2007 R2

Office Communicator 2007 Office Communicator 2007 Phone Edition 9

Current Client Version

Previous Client Versions Supported (with required updates)

2007 release of Office Communicator Mobile 2007 release of Office Communicator Web Access Office Communicator 2005 (basic presence and IM only) 2007 R2 release of Office Communicator Web Access 2007 R2 release of Office Communicator Mobile for Windows Mobile Office Communicator 2007 R2 Phone Edition Supports interoperability with the same clients as Communicator 2007 R2, above Supports interoperability with the same clients as Office Communicator 2007 R2, above Office Communicator 2007 Office Communicator 2007 Phone Edition 2007 release of Office Communicator Web Access Office Communicator 2005 (basic presence and IM only) Office Communications Server 2007 R2 Attendant Supports interoperability with the same clients as Office Communicator 2007 R2 Phone Edition, above

Communicator 2007 R2 Compatibility

This section discusses the compatibility of Office Communicator 2007 R2 with various versions of Microsoft Office, Exchange Server, Windows, and selected public instant messaging clients.

Microsoft Office
The following table describes the Office Communicator 2007 R2 features that are supported by various versions of Microsoft Office. Communicator 2007 R2 and Microsoft Office compatibility
Microsoft Office Version Comments

Office 2000 Office XP SP3

Not supported Contacts No presence menuINFO line only

Office 2003 SP3

Access presence menu Make voice calls 10

Microsoft Office Version

Comments

Reply to IMs Search folders and notifications Office 2007 SP1 View presence button Access presence menu Reply with IM or conference Tagging Contextual data

Exchange Server
The following table describes Office Communicator 2007 R2 support for various versions of Exchange Server. Office Outlook must also be installed on the client computer to handle Extended MAPI calls. Communicator 2007 R2 and Exchange Server Compatibility
Exchange Server Version Communicator 2007 R2 Support

Exchange Server 5.5 Exchange 2000 Server Exchange Server 2003 Exchange Server 2007 SP1

Not supported Extended MAPI only Extended MAPI only Free/Busy information and working hours are available only through Exchange Web Services Public folders are optional in Exchange Server 2007

Windows
The following table describes Office Communicator 2007 R2 compatibility with various versions of Windows. Communicator 2007 R2 and Windows compatibility
Windows Version Communicator 2007 R2 Support

Windows Vista 32-bit operating system Windows Vista 64-bit operating system Windows XP Professional with Service Pack 2 (SP2) or greater

Supported Supported in Windows on Windows 64 mode Supported

11

Windows Version

Communicator 2007 R2 Support

Windows 2003 Server SP2 or greater Windows 2000 SP4

Supported Not supported

Public Instant Messaging Clients

Communicator 2007 R2 supports IM and basic presence when communicating with the following public instant messaging clients: Windows Live AIM Yahoo! Messenger for Mac 7

Presence states are filtered to those supported by the public IM client.

Communicator 2007 R2 Integration

Integrating Office Communicator 2007 R2 and Microsoft Office 2007 Suites provides Microsoft Office users with in-context access to the instant messaging (IM), enhanced presence, telephony, and conferencing capabilities of Office Communicator. Microsoft Office Outlook 2007 users can view a record of Office Communicator 2007 R2 conversations in the Office Outlook 2007 Conversation History folder. Additionally, users can view the availability of contacts and access the messaging capabilities of Communicator and Outlook from an Office Word or Office Excel document with smart tags enabled, or from a Microsoft Office SharePoint Server page. The following figure shows how the enhanced presence button and its associated menu appear in an Outlook 2007 e-mail message.

12

The following topics are discussed in this section: Planning for integration between Communicator 2007 R2, and Outlook 2007 and other Microsoft Office applications Exchange Server interfaces that are used by Communicator 2007 R2 and Outlook 2007 to access and update shared information Group policies that can used to control the level of Communicator 2007 R2 integration Communicator integration with Office SharePoint Server, Office Word, and Office Excel Suggestions for preventing common Communicator integration issues

Planning for Communicator 2007 R2 Integration

Review the following configuration issues to ensure that you have everything required for integration between Communicator and other Microsoft Office applications: Configure integration between Office Communications Server and Exchange Server. For more information, see http://go.microsoft.com/fwlink/?LinkId=147178. Review the integration features which can be configured during Communicator 2007 deployment by using group policies. See Controlling Integration later in this topic. Deploy the Conferencing Add-in for Microsoft Office Outlook. For more information, see http://go.microsoft.com/fwlink/?linkid=146038. In organizations with multiple versions of Communicator or Microsoft Office installed, review the compatibility tables in Client Compatibility. Review the list of suggestions for preventing common integration errors in Common Communicator and Outlook Integration Issues later in this topic. 13

Integration and Exchange 2007

To support Communicator 2007 R2 integration, both Communicator 2007 R2 and Outlook 2007 read and write information directly to the Exchange 2007 server. This section discusses the Exchange Server interfaces used by Communicator and Outlook. To display information about a contact in an e-mail message, Outlook first looks for the contacts SIP address locally, and then makes an RPC call to the Exchange 2007 server if required. During a single Outlook 2007 session, the number of RPC calls decreases as more SIP addresses are cached. In Communicator 2007 R2, integration features that use either MAPI or Exchange Web Services calls directly to the Exchange 2007 server are as follows: Note: Outlook 2007 makes RPC calls to resolve SIP addresses only if the Display online status next to a person name option is selected. To view this option in Outlook 2007: from the Tools menu, select Options, select Other, and then look under Person Names. Access Conversation History and missed calls Play back voice mail message Display Free/Busy information and working hours Display meeting subject, time, and location Display Out of Office status and note

Exchange 2007 Communication Interfaces

The following table describes the communication interfaces used by Communicator 2007 R2 to access and update features shared with Outlook 2007. Exchange 2007 communication interfaces used by Communicator 2007 R2
Communication Interface Function

Outlook Object Model

Send E-mail message Schedule Meeting Receive seed information for EWS Open voice mail folder Open Missed Conversation folder Find Previous Conversations

MAPI

Create Conversation History folder Write Call Logs Write Missed Calls Read Contact Information Voice mail Notifications Missed Conversation Notifications 14

Communication Interface

Function

Exchange Web Service

Read My Free Busy Time and Office Hours Read My Out of Office note

Publishing Free Busy Information

A Communicator 2007 R2 user cannot access another users availability and schedule directly, so Free/Busy and Out of Office details are published as part of a contacts extended presence information. This works as follows: 1. On User As computer, Communicator 2007 R2 uses Exchange Web Services calls to determine the users own Free/Busy and Out of Office status. 2. Communicator 2007 R2 then updates User As enhanced presence data with this information. 3. Other Communicator 2007 R2 and Office 2007 users can now view User As schedule details and Out of Office status, if applicable. The availability of Free/Busy and Out of Office information about a contact is also controlled by a users Access Level settings. For more information about presence and access levels, see http://go.microsoft.com/fwlink/?linkid=147177. Note: Free/Busy times and Out of Office information are obtained through MAPIrather than through EWS for client-server combinations other than Communicator 2007 R2 and Exchange 2007.

Controlling Integration
All the Outlook 2007 integration features are enabled by default, but can be controlled individually from within Communicator 2007 R2 or through Group Policy settings. By default, users can control which integration options are set using the Office Communicator 2007 R2 dialog box shown in the following figure.

15

The following table lists the registry settings that administrators can use to enable or disable individual integration features, either during deployment, or later as part of a maintenance or upgrade cycle. For more information on Communicator 2007 R2 Group Policies, see http://go.microsoft.com/fwlink/?Linkid=146075. Outlook integration options registry settings
Policy Description

CallLogAutoArchivingPolicy

Enables or disables saving of call logs. When this policy is present, the corresponding Options dialog box setting is unavailable. Disables the loading of free or busy data from Outlook 2007. Prevents Communicator from displaying Outlook 2007 information about free or busy states to other contacts. Prevents Communicator from publishing the subject and location information of a meeting. This value is not used if 16

DisableCalendarPresence DisableFreeBusyInfo

DisableMeetingSubjectAndLocation

Policy

Description

DisableCalendarPresence is set, or if the Update my status based on calendar data option on the Personal tab is not set. DisablePresenceNote Prevents users from selecting or clearing the check box labeled Automatically retrieve Out of Office settings from Outlook on the Personal tab of the Options dialog box. Prevents Communicator from saving instant messages. Enables or disables saving of instant messages. When this policy is present, the corresponding Options dialog box setting is unavailable.

DisableSavingIM IMAutoArchivingPolicy

Integration with Office SharePoint Server, Office Word, and Office Excel
As soon as you have successfully configured integration between Communicator and Outlook, users of Office SharePoint Server, Office Word, and Office Excel can also view extended presence information about a contact, and access the combined messaging capabilities of Communicator and Outlook.

Office SharePoint Server

In both Windows SharePoint Services and Office SharePoint Server, users must have Office 2003 or Office 2007 installed to view extended presence. To display the presence button and menu, SharePoint uses a Microsoft Office ActiveX control called name.dll. The ActiveX control makes calls directly to the Office Communicator API, and then Communicator makes MAPI or Exchange callsif requiredto supply the requested information. For more information about how presence is displayed in an Office SharePoint Server page, see this SharePoint developer blog entry on the Microsoft Developer Network (MSDN) at http://go.microsoft.com/fwlink/?LinkId=147181.

Word and Excel

For the presence button and menu to appear next to (or above) a contacts name in Word or Excel, smart tags must be enabled.

17

For instructions on how to enable smart tags from within Word or Excel, see the following Microsoft Knowledge Base article 300950, How to troubleshoot custom Smart Tags in Office, at http://go.microsoft.com/fwlink/?LinkId=147183. For information about how to do large-scale customization of end-user settings in your organization by using Office 2007 group policies, see the Office 2007 Resource Kit at http://go.microsoft.com/fwlink/?LinkId=147185.

Common Communicator and Outlook Integration Issues

This section lists some common configuration issues which might prevent Office Communicator integration with Outlook from working as expected. In organizations with both Office 2003 and Office 2007 installed, ensure that you have deployed the most current version of the Office 2003 and Office 2007 Compatibility Pack. For more information, see http://go.microsoft.com/fwlink/?LinkId=147186. Check that end-user integration settings in both Outlook and Communicatornormally enabled by default when Communicator is installedare correctly set: In Outlook, ensure that the Display online status next to a person name option is selected. To view this option in Outlook 2007: From the Tools menu, select Options, select Other, and then look under Person Names. In Communicator, ensure that Microsoft Office Outlook is selected under Personal information manager on the Personal options page. To view this option in Communicator 2007 R2: On the Presence menu, click Options. The Personal options page is displayed. For other configuration issues to consider, see Common Issues with Sign-in and Discovery and Common Issues with GPO and Registry Settings.

Client Sign-In, Discovery, and Presence

This section describes how clients determine the Office Communications Server 2007 R2 server or pool they should sign in to and the processes that they use for signing in. This section includes the following topics: Office Communicator Sign-in and Discovery Communicator Mobile Sign-in and Discovery Common Issues with Sign-in and Discovery

Office Communicator Sign-in and Discovery

Office Communicator must determine which server it should log on to by using the users URI (for example, jeremy@contoso.com) and any manual settings configured on the client. If manual

18

settings were provided, the server to use is clear. However, if the URI was the only indicator provided, some discovery is required. Communicator discovery varies based on configuration. After the client discovers the server to connect to, it tries to connect by using TCP or TLS over TCP. If TLS is used, the server provides a certificate to authenticate itself to the client. The client must validate the certificate before it continues. The client might negotiate compression (if using TLS over TCP), and then it initiates a SIP registration. Next, the client sends a SIP REGISTER message to the server without any credentials. This prompts Office Communications Server to challenge for user credentials, and specifies to the Communicator client the authentication protocols that it accepts. When it comes to providing credentials, Communicator has two options. Communicator can use the users current Windows credentials to log on, or it can prompt the user for credentials. Note: The credentials manager in Windows can also be used to manage credentials. More information about the credentials manager is in the Microsoft TechNet article Windows XP Resource Kit: Understanding Logon and Authentication at http://go.microsoft.com/fwlink/? Linkid=133674, in the Stored User Names and Passwords section. Authentication failures can occur during the first part of logon processing. This can occur when credentials are not already saved or when the desktop credentials do not match the account that Communicator is trying to use. This can also occur when the SIP URI, account name, or password is typed incorrectly or when credentials and the SIP URI do not match. An example of this is if Jeremy tries to log on with the URI sip:jeremy@contoso.com, but he uses the user account and password for CONTOSO\vadim instead of the account owners own credentials, CONTOSO\jeremy.

Understanding Client Automatic Configuration and DNS Discovery

For organizations that plan to use automatic configuration, one of the requirements during server deployment is to create an internal DNS SRV record that maps one of the following records to the fully qualified domain name (FQDN) of the Enterprise pool or Standard Edition server that handles client sign-in requests: _sipinternaltls._tcp.<domain> (for internal TLS connections) _sipinternal._tcp. <domain> (for internal TCP connections, performed only if TCP is allowed) When the client is set to use automatic configuration, it uses the SIP URI that is provided by the user to discover which server it should sign in to. Communicator does this by using DNS SRV records published for the domain part of the SIP URI. For example, if the user enters a URI of sip:jeremy@contoso.com, Communicator uses contoso.com to discover a SIP server that uses DNS. Communicator looks for the following SRV records in its search for an appropriate server: _sipinternaltls._tcp.contoso.com 19

_sipinternal._tcp.contoso.com _sip._tls.contoso.com sipinternal.contoso.com sipexternal.contoso.com

If these records do not exist, Communicator queries for host (A) records:

The first query looks for an internal server in the contoso.com domain that offers ports supporting TLS over TCP for clients. The second query seeks to discover an internal server in the contoso.com domain that offers TCP ports for clients. Finally, the third query looks for an Internetreachable server for the contoso.com domain that offers ports supporting TLS over TCP for clients. Communicator never looks for an Internet-reachable server that supports TCP, because use of clear-text SIP on the Internet does not make sense from a security standpoint. In other words, Communicator is not aware whether the network that is being used is internal or external. Communicator queries for all DNS SRV records. However, it tries TLS over TCP connections first. TLS over TCP is forced through an Edge Server (no option to allow for unsecured TCP connections). Finally, if all the DNS SRV records do not exist (not if they are not valid; only if they do not exist at all), the client falls back to sipinternal.<URI domain> and tries to resolve that host name. If the host name resolves to an IP address, Communicator tries to connect by using TLS over TCP, TCP, or both, depending on what the policy allows for. If this fails, it will try one last time with sipexternal.<URI domain>. Communicator policies can be put in place to prevent TCP from being used, and this prevents the second query from being issued. The EnableStrictDNSNaming policy can also be specified, which requires strict names for the computers discovered. In this case, Communicator is allowed to connect to servers only if the name is a match with the domain in the domain part of the users SIP URI or if the FQDN is sip.<URI domain>. If this policy is not enabled, any server name of the form <servername>.<URI domain> is allowed. As an example, for sip:jeremy@contoso.com, the host sip.contoso.com is always allowed (strict policy or not). Server77.contoso.com, sipfed.contoso.com, and ap.contoso.com are all also allowed if strict naming policy is not enabled. The following server names are never allowed because they do not tightly fit the domain that the users URI specified. Therefore, the client does not trust these servers as valid logon points: sip.eng.contoso.com, sip.contoso.net, sip.com, sip.contoso.com.cpandl.com, and so on. This tight validation between the host name and the URI is done specifically because the only configuration with which the client is provided is the SIP URI. Because of this, the client must be very careful not to allow DNS attacks to allow it to connect to any man-in-the-middle, who could thereby watch Communicators traffic. By having a tight tie between the URI and the host names allowed for logon, Communicator has better certainty that the certificate the user is validating actually has authority for the domain to which he is trying to log on to. After the host name is identified, Communicator also resolves the host name to an IP address. This usually occurs as the result of the DNS SRV request, but until the IP address is resolved, Communicator cannot connect. This can be a problem during logon also. The latest version of Communicator enables the ability to manually specify both an internal and external server to log on against. Communicator always attempts to connect to the internal server 20

if it is available, but it falls back to the external server. Previously, Communicator had only a single manual entry, which created problems for mobile workers. With the ability to specify an internal and external server, it is now easier for administrators to configure and enable laptop configurations that work across internal and external networks. This increased functionality is also important for companies where the domain in the users URI differs from their SIP enterprise servers domain. Because the administrator can configure Communicator (on a laptop, for example) once, the user does not need to remember the internal or external servers and administrators do not have to publish DNS SRV records for all the domains they want to support for remote access users. The Office Communicator client enables the user to automatically connect to the appropriate Office Communications Server without actually putting in the server name. Regardless of whether the client is inside the internal network or is working externally, this feature redirects the client and allows it to authenticate and connect to its own Office Communications Server (in the case of Standard Edition) or home pool (in the case of Enterprise Edition). This feature has a significant DNS dependency. For this to work successfully, the appropriate SRV records should be published both internally and externally. When the Office Communicator client first starts and the user tries to connect, Office Communicator always tries to connect to the server or home pool in its same domain, or by using the same SIP URI as in the sign-in address. For example, if the sign-in name that is used is kim.akers@fabrikam.com, Office Communicator looks for the home pool or Office Communications Server in the same DNS namespace, which is fabrikam.com. This process is made easier by the usage of DNS SRV records, which ultimately points the client to the FQDN of the home pool or server in the correct domain. The process works the same whether the client is in an internal or external network. The client starts querying SRV records and, by default, it always tries to use TLS for authentication. If TLS fails, then and only then will it fall back to Transmission Control Protocol (TCP). _sipinternaltls._tcp.fabrikam.com _sipinternal._tcp.fabrikam.com

Either of these first two DNS records should be published and available in the internal DNS namespace. So, if by now the client gets the host name back, it directly connects to the home pool or the Office Communications Server. Or else, it continues its query process, knowing that it is currently not in the internal network. _sip._tls.fabrikam.com _sip._tcp.fabrikam.com

If either of these queries is a success, the client is redirected to the external edge of Access Edge Server and subsequently to the internal home pool or the Office Communications Server. However, if it still fails, in a final attempt it tries to look up the host records directly as in the following two examples. If this attempt to configure its settings automatically fails, the Office Communicator will fail and require manual intervention. sip.fabrikam.com sipinternal.fabrikam.com 21

Communicator Mobile Sign-in and Discovery

Communicator Mobile and NTLM Authentication
Sign-in for Communicator Mobile is similar to the sign-in process for Office Communicator that was previously discussed in the section Office Communicator Sign-in and Discovery . Communicator Mobile supports NTLM authentication, which is the default Security Support Provider (SSP) on the Windows Mobile version 6.x platform. However, Office Communicator supports both Kerberos and NTLM authentication. The Kerberos protocol is also the default SSP on the Windows platform. Windows Mobile version 6.x users can install the Kerberos SSP, but Communicator Mobile cannot use it. Figure 1 shows the NTLM protocol messages exchanged by Communicator Mobile and the Office Communications Server 2007 R2. Communicator Mobile sends a SIP REGISTER message. The server responds with an NTLM authentication challenge. Communicator Mobile now knows what server it needs to authenticate against. Communicator Mobile responds to the authentication challenge with another anonymous SIP REGISTER, but this time it specifies that it wants to use NTLM. This prompts the server to generate a true NTLM challenge. Communicator Mobile responds with the credentials. The server can now verify the user and process the SIP REGISTER request.

22

Communicator Mobile NTLM authentication

Endpoint Registration
Communicator Mobile must register with the Office Communications Server infrastructure as a unified communications (UC) endpoint. However, it must indicate that it is a mobile endpoint. RFC 3840 allows for the mobility=mobile parameter during registration. The following diagram shows the call flow required to register a mobile endpoint.

23

Communicator Mobile endpoint registration

Communicator Mobile and Cellular Networks

Communicator Mobile clients connect to an internal server or to an Access Edge server based on the network from which the device is connecting. For cellular networks, there are three main categories: 3G This network enables Data and Voice connections simultaneously. Communicator Mobile requires a DTM phone with 3G networking to support simultaneous Data and Voice connections 2.5G This network enables Data and Voice connections but not simultaneously. 2G Voice-only network connection type

Each mobile operating system has its own set of capabilities, which is represented in the following table. D and V represent data and voice capabilities.
OS/Client DTM STM

Windows Mobile Symbian J2ME (Java 2 Platform Micro Edition) Note:

D and V D and V D or V

D or V D or V D or V

The J2ME client does not allow simultaneous data and voice connections, even in the DTM environment. 24

Dual Transfer Mode (DTM) devices can do simultaneous voice and data connections. Most Communicator Mobile users have DTM devices. Single Transfer Mode (STM) devices alternate voice and data connections. Upon receiving a circuit switched call, these devices lose their data channel. Although Communicator Mobile supports STM devices, the data connections are dropped and are re-established when the circuit switched call has ended if Automatically sign me in is enabled.

Connection Management
Communicator Mobile uses the Windows Mobile 6.0 Connection Manager API for connection management functionality. Using the API, Communicator Mobile does the following tasks and activities: Gives priority when connecting to cellular connections such as General Packet Radio Source (GPRS) over other connections (for example, Wi-Fi, ActiveSync) Provides improved sign-in availability Reduces the frequency of signing in to and out of the application Reacquires the data connection when the connection drops unexpectedly

Changes the priority of the data connection to Low (CONNMGR_PRIORITY_USERBACKGROUND) when the application moves to the background, and to High (CONNMGR_PRIORITY_USERINTERACTIVE) when a user is interacting with the device or the application has moved to the foreground Show relevant errors when there is a data connection loss (for example, FLIGHT_MODE or SUSPENDED/RESUME) The following table provides details about Connection Manager sign-in errors.
Error Code Error Details

CONNMGR_STATUS_CONNECTIONLINKFAILED(0x2A) CONNMGR_STATUS_CONNECTIONFAILED(0x21) CONNMGR_STATUS_EXCLUSIVECONFLICT(0x28)

The connection is prematurely disconnected. Using an ActiveSync connection and the cable is disconnected. The connection could not be established because an exclusive connection exists. Connection settings are not available. User stops the connection or changes modes. The device is out of radio range or is not plugged into its cradle. The selected path to the requested 25

CONNMGR_STATUS_NOPATHTODESTINATION(0x24) CONNMGR_STATUS_CONNECTIONCANCELED(0x22) CONNMGR_STATUS_WAITINGFORPATH(0x25) CONNMGR_STATUS_PHONEOFF(0x27)

Error Code

Error Details

destination network is turned off. CONNMGR_STATUS_WAITINGFORPHONE(0x26) A voice call is in progress and is using resources that are required by this connection. The connection request did not connect because of an authentication failure. A connection path has requested a property, such as WAKE_ON_INCOMING, that is not available. Cannot connect to the network. Cannot connect to the network. Check your connection settings. Cannot connect to the network. Check your connection settings.

CONNMGR_STATUS_AUTHENTICATIONFAILED(0x2B)

CONNMGR_STATUS_NOPATHWITHPROPERTY(0x2C)

CONNMGR_STATUS_UNKNOWN( 0X00) CONNMGR_STATUS_WAITINGFORRESOURCE CONNMGR_STATUS_WAITINGFORNETWORK

Common Issues with Sign-in and Discovery

When troubleshooting issues with sign-in, one of the first things to determine is whether the user is entering the correct information. Next, ensure that the users account is an active account that is enabled for Office Communications Server. If the user information is not an issue, investigate the server-side configuration. When investigating sign-in from the server side, first determine whether the client connection settings are set to automatic configuration or manual configuration. This section describes some common issues encountered during sign-in from both the user and server perspective.

Incorrect User Information

The following scenarios illustrate some common sign-in issues related to the users account or the information that the user is trying to use during sign in. Incorrect Sign-In Address When attempting to sign in to Communicator, a user may see the message, Cannot sign in to Communicator. You may have entered your sign-in address, user name, or password incorrectly, or the authentication service may be incompatible with the version of the program. Frequently, the user is trying to sign in with a sign-in address that does not match the SIP URI that is specified in the users Active Directory properties. The format for the SIP URI is determined by the administrator when enabling users for Office Communications Server. The SIP URL can be generated from the users e-mail address, user principal name, full name, or Security Accounts 26

Manager (SAM) account (the logon name used in older versions of the Windows operating system). The user should try to sign in again by using the correct SIP URI format. User Account Not Enabled for Office Communications Server If the user is entering the correct SIP URI format and sign-in continues to fail, the network administrator should verify that the user account is enabled, that the user is enabled for Office Communications Server, and that the password for the account hasn't expired or been reset. For information about how to enable user accounts, see Managing User Accounts in the Administering Office Communications Server 2007 R2 documentation. User Does Not Have Permissions on Profile Folder If an individual user receives an error saying that the server is unavailable, turn on Windows event logging for Communicator and check the Windows event trace log. The logs may show an access denied error while creating the Communicator folder under C:\Documents and Settings\<user name>\Local Settings\Application Data\Microsoft. To resolve this issue, you can give the user the appropriate rights on the Communicator folder.

Sign-in Failures with Manual Configuration

With manual configuration, sign-in issues usually stem from incorrect server name entries in the Advanced Connection Settings on the client. In the Event Viewer for the client, you may see Communicator failed to connect to server 192.168.0.2 (192.168.0.2) on port 5060 due to error 10061, which references the IP address of a server to which the client could not connect. Or, you will see references stating that the server presented by the server did not match the expected host name. Often these errors occur because a server IP address is entered in the clients Advanced Connection Settings dialog box. Instead of entering the server IP address or a NetBIOS name in the Advanced Connection Settings, enter the servers FQDN. When using manual configuration in connection settings, you also need to know whether TLS is required for connections between clients and Office Communications Server. If TLS is required, the TLS option must be selected in the Advanced Connection Settings, and the servers FQDN must be specified (instead of the server IP address or NetBIOS name) so that server name matches the certificates that are in place. If connections to the server use TCP, ensure that the Office Communications Server pool properties are set to the TCP listening port 5060.

Sign-in Failures with Automatic Configuration

With automatic configuration, there may be issues with DNS configuration, certificates, or server naming. DNS Configuration If you are using automatic configuration, make sure that the published server name in DNS is supported by the server certificate. For information about required creation of DNS records that enable discovery of clients and servers, as well as support for automatic client sign-in (if your organization wants to support it), see the Microsoft Office Communications Server 2007 R2 27

article, Domain Name System (DNS) Requirements, at http://go.microsoft.com/fwlink/? linkid=146936. When clients are configured to sign in automatically, make sure that the appropriate DNS SRV record exists. When using a TLS connection, add the following SRV record and map it to the host record of the server: _sipinternaltls._tcp.<domain> over port 5061. Note: If the SIP domain differs from the Office Communications Server domain, we recommend that you create a host record sip.<domain> instead of the Office Communications Server host record. When using a TCP connection, add the following SRV record and map it to the host record of the server: _sipinternal._tcp.<domain> over port 5060 Strict Name Checking If clients use automatic configuration to sign in and TLS is required, connection failures can sometimes be traced to the EnableStrictDNSNaming policy setting. When Communicator is configured for automatic connection and TLS is enforced, this policy enables Office Communicator to send and receive instant messages securely when using the SIP Communications Service. This policy does not affect Windows .NET or Microsoft Exchange Server services. Much of the confusion surrounding the EnableStrictDNSNaming policy stems from unclear policy description. Setting this policy incorrectly can cause unexpected problems with TLS negotiation and client sign-in. The correct explanation for this policy is as follows. If you set the EnableStrictDNSNaming policy to Enabled, Communicator clients can only connect to a server if its name matches the users SIP URI domain, or if its FQDN is sip.<URI domain>. For example, if the users SIP URI is someone@contoso.com, Communicator will be able to connect only to the following servers: contoso.com sip.contoso.com

If you do not configure this policy or you set it to Disabled, Communicator clients can communicate with any SIP server that has an FQDN that ends with the domain part of the user's SIP URI. For example, Communicator will be able to communicate with servers named sip.division.contoso.com or lc.contoso.com. The downside is that an attacker can respond to the initial DNS query with a server name such as attacker.contoso.com. By not configuring this policy or disabling it, you may be more open to man-in-the-middle attacks. One reason for not enabling this policy is if your organization has multiple subdomains and, when setting up certificates, you need the flexibility of allowing non-strict server names. To enable this policy, make sure that your SIP servers FQDN matches one of the strict naming formats.

28

Note: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence.

External Users Unable to Sign In

If internal users can sign in but external users are encountering issues, there may be an issue with the way authentication protocols are configured, the ports specified during sign-in, or serverside encryption settings. Set the Authentication Protocol to Both NTLM and Kerberos Office Communications Server 2007 R2 uses Kerberos or NTLM authentication protocols, depending on the location of the user. Kerberos protocol, which requires client connectivity to Active Directory, is used for internal users with Active Directory credentials. External users who have Active Directory credentials but who are connecting from outside the corporate firewall use NTLM. If external users cannot authenticate, ensure that the authentication protocol in the Office Communications Server front-end server properties is set to Both NTLM and Kerberos. Client Manual Sign-In on 5061, Access Edge Listening on 443 Clients that connect from outside the corporate firewall use port 443 for SIP communications with Edge servers. Sometimes clients are configured to connect to the server by using manual configuration, but external server is configured with the incorrect port. For example, if a client is manually configured to connect to a server on port 5061 while Access Edge Server is listening on port 443, the connection will fail. Check the clients Advanced Connection Settings under External Server Name or IP Address, and ensure that the entry specifies port 443, for example sip.domain.com:443. Also, specify port 443 if you use Group Policy to specify the external server name, Mismatch between NTLMMINCLIENTSEC and NTLMMINSERVERSEC Organizations may use local policies and group policies to configure specific security settings in Windows Server domains to help tighten security. One such setting is the NTLMv2 authentication setting, which can be configured to require encryption on communication between servers and clients. If the settings on the client side and the server side do not match, communication cannot be established. The settings are for NTLMv2 authentication are located in registry as follows: HKey_Local_Machine\System\CurrentControlSet\Control\Lsa\MSV1_0ntlmminclientsec HKey_Local_Machine\System\CurrentControlSet\Control\Lsa\MSV1_ ntlmminserversec Sometimes the server will be configured to require encryption, and the client will not. In this case, the client NTLM request is not passed on by the front-end server. This situation primarily affects external users, because NTLM is the only authentication protocol that external clients can use to sign in. For example, if the server key is configured to have a value of 0x20080030, which specifies 128-bit encryption, and clients are not, clients will be unable to sign in. You should ensure that this key on the client is configured to match the servers setting. 29

For more information, see Microsoft Knowledge Base article 823659, Client, service, and program incompatibilities that may occur when you modify security settings and user rights assignments, at http://go.microsoft.com/fwlink/?linkid=147230.

Client Group Policy and Registry Settings

In addition to deploying specific server roles, you might also be required to enable voice or conferencing features by using in-band provisioning, setting up Group Policy, or updating client registry keys. The settings you can configure depend on the type of client access license (CAL) you have. This section discusses the CALs that are available with Office Communications Server. It also describes the effect of server settings on clients and discusses how to configure and manage client settings through in-band provisioning, Group Policy, and registry settings. This section includes the following topics: Office Communications Server 2007 R2 CALs Server Settings and Client Behavior In-Band Provisioning Group Policy for Unified Communications Clients Registry Keys Common Issues with GPO and Registry Settings Integrating a Third-Party Collaboration Program with Communicator

Office Communications Server 2007 R2 CALs

Office Communications Server 2007 R2 offers both a Standard Edition CAL and an Enterprise Edition CAL.

Office Communications Server 2007 R2 Standard Edition CAL

Standard Edition provides all IM, presence, and conferencing components, including data storage, on a single computer. Standard Edition call features include the following: Basic computer-to-computer calling: Place, accept, hold, retrieve, and end calls. Able to accept conference invites, but unable to set up conferences.

Because a Standard Edition server represents a single point of failure, we do not recommend it for mission-critical deployments where high availability is essential. For such deployments, Enterprise Edition is the required choice.

30

Office Communications Server 2007 R2 Enterprise Edition CAL

The architecture of Office Communications Server 2007 R2 Enterprise Edition reduces single points of failure through the use of multiple Enterprise Edition servers and a dedicated Back-End Database server. Enterprise Edition call features include the following: All Standard Edition call features. Advanced call features: transfer, deflect, and forward calls. Support for telephony device. Permits scheduling and initiation of multi-party conferences.

Remote call control (RCC), first made available as a part of Live Communications Server 2005, continues to be supported with Office Communications Server 2007 R2. RCC allows Office Communicator 2007 R2 to control a user's PBX phone line and indicate their presence based on the status of their phone. Users can answer their PBX phone with Office Communicator 2007 R2 and update their presence to "In a Call." The following table summarizes these settings. For more information about Group Policy, see Group Policy for Unified Communications Clients. For more information about meeting policies, see Configuring Meeting Policies in the Administering Office Communications Server 2007 R2 documentation. Group Policies for telephony
License Type Server Setting Group Policy Setting

Standard (Basic computer-to-computer calling Voice (also called Standard with Voice)

None (TelephonyMode 0)

Not present, or TelephonyMode 0

TelephonyMode 1, 2, or 3 1. Enterprise voice 2. RCC and computer-tocomputer calling 3. Enables both RCC and Enterprise Voice

TelephonyMode 1, 2, 3, 4, or 5 1. Enterprise voice 2. RCC and computer-tocomputer calling 3. Enables both RCC and Enterprise Voice 4. RCC, no computer-tocomputer calling 5. No audio, only IM and presence available

Enterprise

In the Meeting section of Global Policies:* EnableIPAudio = True EnableIPVideo = True EnableDataCollaboration = True

DisableAVConferencing = 0 DisableDataConferencing = 0

Enterprise with Voice

Settings in both the Voice and

Settings in both the Voice and 31

License Type

Server Setting

Group Policy Setting

Enterprise rows above

Enterprise rows above

* Using the Office Communications Server 2007 R2 Administrative Tools snap-in The following table summarizes the set of functions for each telephony mode.

Function based on Group Policy telephony mode

Function Mode 0 Mode 1 Mode 2 Mode 3 Mode 4 Mode 5

Computer-tocomputer Computer-tophone RCC Forking UC forwarding Handset phone Basic VoIP Advanced VoIP Feature

x x

x x x

x x x x x

x x x x x x x

x* x x x

*When RCC is not present

Server Settings and Client Behavior

Many server settings have a direct effect on the features and functionality available to clients, as well as other aspects of the user experience. For a complete table that describes the effect of server settings on Office Communicator, Live Meeting, and Office Communications Server 2007 R2 Attendant, see How Server Settings Affect Client Functionality in the Administering Office Communications Server 2007 R2 documentation.

In-Band Provisioning
During sign-in, a client uses the methods described in the section Client Sign-In, Discovery, and Presence to determine which server it should sign in to. When the sign-in process begins, the client receives bootstrapping information that specifies the default servers and security mode that the client should use until sign-in is completed.

32

After the client is signed in, it receives settings from the server pool through in-band provisioning. Specific settings that have been configured in the Office Communications Server properties are propagated to the client during this process. For example, Office Communicator clients receive server locations, security information, and settings related to specific client features during in-band provisioning. Office Communicator Phone Edition devices receive the list of supported location profiles and pool-level defaults through in-band provisioning. The following table outlines the settings that are sent to Office Communicator clients during inband provisioning and the location where these settings are configured on the server.

Office Communicator in-band provisioning settings

Settings sent through in-band provisioning Location in server properties

Internal and external URLs for the Address Book Server and Web Service for Distribution Group expansion. Location of the Media Relay Access server SIP high security mode

In the pool properties, Web Component Properties, Address Book tab, Internal URL and External URL In the forest properties, Global Properties, Edge Servers tab, under A/V Edge Servers. In the pool properties, Front End Properties, Voice tab, in the Advanced Voice Options page (after Advanced Options, click Configure), under SIP security mode. Voice license: In the users Active Directory properties, Communications tab, Telephony options. Enterprise license: In the forest properties, Global Settings, Meetings, Global Policies Enterprise with Voice license: Both of the above settings In the forest properties, Global Properties, Meetings, Global Policies In the forest properties, Voice Properties, Policy tab, edit the policy and select or clear Allow simultaneous ringing of phones Pool Properties, Media Tab, under Security Settings, Encryption Level In the forest properties, Voice Properties, Location tab 33

Telephony Mode, which determines whether enterprise and voice telephony features, remote call control, computer-to-computer calling, are enabled

Audio/video conferencing and data conferencing, Simultaneous ringing

Whether encryption is supported or required when making and receiving audio and video calls Default location context for phone calls

Settings sent through in-band provisioning

Location in server properties

Line information for the UC phone line

In the users Active Directory properties, Communications tab, Telephony options, Line URI.

For Office Communicator, an advantage of using in-band provisioning is that information critical to client functionality is stored on the server and not on the computer, enabling a user to sign in from any computer that is running Office Communicator. In-band provisioning simplifies applying policies and server settings across the organization because the settings apply to all clients that sign in to the server pool. However, some organizations may have to apply distinct settings and policies to different groups within the organization. Administrators can achieve this greater level of detail by using Group Policy to apply separate client settings to different Active Directory groups, as described in the next section, Group Policy for Unified Communications Clients. Note: Office Communicator Phone Edition clients receive all settings from the server through inband provisioning and are not configurable through registry-based Group Policy. Some application layer settings are common between Office Communicator and Office Communicator Phone Edition. Because Office Communicator Phone Edition has no Group Policy mechanism, certain application layer settings that were previously controlled only through Group Policy have moved in-band in the Office Communications Server 2007 R2 release. This move was made so that Phone Edition clients could receive these settings through in-band provisioning. However, before you remove any group policies because the settings have moved in-band, you should consider the effect on Communicator clients. The affected settings are as follows: Portrange (Specify dynamic port ranges) and the Enabled, MaxMediaPort, and MinMediaPort subkeys EnableTracing (Turn on tracing for Communicator) EnableSIPHighSecurityMode (Configure SIP security mode)

Of these settings, the SIP Security Mode setting is used during the bootstrapping process to specify whether TLS is required. If your organization has required a TLS connection between clients and servers in earlier versions of Office Communications Server, you have probably already set the Group Policy for SIP Security Mode. Even though the setting has moved in-band for Office Communications Server 2007 R2, you should keep the SIP Security Mode Group Policy because it is still used during bootstrapping, before the client can receive settings through in-band provisioning. Maintaining the SIP Security Mode policy helps to retain security during the bootstrapping process.

34

Group Policy for Unified Communications Clients

Certain features and behaviors that are available to Office Communications Server 2007 R2 clients are determined by registry settings on the client. Administrators can configure registry settings on clients through the use of Group Policy objects, which add, delete, or change the values of entries in the client registry. There are several Group Policy types, including registry-based, software installation, security, script, and folder redirection. To determine features and behaviors in client applications, you configure registry-based Group Policy objects. Group Policy objects are applied to clients within selected Active Directory containers, such as sites, domains, or organizational units. This provides administrators with a greater level of detail when determining the client features that are available to users. While in-band provisioning settings are applied to all users within an Office Communications Server pool, Group Policy objects are applied to individual Active Directory containers. For details about Office Communications Server 2007 R2 client Group Policy and to download the Communicator.adm file, see the Microsoft Office Communications Server 2007 R2 Group Policy Settings documentation at http://go.microsoft.com/fwlink/?LinkID=140494.

How Group Policy Works

Group Policy components are administered using two primary tools. The first tool is Group Policy Object Editor, which is the built-in tool that lets you configure and modify settings within Group Policy objects. The second tool is Group Policy Management Console (GPMC), which is an addon tool that simplifies the management of Group Policy by letting you create, view, and manage the policies that are applied to your Active Directory containers. Administrators can define Group Policy settings by using an administrative template (.adm) file, which contains specific information about which Group Policies a particular application implements, where the policies are stored, and how to configure the policies. The user interface for registry-based policies is controlled by using Administrative Template (.adm) files. These files describe the user interface that is displayed in the Administrative Templates node of the Group Policy snap-in. Note: Another method for adding, modifying, or deleting registry subkeys and values is to use a Registration Entries (.reg) file. Registry Editor uses .reg files to import and export registry subkeys and values. You can use these .reg files to remotely distribute registry changes to several Windows-based computers. For more information, see the Microsoft Knowledge Base article 310516, How to add, modify, or delete registry subkeys and values by using a registration entries (.reg) file, at http://go.microsoft.com/fwlink/? linkid=84245. Some Group Policy objects directly relate to user-configurable options on the client. Depending on how you configure these policies, the user interface may show an option that is selected or deselected and not modifiable, or the option may be available and user-configurable.

35

Adding Administrative Templates

The administrative template file (.adm) consists of a hierarchy of categories and subcategories that together define how options are organized in the Group Policy user interface. To add Administrative Templates (.adm files) 1. Download the Communicator.adm file, available at http://go.microsoft.com/fwlink/? LinkID=140494. 2. Click Start, click Administrative Tools, and then click Active Directory Users and Computers. Select the domain or OU for which you want to set policy, click Properties, and then click the Group Policy tab. 3. In the Group Policy properties page, select the Group Policy Object that you want to edit from the Group Policy objects links list, and then click Edit to open the Group Policy Object Editor snap-in. 4. In the Group Policy Object Editor console, click the plus sign (+) next to either User Configuration or Computer Configuration. The .adm file defines which of these locations the policy is displayed in, so it doesn't matter which node you choose. 5. Right-click Administrative Templates, and then select Add/Remove Templates. This shows a list of the currently active templates files for this Active Directory container. 6. Click Add. This shows a list of the available .adm files in the %systemroot%/inf directory of the computer where Group Policy is being run. Browse to the location where you saved the Communicator.adm file and select it. Once selected, the .adm file is copied to the Group Policy Object Editor. The following figure is an example of how Communicator 2007 R2 Group Polices are displayed using the Group Policy Management Console.

Group Policy Manager view of Communicator 2007 R2 Group Policies 36

Because Live Meeting 2007 R2, Office Communications Server 2007 R2 Group Chat, Office Communicator 2007 R2, and Office Communications Server 2007 R2 Attendant policies are separate, you can deploy Group Policies for any one of the clients without affecting current or future deployments of any other clients. Policies for specific clients are described in the following sections: Communicator 2007 R2 Group Policy Live Meeting Group Policy Group Chat Group Policies

Communicator 2007 R2 Group Policy

Some Communicator 2007 R2 features and behaviors can be configured by the administrator by using Office Communications Server 2007 R2 in-band provisioning, or by the user through the Communicator 2007 R2 Options dialog box. However, Group Policy takes precedence over both of these methods.

Communicator 2007 R2 Group Policy Precedence

The following table summarizes the order in which settings take precedence when a conflict occurs. Order of precedence for Group Policy, in-band provisioning, and Options dialog box settings
Precedence Location or Method of Setting

1 2 3 4

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Communicator HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator Office Communications Server 2007 in-band provisioning Communicator 2007 R2 Options dialog box

Communicator 2007 R2 Group Policy Additions

You can deploy Communicator 2007 R2 Group Policy without affecting users who are running Communicator 2005. This section introduces Communicator 2007 R2 Group Policy. Group Policy additions are summarized in the following table. New Group Policies for Communicator 2007 R2
Policy Name Definition

AllowSimultaneousRinging

Allows "simul-ring" (simultaneously ring an additional number when receiving incoming calls). WMI class is MSFT_SIPGlobalUCPolicyData. 37

Policy Name

Definition

DisableHTMLIM EnableFullScreenVideoPreviewDisabled

Disables HTML instant messages. Enables full screen video with the correct aspect ratio and disables video preview for all Communicator video calls. Changes the length of the dial tone from a 30second dial tone to a fading, 3-second dial tone. Controls whether a conference uses Open Authenticated access or Anonymous access. For peer-to-peer desktop sharing, controls whether encryption is turned on or off. Note: For conferences, desktop sharing reuses the pool setting for AV encryption, which also turns desktop sharing encryption on or off.

PlayAbbrDialTone ConferenceAccess PC2PCASEncryption

DisableVoiceMemo

Controls the ability to leave a voice memo.

Legacy Communicator Group Policies

The following table lists policies that have not changed in Communicator 2007 R2. Legacy Group Policies for Communicator 2007 R2
Policy Name Definition

AutoDiscoveryRetryInterval CalendarStatePublicationInterval CallLogAutoArchivingPolicy ConfiguredServerCheckValues CustomStateURL DGRefreshPeriod DGUrlExternal DGUrlInternal DisableAVConferencing

Set time interval to retry a failed automatic connection to the server. Frequency of updates to presence from Outlook Calendar. Controls saving of call logs to the Outlook Conversation History folder. List of additional servers for logging on. Configure up to four custom presence states. DGRefreshPeriod External address book location. Internal address book location. Supersedes DisableVideo. (See also 38

Policy Name

Definition

DisablePC2PCVideo.) DisableCalendarPresence Disables the loading of free or busy data from the Outlook messaging and collaboration client, and prevents this data from being published. (Replaces DisableCalendarState.) Disable display of custom Conversation window extensions. (Replaces DisableCollaborationApps.) Disable comparison of SMTP address with Outlook user profile. Show the sign-in name or SIP address of federated contacts. DisableHandsetOnLockedMachine Prevents calls from being placed from the handset when the computer is locked. Disable the HTTP connection fallback option. Affects the ability to establish voice or video calls behind a firewall or Network Address Translation (NAT) layer. Prevents Communicator from publishing the subject and location information of a meeting. This value is not used if DisableCalendarPresence is set, or if the Update my status based on calendar data option on the Personal tab is not set. Shows or hides the OneNote 2007 command in the Conversation window. Removes the Find Previous Conversations command and disables display of the previous conversations. Disables peer-to-peer video calls. Supersedes DisableVideo. (See also DisableAVConferencing.) Controls the display of the sign-in name or SIP address of public internet connectivity (PIC) contacts. 39

DisableConversationWindowTabs DisableDataConferencing DisableEmailComparisonCheck DisableFederatedPromptDisplayName DisableFreeBusyInfo DisableHandsetOnLockedMachine DisableHttpConnect DisableICE

DisableMeetingSubjectAndLocation

DisableOneNote12Integration DisableOnlineContextualSearch

DisablePC2PCVideo

DisablePICPromptDisplayName

Policy Name

Definition

DisableRTFIM DisableServerCheck DisableSimultaneousRinging

Disables rich text in instant messages. Controls the sign-in check for server name and version. Disables the Unified Communications Enterprise Voice feature Simultaneously Ring an Additional Number. Users can choose Appear Offline from the Presence menu. Turns on logging of certain errors to the Windows Event log, and disables the user interface for this feature. (Replaces CEIP.) Enables the Customer Improvement Program option and disables the user interface for this feature. (Replaces DisableStrictDNSNaming.) Controls how Communicator interacts with SIP servers that have non-standard FQDNs Creates a log for troubleshooting signaling failures, and disables the user interface for this feature. Identify user account as enabled for voice mail. Controls archiving of instant messages to the Outlook 2007 Conversation History folder, and disables the user interface for this feature. Configures a user's default location profile. Frequency of loading calendar data from MAPI. Location of the Media Relay Access server. Line information for unified communications Enterprise Voice. Controls notifications received when a user is added to another user's contact list, and disables the user interface for this feature. Configures telephony for Communicator 2007 R2. Location of custom voice mail server. 40

EnableAppearOffline EnableEventLogging

EnableSQMData

EnableStrictDNSNaming

EnableTracing

ExUMEnabled IMAutoArchivingPolicy

LocationProfile MapiPollInterval MRASServerURI msRTCLine NotificationsForNewSubscribers

TelephonyMode VoicemailURI

Policy Name

Definition

WebServicePollInterval

Frequency of loading calendar data from the Web services provider.

Changed or Superseded Policies for Communicator 2007 R2

The following table lists the policies that have been changed or superseded in this release. Changed or Superseded Policies for Communicator 2007 R2
Title Definition

CEIP DisableCollaborationApps DisablePC2PCAudio DisableStrictDNSNaming DisableVideo ABSInsideURL

See EnableSQMData. See DisableDataConferencing. See TelephonyMode. See EnableStrictDNSNaming. See DisablePC2PCVideo and DisableAVConferencing. Specifies the address of the Global Address Book server to use when signing on from a location inside the organizations firewall. Specifies the intranet address of the Global Address Book server to be used when signing on from a location inside the organizations firewall. This policy enables users to search for contacts in the organizations Active Directory. Allows the alternate in-band provisioning location for the Office Communications Server Address Book Service files to be used when the policies Address Book Server Inside URL and Address Book Server Outside URL are not specified or do not contain valid information. Controls the ability to send or receive unencrypted files using Microsoft Office Communicator File Transfer. This policy can be used if Communicator must transfer files to instant messaging clients that do not support encryption. Prevents federated contacts from staring an audio, video, or instant messaging session with 41

ABSOutsideURL

ABSUseFallback

AllowUnencryptedFileTransfer

BlockConversationFromFederatedContacts

Title

Definition

a Communicator user, unless the federated contacts access level has been set to Personal. ConfigurationMode Specifies how Communicator identifies the transport and server. If you enable this policy, you must specify the transport and either the server name or server IP address that Communicator will use. Prevents Communicator from showing emoticons in instant messages. Disables the File Transfer command. Prevents Communicator from sending or receiving instant messages that contain Windows XP Tablet PC Edition ink. Requires the user to provide logon credentials for Communicator rather than automatically using the Windows credentials during sign on to a Session Initiation Protocol (SIP) server. Prevents users from selecting or clearing the Automatically retrieve Out of Office settings from Outlook check box on the Personal tab of the Options dialog box. Prevents Communicator users from saving instant messages. Enables Office Communicator to send and receive instant messages securely when using the SIP Communications Service. This policy has no effect on Windows .NET or Exchange Server services. Enables Universal Plug and Play (UPnP). Enables hyperlinks in instant messages. Specifies the text to display to the user in the Help menu for the Help Web site. Specifies which Web site to open when the user selects the Help menu text item in the Help menu.

DisableEmoticons DisableFileTransfer DisableInkIM

DisableNTCredentials

DisablePresenceNote

DisableSavingIM EnableSIPHighSecurityMode

EnableUPNP EnableURL HelpMenuText HelpMenuURL

42

Title

Definition

IMWarning

Allows the administrator to configure the initial text that appears in the instant messaging area when a Conversation window is opened. Limits bandwidth that Communicator 2007 R2 can use for audio and video calls. Set in HKEY_LOCAL_MACHINE only. Cannot be set on a per-user basis. Specifies the maximum number of contacts that users can add to their Contact List. Specifies whether encryption is supported, required, or not supported when making and receiving audio and video calls. We recommend that this value be set to 1 if encryption must be forced. The PortRange subvalues specify the ranges of dynamically-allocated ports that Communicator can use to transmit signaling data using SIP, and to transmit audio and video data using RTP. Set in HKEY_LOCAL_MACHINE only. Cannot be set on a per-user basis. See PortRange/Enabled. See PortRange/Enabled. Prevents users from running Communicator. Enables Communicator to store passwords. URL for the XML file from which the tab definitions are loaded. Controls the availability of the Office Communicator Tour. Provides an address for the Office Communicator Tour. The address can point to the local computer, or to an HTTP or HTTPS site in the Windows Internet Explorer Local intranet or Trusted sites security zones.

MaxAudioVideoBitrate

MaximumNumberOfContacts PC2PCAVEncryption

PortRange/Enabled

PortRange/MaxMediaPort PortRange/MinMediaPort PreventRun SavePassword TabURL TourLaunch TourLaunch /TourURL

Obsolete Communicator 2007 R2 Group Policies

The following table lists Communicator 2005 policies that are no longer used. 43

Obsolete Communicator 2007 R2 Group Policies

Policy Name

ConfigurationMode/MaximumNumberOfExtensions ConfigurationMode/PBXPhoneDomain DisableCRLChecking DisableLiveMeetingIntegration EnableConferencingService EnablePC2Phone (Superseded by TelephonyMode) EnablePhoneControl (Superseded by TelephonyMode) EnableRemoteAssistance PortRange/MinSipDynamicPort

Live Meeting Group Policy

Some Live Meeting 2007 features and behaviors can be configured by the administrator using Office Communications Server 2007 R2 in-band provisioning, or by the user through the Live Meeting 2007 Options dialog box. However, group policies take precedence over both of these methods. If no policy is set for the Windows-based Live Meeting 2007 client or for the Conferencing Add-in for Outlook, default settings apply. Computer policies are observed before user policies. Preferences are observed last. If a preference is set before policies are set, the preferences are not overwritten. If only one policy is set for a server or for a service, the preference will be used for the unset policies. If policies are removed, the previous preference settings will be used. Live Meeting Group Policy is summarized in the following table. Note: You can configure these policy settings under both Computer Configuration and User Configuration, but the policy settings under Computer Configuration take precedence. New group policies for Live Meeting R2
Policy Name Definition

ServerConfiguration

Server Configuration has only one user configurable value Server Configuration 44

Policy Name

Definition

Number. This value must be changed if there are any changes to the Specify Transport settings. We recommend that this value be incremented each time the Specify Transport settings are changed. It is important to note the interaction between the Server Configuration key and the Specify Transport key. If you do set this key and you have not set the Specify Transport key then the DNS lookup will be used. If you are setting the Server Configuration by policy and the DNS lookup is not sufficient then you MUST configure the Specify Transport settings. ServiceConfiguration Set this if you are using a Service Portal. Only the Service Configuration Number and Portal URL are configurable (the others simply force needed registry entries to appear). Service Configuration Number is used to version your settings. Each time the Service Configuration Number is changed by policy it will force an automatic Test Connection in Live Meeting. Once a successful Test Connection has been done, Live Meeting will be configured for use with the Service. Portal URL is the value used to connect to your Service Portal. If you change this value then you must change the Service Configuration Number. We recommend that you just increment the Service Configuration number every time that you change the Portal URL. Specifies how Live Meeting identifies the transport and server. If you enable this policy setting, you must specify the transport and either the server name or the server IP address that Live Meeting uses. If you disable this policy setting, Live Meeting uses a DNS lookup to identify the transport and the server. It is important to note the interaction between this key and the Server Configuration key. If you do not set this key and you have set the Server Configuration key then the DNS lookup will be used. If you are setting the Server Configuration 45

ConfigurationMode

Policy Name

Definition

by policy and the DNS lookup is not sufficient, you MUST use these settings. PreventInitialTestConnectionDialog When Live Meeting starts for the first time, it usually presents the user with a Test Connection dialog box. If you are setting either Server or Service by policy, it is advised that you turn this setting on.

Group Chat Group Policies

Microsoft Office Communications Server 2007 R2 Group Chat group policies can be configured manually by using the registry or by Group Policy objects (GPOs). Note: Only one instant messaging client can be the enabled when both Group Chat and Communicator 2007 R2 are installed on the same computer. You must disable instant messaging for one of the clients. See Group Policy DisableIM for Group Chat in the following table. Group Chat Group Policies are summarized in the following table. Group Chat Group Policies
Policy Name Definition

DisableIM

Disables instant messaging for a specific client. Use this policy to disable instant messaging for either Group Chat or Office Communicator 2007 R2. Only one IM client can be the default IM client for the computer where this policy is enabled. When DisableIM is configured, the following behavior is expected: Group Chat rejects all IM invites. Office Communicator 2007 R2 receives all IM invites. IM Contacts do not display in the My Channels List. When launching an IM from the Participant list or by clicking a user in the chat display, a Communicator 2007 R2 conversation window opens.

PolicyLoginAccountName

This Group Policy specifies a name for the new 46

Policy Name

Definition

account. This name appears in the Group Chat client login form as an available account. AllowAccountConfigurationEdit Enabling this policy allows users to configure accounts in addition to the one specified by this GPO, so they can log on to different servers. Disabling this policy will prevent users from creating and editing custom accounts. LookupServerUri This policy allows the URI of the Lookup Server that will vend Channel Server URIs to be specified. The Lookup Servers URI is normally assumed based on the users SIP URI, which is not reliable if users are allowed to have multiple namespaces for their SIP URIs. Options: Enter the Lookup Server URI in provided field. Administration This policy allows account information to be configured by the Microsoft Office Communications Server 2007 R2 Group Chat Administration Tool. Options: Select the Auto detect global catalog check box, or enter the global catalogs fully qualified domain name in the provided field. Important: IMPORTANT: If the Auto detect global catalog check box is not selected, a value MUST be entered into the Manually Enter Global Catalog FQDN field. Check the Allow Non SSL Active Directory Connections check box to allow non-SSL connections. SSL provides secure, encrypted connections. Set the Maximum Search Result Count value. Clicking the arrow controls of the number field increases or decreases the number in increments of 100. It can also be manually entered. This defines the maximum return when an Active Directory search, such as a user 47

Policy Name

Definition

search, is performed within Microsoft Office Communications Server 2007 R2 Group Chat Server. This value applies only to the Administration Tool. User searches through the desktop client are limited to 20 users returned. DisableNTCredentials Forces the user to provide logon credentials rather than automatically using Windows credentials to authenticate the user by using NTLM or Kerberos protocol. Specifies the host, protocol, and port that Group Chat uses to connect to Office Communicator 2007 R2. Enabling this policy and selecting Disallow peer-to-peer file transfer prohibits private channel-to-private channel file transfer. Enabling this Group Policy allows clients to log on with an account other than the one specified by this GPO. Disabling this policy restricts all clientconfigured accounts except the account specified by this GPO. Important: If the administrator wants to lock the users into using only this account, disable this policy. The client will no longer have write permissions to the Edit Accounts window. It will be readonly.

ConfigurationMode

FileTransferPermissions

Allow client to edit account configuration

Registry Keys
This topic describes the registry keys that are used by Live Meeting 2007 and the registry keys that are shared between Live Meeting 2007 and Office Communicator 2007 R2.

Live Meeting 2007 Registry Keys

The following table lists the registry keys that are used by Live Meeting.

48

Registry keys used by Office Live Meeting

Registry Key Description

HKEY_LOCAL_MACHINE\Software\Microsoft\ Live Meeting\8.0\ProductCode HKEY_LOCAL_MACHINE\Software\Microsoft\ Live Meeting\8.0\Lockdown HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\ LiveMeeting\AllowAnonymousServerJoin HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\ LiveMeeting\AllowServiceJoin HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\ Windows\Installer\DisableUserInstalls HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\ LiveMeeting\MaxAudioVideoBitrate HKEY_CURRENT_USER\Software\Microsoft\Live Meeting\Console\Version 8.0\Attendee\MediaPortRangeMin

In the client computers registry, string value representing the Office Live Meeting version Disables upgrade notifications. Prevents users from joining Office Communications Server meetings as an anonymous user. Prevents users from joining meetings that are hosted on the Office Live Meeting Service. Disables per-user installations. Specifies the maximum bandwidth for audio and video. 1 Specifies a minimum value for the UDP/TCP port range that is used when the client is running in Attendee mode.2 Specifies a maximum value for the UDP/TCP port range that is used when the client is running in Attendee mode. 2 Specifies a minimum value for the UDP/TCP port range that is used when the client is running in Presenter mode. 2 Specifies a maximum value for the UDP/TCP port range that is used when the client is running in Presenter mode. 2 If you are using an Audio Conferencing Provider (ACP) with Office Communications Server 2007 R2, specifies the ACP URL. This key pre-populates the ACP provider name field in the client 49

HKEY_CURRENT_USER\Software\Microsoft\Live Meeting\Console\Version 8.0\Attendee\MediaPortRangeMax HKEY_CURRENT_USER\Software\Microsoft\Live Meeting\Console\Version 8.0\Presenter\MediaPortRangeMin HKEY_CURRENT_USER\Software\Microsoft\Live Meeting\Console\Version 8.0\Presenter\MediaPortRangeMax HKEY_CURRENT_USER\Software\Microsoft\Live Meeting\Preferences\Server\ServerAudioProviderName

Registry Key

Description

audio settings. HKEY_CURRENT_USER\Software\Microsoft\Live Meeting\Preferences\Server\ServerAudioProviderAccount If you are using an ACP, specifies the ACP URL. This key prepopulates the ACP provider account field in the client audio settings. If you are using an ACP, specifies the ACP toll free number in the format+1-8665006738. This key pre-populates the ACP toll free number field in the client audio settings. If you are using an ACP, specifies the ACP toll number in the format+1-2034808000. This key pre-populates the ACP toll number field in the client audio settings.

HKEY_CURRENT_USER\Software\Microsoft\Live Meeting\Preferences\Server\ServerTollFreeNumber

HKEY_CURRENT_USER\Software\Microsoft\Live Meeting\Preferences\Server\ServerTollNumber

[HKEY_CURRENT_USER\Software\Microsoft\Tracing\uccp Enables client-side logging, which \ LiveMeeting] maintains a detailed log in the %USERPROFILE%\tracing\ "EnableFileTracing"= DWORD:00000001 directory (filename LiveMeeting"Tracing"= DWORD:00000001 uccp-*.log). Client-side logging supplements the default logging in the %TEMP% directory (filename pwconsole-debug*.txt). HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\ Outlook\Options\ConflictMsgCls "IPM.Appointment.Live Meeting Request"= DWORD:00000004 Minimizes a conflict error that users of the Conferencing Add-in for Outlook may see when they are running the 2007 Microsoft Office System and Exchange Server 2007. In some circumstances, when the user creates or modifies a Live Meeting appointment, an erroneous Outlook message appears indicating that the appointment conflicts with another appointment.

1 The selected bit rate should account for transmission of both main and panorama video. Therefore, the value should be higher than the equivalent setting for Office Communicator. This 50

setting applies to audio and video traffic. It does not apply to data traffic related to application sharing. 2 The default UDP/TCP port range is 1024-65535. By default none of these registry keys is set. Values in both the Attendee and Presenter modes must be set to make any of these settings become effective.

Live Meeting Registry Keys that are Shared with Office Communicator
The registry keys listed in the following table are shared between the Office Live Meeting client and Office Communicator 2007 R2. When you install one client, these registry keys are created and provisioned for both clients. If a user changes his or her account information manually in one client, the account information changes in the other client. Instead of requiring users to enter their account settings manually, administrators may want to configure these registry keys during client deployment. Otherwise, administrators need to provide instructions to users about how to enter account settings. Registry keys shared between Office Communicator and the Office Live Meeting client
Registry Key Description

HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient\ServerAddressExt ernal

Specifies the server name or IP address used by a federated contact when connecting from outside the external firewall.

HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient\ServerAddressInte Specifies the rnal server name or IP address used by the client when connecting from inside the organizations firewall. HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient\ServerSipUri Specifies the SIP URI used by the client 51

Registry Key

Description

when connecting to Office Live Meeting, the Conferencing Add-in for Microsoft Office Outlook, and Office Communicato r sign-in name. HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient\Transport Defines the network protocol used by the client: Transmission Control Protocol (TCP), or Transport Layer Security (TLS).

Common Issues with GPO and Registry Settings

This section outlines some common issues with the configuration of Group Policy or registry keys.

Where to Find the Communicator.adm Template

As described in the section Group Policy for Unified Communications Clients, one way to provide the appropriate registry settings for each user when deploying Office Communicator 2007 R2 is to define Group Policies by using the Communicator.adm administrative template. The Communicator.adm template and Group Policy documentation can be downloaded at http://go.microsoft.com/fwlink/?LinkID=140494. For instructions about how to install the template, see Group Policy for Unified Communications Clients.

52

Users are Always Prompted for Credentials

With the Kerberos or NTLM authentication method, the users Windows credentials are used automatically for authentication. In a typical Office Communications Server deployment that uses Kerberos protocol, NTLM, or both, users should not have to enter their credentials every time that they sign in, unless you want to explicitly require them to do this. The DisableNTCredentials registry key controls whether users are required to enter credentials every time that they sign in. If users are unintentionally being prompted for credentials, the DisableNTCredentials key may be unintentionally configured on client computers, possibly through a Group Policy. To prevent the additional prompt for credentials, change the value for the following registry key to 0: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator\DisableNTCredentials To make this change to all clients in a pool, use the Communicator.adm file to update the Group Policy object for the pool.

Hyperlinks Are Not Working

By default, Communicator disables hyperlinks in instant messages so that URLs are presented as plain text. The behavior of hyperlinks can be modified by two different means. First, you can configure the EnableURL registry key to modify hyperlink behavior. When the EnableURL key is set to 1, hyperlinks become active and clickable in instant messages. Second, the Intelligent Instant Message Filter in the server pool settings determines whether active hyperlinks are blocked, allowed, or converted to plain text. For more information about the Intelligent Instant Message Filter, see the Configuring Intelligent IM Filtering and Configuring URL Filtering topics in the Administering Office Communications Server 2007 R2 documentation. The settings that you configure apply across the pool. Because these filters are applied at the server, they take precedence over the EnableURL registry key that is set on the client. If you want users in the pool to be able to exchange active hyperlinks, either do not configure the Intelligent IM Filter or configure the Intelligent IM Filter to allow active hyperlinks. Then, configure the EnableURL key on clients (for example through Group Policy) with a setting of 1. If you want only a select group of users to be able to exchange active hyperlinks, the users will need to be in a separate pool or Active Directory container so that you can apply the EnableURL policy to the users. Then, you must not configure the Intelligent Instant Message filter to block hyperlinks.

Disabling Video and A/V Conferencing

Organizations that want to disable video can use Group Policy, but should be aware that there are two policies affecting the use of video. The DisablePC2PCVideo disables video for sessions between two participants. The DisableAVConferencing policy disables video for conferencing sessions with more than two participants. If you want to disable all video, you should enforce both policies.

53

Disabling Communicator Calls

The availability of computer-to-computer calling depends on whether your organization has a Voice license, and the Telephony Mode that you have selected. As described in the section Office Communications Server 2007 R2 CALs, setting the TelephonyMode registry key to 4 disables computer-to-computer calling so that only remote call control is available. To set this registry key for clients in your organization, you can enable the Telephony Mode policy and define a setting of 4. Use the Communicator.adm template file described in the section Group Policy for Unified Communications Clients. Also, see the Microsoft Knowledge Base article 11402, You cannot disable the Communicator Call option in Office Communicator 2007, at http://go.microsoft.com/fwlink/?linkid=147017.

File Transfer is Not Working

Several factors can affect the file transfer feature in Communicator, and the handout and multimedia playback features in the Live Meeting client. These factors include the Intelligent Instant Message Filter feature in Office Communications Server, Group Policy configuration, and client-side, antivirus software. The following list describes the various factors that may be causing file transfer issues. DisableFileTransfer registry key When this Communicator registry key is set to 1, it disables the Send a File option in Communicator. If the issue is affecting one user or a few users, try disabling this registry key (set it to 0) to see whether the issue is resolved. Prevent File Transfer policy When this Communicator policy is enabled, it disables the Send a File option in Communicator for the clients affected by the policy. If the issue is affecting all users in a pool, check whether this policy is enabled. Intelligent Instant Message Filter The File Transfer Tab in the Intelligent Instant Message Filter feature allows administrators to filter the file types that can be transferred in instant message conversations, Live Meeting handouts, and multimedia playback. If the issue affects all users, the filter may have been configured unintentionally to block the file types that you want to allow. Verify the configuration of the Intelligent Instant Message Filter in the server pool settings. For more information about the Intelligent Instant Message Filter, see the Configuring Intelligent IM Filtering and Configuring File Transfer Filtering topics in the Administering Office Communications Server 2007 R2 documentation. Antivirus software An antivirus program that is running on the client might be preventing certain file types from being transferred. Try temporarily disabling the antivirus program to see whether this resolves the issue. Attachment Management Group Policy Attachment Management is a set of Windows Component policies that define the file types that the client can access, based on whether an attachment is received from the restricted zone or Internet zone. You can specify high, moderate, and low risk file types. When these policies are not set or are disabled, Windows uses a built-in list of file types that can pose risk. If a user or a few users are experiencing issues with accessing a common file type such as .doc or .docx, you can check whether the high risk or medium risk policies are enabled and whether that file type is listed. For more information about the Attachment Manager, see the Microsoft Knowledge Base article 54

883260, Description of how the Attachment Manager works in Windows XP Service Pack 2, at http://go.microsoft.com/fwlink/?linkid=147020. To view or modify the Attachment Management policies 1. In the Group Policy Object Editor, expand User Configuration, expand Administrative Templates, expand Windows Components, and then click Attachment Manager. 2. Double-click Inclusion list for high risk file types and check whether the affected file name extensions are in the list. If they are in the list, remove them. 3. Double-click Inclusion list for moderate risk file types and check whether the affected file name extensions are in the list. If they are in the list, remove them. 4. Double-click Inclusion list for low risk file types. Enable this policy and add the affected file types to the list. Click OK. 5. Refresh the policy by running gpupdate /force or log on again.

Audio, Video, or Desktop Sharing Failures

Audio, video, and desktop sharing problems can be caused by the misconfiguration of certain registry keys or Group Policies. MaxMediaPort and MinMediaPort If you use the port range registry key settings to reduce the ports that can be used for media, we recommend that you do this according to the minimums described in this section. For client endpoints, the port range should not be reduced to the point where it can compromise the ability of the media stack to negotiate audio, video, and desktop sharing communication ports during session setup or during a call. More specifically, for an Office Communicator 2007 R2 client, the minimum port range should be 40. A smaller range of ports can result in errors during call transfer, when starting desktop sharing, and conference escalation scenarios. Configuring a minimum of 40 ports will enable the client to evaluate the candidate transport addresses that it can use to stream audio, video, and data to another client, as described in the IETF Interactive Connectivity Establishment (ICE) protocol. Candidate addresses include local addresses and an address on the A/V Access Edge server. A minimum of 40 ports in the port range will also accommodate any escalations from a peer-to-peer call to a conference. (An escalation of a peer-to-peer call to a conference triggers a temporary doubling of the ports being used.) The registry keys for these settings are as follows: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Communicator\Portrange\Enabled REG_DWORD 1 HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Communicator\Portrange\MaxMediaP ort REG_DWORD 40039 (for example)

55

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Communicator\Portrange\MinMediaPo rt REG_DWORD 40000 (for example) MaxAudioVideoBitRate Important: The MaxAudioVideoBitRate setting is expressed in bits, not kilobits. A setting of 512000 would be practical, whereas a setting of 512 (which you might enter if you assumed the setting is in kilobits) would not provide enough bandwidth for audio and video. The MaxAudioVideoBitRate can be used to limit the bandwidth that Communicator can use for audio and video calls. If this key is unintentionally set too low, it can cause audio and video failures.

Integrating a Third-Party Collaboration Program with Communicator

You can integrate Communicator 2007 R2 with any third-party online collaboration program by adding the same registry settings as those used by Live Meeting 2007. The integration process described here is the one used for Live Meeting 2007. Therefore, some steps might not apply to other online collaboration programs. You can use Communicator 2007 R2 to start data conferencing sessions hosted on an in-house server, an Internet-based service, or both. The collaboration or data conferencing session can be started from the Contact List, or from an existing instant messaging, voice, or video session. Communicator acts only as the vehicle for starting the program. Any existing Communicator 2007 R2 conversations remain active after the online collaboration session has begun. The following sections describe how Communicator 2007 R2 is integrated with Internet-based and server-based collaboration programs.

Integrating an Internet-Based Collaboration Program with Communicator 2007 R2

Generally, the steps involved in integrating a third-party collaboration program are as follows: 1. Information about how the program is added to the registry, as described in the following table. 2. The organizer signs in to Communicator and selects contacts for data sharing and collaboration. Or, the organizer may already be in a conversation and decides to add data conferencing. 3. Communicator 2007 R2 reads the registry, starts the collaboration program, and then sends a custom SIP messagean appINVITEto the selected participants. 4. Participants accept the invitation, and the collaboration program is started on each persons computer. Communicator 2007 R2 uses the registry to determine which collaboration program to use, and then starts that program by using the parameters included in the appINVITE message. 56

The following table describes the registry entries required to integrate an Internet-based collaboration program with Communicator 2007 R2. Registry entries for an Internet-based collaboration program (HKEY_LOCAL_MACHINE\Software\Microsoft\Communicator\SessionManager\Apps\<GUI D of Application>)
Name Type Data

Name SmallIcon LargeIcon Path OriginatorPat h

REG _SZ REG _SZ REG _SZ REG _SZ REG _SZ

The program name for Communicator 2007 R2 menus. Path to 16-pixel x 16-pixel icon, BMP or PNG. Path to 28-pixel x 28-pixel icon, BMP or PNG. Participant path for starting the online collaboration program. Organizer path for starting the online collaboration program. This path can contain one or more custom parameters as defined in the Parameters subkey. For example, https://meetserv.adatum.com/cc/%param1%/join?id= %param2%&role=present&pw=%param3% 0 = Local session. The application is started on the local computer. 1 = Two-party session (default). Communicator 2007 R2 starts the application locally, and then sends a desktop message to the other user. The other user clicks the message and starts the specified application on their computer. 2 = Multiparty session. Communicator 2007 R2 starts the application locally, and then sends desktop alerts to the other users, prompting them to start the specified application on their own computer.

SessionType

DWO RD

LiveServerInt egration

DWO RD

0 or not present = The application has its own conferencing mechanisms and does not require Office Communications Server 2007 R2 (default). 1 = Integrates with an in-house server.

ApplicationTy pe

DWO RD

1 = Sets the application type to protocol. The other possible values do not apply in this case. If not present, ApplicationType defaults to 0 (executable). A list of the menus where this command appears, separated by semicolons. Possible values are as follows: MainWindowActions MainWindowRightClick ConversationWindowActions 57

ExensibleMen REG u _SZ

Name

Type

Data

ConversationWindowContextual ConversationWindowRightClick ConversationWindowButton

If ExtensibleMenu is not defined, the default values of MainWindowRightClick and ConversationWindowContextual are used. ButtonPriority DWO RD 0 = Application is displayed on the button (default).

Registry entries for an Internet-based collaboration program (HKEY_LOCAL_MACHINE\Software\Microsoft\Communicator\SessionManager\Apps\Para meters<GUID of Application>)

Name Type Data

Param1

REG_SZ

Used in tokenized format (%Parm1%) to add user-specific values to the OriginatorPath registry key. See Param1. See Param1.

Param2 Param3

REG_SZ REG_SZ

The following example registry settings integrate ADatum Collaboration Client with Communicator 2007 R2. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager\Apps] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager\Apps \{C3F6E17A-855F-44a0-B90D-C0B92D38E5F1}] "Path"="https://meetingservice.adatum.com/cc/%param1%/meet/%param2%" "OriginatorPath"="https://meetserv.adatum.com/cc/%param1%/join?id= %param2%&role=present&pw=%param3%" "SessionType"=dword:00000002 "ApplicationType"=dword:00000001 "LiveServerIntegration"=dword:00000000 "Name"="ADatum Online Collaboration Service" "Extensiblemenu"="MainWindowActions;MainWindowRightClick;ConversationWi ndowActions;ConversationWindowContextual;ConversationWindowRightClick" 58

[HKEY_CURRENT_USER\Software\Microsoft\Communicator\SessionManager] [HKEY_CURRENT_USER\Software\Microsoft\Communicator\SessionManager\Apps] [HKEY_CURRENT_USER\Software\Microsoft\Communicator\SessionManager\Apps\ Parameters] [HKEY_CURRENT_USER\Software\Microsoft\Communicator\SessionManager\Apps\ Parameters\{C3F6E17A-855F-44a0-B90D-C0B92D38E5F1}] "Param1"="meetserv" "Param2"="admin" "Param3"="abcdefg123"

Integrating a Server-Based Collaboration Program with Communicator 2007 R2

The settings to add commands for starting a server-based collaboration program from within Communicator 2007 R2 are similar to those described in the section, Integrating an InternetBased Collaboration Program with Communicator 2007 R2. However, the OriginatorPath is not required, and some values are changed, as described in the following table. Registry entries for a server-based collaboration program (HKEY_LOCAL_MACHINE\Software\Microsoft\Communicator\SessionManager\Apps\<GUI D of Application>)
Name Type Data

Name ApplicationType

REG_SZ DWORD

Name of the application as it appears on the menu. Value = 1. Sets the application type to protocol. The other possible values do not apply in this case. If not present, ApplicationType defaults to 0 (executable). Protocol used to execute the collaboration program. For Live Meeting 2007, the value of Path is set to meet: %conf-uri%. 0 = Local session. The application is launched on the local computer. 1 = Two-party session (default). Communicator 2007 R2 launches the application locally, and then sends a desktop alert to the other user. The 59

Path

REG_SZ

SessionType

DWORD

Name

Type

Data

other user clicks the alert and starts the specified application on their computer. 2 = Multi-party session. Communicator 2007 R2 launches the application locally, and then sends desktop alerts to the other users, prompting them to launch the specified application on their computer. LiveServerIntegration MCUType ExtensibleMenu DWORD REG_SZ REG_SZ 1 = Hosted on the in-house server. DATA = The type of server. A list of the menus where this command appears, separated by semi-colons. Possible values are: ConversationWindowContextual ConversationWindowRightClick If ExtensibleMenu is not defined, the default values of MainWindowRightClick and ConversationWindowContextual are used. The following example adds commands to launch ADatum Collaboration Client from within Communicator 2007 R2. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager\Apps] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager\Apps \{27877e66-615c-4582-ab88-0cb2ca05d951}] "Path"="meet:%conf-uri%" "SessionType"=dword:00000002 "LiveServerIntegration"=dword:00000001 "ApplicationType"=dword:00000001 60 MainWindowActions MainWindowRightClick ConversationWindowActions

"Name"="ADatum Collaboration Client" "MCUType"="Data" "Extensiblemenu"="MainWindowActions;MainWindowRightClick;ConversationWi ndowActions;ConversationWindowContextual;ConversationWindowRightClick"

Communicator 2007 R2 Call Scenarios

Office Communications Server 2007 R2 can work with existing telephony infrastructure. With Office Communications Server 2007 R2, users can not only send and receive calls with the Public Switched Telephone Network (PSTN), but can integrate with a company's Private Branch Exchange (PBX) system. Office Communications Server 2007 R2 also combines VoIP with open standards to make the telephone menu-based part of the unified communications strategy. This extends the integration features that bridge the VoIP standards supported by Office Communications Server 2007 R2 with implementations that use older standards. At the center of this integration is the Mediation Server role of Office Communications Server 2007 R2. It provides a single interface and uses open-standard SIP for signaling interoperability. Mediation Server takes calls from third-party IP-PBX systems or SIP/PSTN Gateways and moves them onto the network using the adaptive codec, remote user, and security models that are the basis for call setup and media with Office Communications Server 2007 R2. The following two configurations are common Office Communications Server 2007 R2 call scenarios. Standalone Users in an organization replace their legacy phones with Office Communicator 2007 R2 or an Office Communications Server 2007 IP phone. This way, users who are configured to use Office Communications Server 2007 R2 will make and receive calls with Office Communicator 2007 R2, and users configured to use the PBX will make and receive calls using the PBX. Each group continues to have a smooth calling experience, including extension-based dialing capability. This scenario works especially well for mobile employees. The standalone scenario can be implemented by using either a SIP/PSTN gateway, or a direct SIP connection to the PBX. Co-existence An incoming call is forked between the PBX phone and the user's loggedin Office Communicator 2007 R2 endpoints. Both the PBX phone and Office Communicator 2007 R2 co-exist on the user's desktop. The co-existence scenario is implemented by using a specification called Dual Forking, and can be deployed with or without remote call control (RCC). This section covers three scenarios for calling as follows: Standalone Communicator (TelephonyMode=1) Co-existence of Office Communicator and PBX (TelephonyMode=2) Dual forking (TelephonyMode=3) 61

Standalone Communicator (TelephonyMode=1)

In the standalone scenario, users in an organization replace their legacy PBX phones with Office Communicator 2007 R2 or an Office Communications Server 2007 R2 IP phone. This way, users who are configured to use Office Communications Server 2007 R2 will make and receive calls with Office Communicator 2007 R2, and users configured to use the PBX will make and receive calls using the PBX. A peer-to-peer call using Communicator 2007 R2 is when one Communicator 2007 R2 client places an Office Communications Server 2007 R2 call to another Communicator 2007 R2 client. In this case, the call is a direct VoIP, it is handled exclusively by the server, and the presence status (in a call) is broadcast to other Communicator clients. The call is a SIP INVITE from one client to another and audio is established. Be aware that when a PSTN gateway and Mediation Server are present, PSTN calls can be made to Communicator clients and Communicator clients can place calls to the outside PSTN network. The following figure shows TelephonyMode=1 when a Communicator 2007 R2 client (Client A) places a peer-to-peer call with another Communicator 2007 R2 client (Client B).

62

Co-existence of Office Communicator and PBX (TelephonyMode=2)

Co-existence is when an incoming call is forked between the PBX phone and the user who is logged on to Office Communicator 2007 R2 endpoints; both the PBX phone and Office Communicator 2007 R2 co-exist for a user. The result is a mix of PBX and Office Communications Server 2007 R2 communication capabilities configured for call routing using IPPBX integration between the user's legacy phone and Office Communicator 2007 R2. Remote call control (RCC) allows Office Communicator 2007 R2 to control a user's PBX phone line and indicate their presence based on the status of their phone. Users can answer their PBX phone with Office Communicator 2007 R2 and update their presence to "In a Call." This figure demonstrates TelephonyMode=2 for a call placed from a PBX phone and received using either the recipients PBX phone, or from the recipients Communicator 2007 R2 client.

As shown in this figure, the following activities occur: Step 1: PBX Phone User B places a direct call to PBX Phone User A. The PBX phone for User A rings. The PBX phone can be answered. Step 2: While the PBX phone for User A is ringing, User A receives a notification from Communicator 2007 R2 to receive the call by using Communicator. The Communicator client can be used to answer the call by using RCC.

63

Dual forking (TelephonyMode=3)

Most IP-PBXs support dual forking, which enables sharing of a common number with Office Communications Server 2007 R2. Additionally, the PBX could also support Direct SIP for certain numbers (managed by Office Communications Server), or manage the numbers themselves (for users not enabled for voice by using Office Communications Server 2007 R2). An extension of this concept is dual forking with RCC. RCC provides information to Office Communications Server 2007 R2 about the state of PBX-connected lines. This allows presence updates when the user is on the PBX-connected station set. The following figure demonstrates dual forking (TelephonyMode=3).

As shown in the figure, the following activities occur: Step 1: User B places a PBX phone direct call to PBX Phone User A. The PBX phone for User A rings. The PBX phone can be answered. Additionally, the call is forked to a Mediation Server and

64

the call simultaneously displays a notification on the Communicator client for User A. The call can be answered by using Communicator. Step 2: A Communicator call is placed from User A to User B. The Communicator client for User B receives a notification to receive the call from User A. Simultaneously, the PBX phone for User B rings.

Communicator Mobile Call Scenarios

This section covers topics related to Microsoft Office Communicator Mobile call scenarios. It provides a review of the Communicator Mobile topology, as well as an overview of the Single Number Reach feature, including a view of its topology. The following topics provide the relevant details for Communicator Mobile call scenarios: Communicator Mobile Topology Single-Number Reach Incoming Calls

Communicator Mobile Topology

The topology for Communicator Mobile works exactly as Office Communicator as soon as it has network connectivity over a wireless data network. Communicator Mobile clients connect to the topology based on the network that the device is connecting to. An external user, connecting by a cellular data connection, communicates with an Office Communications Server Edge Server to gain access to other clients. Internal users, connecting by a Corporate WI-FI connection, communicate directly with their home server. Communicator Mobile and Office Communicator exercise many of the same key processes for client connectivity, authentication and discovery. The following figure displays Communicator Mobile scenarios in an Office Communications Server 2007 R2 deployment.

65

Communicator Mobile Topology

Single-Number Reach
Today, mobile employees need access to presence-enabled communication (voice/IM) both within the enterprise and outside of it. Single-Number Reach is a way for enterprise users to hand out a single identity and be reached wherever and on whichever device. With Single-Number Reach, mobile employees can now manage a corporate identity and personal identity on the same wireless device. Enterprise Cellular Telephony is a feature of Office Communications Server 2007 R2. It provides the ability for a user to use Communicator Mobile to set up and control voice calls over the circuitswitched network.

Topology
The following figure is an example of a Communicator Mobile topology, and the various servers and signaling that occurs.

66

Single Number Reach Topology

Single-Number Reach Features

Single-Number Reach, in combination with Office Communications Server 2007 R2, enables valuable scenarios for users of Communicator Mobile. The following table describes a few features commonly used by Communicator Mobile users.
Feature Description

Click-to-Call SNR - Incoming SNR Outgoing

Call SIP URIs and telephone numbers from contact list and smart search results. Receive calls dialed to their single number on their Communicator Mobile device. Make calls from their Communicator Mobile device. The caller-ID received reflects their single number. Incoming calls may be deflected to other targets for example, voice mail.

Deflection services for voice mail

Server Roles
To implement Single-Number Reach in an Office Communications Server 2007 R2 environment, some additional server roles and technologies are required.
Dependency Description

Call Control Server

Sets up calls between the cellular device and the remote party 67

Dependency

Description

Mediation Server PSTN Gateway

Calls that exit the enterprise voice network exit by the Mediation Server Used to connect a VOIP network to the traditional Public Switched Telephone Network (PSTN)

Incoming Calls
The Single-Number Reach features requires that your Communicator Mobile device discerns if an incoming call is a regular cell phone call, or an enterprise call from the Office Communications Server infrastructure. To support this feature, Communicator Mobile users must configure the Simultaneously Ring feature on their mobile device. This feature is configured on the Calls tab, available from the Options menu. Once configured, when an incoming call is an enterprise call, Office Communications Server forks the call to all registered endpoints, including the Communicator Mobile device. If an incoming call is not an enterprise call from the Office Communications Server infrastructure, the call is handled as a normal cell call.

Diagnosing Microsoft RoundTable

Diagnosing Microsoft RoundTable

This section of topics describes tools and configuration settings for diagnosing Microsoft RoundTable. The following topics provide the relevant details pertaining to Microsoft Roundtable diagnostics. Installing the Microsoft RoundTable Management Tool Using RTManage.exe Configuring the RoundTable Device Common Configuration Tasks Interpreting the Diagnostics Logs Dr. Watson Logs

68

Installing the Microsoft RoundTable Management Tool

Uninstall any earlier versions of Microsoft RoundTable Management Tool. Before you can configure the RoundTable device, you must install the RoundTable Management Tool, RoundTable.msi. You can obtain the RoundTable.msi from the Microsoft Download Center at http://go.microsoft.com/fwlink/?linkid=147085. By default, RoundTable.msi installs the Microsoft Software License Terms to the %ProgramFiles %\Microsoft RoundTable\ directory, and creates two directoriesDevice Management and Driversunder this directory. If you are running Windows Vista, only the Device Management directory will be created. RoundTable.msi copies the following files to the Microsoft RoundTable\Device Management\ directory. RTManage.exeThe RoundTable Device Configuration tool. The current version of this tool is in English only. Usage of this tool is described in this topic in Using RTManage.exe. DeviceConfig.xsnThe Office InfoPath template for RoundTable configuration. DefaultConfig.xmlAn example XML file for configuring the device.

The RoundTable.msi copies the following files to the Microsoft RoundTable\Driver\ directory. Note: The driver files listed are used by Windows XP, 32-bit edition. These files are not required by Windows Vista. Rtyuv.dll RoundTable.inf RoundTable.cat Meaningless text to force a break, maybe.

Using RTManage.exe
RTManage.exe is typically used with a switch that specifies one of three modes: image mode, diagnostic mode, and configuration mode. The three tables describe the mode commands and show the syntax for each. Image mode commands are used to update the firmware images of the RoundTable device's operating system or boot loader, or to download a new configuration. Diagnostic mode commands are used to send diagnostic logs to the image update server. Configuration mode commands are used for several purposes, including resetting the password, setting the device time, and uploading a device configuration to the image update server. All except two operations prompt the user for the RoundTable password. The operations that do not require a password are listed here. Rtmanage.exe -help 69

Rtmanage.exe -m:diag -l:flush For clarity, the following three tables show only the switches used with RTManage.exe. A complete command must include Rtmanage or Rtmanage.exe with the applicable switch, as in the following example. Rtmanage <switch> Rtmanage.exe <switch> Image mode commands
Switch Description

-m:img -help -m:img -i:nk -f:<file path to nk.bin> -s:<file path to nk.cat> -m:img -i:EBOOT -f:<file path to CPUEBOOT.bin> -s:<file path to CPUEBOOT.cat> -m:img -i:config -f:<file path to rtconfig.xml>

Shows usage and flags of the image mode. Performs a USB image update of Nk.bin, the operating system of the RoundTable device. Performs a USB image update of Cpueboot.bin, the boot loader of the RoundTable device. Downloads a new configuration file to the RoundTable device. The device must be restarted before the new configuration takes effect.

After you perform any of the image mode commands, you must restart the RoundTable device. You can do this by using the Rtmanage boot command as shown in the following command. Rtmanage.exe m:cfg -r Diagnostic mode commands
Switch Description

-m:diag -help -m:diag -l:flush

Shows usage and flags of the diagnostic mode. Flushes diagnostics to the image update server. The exact location will be referenced in future documentation for the Microsoft Office Communications Server 2007 R2 Device Update Service. You will not be prompted for a password for this operation.

Configuration mode commands

Switch Description

-m:cfg -help

Shows usage and flags of the configuration 70

Switch

Description

mode. -m:cfg -t:now -m:cfg -r -m:cfg -p -m:cfg -q:cfgparseresult -m:cfg -f:rtconfig.xml Sets the time of the RoundTable device with the time on the computer. Restarts the device. Sets the password for the device. The factoryset default password is 78491. Queries the parser result after a new configuration is downloaded to the device. Uploads the RoundTable device configuration file to a server share on the Office Communications Server 2007 R2 Device Update Service.

Configuring the RoundTable Device

This topic describes how to apply new settings to a RoundTable device. Before you start, make sure that you have a supported version of Office InfoPath installed, either Office InfoPath 2003 or Office InfoPath 2007. 1. In the %ProgramFiles%\Microsoft RoundTable\DeviceManagement\ directory, doubleclick DeviceConfig.xsn to open the InfoPath form. The following figure shows a section of this form.

71

2. After you change the settings to suit your particular installation, save the configuration (as RTConfig.xml, for example) to the same directory as RTManage.exe. The section following this procedure provides details of the InfoPath configuration form. 3. Open a command prompt, change the directory to the %ProgramFiles%\Microsoft RoundTable\DeviceManagement\ directory, and type the following command line. Rtmanage.exe -m:img -i:config -f:RTConfig.xml 4. Check for any XML parsing errors by running this command. Rtmanage.exe -m:cfg -q:cfgparseresult 5. If there are no errors, go to the next step. Otherwise fix the errors and repeat from step 3. 6. Restart the device by running this command line. Rtmanage.exe -m:cfg -r The following tables provide details about the configuration changes that you can make in the InfoPath configuration user interface.

Room settings
Field Description Factory default

Room name

A text description (maximum 63

(empty string) 72

Field

Description

Factory default

characters) for the conference room. Room size The approximate comfortable seating capacity of the conference room. There are three options: 1 6 people (Small) 7 11 people (Medium) 12 or more people (Large) Table size The approximate size of the table in the conference room. There are three options: 5 ft. (1.52 m) Round 10 ft. x 5 ft. (3.05 m x 1.52 m) 20 ft. x 5 ft. (6.10 m x 1.52 m) Lighting A description of the lighting brightness in the conference room. There are three options: Normal Dark Light Notes 1:, Notes 2:, Notes 3: Custom fields (maximum 63 characters for each field) that the administrator can use to tag the devices. (empty string) Normal 10 ft. x 5 ft. (3.05 m x 1.52 m) 7 11 people (Medium)

The values of Room size and Lighting are currently not used by the firmware. Network settings
Field Description Factory default

Device name

A friendly name (maximum 63 characters) for the device. Used in the diagnostics log for tagging the device. This is not the host name for the device. Determines whether Dynamic Host Control Protocol (DHCP) is

(empty string)

DHCP enabled

Checked

73

Field

Description

Factory default

enabled. The options are checked (DHCP is enabled) and unchecked (DHCP is disabled). A check in this field corresponds to a value of "true for the DHCPEnabled attribute in DefaultConfig.xml. If unchecked, the DHCPEnabled attribute has a value of "false." IP Address When DHCP is disabled, enter the IP address in xxx.xxx.xxx format. When DHCP is disabled, enter the subnet mask in xxx.xxx.xxx format. When DHCP is disabled, enter the IP address of the default gateway in xxx.xxx.xxx format. When DHCP is disabled, enter the IP address of the preferred DNS server in xxx.xxx.xxx format. When DHCP is disabled, enter the IP address of the alternate DNS server in xxx.xxx.xxx format. (empty string)

Subnet mask

(empty string)

Default gateway

(empty string)

Preferred DNS server

(empty string)

Alternate DNS server

(empty string)

Time settings
Field Description Factory default

Time zone

Time zone for the device

Set to time zone of the country in which the device is sold. For devices sold in the United States and Canada, the default time zone is Eastern standard time. Checked

Automatically adjust clock for daylight saving

Checked or unchecked Reserved

74

LCD display settings

Field Description Factory default

Display language

Brazilian Portuguese Dutch English French German Italian Japanese Korean Simplified Chinese Spanish Traditional Chinese

U.S. and Canada English U.K. English Australia English Germany German Netherlands Dutch India English France French Italy Italian Spain Spanish Japan Japanese

Screen saver text

Reserved

(empty string)

Telephony settings
Field Description Factory default

Phone number Flash timing

Phone number for the RoundTable device 10 ms through 990 ms, in 10ms increments

(empty string) Default settings for the target country's recommended regulatory compliance agency Australia - 100 ms Canada - 700 ms France - 100 ms Germany - 100 ms India - 300 ms Italy - 100 ms Japan - 700 ms Netherlands - 100 ms Spain - 100 ms U.K. - 100 ms U.S. - 700 ms

Ignore dial tone when dialing

On or Off Reserved

Off

75

Preprogrammed speed dials

Field Description Factory default

Name

Short name (maximum 63 (empty string) characters) of the number in the speed dial Telephone number (maximum 63 characters) (empty string)

Number

By default, the form shows one speed dial entry. You can use the form to add and program four additional speed dials. Software updates settings
Field Description Factory default

Automatically update by using the image update server Exclude configuration file from automatic update

Checked or unchecked. If checked, automatic image updates are enabled.

Checked

Checked or unchecked. If Unchecked checked, the configuration file is excluded from automatic update. Time of day at half hour intervals Every day Every Sunday Every Monday Every Tuesday Every Wednesday Every Thursday Every Friday Every Saturday 3:30 A.M. local time Every day

Update time Update interval

Server Port Uniform resource identifier path

Name of the update server Port for device-server communication URI path on the server with which to communicate.

Ucupdates 80 (empty string)

76

Logging settings
Field Description Factory default

Log to server

Checked or unchecked. If checked, diagnostic log data is sent to the server.

Checked

Upload time Update interval

Time of day at half hour intervals 3:00 A.M. local time Every hour Every day Every Sunday Every Monday Every Tuesday Every Wednesday Every Thursday Every Friday Every Saturday Every hour

Maximum log size in memory

Configurable size of memory reserved for the log. We recommend that you leave this set to 1024 KB. Name of the update server Port for device-server communication URI path on the server to communicate with

1024 KB

Server Port Uniform resource identifier path

Ucupdates 80 (empty string)

Power management settings

Field Description Factory default

Turn off LCD backlight

Amount of time (in minutes) after which the device's LCD backlighting is turned off, when there is no activity. After one minute After five minutes After 10 minutes After 20 minutes After 30 minutes

After five minutes

77

Field

Description

Factory default

After 45 minutes After 60 minutes After 120 minutes After 180 minutes After 240 minutes After 300 minutes

Advanced settings
Field Description Factory default

Active speaker detection algorithm

The device uses either audio only or both audio and video to detect the current speaker. The options are as follows: Use audio only Use audio and video

Use audio and video

Active speaker switching frequency White balance setting Light temperature

Reserved Auto or Manual If the white balance setting is Manual, the light temperature will be used. Incandescent 2800 K Cool white fluorescent 4100 K Daylight/sunlight 6500 K

Default Auto Not applicable

Lighting frequency

The lighting frequency can be set to the following values: Auto 50 Hz 60 Hz The lighting frequency setting should match the AC power frequency of the deployment location to ensure good video quality. If it is set to Auto, the device attempts to detect the frequency from the power

Australia 50 Hz Canada 60 Hz France 50 Hz Germany 50 Hz India 50 Hz Italy 50 Hz Japan* Auto Netherlands 50 Hz Spain 50 Hz U.K. 50 Hz U.S. 60 Hz 78

Field

Description

Factory default

source. Automatic detection results can vary because of variance in the circuit at the time of detection.

* For deployment in Japan, check the AC power frequency at the location, and ensure that Lighting frequency is set accordingly.

Debugging settings
Field Description Factory default

Audio debug logging Video debug logging

Enable verbose audio debug logging. On or Off. Toggle verbose video debug logging. On or Off.

Off Off

System debug logging

Toggle verbose system debug logging. On or Off.

Off

Common Configuration Tasks

This topic provides information about several common tasks that can be performed. For each command it is assumed that you have opened a Command Prompt window, and that the current directory is %ProgramFiles%\Microsoft RoundTable\Device Management\.

Set the Time

The following command uses the computer's time to reset the time on the RoundTable device. Rtmanage.exe -m:cfg -t:now

Change the Display Language

1. Double-click DeviceConfig.xsn to open the InfoPath form. 2. In the LCD Display section of the InfoPath form, change the Display language setting to the appropriate value. 3. Save the file (as RTConfig.xml, for example) to the directory that contains RTManage.exe. 4. Open a command prompt and run the following command: Rtmanage.exe -m:img -i:config -f:RTConfig.xml

79

5. Check for any XML parsing errors by using the following command: Rtmanage.exe -m:cfg -q:cfgparseresult 6. If there are no errors, go to the next step. Otherwise, fix the errors and repeat from step 3. 7. Restart the device using the following command. Rtmanage.exe -m:cfg r

Change the Time Zone

1. Double-click DeviceConfig.xsn to open the InfoPath form. 2. In the Time section of the InfoPath form, change the Time zone setting to the appropriate time zone. 3. Save the file (as RTConfig.xml, for example) to the directory that contains RTManage.exe. 4. At the command prompt, run the following command. Rtmanage.exe -m:img -i:config -f:RTConfig.xml 5. Check for any XML parsing errors using the following command. Rtmanage.exe -m:cfg -q:cfgparseresult 6. If there are no errors, go to the next step. Otherwise, fix the errors and repeat from step 3. 7. Restart the device by using the following command. Rtmanage.exe -m:cfg -r

Getting the Device's Current Configuration

Open a command prompt and run the following command. Rtmanage.exe -m:cfg -f:RTconfig.xml The device configuration file will be uploaded to a server share on the Office Communications Server 2007 Update Service.

Update the Firmware Images

The fastest way to update the RoundTable device is by means of an automatic image update using the image update server. However, if there is no update server and you must update the device, you can use the USB image update function. 1. Obtain the latest firmware image files from the Microsoft download center at http://go.microsoft.com/fwlink/?linkid=147102. Boot loader packageCPUEBOOT.cat and CPUEBOOT.bin Operating system packageNK.cat and NK.bin

2. To update the boot loader, run the following command at a command prompt.

80

Rtmanage.exe -m:img -i:EBOOT -f:<file path to CPUEBOOT.bin> -s:<file path to CPUEBOOT.cat> 3. To update nk.bin, run the following command at a command prompt. Rtmanage.exe -m:img -i:nk -f:<file path to nk.bin> -s:<file path to nk.cat>

Reset the Device to Factory Settings

A RoundTable device stores two copies of its firmware: a read-only copy that is installed at the factory, and an updatable working copy. A RoundTable device ordinarily runs the updatable copy. When a device reset is performed, the working copy is erased. The device then starts the readonly factory firmware. The factory firmware copy enables you to update the RoundTable device with current firmware revisions without having to return the device to the factory. If you forget your device password or the firmware images have become corrupted (because of a power outage, for example), you can perform a factory reset. To perform a factory reset 1. Press and hold the On/Off Hook button. 2. While still holding the On/Off Hook button, press and then release the Reset button at the back of the device. A screen appears that prompts you to confirm that you want to continue with the reset or to continue without resetting. 3. Press the Flash/Conference button to continue with the reset, or press the Mute button to continue without resetting. Hold the Flash/Conference button until the device LED lights start to blink. If you do not hold this button long enough, the factory reset will not occur and the device will restart. After you perform a factory reset, apply the latest RoundTable firmware to the device to help make operations secure and at a high performance level. After a factory reset you have to reapply the device configuration for your device. Failure to apply the latest RoundTable firmware after a factory reset can result in the device becoming noncompliant with telephony regulations in your country or region. Any liability that results from failure to apply the latest firmware upgrade is the responsibility of the end user.

Reset the Device Password

As a best practice to help ensure security, change the device password from its default setting by running the following command line. Rtmanage.exe -m:cfg -p You are prompted to enter the existing password, enter the new password, and then re-enter the new password. The password consists of ANSI characters, and must be at least one character, but no more than 15 characters.

81

Upload the Diagnostics Logs

The following command line flushes diagnostic logs on the RoundTable device and sends them to the image update server. rtmanage.exe -m:diag -l:flush

Interpreting the Diagnostics Logs

This topic outlines several Windows CE logging tasks, diagnostics logging, and the Watson dump features of Microsoft RoundTable.

CE Logging Tasks
RoundTable writes to the CE Log for hardware functional tests and critical system issues. This section identifies several tasks that are related to the CE log, that you can perform.

Send the CE Log to the Update Service Server

Open a command prompt, and execute the following command line. rtmanage.exe -m:diag -l:flush The CE log for the device is written to a directory on the share. The directory name is the product ID of the device. The CE log file name has the form YYYYMMDDHHMMSS-CELOGn.clg, where n is 0 or 1. An example CE log file name is 20070501170926-CELOG0.clg. Note: The file name might change based on the implementation of Office Communications Server 2007 Update Service.

Interpret the CE Log

You must use the Readlog.exe that is included with Windows CE Platform Builder to interpret the .clg file. Alternatively, you can send the file to Microsoft Customer Service and Support for investigation. For information about Readlog Command-Line Options, see http://go.microsoft.com/fwlink/?linkid=147112. To extract the contents of the .clg file to a text file, use the -v (verbose) print option when you run Readlog.exe. For example, Readlog.exe -v CE_log_file output_file.txt. The CE log contains the results of the hardware functional tests and critical system errors. The following is an example of the contents of a CE log. 0:00:01.523.868 : Raw data 0:00:01.524.306 : Raw data 0:00:01.524.769 : Raw data REV,,NA,1.0.3528.0,, 31 (wchar), ,,,FIRMWARE REV,,NA,1.0.3528.0 31 (wchar), ,,,FIRMWARE CURRENT REV,,NA,,, 41 (wchar), ,,,FIRMWARE FACTORY 82

0:00:01.525.254 : Raw data 0:00:01.525.674 : Raw data 0:00:01.526.107 : Raw data 0:00:01.526.557 : Raw data DONE,0xFFFFFFFF,, 0:00:01.527.109 : Raw data DONE,0xFFFFFFFF,, 0:00:01.527.626 : Raw data STATUS,,PASS,0x30000,, 0:00:01.528.088 : Raw data STATUS,,PASS,0x30001,, 0:00:01.528.539 : Raw data STATUS,,PASS,0x30002,, 0:00:01.528.965 : Raw data 0:00:01.529.756 : Raw data VERIFY,,PASS,0x40000,, 0:00:01.530.221 : Raw data VERIFY,,FAIL,0xFFFFFFFF,, 0:00:01.530.671 : Raw data VERIFY,,PASS,0x60000,, 0:00:01.531.213 : Raw data 0:00:01.531.646 : Raw data 0:00:01.532.087 : Raw data

27 (wchar), ,,,OS REV,,NA,1.0.3528.0,, 26 (wchar), ,,,POST Version,,NA,1.0,, 30 (wchar), ,,,CPU STATUS,,PASS,0x10000,, 36 (wchar), ,,,ETH0 TEST,,NOT 36 (wchar), ,,,ETH1 TEST,,NOT 36 (wchar), ,,,VDSP ENUM 36 (wchar), ,,,USBF ENUM 36 (wchar), ,,,USBH ENUM 30 (wchar), ,,,RTC VERIFY,,PASS,0x40001,, 35 (wchar), ,,,TOUCHCTL 38 (wchar), ,,,NORFLASH 36 (wchar), ,,,NANDFLASH 30 (wchar), ,,,LCD VERIFY,,PASS,0x70000,, 30 (wchar), ,,,SDRAM TEST,,PASS,0x80000,, 32 (wchar), ,,,System Cable,,PASS,0x90000,,

0:00:01.532.540 : Raw data 39 (wchar), ,,,UFN1: Initialize,,PASS,0x00000000,, 0:00:01.532.989 : Raw data 39 (wchar), ,,,HCD1: Initialize,,PASS,0x00000000,, 0:00:01.533.518 : Raw data 39 (wchar), ,,,HCD3: Initialize,,PASS,0x00000000,, 0:00:01.534.027 : Raw data 53 (wchar), ,,,Display Hardware,,PASS,Initialized Successfully,, 0:00:07.754.119 : Raw data 0:00:08.737.588 : Raw data 0:00:08.738.118 : Raw data Test,,PASS,,, 0:00:46.745.599 : Raw data 0:00:46.746.059 : Raw data 31 (wchar), ,,,PSTN,,FAIL,Initialization,, 31 (wchar), ,,,PSTN,,FAIL,Initialization,, 33 (wchar), ,,,ADSP Microphone 29 (wchar), ,,,Camera ID,,PASS,723308F,, 22 (wchar), ,,,Restarts,,PASS,0,, 83

0:00:46.746.553 : Raw data Dropped.,, 0:00:46.747.036 : Raw data Y ,, 0:00:46.747.496 : Raw data 0:00:46.747.936 : Raw data 0:00:46.749.127 : Raw data 0:00:46.749.719 : Raw data 0:00:46.750.187 : Raw data 0:00:01.526.107 : Raw data 0:00:01.527.626 : Raw data STATUS,,FAIL,0x30000,, 0:00:01.528.088 : Raw data STATUS,,FAIL,0x30001,, 0:00:01.528.539 : Raw data STATUS,,FAIL,0x30002,, 0:00:01.528.965 : Raw data 0:00:01.529.756 : Raw data VERIFY,,FAIL,0x40000,, 0:00:01.530.671 : Raw data VERIFY,,FAIL,0x60000,, 0:00:01.531.213 : Raw data 0:00:01.531.646 : Raw data 0:00:01.532.087 : Raw data

40 (wchar), ,,,Video Port,,PASS,0 Frames 35 (wchar), ,,,Camera Video,,PASS,Y Y Y Y 29 (wchar), ,,,I2C Status,,PASS,OK 0 C,, 26 (wchar), ,,,Calibration,,PASS,OK,, 28 (wchar), ,,,White Balance,,FAIL,NO,, 19 (wchar), ,,,POST,,PASS,OK,, 27 (wchar), ,,,Stack Health,,PASS,OK,, 30 (wchar), ,,,CPU STATUS,,FAIL,0x10000,, 36 (wchar), ,,,VDSP ENUM 36 (wchar), ,,,USBF ENUM 36 (wchar), ,,,USBH ENUM 30 (wchar), ,,,RTC VERIFY,,FAIL,0x40001,, 35 (wchar), ,,,TOUCHCTL 36 (wchar), ,,,NANDFLASH 30 (wchar), ,,,LCD VERIFY,,FAIL,0x70000,, 30 (wchar), ,,,SDRAM TEST,,FAIL,0x80000,, 32 (wchar), ,,,System Cable,,FAIL,0x90000,,

A hardware failure can be identified by a FAIL in the following entries:

0:00:01.532.540 : Raw data 39 (wchar), ,,,UFN1: Initialize,,FAIL,0x00000000,, 0:00:01.532.989 : Raw data 39 (wchar), ,,,HCD1: Initialize,,FAIL,0x00000000,, 0:00:01.533.518 : Raw data 39 (wchar), ,,,HCD3: Initialize,,FAIL,0x00000000,, 0:00:01.534.027 : Raw data 53 (wchar), ,,,Display Hardware,,FAIL,Initialization failed,, Note: The CE logs are not localized because they are required for debugging by Microsoft developers. 84

Errata in the RoundTable CE log

The CE log contains a harmless incorrect entry, similar to the following: 0:00:01.530.221 : Raw data VERIFY,,FAIL,0xFFFFFFFF,, 38 (wchar), ,,,NORFLASH

The NORFLASH VERIFY test is not run and does not have to be run. If there is a NORFLASH failure, the RoundTable device will not start.

Diagnostics Logging
If the Log to the server field is checked in the Logging section of the RoundTable device configuration, the device writes self-diagnostic data to the Microsoft Office Communications Server 2007 Update Service. For the file name and location of the log, see the documentation for Office Communications Server 2007 Update Service.

Diagnostics Log Schema

The following table lists the column names and their data types by column number. Data in the diagnostics log is comma-delimited. Diagnostic log schema names by column number
Column Number Column Name and Data Type

1 2 3 4 5 6 7 8 9 10 11 12 13 14

DeviceType (varchar(32)) Date Time (datetime) ID (varchar(32)) (Product ID from Microsoft RoundTable) LoggingType (Error/Health/Debug/POST) Device Name (varchar(32)) Component (varchar(32)) (Hardware | System | Video | Audio) SubComponent1 (varchar(32)) SubComponent2 (varchar(32)) SubComponent3 (varchar(32)) Property (varchar(32)) Value1 (varchar(64)) Value2 (varchar(64)) Value3 (varchar(64)) Value4 (varchar(64)) 85

Column Number

Column Name and Data Type

15

Value5 (varchar(64))

Interpreting Diagnostics Logs

The RoundTable diagnostics logs fall into three LoggingType categories: POST, Health, and Image Update. Power-on self-test (POST) diagnostics consist of information generated when the device is powered on. Health diagnostics relate to the health of the device, with regard to either system performance or resource usage. Image update diagnostics relate to updating the device firmware.

LoggingType == POST
RoundTable powers on and performs a POST. The following table shows the columns that are used, together with the values that are logged. The three values of Component represent the system, audio digital signal processor, and video digital signal processor. Columns and values used in POST logging
Physical Column Value Logged

Device Type Date Time ID LoggingType Device Name Component

RoundTable Value of [Date Time] Value of [Product ID] POST Value of [Device Name] System | ADSP | VDSP

When Component = System, only the Property, Value2, and Value3 columns are used. The Property column contains the name of the test. The Value2 column contain the status (PASS | FAIL | NOT DONE | NA). The Value3 column contains the detailed status code. These entries indicate the general health of the system. Note that some entries are reserved for system use. The following table shows the possible values in the Property, Value2, and Value3 columns when the Component value is System. Properties and values for POST logging, Component == System
Property Value2 Value3

ADSP Microphone Test CPU STATUS Display Hardware

PASS | FAIL PASS | FAIL PASS | FAIL

NULL Status code Detailed status 86

Property

Value2

Value3

ETH0 TEST ETH1 TEST FIRMWARE CURRENT REV FIRMWARE FACTORY REV

NOT DONE NOT DONE Not applicable Not applicable

Reserved Reserved Reserved Revision number for factory default version of EBOOT.bin in the format of 1.0.xxxx.x Revision number for working version of EBOOT.bin in the format of 1.0.xxxx.x Status code Status code Status code Status code Reserved Revision number for working version nk.bin in the format of 1.0.xxxx.x Reserved Initialization Status code Status code Status code Status code Status code Status code Status code Status code

FIRMWARE REV

Not applicable

HCD1: Initialize HCD3: Initialize LCD VERIFY NANDFLASH VERIFY NORFLASH VERIFY OS REV

PASS | FAIL PASS | FAIL PASS | FAIL PASS | FAIL NOT DONE Not applicable

POST Version PSTN RTC VERIFY SDRAM TEST System Cable TOUCHCTL VERIFY UFN1: Initialize USBF ENUM STATUS USBH ENUM STATUS VDSP ENUM STATUS

Not applicable PASS | FAIL PASS | FAIL PASS | FAIL PASS | FAIL PASS | FAIL PASS | FAIL PASS | FAIL PASS | FAIL PASS | FAIL

When component = VDSP, only the Property, Value2, and Value3 columns are used. The Property column contains the name of the test. The Value2 column contains the status (PASS | FAIL | NOT DONE | NA). The Value3 column contains the detailed status code. These entries indicate the general health of the video subsystem. 87

The following table shows the possible values in the Property, Value2, and Value3 columns when the Component value is VDSP.

Properties and values for POST logging, Component == VDSP

Property Value2 Value3

Calibration Camera ID Camera Video

PASS | FAIL PASS | FAIL PASS | FAIL

OK | FAIL The camera ID XXXXX The health of each of the five cameras. X can be Y or N, with Y = Pass and N = Fail

I2C Status POST Restarts Stack Health Video Port White Balance

PASS | FAIL PASS | FAIL PASS | FAIL PASS | FAIL PASS | FAIL PASS | FAIL

OK | FAIL OK | FAIL Number of restarts since boot OK | FAIL X Frames Dropped. YES | NO (Expect yes)

When Component = ADSP, only the Property, Value2, and Value3 columns are used. The Property] column contains the name of the test. The Value2 column contain the status (PASS | FAIL | NOT DONE | NA). The Value3 column contains the detailed status code. These entries indicate the general health of the initialization phase of the audio sub-system. The following table shows the possible values in the Property, Value2, and Value3 columns when the Component value is ADSP. Property and values for POST logging, Component == ADSP
Property Value2 Value3

ADSP FBAB POST

PASS | FAIL

Detailed status

Logging Type == Health

There are two types of health logging: system performance and usage. This section discusses system performance logging. Usage logging is discussed in the next section. System performance refers to memory usage, system uptime, and health of the audio digital signal processor. The following table shows the columns used and values logged in health logging. 88

Columns and values that are used in system performance logging

Physical Column Value Logged

DeviceType Date Time ID LoggingType Device Name

RoundTable Value of [Date Time] Value of [Product ID] Health Value of [Device Name]

For performance logging, only the Component, Subcomponent, Property, and Value1 columns are used. The following table shows the possible values of these columns for System (either memory usage or uptime) and for audio digital signal processor (ADSP) health. Possible values for Component, Subcomponent, Property, and Value1 Columns
Component Subcomponent Property Value1

System System ADSP

Name of exe to which the property applies. NULL NULL

MemoryUsage Uptime ADSP HEALTH

Usage in bytes Uptime since boot nI2CStatus:<#> : nSPIErrorCounts: <#> : nSPILastError: <#> : nI2SReadGlitchCount: <#> : nI2SWriteGlitchCount: <#> :

This section discusses usage logging. The following table shows the columns and values that are used when LoggingType == Health and Property == Usage. Columns used in usage logging
Physical Column Value Logged

DeviceType Date Time ID LoggingType

RoundTable Value of [Date Time] Value of [Product ID] Health 89

Physical Column

Value Logged

Device Name

Value of [Device Name]

The following table shows the columns and values that are used in usage logging. This type of usage logging uses the Component, Property, Value1, Value2, Value3, Value4, and Value5 columns. The Value3 value is the session type, which can be one of PcAudio, PcVideo, or PstnCall. When VoIP is used with Microsoft RoundTable, a PcAudio usage entry is logged with the start time and end time. When video streams are used in Microsoft RoundTable, a PcVideo usage entry is logged with the start time and end time. When Microsoft RoundTable is used as an analog phone, a PstnCall usage entry is logged with the start time, end time, originating phone number (configured in the RoundTable device configuration), and the first digit of the dialed phone number. Values used in usage logging when Component == System
Component Property Value1 Value2 Value3 Value4 Value 5

System System System

Usage Usage Usage

Start time Start time Start time

End time End time End time

PcAudio PcVideo PstnCall

Null Null Phone number of the originating RoundTable First digit of dialed number

Note: To create a report about usage, import the diagnostics log on to a database and create a view of all records where Component = System and Property = Usage.

Logging Type == Image Update

The following table shows the columns used and values logged when LoggingType == Image Update.

Columns and values that are used in Image UpdateLogging

Physical Column Value Logged

DeviceType Date Time ID LoggingType Component

RoundTable Value of [Date Time] Value of [Product ID] Image Update System 90

Physical Column

Value Logged

SubComponent1 SubComponent2 SubComponent3 Property Value1 Value2 Value3 Value4 Value5

<NULL> <NULL> <NULL> Version Value of [EBOOT Version] Value of [Nk.bin Timestamp] Value of [Config Timestamp] Value of [Last Update Time] Value of [Image Update Success/Fail]

Dr. Watson Logs

Dr. Watson is a program error troubleshooting tool that traps program faults (that are running in ring three of the processor), and generates a snapshot of the operating system that you can use to diagnose the fault. If the Log to the server field is checked in the Logging section of the RoundTable device configuration, the device automatically logs to the same server if there is a crash. The dump files are in kdmp format. IT Pros can submit these logs to Microsoft Customer Service and Support to file bug reports. The dump files can be read using Windows CE Dump Viewer. For more information, see http://go.microsoft.com/fwlink/?linkid=147114. The path of the Watson logs on the server is under the \RTLogs\DiagLogs\ directory. The Watson log files encode the device serial number, the date, and the software revision number in the following naming convention: <Device Serial Number>-YYYY-MM-DDHHMMSS-WATSON1.0.<Device Software Revision Number>.0.kdmp. An example Watson log file is 78491-3220002937-00652-2007-06-08151023-WATSON-1.0.3626.0.kdmp.

Diagnosing Live Meeting 2007

When you encounter sustained and reproducible audio quality problems, you can capture audio traffic signals, which a support team can use to diagnose the problem. These signals are drawn from the original audio signal that the user either sends or receives. The signal is captured by sub-sampling the speech waveform by a factor of 40, meaning that only 1 out of 40 consecutive samples is retained in the audio records. In addition, the 16-bit samples are quantized to 8-bit samples. No other type of data processing, data encryption, or data scrambling is applied. 91

This feature is typically used for a peer-to-peer test call and is turned off after testing is complete. Remember to comply with legal requirements related to privacy and to sampling conversations. This feature is also available in Communicator. For more information, see the Microsoft Office Communicator 2007 R2 Deployment Guide at http://go.microsoft.com/fwlink/?linkid=140471. To join the local Performance Log Users group 1. Click Start, right-click Computer, and then click Manage. 2. Expand System Tools, expand Local Users and Groups, and then click Groups. 3. Right-click Performance Log Users, click Add to Group, and then click Add. 4. Type your domain account, click Check Names, and then click OK. 5. Restart the Live Meeting client. To enable the audio capture feature for the Live Meeting client 1. Click Start, and then click Run. 2. In the Open box, type REGEDIT, and then click OK to start Registry Editor. 3. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Tracing\WPPMedia. 4. Create a new registry key named DebugUI. 5. Create a property named TraceLevelThreshold, right-click the new property, and then click Modify. 6. Select Decimal, enter a value of 5, and then click OK. 7. Create a property named WPP_FLAG_S_DEBUGUI_AEC_PCM, right-click the new property, and then click Modify. 8. Right-click the property, and then select Modify. 9. Select Decimal, enter a value of 1, and then click OK. 10. Exit Registry Editor. 11. Start the Office Live Meeting client. Data is captured in a circular buffer, which is 20 MB by default. This limits the size of the file that will be saved in the file system. If the capture exceeds the size of the buffer, the old data will be overwritten starting at the beginning of the buffer. At 20 MB, the maximum amount of audio data saved in the file is approximately two hoursabout 1 MB for every 6 seconds of audio. By default, the audio samples are written to the following file: C:\Users\username\Tracing\WPPMedia\LiveMeeting_rtmdebug.etl The path and filename are specified in the following registry properties: HKEY_CURRENT_USER\Software\Microsoft\Tracing\WppMedia\Debug\WPPFilePath HKEY_CURRENT_USER\Software\Microsoft\Tracing\WppMedia\Debug\WPPFileName When the test is complete, disable the audio capture and send your audio files to Microsoft. To disable the audio capture feature for the Live Meeting client 1. Click Start, and then click Run. 2. In the Open box, type REGEDIT, and then click OK to start Registry Editor.

92

3. Navigate to the HKEY_CURRENT_USER\Software\Microsoft\Tracing\WPPMedia\DebugUI key. 4. Right-click DebugUI, and then click Delete.

Diagnosing Communicator Mobile

Watchdog is a diagnostic tool that is used by Communicator Mobile to recover from unexpected failures. The Watchdog applications is started in the following scenarios: Watchdog is scheduled to run every four hours When a user updates their preferences, and Remember Password and Automatically sign me in are set. When the Communicator Mobile application crashes or exits abruptly. After the device restarts and Automatically sign me in is set. The Watchdog application will launch Communicator Mobile. This is done to optimize system performance afer the device restarts by delaying the Communicator Mobile launch process. The key benefits of the Watchdog application include: It restarts the Communicator Mobile application if it has crashed or exited abruptly. It delays start of the Communicator Mobile launch process after a device reboot. It waits approximately 2 minutes after a device is rebooted before it attempts to relaunch Communicator Mobile. It checks system metrics (battery life >= 10%, and physical memory available >= 15MB) before it attempts to start Communicator Mobile. The Watchdog program settings are configured on the Accounts tab on the Options page. Watchdog runs automatically when both Remember password and Automatically sign me in are checked. When Communicator Mobile preferences are updated on the Options page, Watchdog reschedules itself to run every four hours from the time that the preferences were updated. To prevent Communicator Mobile from starting when the device is restarted, clear the Automatically sign me in check box on the Accounts tab. Users who want to conserve all available resources on their mobile device must turn off Watchdog by clearing the Automatically sign me in check box. If the Automatically sign me in check box is not cleared, Watchdog continues to run and will restart Communicator Mobile at its next scheduled time. If the mobile device is restarted, Watchdog restarts Communicator Mobile. If Communicator Mobile is closed by using the CTRL-Q key sequence or by using Task Manager, Watchdog restarts the program at its next scheduled interval, which is typically four hours from the last preference update. Watchdog supports the high availability goals of Communicator Mobile. When Communicator Mobile is set to start automatically, Watchdog analyzes the resources of the mobile device by 93

checking for low memory conditions before starting the application. Until the Automatically sign me in check box is cleared, it will continue to try to start Communicator Mobile. If you know that you do not want Communicator Mobile started on your mobile device (for example, you are on vacation or roaming), you must clear this check box.

94