Nortel Networks NN43001-121 User Manual

Nortel Communication Server 1000

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

NN43001-121

Document status: Standard Document version: 01.03 Document date: 30 April 2008

LEGAL NOTICE While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing. NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice.

Nortel, the Nortel logo, the Globemark, Meridian 1, and Succession are trademarks of Nortel Networks. All other trademarks are the property of their respective owners. Sourced in Canada

Contents

New in this release 9

Ofﬁce Communications Server 2007 features 9 Other changes 9

How to get help 11

Getting help from the Nortel web site 11 Getting help over the telephone from a Nortel Solutions Center 11 Getting help from a specialist by using an Express Routing Code 11 Getting help through a Nortel distributor or reseller 12

Introduction 13 Converged Ofﬁce component overview 15

Converged Ofﬁce 15 Enterprise Voice 17 OCS 2007 Voice components 18 Media Gateways 19 Mediation Server 20 Remote Call Control with SIP CTI (TR/87) 22 Telephony Gateway and Services 23 Personal Call Assistant 25 Access Edge Server 27 OCS 2007 snap-in 27 Multimedia Convergence Manager 28 CDR data collection 28 SIP CTI (TR/87) Protocol 29 Hardware Load Balancer 31 Ofﬁce Communicator 2007 32 Documentation References 32

Revision History 10

Planning and engineering 35

Planning process 35 Network conﬁguration 36

Multiple customer network 40 Multiple location network 42

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

4 Contents

Load Balancer planning 43

Load Balancer requirements 44 Redundancy with Load Balancers 45 Nortel Application Switch 46

Capacity planning 46

OC 2007 client requirements 47 Load Balancer capacity requirements 47 SIP CTI (TR/87) services requirements 47 Mediation server requirements 49 Signaling Server requirements 49 Call Server requirements 50 OCS Proxy and MCM capacity requirements 50

General requirements 51

Server topology 52 Operating System Requirements 52 Hardware Requirements 53 Virtual Server 2005 54 Storage 55 Trunks 55 Basic Client Conﬁguration 58 Port use 58 Security 59 Dial Plan considerations 61 Number formats supported by Ofﬁce Communicator 63 E.164 international format numbers for SIP Gateway and SIP CTI 66

Telephony Gateway and Services planning 66

Systems, platforms, and applications 66 Remote Call Control with SIP CTI 73 LCS 2005 and OCS 2007 coexistence 82

Client considerations 82

Converged Ofﬁce functionality 82

MCM 2.0 to MCM 3.0 84

Load balancer considerations 84 Migration planning from LCS 2005 to OCS 2007 84

Determine your deployment options 86

Migration process 86

Description of Migration Phases 88 Uniﬁed Messaging 90

OCS 2007 users using CallPilot 90

OCS 2007 users using UM 2007—integrated 92

OCS 2007 users using UM 2007—non-integrated 95

Signaling with integrated Voice Mail 97

Signaling with non-integrated Voice Mail 98

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

Contents 5

Installation 101

OCS 2007 installation preparation and deployment 103 CS 1000 and Signaling Server installation 105 OCS 2007 component installation 105 OCS Proxy server installation 107 Load Balancer installation 108 MCM installation 109

Conﬁguration 111

Active Directory conﬁguration 112 Ofﬁce Communications Server conﬁguration 119

Load Balancer conﬁguration 120

Voice Properties conﬁguration 120

OCS conﬁguration procedures 122

Conﬁguration of Static Routes 122

Host Authorization and Routing conﬁguration 122

Mediation Server conﬁguration 133 MCM 3.0 conﬁguration 134

MCM architecture 135

MCM Direct conﬁguration 137

MCM management console 137 Telephony Gateway and Services conﬁguration 150

Call Server conﬁguration 151

Conﬁguring the Codec 151

Loss Plan conﬁguration 152

Dialing Plan conﬁguration to route to MCM 153

Conﬁguring the Personal Call Assistant 154

Caller ID table conﬁguration 157

Home LOC and Home NPA conﬁguration 159

DNS Server conﬁguration 159

SIP Trunk conﬁguration 160

Domain naming 163

URI Mapping 165

SIP Gateway CLID Parameters conﬁguration 167

SPS conﬁguration 168

NRS conﬁguration 169

CDR conﬁguration 170

E.164 International Format Numbers from Ofﬁce Communicator - Computer

Calls (SIP Gateway) 170

Phone number normalization 171 Remote Call Control conﬁguration 171

Remote Call Control and PBX integration 171

