Planning, Deploying, and Administering Office Communications Server 2007 R2, Extensible Messaging and Presence Protocol (XMPP) Gateway
Published: September 2009
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.
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.
Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred.
® 2009 Microsoft Corporation. All rights reserved.
Microsoft, Windows, Windows Server, Active Directory, and Visual C++ are trademarks of the Microsoft group of companies.
All other trademarks are property of their respective owners.
Planning, Deploying, and Administering Office Communications Server 2007 R2, Extensible Messaging and Presence Protocol (XMPP) Gateway i
How to Use This Document 4
Terms and Concepts 5
Planning for XMPP Gateway 6
Topology Overview 6
Capacity Planning 10
User Experience 10
Prerequisites for Installation 11
Infrastructure Requirements 11
System Requirements 12
Deploying XMPP Gateway 13
Installing XMPP Gateway 13
Configuring Gateway IP 23
Configuring DNS Entries 24
Configuring Edge Server 27
Configuring XMPP Server 29
Achieving High Availability 29
Administering XMPP Gateway 30
Using the XMPP Gateway Snap-in 30
Start, Stop, or Restart the XMPP Gateway Service 31
SIP Configuration 31
XMPP Configuration 34
Security Settings 40
Configuring Additional Settings 44
Office Communications Server 2007 R2, Extensible Messaging and Presence Protocol (XMPP) Gateway enables users to share presence information and communicate via instant messaging (IM) between Office Communications Server and XMPP-based providers and servers, such as Google Talk and Jabber. After XMPP Gateway is deployed in an Office Communications Server environment, users hosted on Office Communications Server can do the following:
Add or delete users of an XMPP environment as contacts.
Communicate with users of an XMPP environment through one-on-one IM conversations.
For details about XMPP Gateway, see http://go.microsoft.com/fwlink/?LinkID=141529.
This document describes how to plan, install, configure and manage XMPP Gateway. It contains the following sections:
Introduction (this section) provides information about how to use this document and a glossary of the term and concepts used in the document.
Planning for XMPP Gateway provides the topology overview, supportability, capacity planning, and user experience information for XMPP Gateway.
Prerequisites for Installation provides the infrastructure and system prerequisites for installing XMPP Gateway.
Deploying XMPP Gateway provides a step-by-step guide to installing XMPP Gateway, configuring Domain Name System (DNS) entries for gateway, and configuring Edge Server and XMPP servers. This section also discusses high availability.
Administering XMPP Gateway describes configuration settings available on XMPP Gateway.
References provides links to additional information about the topics covered in this document.
Terms and Concepts
Access Edge Service. An Office Communications Server 2007 service in the perimeter network that validates incoming Session Initiation Protocol (SIP) traffic then forwards the IM traffic between internal and external users.
contoso.com. A fictitious company Contoso, Ltd, which supports SIP domains of ocs.contoso.com, ocs.contoso.com and XMPP domain of xmpp.contoso.com.
Edge Server. An Office Communications Server role that resides in the perimeter network and provides connectivity for external users and public IM connections.
External user. A user connecting from outside the corporate firewall. External users include anonymous users, federated users, and remote users.
fabrikam.com. The domain name of a fictitious company, Fabrikam, Inc., which supports XMPP domain of fabrikam.com.
Federated user. An external user who possesses valid credentials with a federated partner and who, therefore, is treated as authenticated by Office Communications Server.
FQDN. Fully qualified domain name.
Front End Server. An Office Communications Server 2007 server in the internal network that hosts the IM Conferencing service, Address Book service, and Telephony Conferencing service to support registration, presence, IM, and conferencing. This server role is available on a Standard Edition server. In an Enterprise pool, it can be collocated with the Web Conferencing Server and A/V Conferencing Server, or can be deployed on a separate server.
GUI. Graphical user interface.
litwareinc.com. The domain name of a fictitious company, Litware, Inc., which supports XMPP domain of litwareinc.com.
MMC. Microsoft Management Console.
SASL. Simple Authentication and Security Layer (SASL) is a framework for authentication and data security in Internet protocols.
SIP. Session Initiation Protocol, a signaling protocol.
SIP domain. The domain portion of a user’s SIP Uniform Resource Identifier (URI) used by Office Communications Server to direct communications. For example, if Bob’s SIP URI is email@example.com, contoso.com is the SIP domain.
XMPP. Extensible Messaging and Presence Protocol.
XMPP domain. The domain portion of a user’s XMPP URI used by XMPP Server to direct communications. For example, if John’s XMPP URI is firstname.lastname@example.org, fabrikam.com is the XMPP/allowed domain.