RCC and PBX integration on OC client 172

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

6 Contents

CS 1000 conﬁguration 173

Signaling Server conﬁguration 177

SIP CTI Services conﬁguration settings 181

SIP CTI CLID conﬁguration parameters 185

Conﬁguring the SIP URI Map 189

Conﬁguring CDR 190

Dialing E.164 International Format Numbers from Ofﬁce Communicator - Phone

Calls (SIP CTI) 190 Normalizing phone numbers 192 SIP Routing and Redundancy conﬁguration 198 OCS 2007 users using UM 2007 in integrated mode 198

Option 1 adding user Alias as Exchange UM 198 Option 2 adding CS 1000 DN as Exchange UM 203

Maintenance 209

Introduction 209 Communication Server 1000 209 MCM 3.0 209 Remote Call Control 210

Operational Measurements for SIP CTI 212

Troubleshooting 215

Checking Telephony Gateway (SIP Gateway) conﬁguration 215 Checking Remote Call Control (SIP CTI) conﬁguration 216 Lack of memory on Signaling Server 216 SIP CTI services does not come up 217

SIP Dialog not established 217 Solution 1: Check conﬁguration parameters in AD 218 Solution 2: Conﬁrm FQDN and the IP address are correct 218 SIP CTI service is down 218

MCM not synchronizing new users in AD Cache mode 220

Solution 1: Check the Global Catalog content manually 220 Solution 2: Access permissions for the AD object properties 221

Solution 3: Enable propagation of the AD to the Global Catalog 222 OC client not registered 223 Pop-up not displayed 223 Two pop-ups are displayed 224 Delay for a SIP Gateway call 224 Call Forward is cancelled by Ofﬁce Communicator 224 Ofﬁce Communicator disconnecting from the network 225 Capturing traces and logs 225

Communication Server 1000 traces 225

AML traces on the Call Server (SIP CTI only) 226

SIP CTI traces on the Signaling Server 226

SIP Gateway traces on the Signaling Server 227

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

Contents 7

MCM logs 228

Activating MCM logging 229

OCS logs 231 Case checklists 234

Appendix A Call Flow and protocol details 237

Contents 237 Overview 237 Message sequence 238 Call ﬂow 239

Telephony Gateway and Services call ﬂow 239 Supported features 246

Appendix B Conﬁguration Examples 249

Contents 249 Introduction 249 Standard Edition 249

Setting up the lab 250

Collecting required data 251

Conﬁguring the Call Server 252

Signaling Server checklist 262

Active Directory user conﬁguration 269

Checking the MCM installation and conﬁguration 272 Enterprise Edition 275

Overview of general lab set-up 275

OCS Management Console 278

Security/Certiﬁcates 282

Host Authorization 283

Routing 284

Conﬁguring DNS 286

Active Directory conﬁguration 288

Installing and conﬁguring MCM 289

Signaling Server checklist 292

Conﬁguring NRS 293

Normalizing Phone Numbers 295

Appendix C Abbreviations 297 Procedures

Procedure Migrating users from LCS to OCS 89 Procedure Installing the OCS Proxy server 108 Procedure Installing the Load Balancer 108 Procedure Installing MCM 3.0 109 Procedure Deﬁning users 114 Procedure Conﬁguring the Host Authorization and Routing for the OCS

Procedure Conﬁguring host authorization for the OCS Proxy 126

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Front End server 123

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

8 Contents

Procedure Conﬁguring a Mediation Server 133 Procedure Enabling replication to the Global Catalog 146 Procedure Conﬁguring the SIP Trunk Domain name 164 Procedure Enabling Remote Call Control and PBX integration 171 Procedure Adding a new normalization rule 195 Procedure Conﬁguring a basic mailbox for the UM user 199 Procedure Adding user Alias as Exchange UM 199 Procedure Conﬁguring a basic mailbox for the UM user 203 Procedure Adding Exchange UM 204 Procedure Checking Telephony Gateway conﬁguration 215 Procedure Checking Remote Call Control conﬁguration 216 Procedure Reconﬁgure SIP CTI service 219 Procedure Checking the Global Catalog content manually 221 Procedure Accessing permissions for the AD object properties 222 Procedure Enabling propagation of the Active Directory ﬁeld to the Global

Catalog 223 Procedure Resetting MCM debug trace 231 Procedure Activating OCS logs 232 Procedure Enabling OC logs 232 Procedure Setting up the lab 250 Procedure Checking the Call Server conﬁguration 252 Procedure Checking the conﬁguration of the Signaling Server 262 Procedure Checking NRS conﬁguration 266 Procedure Checking the settings of Active Directory user

conﬁguration 269 Procedure Checking the MCM installation and conﬁguration 273 Procedure Identifying the active default applications 280 Procedure Checking the conﬁguration of Certiﬁcates 282 Procedure Checking the conﬁguration of Host Authorization 283 Procedure Checking that Routing is correctly conﬁgured 284 Procedure Checking that DNS is correctly conﬁgured 286 Procedure Checking that MCM is correctly installed and conﬁgured. 290 Procedure Checking that the Signaling Server is correctly conﬁgured 293 Procedure Checking that NRS is correctly conﬁgured 293

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

New in this release

Ofﬁce Communications Server 2007 features

Signaling trafﬁc between Communication Server 1000 and Ofﬁce Communications Server 2007 is supported by Multimedia Convergence Manager (MCM) 3.0 . Media trafﬁc is supported through the Mediation Server.

The following list shows new Ofﬁce Communicator 2007 client features for Voice over IP (VoIP) mode:

•

Conference Call

•

Announced (Consulted) Call Transfer

•

Call Forward

•

Call Redirect (Deﬂect)

•

Dual Forking

•

DoNotDisturb (DND)

•

Federated calls

Other changes

•

The Mediation Server is introduced in OCS 2007 as a new component. For more information about the Mediation Server, see"Mediation Server"

(page 20). Due to the introduction of the Mediation Server, the following

changes occur: — Transport Layer Security (TLS) and Secure Real-Time Transport

Protocol (SRTP) are not supported.

— OCS 2007 can talk to the Communication Server 1000 over a

Transport Control Protocol (TCP) or Transport Layer Security (TLS) link. TLS transport is supported between MCM/OCS Proxy and CS 1000/SPS.

— Video support for Session Initiation Protocol (SIP) gateway calls is

not supported. Direct VOIP to VOIP and RCC to RCC calls can use video. For more information, see "Feature Interactions" (page 68).

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

10 New in this release

•

• The 8540 OCS desk phone can register as an OC 2007 client, however,

— SIP UPDATE method is not supported by Mediation Server. This

method enables SIP Gateways and Endpoints to update the call information during a call. Because the OCS 2007 Mediation Server does not support UPDATE, re-INVITE’s need to be sent to the Mediation Server for every change in the call information during a call. This has not changed since LCS 2005. There were no interoperability issues.

— G.711 codec for the short leg (Mediation Server to Communication

Server 1000) and RT audio for the long leg of a call (Mediation Server to OCS) is supported.

The NortelMultimedia Convergence Manager (MCM) 3.0 is introduced in Converged Ofﬁce. For more information, see "Multimedia Convergence

Manager (MCM)" (page 28).

OCS 2007 snap-in for MMC. For more information, see "OCS 2007

snap-in" (page 27).

Microsoft does not support using a CS 1000 twin phone with them.

Revision History

April 2008 Standard 01.03. This document is up-issued to correct the

syntax in the Installing the OCS Proxy section.

January 2008

Standard 01.02. This document is up-issued for new content to address CRs, Uniﬁed Messaging, and LCS to OCS migration.

December 2007

Standard 01.01. This is a new document for Converged Ofﬁce with Microsoft Ofﬁce Communications Server 2007.

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

How to get help

This chapter explains how to get help for Nortel products and services.

Getting help from the Nortel web site

The best way to get technical support for Nortel products is from the Nortel Technical Support web site:

ww.nortel.com/support

This site provides quick access to software, documentation, bulletins, and tools to address issues with Nortel products. From this site, you can:

•

download software, documentation, and product bulletins

•

search the Technical Support Web site and the Nortel Knowledge Base for answers to technical issues

•

• open and manage technical support cases

Getting help over the telephone from a Nortel Solutions Center

If you do not ﬁnd the information you require on the NortelTechnical Support web site, and you have a Nortel support contract, you can also get help over the telephone from a Nortel Solutions Center.

In North America, call 1-800-4NORTEL (1-800-466-7835). Outside North America, go to the following web site to obtain the telephone

number for your region:

ww.nortel.com/callus

Getting help from a specialist by using an Express Routing Code

To access some NortelTechnicalSolutions Centers, you can use an Express Routing Code (ERC) to quickly route your call to a specialist in your Nortel product or service. To locate the ERC for your product or service, go to:

ww.nortel.com/erc

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

12 How to get help

Getting help through a Nortel distributor or reseller

If you purchased a service contract for your Nortel product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller.

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

Introduction

This document describes the elements and processes necessary to integrate Nortel Communication Server 1000 (CS 1000) with the Ofﬁce Communications Server 2007 (OCS 2007) in the Nortel Converged Ofﬁce.

Prerequisites

•

Ensure CS 1000 Release 5.0 and the Product Enhancement Package is installed.

•

Microsoft supportsthe coexistenceof LCS 2005 SP1 Standard Edition or Enterprise Edition with OCS 2007 Standard Edition or Enterprise pools. For more information, see "LCS 2005 and OCS 2007 coexistence"

(page 82).

Introduction navigation

•

"Converged Ofﬁce component overview" (page 15)

•

"Planning and Engineering" (page 35)

• "Installation " (page 111)

•

"Conﬁguration" (page 119)

•

"Maintenance" (page 209)

•

"Troubleshooting" (page 215)

•

Appendix "Call Flow and protocol details" (page 237)

•

Appendix "Conﬁguration Examples" (page 249)

•

Appendix "Abbreviations" (page 297)

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

14 Introduction

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

Converged Ofﬁce component overview

This chapter provides a brief technical description of all the components associated with Nortel Converged Ofﬁce.

Component overview navigation

•

"Converged Ofﬁce " (page 15)

•

"Enterprise Voice " (page 17)

•

"OCS 2007 Voice components" (page 18)

•

"Media Gateways" (page 19)

•

"Mediation Server" (page 20)

•

"Remote Call Control with SIP CTI (TR/87)" (page 22)

•

"Telephony Gateway and Services" (page 23)

• "Personal Call Assistant (PCA)" (page 25)

•

"Access Edge Server" (page 27)

•

"OCS 2007 snap-in" (page 27)

• "Multimedia Convergence Manager (MCM)" (page 28)

•

"CDR data collection" (page 28)

•

"SIP CTI (TR/87) Protocol" (page 29)

• "Hardware Load Balancer" (page 31)

•

"Ofﬁce Communicator 2007" (page 32)

•

"Documentation References" (page 32)

Converged Ofﬁce

Many Nortel CS 1000 customers base their multimedia strategy on deploying Ofﬁce Communications Server (OCS) 2007 and the Ofﬁce Communicator (OC) 2007 soft clients.

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

16 Converged Ofﬁce component overview

The Nortel Converged Ofﬁce feature combines the business-grade telephony of the CS 1000 with the OCS 2007 Enterprise Voice solution to offer a powerful converged ofﬁce solution set that improves worker productivity. Telepresence and Multimodal (business set Voice over Internet Protocol (VoIP), Instant Messaging (IM), and e-mail) communications bundles, with applications such as Click-to-call and Access mobility, allow workers to stay connected when not at their desks.

Nortel Converged Ofﬁce comprises the following components:

•

Remote Call Control (RCC) with Session Initiation Protocol Computer Telephony Integration (SIP CTI) (TR/87) provides full Microsoft Ofﬁce telephony integration to control business-grade telephony phones from within Microsoft Ofﬁce applications, as well as support for a standards-based CTI interface deﬁned by the TR/87 protocol.

•

Telephony Gateway and Services provides a basic SIP Telephony Gateway to connect between Private and Public Telephony networks and OC 2007 clients.

Nortel offers unique value with the two components that provide its telephony services to OC 2007 clients and connectivity between the Ofﬁce Communications Server 2007 and the Nortel telephony network.

Nortel Converged Ofﬁce provides the following beneﬁts:

•

federated IM with industry name instant messaging

•

Microsoft application integration

•

click-to-call commands and missed call log

•

easy-to-use single soft client for IM, telepresence, and VoIP telephony presence integration with Microsoft desktop and applications

•

a powerful suite of Nortel applications which include: — Nortel Uniﬁed Messaging — Contact Center — Interactive Voice Response (IVR) — conferencing — click-to-call

Leveraging the CS 1000 and Microsoft desktop software allows end users to access business-grade telephony services on the Nortel CS 1000 from the Microsoft Ofﬁce Communicator desktop client. End users can:

•

originate and receive telephone calls over existing CS 1000 phones from an Ofﬁce Communicator (OC) 2007 desktop client.

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

•

Enterprise Voice

This section describes the Ofﬁce Communications Server (OCS) 2007 Enterprise Voice solution. The Nortel Converged Ofﬁce feature integrates the OCS 2007 with the CS 1000. For a description of the integrated network from the CS 1000 perspective, see "Network conﬁguration" (page 36). Enterprise Voiceis Microsoft’s software-powered VoIPsolution, a SIP-based implementation of IP telephony for the enterprise that does not rely on proprietary hardware investments. Enterprise Voice is a full-featured VoIP solution that includes connectivity to the PSTN gateways and interoperation with the CS 1000. Enterprise Voice, IM, group IM, enhanced presence, and audio-video conferencing together constitute the Microsoft Uniﬁed Communications solution.

The following ﬁgure shows the OCS 2007 Enterprise Voice components extracted from the overall OCS 2007 architecture. COMO refers to Communicator Mobile.

Enterprise Voice 17

originate and receive Public Switched Telephone Network (PSTN) calls from the Ofﬁce Communicator (OC) 2007 soft client when away from the ofﬁce.

take advantage of existing business telephony features on the CS 1000.

Figure 1 Enterprise Voice components - OCS 2007

When a user calls from an Enterprise Voice client by dialing or clicking on a contact name or number in OC 2007 or Outlook:

•

the OCS Front End server normalizes the number to the E.164 format, and invokes routing rules based on the location proﬁle and user policy, and directs the call to the appropriate Mediation Server

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

18 Converged Ofﬁce component overview

•

the Mediation Server performs all necessary media transcoding and routes the call to the IP-PSTN gateway.

•

the IP-PSTN gateway, based on topology, applies local or PBX dialing rules and passes the call to the PSTN or PBX

Enterprise Voice uses Real-Time Transport Protocol (RTP) for media. Like SIP, RTP is an InternetEngineering Task Force (IETF) standard. It deﬁnes a packet format to carry audio and video over IP networks.

Enterprise Voice uses SIP for signaling and RTP for media. In the OCS, SIP is used for IM, conferencing, presence subscriptions, video, and voice enabling Enterprise Voice clients to provide a common user experience across the communication modes.

Enterprise Voice is the Microsoft SIP–based implementation of IP telephony for the Enterprise.

SIP sessions can include the sharing of real-time media. However, SIP itself does not handle the actual media data, such as audio, video, and application sharing. This separation means that SIP and various media protocols can evolve independently.

OCS 2007 Voice components

The core routing components for Enterprise Voice reside on the following:

•

Standard Edition Server (in the role of Front End Server or Director)

•

Enterprise Edition Front End Server

Other core routing server components include

• Translation Service—translates a dialed number into E.164 format

based on the normalization rules deﬁned by the administrator.

•

Inbound Router—handles incoming calls according to user-speciﬁed preferences.

•

Outbound Router—routes calls to CS 1000 or PSTN destinations after it applies authorization rules to callers and determines the optimal media gateway to route each call.

OCS 2007 Front End or Director components essential for voice support, but are not voice components include

•

User Services—performs Reverse Number Look-up on the target phone number for incoming phone calls.

• User Replicator—extractsuser phone numbers from the Active Directory

for use by User Services and the Address Book Service.

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

•

Address Book Service—normalizes enterprise user phone numbers to E.164 format to provision user Contacts in Ofﬁce Communicator.

The following ﬁgure shows the components essential for voice support.

Figure 2 Core routing server components

Media Gateways 19

Media Gateways

Media gateways are third-party hardware components that provide a common interface between the Enterprise Voice infrastructure and the PSTN. Media gateways translate signaling and media between the PSTN and Enterprise Voice infrastructure.

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

20 Converged Ofﬁce component overview

Media gateways translate the following protocols between the circuit-switched PSTN network and the packet-switched Enterprise Voice infrastructure:

•

Signaling protocol—SS7 and other protocols on the PSTN translate to SIP for Enterprise Voice

•

Transport protocol—T-Carrier or E-Carrier on the PSTN convert to RTP or Secure Real-Time Transport Protocol (SRTP) for Enterprise Voice

From the Nortel perspective, the CS 1000 functions as a media gateway for the clients of the OCS 2007 server.

Mediation Server

The Mediation Server provides signaling and media translation between the Enterprise Voice infrastructure and a CS 1000 gateway.

Figure 3 CS 1000 and OCS 2007 logical network elements

The Mediation Server provides the following functions:

•

translates SIP over Transport Control Protocol (TCP) (on the CS 1000 gateway side) to SIP over mutual Transport Layer Security (TLS) on the Ofﬁce Communications Server side

•

encrypts and decrypts SRTP on the Ofﬁce Communications Server side

•

translates media streams (G.711) on the CS 1000 gateway side and RT Audio on the Ofﬁce Communication Server side

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

Mediation Server 21

•

connects clients outside the network to internal Interactive Connectivity Establishment (ICE) components, to enable media traversal of NAT and ﬁrewalls

•

acts as an intermediary for call ﬂows that a gateway does not support (such as calls from remote workers on an Enterprise Voice client)

The Mediation Server uses the following types of signaling:

•

For an inbound call from the CS 1000, the ms-call-source:non-ms-rtc SIP header is inserted by the Mediation Server.

•

For an inbound call from the CS 1000, the Mediation Server Back 2 Back User Agent (B2BUA) generates a Session Description Protocol (SDP) offer based on its capabilities in the OCS 2007.

•

For an inbound call from the CS 1000, the Mediation Server adds a phone-context attribute to a number that is not in E.164 format.

•

For an outbound call from an OC 2007 client, the Mediation Server Back 2 Back (B2B) terminates the dialog and originates a new dialog with the CS 1000. The From header is replaced with a phone number derived from the p-asserted-identity header.

•

OC 2007 single step transfer. The Mediation Server terminates the REFER message and returns the response code 202. The Mediation server sends an INVITE message. The Mediation Server does not forward the REFER message to the CS 1000.

Figure 4 Signaling and Media path between the OC client and CS 1000

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

22 Converged Ofﬁce component overview

Remote Call Control with SIP CTI (TR/87)

The CS 1000 and OCS 2007 integration feature allows clients of the two systems (Microsoft OCS 2007 and Nortel CS 1000) to communicate with each other. You can associate an OC Client, which connects to the OCS, with a CS 1000 line. You can perform operations on the CS 1000 line through the OC Client using Remote Call Control (RCC) often referred to as Phone-Mode. This feature allows for consistent access to RCC, service control and conﬁguration and telepresence functions across different endpoints supported by the CS 1000.

The Nortel Converged Ofﬁce Solution is implemented through an open interface to ensure that any CS 1000 feature supported through OC 2007 is also accessible to applications from other vendors and application developers who support these interfaces.

The SIP CTI (TR/87) protocol is on the CS 1000 Signaling Server. OC 2007 uses the TR/87 speciﬁcation to implement phone integration throughout the suite of Microsoft Ofﬁce applications. You cannot use Ofﬁce Communicator to invoke a feature that is not supported by the phone.

Example of RCC with SIP CTI (TR/87)

Figure 5 "Remote Call Control with SIP CTI (TR/87)" (page 23) shows

an example of a CS 1000 call to a mobile client. The following steps correspond to the numbers in the ﬁgure:

1. A user selects Call to Chris’ mobile phone number from the CS 1000 telephone.

2. The Ofﬁce Communications Server 2007 sends a call request to the CS 1000.

3. The CS 1000 sets up a call from the user’s phone to Chris’ mobile phone number.

4. Chris answers his mobile phone and a media path is established between the two phones.

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

Figure 5 Remote Call Control

Telephony Gateway and Services 23

The full set of business-grade telephony features available with CS 1000 telephones is integrated with the OC 2007 client and can also be operated from a CS 1000 IP Phone, even when the client is unavailable. This integration ensures that telephony service reliability is preserved during interruptions in soft client operation. With the convergence of the CS 1000 with the OCS 2007, the OC 2007 client compliments the voice communications between two users by allowing other media types, such as IM, ﬁle, and application sharing to an existing voice call without the need to establish an independent session between the users.

Telephony Gateway and Services

With the Telephony Gateway and Services component, users can choose how to make and receive calls. For outgoing calls, users can make a call from their Ofﬁce Communicator soft client instead of their CS 1000 phone. You can handle incoming calls in one of two ways: through the computer with OC 2007 or through a phone. This feature provides users with computer-to-phone and phone-to-computer connectivity, leveraging the Nortel provided dial plan, telephony infrastructure, and telephony features to make and receive calls using Ofﬁce Communicator (OC) 2007 Client as a soft client.

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

24 Converged Ofﬁce component overview

With this solution, you can conﬁgure Personal Call Assistant (PCA) on the CS 1000 for each user with this functionality. The CS 1000 conﬁgured with the PCA provides number plan translations, Call Detail Recording (CDR) for outgoing calls, and enables telephony features, such as Call forward No Answer to Voice Mail, Attendant Recall, and participation as a client in a Group Call for incoming calls.

With the Telephony Gateway and Services component, you can conﬁgure the OC 2007 as a Multiple Appearance Directory Number (MADN) member for users with PCA on the CS 1000. With PCA , calls to a user’s phone number can be presented to both the desktop phone and to the OC 2007 client simultaneously. The user can then choose to answer on the most convenient device.

The ability to connect between computers and phones is not natively provided by Ofﬁce Communications Server 2007; however, the Telephony Gateway and Services component enables this functionality using the SIP Gateway and Multimedia Convergence Manager (MCM) application. MCM directs calls from an Ofﬁce Communicator user to the CS 1000 connected to their twinned telephone. Telephony Gateway and Services allows you to originate and receive SIP calls (for example, VoIP and Computer calls) from Ofﬁce Communicator.

In Figure 6 "Dual forking example" (page 25), OCS Front End (FE) forks the call to the CS 1000. The twin phone rings once and does not send another invite. The same scenario applies to calls originating from the CS 1000, the OCS does not get informed to perform another fork. A new setting is introduced on OCS 2007 server that enables or disables dual forking for each user. Remote Call Control (SIP CTI) is available when dual forking is enabled.

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

Figure 6 Dual forking example

Personal Call Assistant

Many of the features provided by CS 1000 to traditional telephones are extended to Ofﬁce Communicator clients conﬁgured with the Personal Call Assistant (PCA). For example, calls that remain unanswered can be forwarded using the Call Forward No Answer feature.

Personal Call Assistant 25

To use the Ofﬁce Communicator soft client for voice calls using the Telephony Gateway and Services, a PCA must be conﬁgured with the same DN as the user in a MADN arrangement. This offers incoming voice calls to the user’s DN on their Ofﬁce Communicator, as well as any phones that they have been conﬁgured with the same DN.

For incoming calls to be extended to the "twinned" Ofﬁce Communicator client, a PCA Terminal Number (TN) must be deﬁned for that DN. A new PCAM Class of Service prompt has been introduced so a distinction is made between PCA associated with the OCS 2007 client and PCA associated with other types of clients. Class is conﬁgured using BCC. For more information on BCC, see Basic Client Conﬁguration (BCC). PCA associated with the OCS 2007 client, the class is set to PCAM . Other types of clients use the default class PCAG. During call processing, the class is checked to determine whether an incoming call should be extended to the PCA target DN or not. For more information on conﬁguring PCA , see Features and Services (NN43001-106).

For outgoing calls from the Ofﬁce Communicator, the user must have at least one TN conﬁgured on the CS 1000 Call Server. The MCM locates the Call Server associated with a user by their numbering plan entry in the NRS. This generates calls from Ofﬁce Communicator clients on Telephony

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

26 Converged Ofﬁce component overview

Gateway and Services to always tandem through the user’s active Call Server. Note that with Geographic Redundancy features, a user’s active Call Server may change during failure scenarios.

The Network Class of Service (NCOS) setting for outgoing calls from Ofﬁce Communicator clients is determined by the conﬁguration of the MARP TN when in a MADN group, or by the conﬁguration of the PCA when it is the only TN for the user.

With PCA and Remote Call Control conﬁgured, users receive one pop-up window for the incoming call to the phone or computer. Users can choose the most convenient way to answer an incoming call.

Personal Call Assistant (PCA) service

While at the ofﬁce, a user may decide to use a desktop phone to answer calls. However, the user can still accept calls through the OC 2007 while they travel to locations that have network connectivity (for example, at hotels). The following steps correspond to the numbers in the ﬁgure:

1. The CS 1000 system receives a PSTN call to the user’s phone number.

2. The CS 1000 uses the PCA feature to provide simultaneous ringing to both the user’s phone and the Ofﬁce Communicator voice client.

3. The user can answer the call through the CS 1000 phone or the Ofﬁce Communicator voice client.

Users can be reached anywhere on the network and signiﬁcant cost savings are incurred by using IP telephony through Virtual Private Network (VPN) access to their private network. As part of the telephony services, many incoming call features are available even when using the OC 2007 as a telephony device or more

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

speciﬁcally in Computer mode. Features such as Call Forward No Answer, Uniﬁed Messaging, Call Detail Recording, and Attendant Recall are maintained within the CS 1000 system for calls presented to the OC 2007. Telephony Gateway and Services can access all of the telephony network resources using the OC 2007 client. Calls can originate from the OC 2007 client to the PSTN, phones, or services within the telephony network. Users can access all of their telephony network resources as long as they have the soft client and a high-quality connection to their private network. Telephony Gateway and Services is enabled by the interworking of the CS 1000 SIP Gateway with the OCS 2007 SIP gateway software.

Access Edge Server

Access Edge Servers allow internal and external users to communicate across corporate ﬁrewalls. Access Edge Servers enable IM and presence, as well as Web conferencing and audio/video (A/V) collaboration between internal and external users.

Access Edge Servers include the following server roles deployed on one or more computers in the perimeter network:

OCS 2007 snap-in 27

•

The Access Edge Server handles the SIP trafﬁc necessary to establish and validate connections between internal and external users.

•

The Web Conferencing Edge Server enables external users to participate in internal conference meetings. The Web Conferencing Edge Server handles the exchange of meeting content between internal and external users.

•

The Audio/Video (A/V) Edge Server enables A/V conferencing between internal and external users to allow for the sharing of audio and video with external users.

Microsoft recommends that you use the OCS 2007 Director, although it is not required.

Ofﬁce Communicator video is supported only for Remote Call Control between two Ofﬁce Communicator clients. Ofﬁce Communicator video is not supported if one of the clients goes through the SIP Gateway.

OCS 2007 snap-in

The Ofﬁce Communications Server 2007 snap-in for MMC is redesigned. The Status pane of the Ofﬁce Communications Server 2007 snap-in provides conﬁguration settings at-a-glance for your forest, domains, pools,

ATTENTION

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

28 Converged Ofﬁce component overview

servers, and users. The Status pane also features a new Database tab, which can be used to query a pool’s back-end databases. Each query is displayed as an expandable item in a list.

Microsoft Management Console (MMC) is automatically installed on each server in the domain that is running Ofﬁce Communications Server 2007 or any computer on which Ofﬁce Communications Server 2007 administrative tools are installed. It is not used to administer Edge Servers or Proxy Servers.

Enhanced presence must be enabled prior to Converged Ofﬁce telephony integration. You can enable enhanced presence from the Ofﬁce Communications Server Users Wizard in the Conﬁgure Users Settings window.

Multimedia Convergence Manager

MCM 3.0 is a software component that ensures interoperability between the Nortel CS 1000 and the Microsoft Ofﬁce Communicator Server (OCS) 2007. The MCM ensures CS 1000 and OCS interoperability of protocols, users, and phone numbers are managed within the Microsoft Active Directory. It also allows the system to block calls where the client is not in the Active Directory (AD). The MCM performs a number of functions that include:

ATTENTION

•

translation between telephony phone numbers and user IDs within the Active Directory

•

authentication of user phone numbers for RCC

•

Numbering Plan normalization

• protocol interworking

•

redundant connections to the CS 1000 network components (SIP Redirect Service (SRS), Sip Proxy Server (SPS), and redundant Signaling Servers)

CDR data collection

OCS 2007 supports CDR capability. OCS 2007 CDRs collect different kinds of data that include user logon and logoff, IM and audio call details, Conferencing start and join. You must install the Archiving and CDR Server to support these features. The outgoing calls from the OC 2007 to CS 1000 telephone are captured by this server, as well as OC to OC calls. Thus a call accountant can retrieve CDRs from both the CS 1000 and Archiving server to obtain a consolidated report. In RCC mode, CDRs are captured only on the CS 1000 side. For more information, see Microsoft

Ofﬁce Communications Server 2007 Archiving and CDR Server Deployment Guide Download Microsoft technical documentation from the Download

Center at w

ww.microsoft.com.

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

SIP CTI (TR/87) Protocol

The SIP CTI (TR/87) FE application introduced with this package is not limited to Microsoft applications. Through support of the ECMA TR/87 standard, Nortel partners can use this interface to develop SIP CTI capabilities for use with any speciﬁcation-compliant application.

If Preferred Calling Device is conﬁgured as Phone, a user receives one pop-up notiﬁcation with an incoming call, as depicted in Figure 7 "Call

Appearance pop-up window" (page 29). The OC user can click Redirect to

choose the client as the answering device. Certain portions of the protocol are not supported at this time. Additional

information about the SIP CTI (TR/87) protocol is available to Nortel partners upon request.

Figure 7 "Call Appearance pop-up window" (page 29) shows an example

of an incoming call pop-up window.

Figure 7 Call Appearance pop-up window

SIP CTI (TR/87) Protocol 29

Figure 8 "SIP diagram" (page 30) depicts the SIP protocol information.

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

30 Converged Ofﬁce component overview

Figure 8 SIP diagram

Figure 9 "IP diagram" (page 31) depicts the IP protocol information.

Nortel Converged Ofﬁce Fundamentals — Microsoft Ofﬁce Communications Server 2007

Nortel Communication Server 1000

NN43001-121 01.03 Standard

Release 5.0 30 April 2008

+ 274 hidden pages