Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 .
Document status: Standard Document version: 01.03 Document date: 30 April 2008 Copyright © 2005–2008, Nortel Networks All Rights Reserved. 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.
Contents New in this release 9 Office Communications Server 2007 features Other changes 9 Revision History 10 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 Office component overview 15 Converged Office 15 Enterprise Voice 17 OCS 2007 Voice components 18 Media Gatewa
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 Serv
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 Configuration 111 Active Directory configuration 112 Office Communications Server configuration 119 Load Balancer configuration 120 Voice Properties configuration 120 OCS configuration procedures 122 Configuration of Static Routes 122 Host Authorization and
Contents CS 1000 configuration 173 Signaling Server configuration 177 SIP CTI Services configuration settings 181 SIP CTI CLID configuration parameters 185 Configuring the SIP URI Map 189 Configuring CDR 190 Dialing E.
Contents 7 MCM logs 228 Activating MCM logging OCS logs 231 Case checklists 234 229 Appendix A Call Flow and protocol details Contents 237 Overview 237 Message sequence 238 Call flow 239 Telephony Gateway and Services call flow Supported features 246 237 239 Appendix B Configuration Examples 249 Contents 249 Introduction 249 Standard Edition 249 Setting up the lab 250 Collecting required data 251 Configuring the Call Server 252 Signaling Server checklist 262 Active Directory user configuration 269 Ch
Contents Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Configuring a Mediation Server 133 Enabling replication to the Global Catalog 146 Configuring the SIP Trunk Domain name 164 Enabling Remote Call Control and PBX integration 171 Add
New in this release Office Communications Server 2007 features Signaling traffic between Communication Server 1000 and Office Communications Server 2007 is supported by Multimedia Convergence Manager (MCM) 3.0 . Media traffic is supported through the Mediation Server.
New in this release — 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.
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: www.nortel.com/support This site provides quick access to software, documentation, bulletins, and tools to address issues with Nortel products.
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 Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Introduction This document describes the elements and processes necessary to integrate Nortel Communication Server 1000 (CS 1000) with the Office Communications Server 2007 (OCS 2007) in the Nortel Converged Office. Prerequisites • Ensure CS 1000 Release 5.0 and the Product Enhancement Package is installed. • Microsoft supports the coexistence of LCS 2005 SP1 Standard Edition or Enterprise Edition with OCS 2007 Standard Edition or Enterprise pools.
Introduction Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Converged Office component overview This chapter provides a brief technical description of all the components associated with Nortel Converged Office.
Converged Office component overview The Nortel Converged Office feature combines the business-grade telephony of the CS 1000 with the OCS 2007 Enterprise Voice solution to offer a powerful converged office solution set that improves worker productivity.
Enterprise Voice 17 • originate and receive Public Switched Telephone Network (PSTN) calls from the Office Communicator (OC) 2007 soft client when away from the office. • take advantage of existing business telephony features on the CS 1000. Enterprise Voice This section describes the Office Communications Server (OCS) 2007 Enterprise Voice solution. The Nortel Converged Office feature integrates the OCS 2007 with the CS 1000.
Converged Office 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 Internet Engineering Task Force (IETF) standard. It defines a packet format to carry audio and video over IP networks.
Media Gateways 19 • Address Book Service—normalizes enterprise user phone numbers to E.164 format to provision user Contacts in Office Communicator. The following figure shows the components essential for voice support. Figure 2 Core routing server components Media Gateways Media gateways are third-party hardware components that provide a common interface between the Enterprise Voice infrastructure and the PSTN.
Converged Office 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 o
Mediation Server 21 • connects clients outside the network to internal Interactive Connectivity Establishment (ICE) components, to enable media traversal of NAT and firewalls • acts as an intermediary for call flows 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.
Converged Office 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.
Telephony Gateway and Services 23 Figure 5 Remote Call Control 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.
Converged Office component overview With this solution, you can configure Personal Call Assistant (PCA) on the CS 1000 for each user with this functionality. The CS 1000 configured 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.
Personal Call Assistant 25 Figure 6 Dual forking example Personal Call Assistant Many of the features provided by CS 1000 to traditional telephones are extended to Office Communicator clients configured with the Personal Call Assistant (PCA). For example, calls that remain unanswered can be forwarded using the Call Forward No Answer feature.
Converged Office 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 Office Communicator clients is determined by the configuration of the MARP TN when in a MADN group, or by the configuration of the PCA when it is the only TN for the user.
OCS 2007 snap-in 27 specifically in Computer mode. Features such as Call Forward No Answer, Unified 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.
Converged Office 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 Office Communications Server 2007 or any computer on which Office Communications Server 2007 administrative tools are installed.
SIP CTI (TR/87) Protocol 29 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 specification-compliant application. If Preferred Calling Device is configured as Phone, a user receives one pop-up notification with an incoming call, as depicted in Figure 7 "Call Appearance pop-up window" (page 29).
Converged Office component overview Figure 8 SIP diagram Figure 9 "IP diagram" (page 31) depicts the IP protocol information. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Hardware Load Balancer 31 Figure 9 IP diagram ATTENTION Customers must not use their Office Communicator client to call Emergency numbers (for example, 911). To ensure that emergency service organizations can accurately trace the source of the call, always use a desktop phone to place an emergency call. Hardware Load Balancer Hardware IP Load Balancers (for example, Nortel Application Switches) are required for multiple Office Communications Server 2007 Enterprise Edition deployment.
Converged Office component overview Hardware Load Balancers deliver load distribution to avoid a single point of failure. Other benefits include increased performance and added redundancy. The CS 1000 uses Load Balancers for the signaling path of VoIP calls and Remote Call Control.
Documentation References 33 Table 1 Nortel technical documentation Technical document Content Primary audience Converged Office User Guide — Microsoft Office Communications Server 2007 (NN43001-123) Contains information about using the OC client. General users Communication Server 1000E Planning and Engineering (NN43041-220) Contains instructions about calculating the anticipated call traffic for the CS 1000.
Converged Office component overview Technical document Content Primary audience Transmission Parameters (NN43001-282) Contains information about configuring the loss plan and DTI Data Bock. Administrators Element Manager System Administration (NN43001-632) Contains information about Administrators how to access Operational Measurements through Element Manager. NRS Installation and Commissioning (NN43001-564) Contains procedural information.
Planning and engineering This chapter contains information about topics you must consider before you implement Converged Office.
Planning and engineering Nortel recommends that you implement the Telephony Gateway and Services component to provide basic connectivity (which you can more readily debug), followed by the Remote Call Control (RCC) for more complex feature operation. Configure both Telephony Gateway and Services and RCC only in situations where both components are required. Consider the following during the planning process. • Consider the size of your network.
Network configuration 37 Note: The descriptions and graphical representations of the three network types are for illustration only, and are not actual configurations. The number of CS 1000 systems and Office Communications Server 2007 servers will be based on the engineering guidelines found in this document and those provided by Microsoft. Small network If you have a small network that requires ease of management, you can choose a basic configuration.
Planning and engineering Figure 10 Small network configuration Medium network A medium network can include the following components: • one or multiple CS 1000 systems with Media Gateway and Signaling Server • a Primary NRS with an Alternate Network Routing Service (NRS) that co-reside on one of the Signaling Servers • up to 5000 users • high availability with system redundancy for OCS 2007 You will need: • an Office Communications Server 2007 Enterprise Edition • an OCS Proxy server that runs
Network configuration 39 Figure 11 Medium network configuration Large network A large network can include the following components: • multiple CS 1000 systems with Media Gateway and Signaling Server • configured collaborative NRS • redundant Primary and Alternate NRS • more than 5000 users • high availability with system redundancy for OCS 2007 You will need: • an OCS 2007 Enterprise Edition server with Load Balancers to Front End the pool of Enterprise Edition servers • a redundant OCS Prox
Planning and engineering The redundant, primary, and alternate NRS can be either the VxWorks NRS or the Linux-based NRS (SPS/SRS). For the OCS 2007 Enterprise Edition server, a SQL back end database server is a requirement. ATTENTION If you set up more than one server that runs the Enterprise Edition of Microsoft Office Communications Server 2007, you must use a Load Balancer in accordance with the Unified Communications Engineering Rules and Guidelines.
Network configuration 41 Figure 13 "Multiple customer network" (page 41) provides an example of a multiple customer network. The figure shows two customers: Customer 1 (Ottawa) and Customer 2 (Belleville), each with their own set of associated phones and Signalling Servers. This type of configuration is required for any deployment that uses the Telephony Gateway and Services functionality, or in scenarios where both Telephony Gateway and Services and Remote Call Control functionality is deployed.
Planning and engineering The Signaling Server, OCS Proxy server (which runs MCM), OCS 2007 Front End server, and Active Directory are separate. The number of Signalling Server(s), OCS 2007 Proxies, and OCS 2007 Front End servers required for each customer are the same as if each customer were part of a single system. However, the total number of users allowed for the CS 1000 is the total number of users for all customers.
Load Balancer planning 43 Mediation servers supports only TCP. However, it can interact with TLS gateway through SPS. SPS can act as a redirect server for SIP messages so the link between CS 1000 and the SPS can be TLS. Load Balancer planning This section provide information on the Load Balancer requirements.
Planning and engineering Table 3 Load balancer minimum configuration Service Protocol Port (range) Description TLS pool TCP 5061 The client listens over the same connection that is open to the server. By default, the server listens on port 5061 (TCP). The server sends packets to the client only over the client TLS session. DCOM TCP 135 Installation and management. — Optionally, configure the TCP pool on port 5060 for clients to connect to the Load balancer through TCP.
Load Balancer planning 45 • Every Office Communications Server must have exactly one network adapter. Multihoming an Office Communications Server is not supported. If a 10/100 network adapter does not meet the required bandwidth constraints, a gigabit network adapter must be used. • The network adapter must have at least one static IP address. This IP address will be used for the incoming load-balanced traffic. • The computer must have a registered FQDN.
Planning and engineering address is used by clients as a single point of connection to the pool. This address is listed in DNS and has an FQDN. Internal OCS clients require the DNS server to establish a connection with the Enterprise Edition Pool. Figure 15 Incoming Load Balancer Nortel Application Switch Nortel recommends that you use the Nortel Application Switch (NAS) for Load Balancing. Capacity planning This section provides the capacity requirements for the various components.
Capacity planning 47 Capacity planning navigation • "OC 2007 client requirements" (page 47) • "Load Balancer capacity requirements" (page 47) • "SIP CTI (TR/87) services requirements" (page 47) • "Mediation server requirements" (page 49) • "Signaling Server requirements" (page 49) • "Call Server requirements" (page 50) • "OCS Proxy and MCM capacity requirements" (page 50) OC 2007 client requirements The PC that runs the OC 2007 must be registered to the domain in which the OCS 2007 server ru
Planning and engineering To illustrate this, consider the following high-level example: Client A sends a TR/87 SIP INVITE to Node 1 to monitor DN 1000. The TR/87 association is established. Client B then sends a TR/87 SIP INVITE to Node 1 (the same node) to monitor DN 1000. Both sessions are established successfully. As a result of this sequence, two TR/87 sessions exist for DN 1000 through Node 1.
Capacity planning 49 Figure 16 SIP CTI (TR/87) example Mediation server requirements The CS 1000 can process up to 13 000 simultaneous calls. Therefore, you may require several Mediation servers for one CS 1000. To correctly deploy OCS 2007 to interwork with the CS 1000, you must correctly engineer the network to handle the anticipated call traffic. Calculate the anticipated call traffic for the CS 1000 using the instructions in Communication Server 1000E Planning and Engineering (NN43041-220).
Planning and engineering For example, MCM works as a software load balancer in addition to a router. MCM uses a round-robin algorithm for load balancing. When the current Mediation Server does not answer, MCM jumps to the next Mediation Server. You can use load balancing for direct mode and with SPS or SRS. For Release 5.0, 1 GB of memory is required for a standard Signaling Server. All signaling servers must run the latest software version.
General requirements 51 The number of users the OCS Proxy server with MCM can handle depends on the usage and the number of calls per hour per user. For example, assuming 5 cph/user for VoIP calls would give 3000 users (15 000 cph/5 cph/user = 3000 users). The following are the formulas (based on SPECint_rate2000) to calculate the maximum call rate for different platforms: • VoIP calls only. Number of calls per hour supported = (15 000 x SPECint of HW) / 29.8. • SIP CTI (TR/87) RCC calls only.
Planning and engineering • "OC client authentication" (page 59) • "Authorization of TR/87 (Remote Call Control) Service Requests" (page 59) • "Signaling and Media Encryption" (page 59) • "Dial Plan considerations" (page 61) • "Computer (SIP) Calls" (page 61) • "Phone (RCC or TR/87) Calls" (page 62) • "Number formats supported by Office Communicator" (page 63) • "E.
General requirements 53 Hardware Requirements Use the following table to determine hardware requirements for the OCS 2007 Standard and Enterprise Edition server. Table 6 Office Communications Server 2007 Standard and Enterprise Edition hardware requirements Hardware Requirements CPU Dual processor, dual core 2.
Planning and engineering Table 9 Back end database for a small to medium Enterprise pool CPU Dual processor, dual-core 2.6 GHz + Disk Drive 1 (2 × 18 GB) for OS and Page File Drive 2 (36 GB, 15K RPM) for database log file Drive 3 (36 GB, 15K RPM) for database log file Drive 4 (8 x 36 GB, 15K RPM, RAID 0+1) for database files Cache 2 MB L2 per core Memory 8 GB Network Gbit NIC Table 10 Back end database for a large Enterprise pool CPU Quad processor, dual-core 2.
General requirements 55 Communications Server that runs Microsoft Virtual Server 2005. For additional information about Virtual Server 2005, see the Virtual Server Web site at www.microsoft.com/windowsserversystem/virtualserver/default.mspx. Storage Store internal hard disks used for operating system and executable software, data, and transaction files separately.
Planning and engineering Table 12 Inputs Input Description TN_MO_Users Total number of Office Communicator users that use the SIP Access Ports for voice services. PCA_MO_Users Number of Office Communicator users that use Personal Call Assistant (PCA). The PCAs required here are additional to the number of PCAs provided in the Enterprise Configurator (EC) tool Software screen. P_PCA_SIP Percentage of PCA calls that use the soft client to answer a call.
General requirements Traffic (CCS) Traffic (Erlang) Number of ports 70 1.94 7 75 2.08 7 80 2.22 7 85 2.36 7 90 2.5 8 95 2.64 8 100 2.78 8 125 3.47 9 150 4.17 10 175 4.86 12 200 5.56 13 225 6.25 14 250 6.94 15 275 7.64 16 300 8.33 17 325 9.03 18 350 9.72 19 375 10.42 19 400 11.11 20 425 11.81 21 450 12.5 22 475 13.19 23 500 13.89 24 550 15.28 26 600 16.67 28 650 18.06 29 700 19.44 31 750 20.83 33 800 22.22 35 850 23.
Planning and engineering Traffic (CCS) Traffic (Erlang) Number of ports 2000 55.56 74 2500 69.44 90 3000 83.33 106 3500 97.22 121 4000 111.11 137 4500 125 152 5000 138.89 168 6000 166.67 198 7000 194.44 228 8000 222.22 258 9000 250 288 10 000 277.78 318 20 000 555.56 611 30 000 833.33 908 40 000 1111.11 1205 50 000 1388.89 1502 60 000 1666.67 1799 70 000 1944.
General requirements 59 The port range can be controlled (restricted) to a smaller range using the group policy settings as described on the Microsoft Web site: support.microsoft.com/default.aspx?scid=KB;EN-US;903056 Port ranges must not overlap. Security When you consider a Converged Office deployment, ensure you understand the following security concepts and integrate them into your deployment planning.
Planning and engineering Figure 17 Signaling security • Secure Management Zone (SMZ) provides management access to local and remote devices over a secure connection. SMZ documents the LAN and WAN configurations required for secure management. • Virtual Private Network (VPN) enables secure communications through Secure Internet Protocol (IPSec) encryption. • Transport Layer Security (TLS) ensures that third-parties cannot eavesdrop or tamper with messages when a server and client communicate. MCM 3.
General requirements 61 Figure 18 Signaling security with TLS Dial Plan considerations Nortel Converged Office is comprised of the following two components: • SIP CTI Services provides CS 1000 native TR/87 support to enable the Remote Call Control functionality available with Office Communicator. • Telephony Gateway and Services allows you to originate and receive SIP calls (for example, VoIP and Computer calls) from Office Communicator.
Planning and engineering • CS 1000 Call Server configuration relating to the SIP Gateway • OCS Location Profile, Policy, Phone Usage, and Route configuration.
General requirements 63 Figure 19 Signaling and media paths Number formats supported by Office Communicator Dialstrings and E.164 International number format are the two types of numbers used by Office Communicator. Both number formats apply to computer and phone calls with Office Communicator. Dialstrings By default, digits dialed from Office Communicator that are not fully qualified are sent as dialstrings.
Planning and engineering All E.164 numbers presented to the CS 1000, computer, or phone are expected in the following format: + For example, in North America, the Office Communicator Phone Number configuration input dialog box would have an entry similar to Figure 20 "North American format" (page 64).
General requirements 65 A normalization rule can be used to strip the digit in brackets to conform to the expected format for E.164 numbers when using the Converged Office feature: +31123456789 For more information about Normalization rules, see "Creating Normalization rules" (page 193). Handling numbers called from Office Communicator in E.
Planning and engineering If calls that enter the Call Server are international and outside of the country of the caller, the translator must contain entries that recognize the international numbers and route the call to the appropriate route list. These entries are generally within the existing AC1/AC2 translator, as they are used to route international calls that are dialed directly from telephones. E.164 international format numbers for SIP Gateway and SIP CTI For information about E.
Telephony Gateway and Services planning System, platform, or application 67 Supported M1/CS 1000 Systems CS 1000M SG (CP PIV) Yes CS 1000M MG (CP3/4) Yes CS 1000M MG (CP PIV) Yes CS 1000E Yes MG 1000B Yes Capacity For more information relating to the Telephony Gateway and Services and Remote Call Control components, see "Capacity planning" (page 46). Redundancy Office Communications Server 2007 redundancy model is supported, with limitations, using Load Balancers.
Planning and engineering Figure 22 SIP routing Calls made to a CS 1000 that is different from the twinned telephone base uses two SIP trunks: one incoming and one outgoing. Additional SIP trunks are needed, if users commonly call between CS 1000 systems. For more information about the number of required SIP trunks, see the calculations described in "Trunking" (page 55) and the platform-specific Planning and Engineering document.
Telephony Gateway and Services planning 69 Figure 23 Computer call LG-Nortel IP Phone 8540 OCS desk phone An Enterprise Voice only client (no PBX integration enabled) that is configured for an OC 2007 client or 8540 OCS desk phone, will be able to make PSTN calls using the CS 1000 as the gateway. You are required to configure a TN and twinned PCA on the CS 1000 even if there is no actual phone present for this client.
Planning and engineering Office Communicator-initiated Call Transfer in Computer and PBX Integration Enabled If the Office Communicator transfers a call, the SIP stack of the CS 1000 must handle the request to transfer the call. As such, the number a user is transferred to is not subject to the Class of Service associated with either user (the transferred party or the party performing the transfer). The Class of Service and Call Restriction that control the transfer is that of the SIP trunk itself.
Telephony Gateway and Services planning 71 VoIP calls can only be placed to other Office Communicator users (computer to computer calls). Outgoing VoIP calls to telephone numbers for Microsoft Office Communicator Mobile are not supported. Microsoft Virtual Server 2005 Microsoft Virtual Server 2005 is not supported as part of Nortel Converged Office. DTMF CS 1000 supports in-band DTMF digits and out-of-band DTMF digits for SIP calls through RFC2833. RFC2833 is an out-of-band mechanism for DTMF signaling.
Planning and engineering Video Call Transfer Office Communicator calls made in Computer mode that have established video can transfer to another Office Communicator user in Computer mode—although the new call is audio only. The transferred Office Communicator user experiences the call becoming audio only. After the transferred call is answered by the new endpoint, video can be established.
Remote Call Control with SIP CTI 73 ipDialog Ethernet Phone Office Communicator clients can work with the ipDialog Ethernet Phone only if it is tandemed through a CS 1000. Country or region tone configuration Country or region tone configuration is not supported by Office Communications Server or Office Communicator. Conference Incorrect participants are displayed on the conference conversation window in the following scenario.
Planning and engineering Figure 24 Simple network diagram The TR/87 FE is the application that resides on the CS 1000 Signaling Server to support the telephony control requests and responses received from the Office Communicator 2007 client within an Office Communications Server 2007 deployment. CS 1000 is supported in both the Office Communications Server 2007 Standard Edition and Enterprise Edition network configurations. For more information about restrictions, see "Capacity planning" (page 46).
Remote Call Control with SIP CTI Systems, platforms, and applications Interoperable Supported CS 1000M SG (CP-PII and -PIV) Y Y CS 1000M SG (CP PIV) Y Y CS 1000M MG (CP-PII and -PIV) Y Y CS 1000E SA/HA (CP-PII, -PIV, and -PM) Y Y MG 1000T (SSC) Y N MG 1000B (MGC and CP-PM) Y Y* MG 1000E (MGC) Y Y* * Digital and analog telephones in Branch Offices are supported when access to the proxy/redirect server and OCS 2007 is available.
Planning and engineering Systems, platforms, and applications Interoperable Supported WLAN Handset 2212 Y Y IP Phone 1110 Y Y IP Phone 2007 Y Y IP Phone 1120E Y Y IP Phone 1140E Y Y IP Phone 1150E Y Y TDM Phones M3900 series Y Y M3000 Y Y M2317 Y Y M2006 Y Y M2008 Y Y M2316 Y Y M2016S Y Y PC Console Interface Unit Y Y CDR Y N Telephony Manager (TM) Y Y Element Manager (EM) Y Y Element Subscriber Manager (ESM) Y N Call Pilot Y N Call Pilot Mini
Remote Call Control with SIP CTI Systems, platforms, and applications Interoperable Supported Symposium Agent Y N Symposium Agent Greeting Y N Symposium Express Call Center (SECC) Y N Symposium Call Center Server [SCCS] Y N Symposium Web Centre Portal (SWCP) Y N Periphonics Open IVR (VPS/is) Y N Periphonics Integrated Package for Meridian Link (IPML) – VPS Y N Periphonics Multimedia Processing Server (MPS) 100 Y N Periphonics Multimedia Processing Server (MPS) 500 Y N Integrat
Planning and engineering Systems, platforms, and applications Interoperable Supported AT&T SIP trunk Y N Broadsoft Y N ACME SBC Y N 3100 Mobile Communication Gateway Y N Redundancy Remote Call Control (RCC) services are supported (with limitations) in the following scenarios: • Single node redundancy • Campus redundancy • Geographic redundancy Single node Redundancy The same master and follower mechanism used for Virtual Trunk (VTRK) and TPS applications is used to support redundanc
Remote Call Control with SIP CTI • 79 After an event occurs that causes the IP Phones to register to a server other than the Front End server (and then to return to the Front End server), the Office Communicator 2007 client does not automatically follow the IP Phone registration.
Planning and engineering The Microsoft Office Communicator client has no automated mechanism to register to the branch. Users must wait for the existing dialog to time out (30 minutes) or manually log out and log on again after the IP phones change to local mode. Digital and analog telephones in the Branch Office can have Remote Call Control (RCC) and PBX Integration Enabled support when the Branch Office has access to the NRS and OCS.
Remote Call Control with SIP CTI Feature Operation Description • Conference Call - cannot be performed through Office Communicator . • Call Hold - can be performed through Office Communicator. • Call Transfer - Analog telephones do not support the Conference and Transfer key features. As a result, Call Conference and Call Transfer (Announced and Blind) cannot be performed through Office Communicator. Flexible Feature Code (FFC) is not supported by AML and RCC.
Planning and engineering Feature Operation Description Office Communications Server and MCS coexistence ATTENTION All Converged Office users must have their extension configured as CLS CDMR. A user cannot have both Office Communications Server and MCS enabled for their extension (all TN’s that have a particular number and extension). If any of the TN’s have CLS CDMV or CLS CDMO configured, the extension is treated as having MCS enabled.
LCS 2005 and OCS 2007 coexistence 83 supported configuration because of incompatible underlying libraries. The same CS 1000 can be connected to two or more different communication servers (LCS 2005 or OCS 2007). The following must be considered for coexistence of LCS 2005 and OCS 2007: • The CS 1000 must be upgraded to Release 5.0 with the required Product Enhancement Packages (PEPs) . • OCS 2007 patches from Microsoft must be in service.
Planning and engineering MCM 2.0 to MCM 3.0 There is no direct upgrade path from MCM 1.0 or 2.0 to MCM 3.0 . MCM 3.0 must be installed on the OCS Proxy server. The OCS Proxy install is done from command line and not from the install wizard. It is still possible to preserve the configuration data from a previous installation by first performing a backup operation on MCM 2.0 and restore the data to MCM 3.0 on the OCS Proxy server.
Migration planning from LCS 2005 to OCS 2007 Prerequisites Upgrading to Office Communications Server 2007 assumes the following: • An understanding of the basic migration process. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Planning and engineering • An understanding of the coexistence interactions. For more information, see "LCS 2005 and OCS 2007 coexistence" (page 82). • An understanding of CS 1000, Signaling Server, and networks. • An understanding of the user migration process. Determine your deployment options There are two deployment options depending on whether you are migrating a small or large client base.
Migration planning from LCS 2005 to OCS 2007 Phase Description User experience 2. Deploy OCS 2007 and begin moving users to the new server or pool. Deploy a new Office Communications Server 2007 Enterprise pool or Standard Edition server. If required, deploy an Archiving and CDR Server. Users are moved to the new server or pool but will continue to use OC 2005 . No changes. OC 2007 client is not rolled out at this phase so users continue to use OC 2005 and have the same IM and presence functionality.
Planning and engineering Phase Description User experience 8. Continue migrating users. • Migrate remaining users. Enable users for enhanced presence. Roll out the OC 2007 client and the Live Meeting 2007 client to the users. • OC 2007 users can use the full functionality of OC 2007 when communicating with other OC 2007 users.
Migration planning from LCS 2005 to OCS 2007 89 Migrating users from LCS to OCS Step Action 1 Upgrade your perimeter network by deploying an Access Edge Server that communicates with Live Communications Server 2005 Director.
Planning and engineering 7 Configure PCA routing for new OC client users on the CS 1000. After configuration of PCA routing, users will be allowed to use Telephony Gateway and Services (VoIP) and RCC functionality. A Server URI field should be changed for migrated users to enable SIP CTI functionality. Change NRS and SPS routing. 8 Continue migrating users. Enable users for enhanced presence. Roll out the OC 2007 client and the Live Meeting 2007 client to the users.
Unified Messaging 91 Table 20 CallPilot configurations OC User (VoIP) with RCC and CS 1000 Phone OC User (VoIP) with no RCC and CS 1000 Phone OC User (VoIP) with no RCC and no CS 1000 Phone LG-Nortel 8540 (VoIP) with no RCC and no CS 1000 Phone OC User RCC only, with CS 1000 Phone CS 1000 configuration PCA + SIP CTI PCA PCA PCA SIP CTI VM access from phone Dial CP DN Dial CP DN N/A N/A Dial CP DN Login from phone p/w only p/w only N/A N/A p/w only MWI on phone Yes Yes N/A N/A Yes
Planning and engineering ATTENTION For Converged Office users not using a Nortel telephone For Converged Office users who use voice communications through the OC client or from an LG-Nortel 8540 telephone (or both) and are configured with a Personal Call Assistant (PCA) , the following cautions apply: • Ensure that the Call Forward No Answer and Call Forward Busy settings for the PCA are properly set to the CallPilot DN.
Unified Messaging 93 Logon from OC Logon and password direct direct direct N/A MWI on OC Yes Yes Yes Yes Yes Outlook New msg in inbox New msg in inbox New msg in inbox New msg in inbox New msg in inbox Phone CFNA SA DN SA DN Not Required Not Required SA DN Phone CFB SA DN SA DN Not Required Not Required SA DN Phone CFAC SA DN SA DN N/A N/A SA DN OC client FC On Phone (RCC to SA DN) No No No On Phone (RCC to SA DN) OC client Re-direct N/A No No No N/A OC clien
Planning and engineering Table 22 Unified Messaging 2007 integrated Option 2 OC User (VoIP) with RCC and CS 1000 Phone OC User (VoIP) with no RCC and CS 1000 Phone OC User (VoIP) with no RCC and no CS 1000 Phone LG-Nortel 8540 (VoIP) with no RCC and no CS 1000 Phone OC User RCC only, with CS 1000 Phone CS 1000 configuration PCA + SIP CTI PCA PCA PCA SIP CTI VM access from phone Dial SA DN Dial SA DN N/A N/A Dial SA DN Login from phone p/w p/w N/A N/A p/w MWI on phone No No N/A
Unified Messaging 95 ATTENTION For Converged Office users not using a Nortel telephone For Converged Office users who use voice communications through the OC client, an 8540 telephone, or both and are configured with a Personal Call Assistant (PCA) , the following cautions apply: • Ensure users only use the OC 2007 client Voice Mail settings for forwarding or redirecting calls to Voice Mail.
Planning and engineering VM access from OC Dial SA DN Dial SA DN Dial SA DN Dial SA DN N/A Login from OC p/w only p/w only p/w only p/w only N/A MWI on OC Yes Yes Yes Yes Yes Outlook New msg in inbox New msg in inbox New msg in inbox New msg in inbox New msg in inbox Phone CFNA SA DN SA DN PCA CFNA PCA CFNA SA DN Phone CFB SA DN SA DN PCA CFB PCA CFB SA DN Phone CFAC SA DN SA DN N/A N/A SA DN OC client FC On Phone (RCC to SA DN) Not recommended Not recommende
Unified Messaging 97 ATTENTION For Converged Office users not using a Nortel telephone For Converged Office users who use voice communications through the OC client, an 8540 telephone, or both and are configured with a , the following cautions apply: • Ensure that the Call Forward No Answer and Call Forward Busy settings for the PCA are properly set to the Exchange Unified Messaging System Access number.
Planning and engineering Figure 25 Signaling integrated Signaling with non-integrated Voice Mail In a non-integrated configuration, the Office Communicator (OC) client does not have the capability of selecting a Voice Mail option, the signaling between Exchange and the OC client is not defined. The following diagram depicts the signaling between OCS 2007, Exchange, and the CS 1000 components in a non-integrated configuration.
Unified Messaging 99 Figure 26 Signaling non-integrated Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Planning and engineering Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Installation This chapter contains the procedures necessary to install CS 1000 components and Office Communications Server (OCS) 2007 on a CS 1000 system. The first step is to install the necessary CS 1000 components (if you do not already have a working CS 1000 system in place), and then install the Microsoft server components. After all hardware and software is installed, you can then configure the Telephony Gateway and Services or Remote Call Control components.
Installation Installation navigation Figure 27 Installation and configuration flow • "CS 1000 and Signaling Server installation" (page 105) • "OCS 2007 component installation" (page 105) • "OCS Proxy server installation" (page 107) • "Load Balancer installation" (page 108) • "MCM installation" (page 109) Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.
OCS 2007 installation preparation and deployment 103 OCS 2007 installation preparation and deployment The following figure Figure 28 "OCS 2007 installation preparation and deployment flow chart" (page 104) depicts the high-level topics required to deploy OCS 2007. After your internal deployment is complete, you can then deploy Edge Servers for external user access. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.
Installation Figure 28 OCS 2007 installation preparation and deployment flow chart Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
OCS 2007 component installation 105 CS 1000 and Signaling Server installation The first step in the installation and configuration process is to install the CS 1000 and Signaling Server.
Installation ATTENTION The following is a list of the required patches for the Microsoft OCS 2007 installation: • OCS 2007 – Standard Edition RTM KB 942872 Version 6362.0 plus hotfix • Description of the Office Communicator 2007 hotfix package: December 17, 2007 KB 943083 Version 2.0.6362.36 • Description of Office Communications Server 2007, Unified Communications Managed API v1.0 Redist: December 17, 2007 KB 944285 Version 3.0.6362.
OCS Proxy server installation 107 Office Communications Server (OCS ) 2007 Enterprise Pool OCS 2007 Enterprise Edition is designed for large-scale deployment where multiple Office Communications Server Enterprise Edition servers are deployed as a pool, typically behind a load balancer. Servers in the pool share a central SQL back end database server that stores user data. If your pool consists of more than one server, a Load Balancer is required.
Installation Installing the OCS Proxy server Step Action 1 On the Windows Start menu, choose Run. 2 Navigate to the C:\Office Communications Server_Eval\se_eval\setup\i386\ folder. 3 For OCS Standard Edition: server.msi SERVER=PROXY SKU=SE OR For OCS Enterprise Edition: server.msi SERVER=PROXY SKU=EE A new Windows wizard opens prompting you to install the Forwarding Proxy. You must complete all the steps in the wizard before continuing.
MCM installation 109 3 Select TCP/IP properties and add DNS server IP. For example, 47.11.108.50. 4 Go to My Computer, right-click and select System Properties. 5 Enter the Computer Name of each FE server. For example, ocs-fe-1. 6 Click domain. For example, ocs2007a.corp.nortel.com. 7 Restart server. —End— MCM installation Prerequisite MCM information • Ensure MS Windows Server 2003 operating system is installed with SP1 or R2. • Ensure the OCS Proxy server is installed.
Installation 2 Select Use an existing account and enter your user ID and password OR select Create a new account. 3 Open the MCM Console window and select the Actions menu. 4 On the Actions menu, choose Start to start the MCM service. —End— MCM must be installed on the OCS Proxy Server. See "MCM menu options" (page 139) for more information about using the MCM menu options.
Configuration The following flow chart depicts the configuration order of the components. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Configuration Figure 29 Configuration flow chart Active Directory configuration Active Directory configuration takes place in the Active Directory Users and the Computers (ADUC) window. Selecting the Users folder reveals the list of users as depicted in Figure 30 "Active Directory (Microsoft LDAP server)" (page 113). All users are defined in this folder. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.
Active Directory configuration 113 By default MCM uses GC LDAP server which contains partial information about all objects in the Active Directory domain forest. It requires replication from all Domain controllers to the GC domain controller to be performed after changes made in the Active Directory User’s configuration "Active Directory Sites and Services" snap-in.
Configuration Defining users Step Action 1 Select a user from the list in the Users folder. 2 Right-click the user, and select Properties. 3 The Properties window opens as depicted in Figure 31 "User properties" (page 114). 4 Enter the user’s information (first name, last name, telephone number, and so on) in the appropriate fields in the General tab. 5 Select the Communications tab.
Active Directory configuration 6 Click the check box next to Enable user for Office Communications Server. 7 In the fields provided, define the user Sign-in name and the Server or pool ). Office Communicator 2007 uses these addresses to place calls. Figure 32 Enable Office Communications Server connectivity for a user in Active Directory 8 Click the Configure button. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.
Configuration 9 For enabling Remote Call Control only, select Enable Remote Call Control and configure the Server URI and Line URI. See Figure 33 "Enable Remote call control" (page 117). 10 For enabling Enterprise Voice and PBX integration only (without RCC), select Enable Enterprise Voice and the Enable PBX integration check box. See Figure 34 "Enable Enterprise Voice and PBX integration" (page 118).
Active Directory configuration Figure 33 Enable Remote call control Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Configuration Figure 34 Enable Enterprise Voice and PBX integration Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Office Communications Server configuration 119 Figure 35 Enable both RCC and Enterprise Voice Office Communications Server configuration The starting point for Telephony Gateway and Services configuration is the Office Communications Server 2007 component. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Configuration Load Balancer configuration The pool of Front End servers is organized to process inbound and outbound traffic. The role of the Load Balancer in this architecture is to route incoming SIP-messages to the less busy server on the base of configured algorithm. Load Balancer’s VIP-address is used by clients as a single point of connection to the pool. This address is listed in DNS and has a FQDN.
Office Communications Server configuration 121 Voice mail must always be configured on the CS 1000 and not Office Communicator. Configuring communication to the CS 1000 gateway is performed at the Mediation Server. Dual forking is configured based on OCS Voice Policies, which in turn may be applied globally or on a per user basis. For more information on configuring Voice Policies, see Microsoft Office Communications Server 2007 Enterprise Voice Planning and Deployment Guide.
Configuration —End— Applying policy Step Action 1 In the User Options window, click Enable Enterprise Voice. 2 Select Another Policy. The policy can be assigned simultaneously to several users using the Configure Users wizard. —End— OCS configuration procedures Download Microsoft technical documentation from the Download Center at www.microsoft.com.
Office Communications Server configuration 123 1000. In this situation, the IP address of the CS 1000 must be added to the Authorized Host list. Configuring the Host Authorization and Routing for the OCS Front End server Step Action 1 Open Office Communications Server (accessed from the Windows server that runs the OCS server) as shown in Figure 36 "Opening Office Communications Server " (page 123). Click on the Start menu and then select Administrative Tools, Office Communications Server 2007.
Configuration Figure 37 Office Communications Server Front Ends 3 Click on the Host Authorization tab and select the Edit button. 4 In the Server section, click on the IP Address button and enter the IP address of the OCS Proxy server. For details, see Table 25 "Routing rules" (page 130). 5 In the Settings section, select Throttle As Server and the Treat as Authenticated check boxes. 6 Click OK.
Office Communications Server configuration 125 Figure 38 Routing tab 8 In the Add Static Route window, For Domain: enter the domain defined in the Server URI. For Next Hop: enter the IP address of the OCS Proxy. —End— For each OCS Proxy with MCM, Host Authorization is required for the Node IP address of all CS 1000 servers that the Office Communications Server interacts with, as well as the TLAN IP address of the Primary, Secondary, and all possible collaborative NRS.
Configuration Configuring host authorization for the OCS Proxy Step Action 1 Open the OCS Proxy server, click the Windows Start button, point to Administrative Tools, and then click Computer Management. Figure 39 Opening the Computer Management console 2 Choose Microsoft Office Communications Server and right-click to select Properties. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.
Office Communications Server configuration 127 Figure 40 Office Communications Server Management Console 3 For the OCS Proxy, no static route is required. MCM routes inbound calls to the proper Mediation Server based on the Routing Table settings on the MCM. 4 Click the Routing tab to confirm no route is configured. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.
Configuration Figure 41 Routing tab 5 Click the Host Authorization tab. 6 Click Edit to open the Edit Authorized Host window. 7 In the Edit Authorized Host window, enter the IP address, select both the Throttle As Server and Treat As Authenticated check boxes, and then click OK.
Office Communications Server configuration 129 Figure 42 Edit Authorized Host —End— The following table shows a number of possible configurations of OCS 2007 and the required entries for each. The transport to CS 1000 is TCP for all configuration types.
Configuration Host Authorization OCS Front End Servers Pool Port: 5060 Phone URI: No Replace host in request URI: No OCS Mediation Server OCS Application Server • None • NRS/SPS IP Address • Signaling Server Node IP Address • All IP Addresses of Mediation Servers • IP Address of all Front End Servers IP Address of the OCS Application Proxy Server Outbound Only: No Throttle as Server: Yes Treat as Authenticated: Yes Table 25 Routing rules Configuration Type Component Host Authorization
Office Communications Server configuration Configuration Type Component 3. Pool of Front End Front End servers servers and Pool Single OCS Proxy.
Configuration Configuration Type Component Host Authorization Destination User / Domain Phone URI Transport Port Proxy Load Balancer FQDN No TLS 5061 Proxy Load Balancer IP No TCP 5060 Mediation Servers IP 6. Single Front End server and Pool of OCS Proxies, SIP CTI TLS Front End server Proxy Load Balancer FQDN OCS Proxies Front End server FQDN Proxy Load Balancer FQDN SPS/SRS IP Node IP Mediation Servers IP 7.
Office Communications Server configuration 133 Configuration Type Component Host Authorization Destination User / Domain Phone URI Transport Port 8. Pool of Front End servers and Pool of OCS Proxies.
Configuration 5 In the FQDN box, make sure the FQDN listed matches that of the Mediation Server you have selected. 6 Open a command prompt, change to the root directory, and type nslookup and (FQDN of the server) using the FQDN displayed on the Mediation Server General tab, and then press Enter. 7 From the list of IP addresses displayed in the Communications Server listening IP address list, select the IP address returned in Step 6.
MCM 3.0 configuration • 135 Management Console The MCM Call Processing Service handles the Session Initiation Protocol (SIP) telephony traffic between the CS 1000 and the Office Communications Server. The Management Console provides real-time status of the MCM, Office Communications Server, Primary Network Routing Service (NRS), and Secondary NRS. It also provides Administrative, Maintenance, and Configuration tools.
Configuration Figure 43 MCM architecture The following examples illustrate how MCM handles call information. Understanding the role of MCM in the Telephony Gateway and Services component helps you to determine the configuration. Example 1: Outgoing calls from Office Communicator In this example, an invite travels from the client to the OCS Front End server, and then to the Office Communications Server MCM Proxy through the Mediation Server.
MCM 3.0 configuration 137 The call is routed to the NRS. The invite is sent to the NRS, which returns a 302, and the CS 1000 sends an invite to the MCM Proxy. At this stage, the invite includes a special header called x-nt-ocn that contains the actual number called. Use this header to compare against the Active Directory map for the user’s Line URI. This method is used to prevent you from having to program the for each user to determine the correct DN upon which to terminate the call.
Configuration — Not responding - Primary SRS/SPS is not responding. For normal processing, the Secondary SRS/SPS must be switched to an Active state. — Unknown - An unknown response is received by the SRS or SPS. • Secondary SRS/SPS (the IP address of the Secondary SRS/SPS server) — Active - Secondary SRS/SPS is active, which is possible only if the Primary SRS/SPS is down. — Standby - Secondary SRS/SPS is alive, which is the normal state if the Primary SRS/SPS is active.
MCM 3.0 configuration Figure 44 MCM MCM menu options The following lit describes the function of each MCM menu command: • Actions — Start - start MCM service — Stop - stop MCM service — Restart - stop and start MCM service — Exit - close current GUI for MCM service • Tools — Configuration — Active Calls Count Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.
Configuration — Active Directory Query — Backup — Restore — Set Log Level • Help — Get help and general information about MCM MCM Configuration To access the MCM Configuration window, go to the MCM console window, select the Tools menu and then select Configuration. Figure 45 MCM configuration window Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.
MCM 3.0 configuration 141 Network Topology section The following is a description of some of the configuration fields in the Network Topology section of the MCM configuration window. Table 26 Network topology fields Configuration field Description Call Server Type of call server CS 1000, CS 2000, CS 2100 SRS Outgoing SIP messages from the MCM will use the SIP Redirect Server for routing. SPS Outgoing SIP messages from the MCM will go through the SIP Proxy Server.
Configuration an INVITE request providing information about which dedicated Mediation Server or Mediation Server pool to process this message. The parameter value for SIP Gateway Endpoint Name is configured in Element Manager under System, IP Network, Nodes: Servers, Media Cards, Signaling Server Properties. The MCM contains a predefined list of Mediation Server addresses associated with a given sip-gw-id . The MCM is then able to determine what pool is used.
MCM 3.0 configuration 143 Table 27 Incoming Call Processing parameters Configuration field Description Called Phone Context Phone Context of calls to be processed by MCM. This entry depends on the dial-plan (CDP or UDP) and should be the same as Private/CDP domain name entries in the Signaling Server Element Manager.
Configuration Figure 47 Element Manager SIP URI MAP Active Directory configuration section There are two modes for Active Directory (AD) Configuration: Realtime or Local Cache. Realtime mode is used for end-user ID mapping, which requires a Lightweight Directory Access Protocol (LDAP) query. Local Cache mode involves caching the Active Directory on the MCM server and using that cache information for queries.
MCM 3.0 configuration 145 Active Directory query The Active Directory Query tool is used to check Active Directory mapping configuration. It searches for a user-id (SIP URI) by a given telephone number, and vice versa. This tool is only used for maintenance, and emulates the same algorithm that is used by the MCM service in run-time. For example: user Brendan McCarthy is defined in the Active Directory as: SIP URI: sip:brendan@ocs2007a.corp.nortel.
Configuration Figure 49 Get phone Field propagations to the Global Catalog MCM uses the Active Directory Global Catalog to search for necessary user information. However, by default, this Global Catalog contains few Active Directory fields that can be used for MCM (for example, otherTelephone). To enable a field, for propagation to the Global Catalog, the current schema used by Active Directory must be updated. The isMemberOfPartialAttributeSet field of the attribute is responsible for propagation.
MCM 3.0 configuration Step Action 1 Open the Active Directory Schema snap-in as depicted in the example Figure 50 "Replicating attributes to the Global Catalog" (page 147). 2 Select Attributes on the left pane. 3 In the Name pane, select the required field. For example otherTelephone. 4 Right-click and select Properties . 5 Select the Replicate this attribute to the Global Catalog check box. 6 Click OK.
Configuration Network dial plan section The following table describes the fields for Dial plan and Access code. Table 29 Network dial plan Configuration field Description Dial plan Use the dial plan to make calls between the CS 1000 and OCS (CDP or UDP). If the Line URI is configured as UDP, the dial plan will also be UDP. Access code Access code for the UDP plan. This code is added to the phone number stored in the OC user’s Line URI.
MCM 3.0 configuration 149 Configuring MCM for Remote Call Control For Remote Call Control, the Nortel MCM application that resides within the Office Communications Server domain provides support for authorizing TR/87 service requests and redundancy. Authorization of TR/87 service MCM supports authorization of Remote Call Control service requests from Office Communicator clients. The following is a summary of the authorization algorithm: 1.
Configuration Figure 51 Enable phone integration on the client Redundancy Redundancy of the TR/87 interface is not provided natively with Office Communications Server 2007. Office Communicator does not support multiple Remote Call Control SIP URIs or SIP 300/302 redirection messages. To provide for redundancy of the TR/87 interface, the Nortel MCM application uses the redundancy of NRS and multiple FE endpoints.
Telephony Gateway and Services configuration 151 Call Server configuration CS 1000 configuration involves two separate functions: Signaling Server configuration and Call Server Configuration. All of the Signaling Server configuration is performed in Element Manager. Most of the Call Server configuration can also be done in Element Manager, although some can be done at the Call Server prompt. This document assumes that you are already familiar with how to configure a CS 1000.
Configuration Figure 52 Codec configuration Loss Plan configuration In order for DTMF digits to be transmitted at the correct volume, especially for Office Communicator 2007 to PSTN communications, the Loss Plan for the CS 1000 must be correctly configured. Calls from Office Communicator 2007 to a residential Voice Mail system (VoIP to PSTN) is an example of the necessity of Loss Plan configuration.
Telephony Gateway and Services configuration 153 ATTENTION When any kind of in-band signaling is to be used as payload audio packets (for example, DTMF tones) in the egress direction (IP to TDM), the Signal Limiter functionality must be disabled. If problems are encountered with DTMF tones from Office Communicator contact Nortel support to ensure the Signal Limiter functionality is disabled.
Configuration In this figure, the CS 1000 has a HLOC of 354 and an LOC dialing plan entry of 344. The LOC dialing plan 344 is not dialable, however, calls to the DN: 6712 extend the call to the number 6-344-5000. By PCA extending the call to 6-344-5000, a SIP Invite is sent to the OCS Proxy server. The OCS Proxy server runs MCM, which handles the Invite and reads the Original Called Number as 354-6712. The call is sent to the Mediation server and To and RequestURI are mapped to the Line URI.
Telephony Gateway and Services configuration 155 When you use a PCA, the MARP must be on the DN key of the phone itself, not the PCA. If the MARP is on the PCA, CTI clients (such as Office Communicator) do not receive Remote Call Control call pop-ups for incoming calls (in addition to other problems). This is an unsupported configuration. Note that MARP is assigned to the first DN key created, so if you create the PCA first and assign a DN key, it becomes the MARP by default.
Configuration DES PCA TN 096 0 08 15 VIRTUALTYPE PCA CDEN 8D CTYP XDLC CUST 0 NUID NHTN CFG_ZONE 000 CUR_ZONE 000 ERL 0 ECL 0 FDN TGAR 1 LDN NO NCOS 0 SGRP 0 RNPG 0 SCI 0 SSU XLST SFLT NO CAC_CIS 0 CAC_MFC 0 CLS CTD FBD WTA LPR MTD FND HTD TDD HFD CRPD MWD LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1 POD DSX VMD SLKD CCSD SWD LND CNDD CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD ICDD CDMD LLCN MCTD CLBD AUTU GPUD DPUD DNDD CFXD ARHD CLTD ASCD CPFA CPTA ABDD CFHD FICD NAID DNAA BUZZ UDI RCC HBTD AH
Telephony Gateway and Services configuration 157 ANIE 0 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 TRN 18 AO6 19 CFW 16 20 RGA 21 PRK 22 RNP 23 24 PRS 25 CHG 26 CPN 27 28 29 30 31 DATE 30 AUG 2007 For more information about PCA, see Features and Services (NN43001-106). Caller ID table configuration The Caller ID table is used to correctly build the Caller ID (CLID) for both Private network and Public network calls from a number/extension.
Configuration For PCA twinning to work correctly in a UDP environment, the full Original Called Number (OCN) must be sent by the CS 1000 to the Office Communications Server. To have the full OCN sent, the CLID table must be configured with the Home Location (HLOC) of the CS 1000. Outgoing Office Communicator calls to the Public network must have the Call ID table used by the associated MARP TN (a TN with the same extension used by Office Communicator marked as MARP) correctly configured.
Telephony Gateway and Services configuration 159 Table 35 LD 15 Prompt Response REQ chg TYPE net Description TYPE NET_DATA 0 CUST OPT AC2 FNP CLID yes SIZE 5 INTL 1 ENTRY 0 HNTN HLCL 967 HLOC 354 ... The response to SIZE must be a number greater than 0. The response to ENTRY must match the CLID table entry for the target telephones. Generally the default is 0.
Configuration all OCS and Enterprise Edition Pools. Also, the FQDN must resolve to the IP address of the OCS for all types of DNS queries (not just for the SIP service type). DNS server must respond with the correct IP for a generic DNS query. There are a number of different types of DNS queries that can be performed. ATTENTION The Signaling Server must be rebooted to ensure that all DNS server configurations take effect.
Telephony Gateway and Services configuration 161 A CS 1000 with existing SIP trunks requires a configuration change to be compatible with Office Communications Server. In order for a SIP Trunk to communicate with Office Communications Server, the SIP Transport Protocol must be configured as TCP, not UDP (see SIP Gateway configuration). However, this is not valid when SPS in Proxy All mode is used, since everything goes through SPS. The default Local SIP Port of 5060 is required.
Configuration ATTENTION The Route Data Block (RDB) must not have a value configured for the prompt INST. Otherwise, incoming calls from Office Communicator to the CS 1000 do not work. ATTENTION When configuring the D Channel used by the SIP Trunk for Converged Office Telephony Gateway and Services, configure the NASA prompt to Yes. Failure to do so can result in limited call transfers through Office Communicator.
Telephony Gateway and Services configuration 163 The Route Data Block is ESN5 if the output from Element Manager, or a terminal window, is: TYPE RDB CUST 00 DMOD ROUT 10 DES IPROUTE TKTP TIE VTRK YES ZONE 100 PCID SIP ... ANTK SIGO ESN5 STYP SDAT ATTENTION If the Route Data Block (RDB) already has associated Virtual Trunks and is configured to SIGO STD, all Virtual Trunks must be removed before the RDB can be changed to ESN5.
Configuration Figure 56 SIP Trunk Domain name Configuring the SIP Trunk Domain name describes how to configure the SIP Trunk domain name to match the Office Communications Server domain name. Configuring the SIP Trunk Domain name Step Action 1 Log into the Element Manager page for the Signaling Server. 2 Go to IP Telephony. 3 Click Nodes, Servers, Media Cards. 4 Select Configuration. 5 Click Edit next to the correct node.
Telephony Gateway and Services configuration 165 Figure 57 Element Manager Signaling Server Properties 7 In most cases, the value for the field SIP Domain Name must match the domain of the Office Communications Server. In Figure 57 "Element Manager Signaling Server Properties" (page 165), the SIP Domain name is ocs2007a.corp.nortel.com. Only in situations where the MCM is configured to register to the NRS using End_Point_Name@Service_ Domain_Name can the two SIP Domain Names not match.
Configuration Figure 58 SIP URI Map The SIP URI Map must match the NRS server configuration in the following manner: • The Private/UDP domain name maps to the L0 Domain on the NRS • The Private/CDP domain name maps to the L1 Domain on the NRS MCM must be configured to match one of the domain names. For example, in a UDP network, the configured domain name is OCS2007_UDP in MCM. Mediation server supports Mediation server routing and Mediation server load balancing. MCM 3.
Telephony Gateway and Services configuration 167 SIP Gateway CLID Parameters configuration The SIP Gateway CLID parameters are used to adjust the format of telephone numbers for incoming call appearances. For Office Communicator, these settings impact the format of numbers that appear on the incoming call pop-up for Telephony Gateway and Services (the SIP call leg for Office Communicator clients that are twinned with a CS 1000 DN through a PCA ).
Configuration +. The parameters Subscriber/Number of digits to strip and prefix to insert are used to modify the format of subscriber numbers presented from the PSTN due to region specific requirements. The E.164 format of national calls (for example, NPA in North America) is: • +.
Telephony Gateway and Services configuration 169 • Three different modes: Proxy All, Redirect, and Proxy SIP Gateway Calls • Transport: TLS (5061) and TCP (5060) For information on configuring the SPS, see NRS configuration. NRS configuration The Server IP running the MCM application (generally an Office Communications Server 2007 Proxy) must be configured on the NRS as a dynamic SIP endpoint, or gateway, and not as a collaboration server.
Configuration The NRS must have the same UDP or CDP dialing plan prefix to route calls to the MCM endpoint. This UDP or CDP dialing plan prefix is the same one configured for the PCA calls.
Remote Call Control configuration 171 In order to support these calls, placed through the SIP Gateway, you must configure the parameters CNTC, NATC, and INTC in LD 15. These parameters ensure that fully qualified numbers within the same country are dialed as national numbers by stripping the country code and adding the national dial prefix. Example 1 (Outside of North America) AC1=0, CNTC=31, NATC=0, INTC=00 The URI incoming for the SIP INVITE for the call is: sip:+31123456789@domain.
Configuration 4 Choose Enable Remote call control to enable clients control of the PBX phone or Enable Enterprise Voice and click the Enable PBX integration box to enable both Remote Call Control and Enterprise Voice. —End— RCC and PBX integration on OC client After phone integration options are enabled for a user on the server, they are enabled on the OC client. Step Action 1 Go to the Office Communicator menu. 2 Choose Tools and then select Options. 3 Go to the Phones tab.
Remote Call Control configuration 173 Figure 61 Enable integration with your phone system CS 1000 configuration Application Module Link (AML) is the main interface used to support call control requests from SIP CTI clients between the SS TR/87 FE application and the CS 1000. Incremental Software Management (ISM) defines the number of TNs that can be accessed through SIP CTI by the Class of Service (CLS) T87A.
Configuration LD 17: Configure AML Link Prompt Response Description REQ CHG Change existing data. TYPE ADAN ADAN A new AML link; the link is an ELAN type. The link number can be from 32 to 47 on a small system and from 32 and 127 on a large system. An AML link number within the above range implies that the transport is over a TCP link.
Remote Call Control configuration 175 Configuring the SIP CTI TR/87 ISM limit Incremental Software Management (ISM) (SIP CTI TR/87) is used to define the number of TNs that can be configured with the T87A class of service. The TR/87 configuration for a given TN requires that in addition to the existence of the CLS T87A, the controlled line itself must also be identified as an AST DN. This implies that AST ISMs are also required.
Configuration A new CLS (T87A) is introduced to allow a TN to support the SIP CTI application. The AST prompt is used to configure which DN key on the TN is controlled or monitored by the SIP CTI application. A maximum of two keys per TN can be configured as AST keys. CLID information is sent, or suppressed, to Office Communicator based on the CLS CNDA/CNDD consistent with the presentation of the CLID information on the station display itself.
Remote Call Control configuration 177 • Any Remote Call Control service request sent by Office Communicator, such as Make Call or Answer Call, always apply to the device defined as the MARP TN. • For SCR keys telephony, presence updates (for example, on the phone) are supported for all TNs within a MADN group Example: Answering a call on a wireless station SCR key on a non-MARP TN shows the Office Communications Server user as "On the Phone".
Configuration Node parameter configuration The node IP is the IP address of the TR/87 FE: • You can configure multiple nodes to support TR/87 applications for additional capacity. The Remote Call Control SIP URI of users determines which node they use. • An AML restriction dictates that only one application can acquire a given DN on a Call Server.
Remote Call Control configuration 179 SIP Gateway parameter configuration The SIP Gateway application must be enabled.
Configuration Also, the FQDN must resolve to the IP address of the OCS server for all types of DNS queries (not just for the SIP service type). (see Figure 65 "DNS configuration" (page 180)) DNS server must respond with the correct IP for a generic DNS query. There are a number of different types of DNS queries that can be performed. Step Action 1 Log on to Element Manager and navigate to LAN configuration. 2 Enter the FQDN of up to three DNS servers.
Remote Call Control configuration 181 SIP CTI Services configuration settings In Element Manager, under SIP CTI services, the Calling Device URI Format must be configured as phone-context= to support OCS 2007 RCC. Ensure the Dial Plan prefix section values under SIP CTI Services are configured. Click Save and Transfer the configuration and then reboot the Signaling Server.
Configuration Figure 66 SIP CTI Services settings Parameter: Service Enabled The default state of the SIP CTI service is disabled. To enforce the change of state for this parameter, you must reboot. The SIP CTI service consumes approximately 140 MB of RAM on the Signaling Server when enabled. ATTENTION The configuration change to enable or disable the SIP CTI service is propagated to all Signaling Servers within the node.
Remote Call Control configuration 183 Parameter: Maximum Associations Per DN This parameter defines the maximum number of simultaneous TR/87 SIP dialogs that can be active for a single DN. Multiple instances of Office Communicator (for example, home, office, laptop) are active and each of them can have its own active TR/87 session. This parameter limits the number of simultaneous client sessions for a single DN.
Configuration SIP CTI Dial Plan prefixes The SIP CTI dial plan prefixes configuration settings are used to prefix phone numbers sent to the Call Server as a result of SIP CTI call attempts. Parameter: National Prefix When calls are made to E.164 fully qualified numbers this parameter is used in combination with the “International Calls as National” setting in the CTI IP settings section. When a call to an E.
Remote Call Control configuration 185 SIP CTI CLID configuration parameters The SIP CTI CLID parameters are used to adjust the format of phone numbers for incoming call appearances. For Office Communicator these settings impact the format of numbers that appear on the incoming call pop-up for Remote Call Control. ATTENTION These settings are independent of the similar SIP GW CLID parameters to allow independent control of the format of numbers on the incoming call pop-up for Remote Call Control.
Configuration can be entered using the home location code to ensure a consistent unique format throughout the enterprise. Two scenarios are provided using the following example parameters: • SIP CTI Dial Plan Prefix - Location Code Call Prefix = 6 • SIP CTI CLID Parameters - Home Location Code = 343 Scenario 1 - SIP STI Dial Plan = CDP A call is placed to the DN controlled by Office Communicator for RCC from DN 3000 on the same Call Server.
Remote Call Control configuration 187 Scenario 2, Dial Plan = CDP, Calling Device URI Format = phone-context= SIP GW URI map entries: The TEL URI generated for the caller is: "tel:3000;phone-context=cdp.nortel.com" Parameter: Home Location Code This parameter defines the home location code to be used in CLID generation in combination with the SIP CTI dial plan setting. See section "Parameter: Dial Plan" for an example of the use of this parameter.
Configuration • An RCC call from Office Communicator to the E.164 number +16135006000 produces a call from the controlled DN to 616135006000. An RCC call from Office Communicator to the E.164 number +33123456789 produces a call from the controlled DN to 601133123456789.
Remote Call Control configuration 189 • An RCC call from Office Communicator to the E.164 number +31123456789 produces a call from the controlled DN to 00123456789. • An RCC call from Office Communicator to the E.164 number +33123456789 produces a call from the controlled DN to 00033123456789.
Configuration Figure 69 SIP URI Map Configuring CDR Call Detail Recording (CDR) records are produced for calls controlled using the Remote Call Control feature. The format of these CDR records is the same as those of calls dialed directly from a telephone’s keypad. Dialing E.164 International Format Numbers from Office Communicator Phone Calls (SIP CTI) When a call is originated from Office Communicator to an E.
Remote Call Control configuration 191 Figure 70 SIP INFO message The TR/87 FE that resides on the Signaling Server contains a feature to insert the appropriate dial plan prefix, either national or international, depending on the location of the Call Server and destination of the call. This ensures calls within the country use the national dial format and calls outside the country use the international dial format. This feature is enabled or disabled in Element Manager in the SIP CTI Settings section.
Configuration Normalizing phone numbers Office Communicator 2007 requires that all phone numbers be in standard TEL URI format as defined in RFC 3966 for dialing and for reverse number lookup. Office Communicator 2007 uses phone numbers that are provisioned (Active Directory and Outlook) and that are adhoc from the user through the user interface. All sources can be free format—a convention that is not in compliance with TEL URI.
Normalizing phone numbers 193 tel:+14255551212;ext=5551212;ad-rdn=telephoneNumber;displayName=(425)555-1212 The ad-rdn = telephoneNumber is a proprietary parameter describes the type of the phone number and displayName, which is a proprietary parameter that holds the display format of this phone number (by default, the original phone number before normalization). By default, the msRTCSIP-RCC Line is copied from the proxy address (attribute ad-rdn=telephoneNumber).
Configuration MCM provides authorization of Remote Call Control service requests based on the configuration defined in Active Directory for each Office Communications Server user. Office Communicator requires that all phone numbers be in the standardized TEL URI format (RFC 3966) for reverse number lookup (matching the phone number of an incoming call to a known Office Communications Server user) and for dialing (either through an adhoc interface or through a menu from a user object).
Normalizing phone numbers 195 Figure 71 Normalization rule example for UDP dial plan Result • The normalized version (tel:+16139675000;ext=$1$2) of the business number in Active Directory entries is stored in the Global Address List (GAL) and downloaded at login by the Office Communicator 2007 client from the Address Book Service.
Configuration Figure 72 Company phone number normalization rules for CDP 2 Refresh the Address Book on the server by issuing the following command on the server running ABService as shown in the example Figure 73 "Refresh Address Book on the server" (page 197): %ProgramFiles%\Microsoft Office Communications 2007\Server\Core\ABServer.exe -syncNow Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.
Normalizing phone numbers 197 Figure 73 Refresh Address Book on the server 3 Exit from Office Communicator 2007. 4 Refresh Address Book on the client as shown in Figure 74 "Refresh Address Book on the client" (page 197). Issue the following command on the PC running Office Communicator 2007: Del “%UserProfile%\Local Settings\Application Data\Microsoft\ Communicator\*" /q Figure 74 Refresh Address Book on the client 5 Launch Office Communicator 2007.
Configuration SIP Routing and Redundancy configuration Office Communicator is a soft phone application as well as a SIP User Agent (UA). Office Communications Server Front End server (Standard Edition Server or Enterprise Edition Server) hosts Office Communicator . The TR/87 FE within the Communication Server 1000 is also a SIP UA. Office Communicator 2007 establishes a SIP dialog in one direction only: from the application to the TR/87 FE.
OCS 2007 users using UM 2007 in integrated mode Configuring a basic mailbox for the UM user Step Action 1 Configure the OCS user mailbox in Exchange UM. 2 Configure SIP URI. For example, ocs2007a.corp.nortel.com 3 Add the Exchange UM Address (Extension) for every Exchange UM user. 4 Select Manually enter mailbox extension and enter the CS 1000 DN xxxx.
Configuration Figure 75 User Properties window for Exchange UM 4 Click on the E-mail Addresses tab. 5 Click on the Add menu and select EUM Address. 6 In the UM Address (Extension) window, enter the useralias@domain of the user in the Address/Extension field . For example, brendanmccarthy@ocs2007a.corp.nortel.com Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.
OCS 2007 users using UM 2007 in integrated mode 201 Figure 76 UM Address 7 Click on the Browse button to find the associated Dial plan for the user. Click OK and then click Apply from the E-Mail Addresses tab of the Properties window. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Configuration Figure 77 Dial plan window 8 The new EUM address is added. To find the new UM Extension, click on the Mailbox Features tab, right-click on Unified Messaging , and select Unified Messaging Properties . In the UM Addresses (Extensions) field, there are three addresses. • CS 1000 DN • CS 1000 DN@domain • useralias@domain Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.
OCS 2007 users using UM 2007 in integrated mode 203 Figure 78 Unified Messaging Properties window —End— Option 2 adding CS 1000 DN as Exchange UM These procedures assume the installation procedures for Exchange UM have already been completed. Download Microsoft documentation from the Download Center at www.microsoft.com. Configuring a basic mailbox for the UM user Step Action 1 Configure the OCS user mailbox in Exchange UM.
Configuration 4 —End— Adding Exchange UM Step Action 1 From the Exchange Management Console window, click on Recipient Configuration, and select Mailbox. 2 Select a user. For example, Brendan McCarthy 3 Right-click on the user and select Properties. Figure 79 User Properties window for Exchange UM 4 Click on the E-mail Addresses tab. 5 Click on the Add menu and select EUM Address.
OCS 2007 users using UM 2007 in integrated mode 205 Figure 80 UM Address 7 Click on the Browse button to find the associated Dial plan for the user. Click OK and then click Apply from the E-Mail Addresses tab of the Properties window. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Configuration Figure 81 Dial Plan window 8 The new EUM address is added. To find the new UM Extension, click on the Mailbox Features tab, right-click on Unified Messaging , and select Unified Messaging Properties . In the UM Addresses (Extensions) field, there are three addresses. • CS 1000 DN • CS 1000 DN@domain • useralias@domain Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.
OCS 2007 users using UM 2007 in integrated mode Figure 82 Unified Messaging Properties window —End— Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Configuration Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Maintenance Introduction The following are maintenance tips for MCM 3.0 . For more information on troubleshooting tips, see "Troubleshooting" (page 215) section. Communication Server 1000 No new SIP tracing capabilities are available on the Communication Server 1000. Existing SIP Trunk and Gateway tracing capabilities are used. MCM 3.0 MCM 3.
Maintenance SIP tracing can be filtered by DN number. MCM SIP tracing is implemented as part of the application logging functionality. Special commands are not required. For more information on tracing, see Capturing traces and logs — You can remotely access the Office Communications Server application using the Windows 2003 server remote access capability. — Task Manager is supported in Windows 2003 Server for MCM. Patches and upgrades Patching is not supported in MCM 3.0 ..
Remote Call Control 211 Prompt Response Description > SIPCTITraceLevel Configure the TR87 SIP message Trace Level. The level can be one of the following: 0 –TR87 SIP message body (ECMA 323) only 1 – TR87 SIP message body (ECMA 323) and message headers > SIPCTITrace on Turn on SIP CTI trace for all soft clients in both incoming and outgoing directions. > SIPCTITrace off Turn off SIP CTI trace for all soft clients in both incoming and outgoing directions.
Maintenance Prompt Response Description > SIPCTIStop all De-acquire all AST DNs and terminate all the TR87 SIP sessions. > SIPCTIStop De-acquire one specific AST DN and terminate all the TR87 SIP sessions associated with this AST DN.
Remote Call Control • SIPCTITotalMonitorStopSuccesses • SIPCTITotalConferenceCallRequests • SIPCTITotalConferenceCallSuccesses • SIPCTITotalSetForwardingRequests • SIPCTITotalSetForwardingSuccesses • SIPCTITotalGetForwardingRequests • SIPCTITotalGetForwardingSuccesses • SIPCTITotalSessionTerminated 213 For information on how to access these OM’s through Element Manager, see Element Manager System Administration (NN43001-632).
Maintenance Prompt Response Description 4—Print all input and output AML data buffer except POLLING message with IE type and data decoding. ATTENTION This trace prints out AML messages to and from CS at the transport layer. Because sending and receiving AML messages are per AML link instead of per DN or TN, no good solution exists to filter on this AML trace tool. Nortel recommends that you do not turn on the trace in a busy system.
Troubleshooting Use the following procedures to assist in troubleshooting general Converged Office problems. Checking Telephony Gateway (SIP Gateway) configuration Checking Telephony Gateway configuration Step Action 1 Check all required Communication Server 1000 resources (packages, license, and Communication Server 1000 patches). 2 Check the DN, telephone TN and PCA configuration. 3 Check the DNS on the Signaling Server.
Troubleshooting Checking Remote Call Control (SIP CTI) configuration Checking Remote Call Control configuration Step Action 1 Check all required Communication Server 1000 resources (packages, license, and Communication Server 1000 patches). 2 Check the DN, telephone TN, and PCA configuration. 3 Verify that AST, IAPG, and CLS (CDMR/TR87A) are configured correctly (SIP CTI only). 4 Verify that the AML Link status is up. Make sure that the ELAN ID is greater or equal to 32 (SIP CTI only).
SIP CTI services does not come up 217 Symptom: After SIP CTI services are activated, you are unable to log on to the Signaling Server through Element Manager. When rebooting, some HTTP tasks are not up. Possible cause: Insufficient memory. Solution: Check the memory and upgrade the memory to 1 gigabyte (GB), if required. The Signaling Server (running Converged Office) requires 1 GB of memory. Release 4.5 only required 512 megabytes (MB).
Troubleshooting Figure 83 nslookup tool Solution 1: Check configuration parameters in AD Check the configuration parameters in Active Directory for this user. Run a SIPCTITrace on the Signaling Server and check the MCM logs. For more information on activating the trace, see "SIP CTI traces on the Signaling Server" (page 226) and Activating MCM debug trace Solution 2: Confirm FQDN and the IP address are correct Solution 2: Confirm that the FQDN (case sensitive) and the IP address are correct.
SIP CTI services does not come up 219 Possible cause: VSID or ELAN ID is lower than 32. Solution: Follow the procedure "Reconfigure SIP CTI service" (page 219) to solve this issue. Reconfigure SIP CTI service Step Action 1 Reconfigure the VSID and ELAN IDs so both are greater than 32. Confirm that the SIP CTI service is up. 2 Check the SIP CTI status on the Signaling Server.
Troubleshooting 3 In LD 48, check the ELAN status on the Call Server Table 40 LD 48 Prompt Response Description .stat elan Check the ELAN status on the Call Server Screen output: SERVER TASK: ENABLED ELAN #: 032 DES: CDLCS APPL_IP_ID: 47.11.157.112 : 0000F600 LYR7: ACTIVE EMPTY APPL ACTIVE —End— MCM not synchronizing new users in AD Cache mode Problem: MCM cannot synchronize new users in AD Cache Mode.
MCM not synchronizing new users in AD Cache mode 221 Checking the Global Catalog content manually Step Action 1 Install the Operating System Support Tools on the server (usually the Tools setup is on the MS Windows 2003 Server setup disk). 2 Run the LDP tool (%ProgramFiles%\Support Tools\ldap.exe). 3 Connect to the GC server IP address at the port 3268 (Connection -> Connect …). 4 Bind with the MCM service account credentials (Connection -> Bind …).
Troubleshooting Accessing permissions for the AD object properties Step Action 1 Install the Operating System Support Tools on the server (usually the Tools setup is on the MS Windows 2003 Server setup disk). 2 Run the ADSIEdit tool (%ProgramFiles%\Support Tools\adsiedit.msc). 3 Navigate to the users object container or the specific user’s object. 4 Right-click the item and open Properties. 5 Go to the Security tab and click the Advanced button.
Pop-up not displayed 223 Enabling propagation of the Active Directory field to the Global Catalog Step Action 1 Open the Active Directory Schema snap-in. 2 Select the Attributes folder on the left pane. 3 Find and the right-click the necessary field (otherTelephone). 4 Click the Property menu item. 5 Enable Replicate this attribute to the Global Catalog. 6 Click OK.
Troubleshooting Possible causes: The Phone Context may be not correct. Address Book Service may not be properly setup. Phone integration is not activated. Solutions: • Ensure that the user’s name is in Active Directory, the MCM, and the Signaling Server (L1 parameter) have the correct Phone Context.
Capturing traces and logs 225 Symptom: The telephone is on Call Forward to another number. When the Office Communicator user who is associated to this telephone logs in (this telephone is controlled by the Office Communicator user through SIP CTI), the Office Communicator cancels the Call Forward. Possible cause: This is a Microsoft issue that Nortel has escalated to Microsoft. Solution: No solution yet.
Troubleshooting AML traces on the Call Server (SIP CTI only) In LD 48, activate AML traces on the Call Server (SIP CTI only): Table 41 LD 48 Prompt Response Description EDD000 enl msgi 32 Enable incoming AML traces for ELAN 32 EDD000 enl msgo 32 Enable outgoing AML traces for ELAN 32 Screen output: ELAN32 I MTYP=3B IACR TN=0 TIME=18:07:34 ELAN32 IN B1B1BE7A OUT B1B1BE7C QSIZE 00000000 ELAN32 03 20 00 00 00 00 1E 3B 00 0B 00 00 95 01 05 36 02 72 14 E6 ELAN32 0C BF EE 01 FF FF FF 00 00 0F FF 00
Capturing traces and logs Figure 85 Example of screen output for SIP CTI Traces on the Signaling Server SIP Gateway traces on the Signaling Server In PDT, activate Gateway traces on the Signaling Server. Table 43 SIP Gateway trace in PDT Prompt Response pdt SIPCallTrace on pdt SIPTraceLevel 1 Description Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.
Troubleshooting Figure 86 Example of screen output for SIP Gateway trace MCM logs MCM 3.0 generates a daily log file with no maximum size restrictions and no cleanup procedures are implemented. The contents of the existing log file remain in all cases. SNMP is not supported on the MCM 3.0 application. Alarms are logged to an MCM log file in addition to the Windows 2003 Event Viewer. MCM 3.0 logging has the following levels: • None: No messages or alarms are logged to the file.
Capturing traces and logs 229 • SIP: SIP messages (filtered by distinct DN) are logged further to alarms. Only one DN can be specified at the same time in MCM. • Debug: Debug information is logged to the MCM log file. • SIP and Debug To clear a log, click on the Clear Log button. The backup file is stored as MCMlog.bak. See Figure 87 "MCM logs" (page 229) for an example of the Logs window. Figure 87 MCM logs Activating MCM logging The following section details how to turn on MCM logging.
Troubleshooting To turn off MCM logging, see "Resetting MCM debug trace" (page 231). MCM log file output The following shows a snippet from the log output file: 12/14/2007 11:11:37 AM: 3.0.1.76: Debug: OnCustomCommand: got command: update config data 12/14/2007 11:11:38 AM: 3.0.1.76: Debug: ConfigurationData: ReadConfigFile: Invalid secondary NRS address: 0.0.0.0 12/14/2007 11:11:38 AM: 3.0.1.76: Debug: ConfigurationData: ReadConfigFile: Invalid LDAP server IP address: 0.0.0.
Capturing traces and logs 231 Figure 88 Event Viewer window Resetting MCM debug trace Use the following procedures to reset the MCM debug trace. Resetting MCM debug trace Step Action 1 On the MCM interface, select Tools and then choose Logs from the menu. 2 Go to Log Level and choose None. 3 Delete the MCM.log file from the directory where MCM is installed. —End— OCS logs Use the following procedures to activate an OCS log.
Troubleshooting Activating OCS logs Step Action 1 Right-click on the OCS pool and select Logging Tool and then choose New Debug Session. 2 In the OCS 2007 Logging Tool window, specify the Components to trace, Severity level, and other log file options. See example Figure 89 "OCS debugging tool" (page 232). 3 Click the Start Logging button. 4 To view the log file, click the Analyze Log Files button. The log file is stored as a .txt file in c:\WINDOWS\Tracing folder.
Capturing traces and logs 2 Choose the General tab. 3 Select the Turn on logging in Communicator and the Turn on Windows Event Logging for Communicator checkboxes. See Figure 90 "Turn on Logging and Windows Event Logging" (page 233). 4 Click OK. 233 —End— Figure 90 Turn on Logging and Windows Event Logging OC client start-up debugging To determine if there is a PBX connection, a handset icon will be present in the upper right of the OC client window.
Troubleshooting Figure 91 No PBX connection for OC client Case checklists Use the following checklists prior to opening a case to ensure that all relevant information is collected: Table 44 Signaling Server information Check The patches list installed on the Signaling Server: pdt>mdp issp The configuration on the Signaling Server: • pdt>cd /u/config • pdt>copy config.
Case checklists Check In LD 48, perform the command stat elan Provide the print out for the SIP Route and all related RLI/DMI Table 46 NRS configuration information Check NRS configuration Print capture of the Signaling Server endpoint configuration Print capture of the MCM endpoint configuration Print capture of the Routing Entries for the MCM endpoint Table 47 MCM configuration information Check Send the MCM.
Troubleshooting Check Print Capture of the OCS user for the Office Communications Server Print Capture of the OCS user for the Office Communication, Advanced Settings Table 50 Tracing information Check An example AML trace on the Call Server (if it is a problem regarding the RCC feature not able to control the telephone An example Signaling Server trace: SIPCallTrace (For problem related to SIP Gateway) An example Signaling Server trace: SIPCallTrace (For problem related to SIP Gateway) An example Sign
Appendix A Call Flow and protocol details Contents This section contains information about the following topics: "Overview" (page 237) "Message sequence" (page 238) "Call flow" (page 239) Overview The Converged Office feature provides interworking between Nortel and Microsoft products. It addresses the market need of our customers who want to use Microsoft client software for their multimedia needs while continuing to use the Business Grade Telephony of the Nortel IP PBX.
Appendix A Call Flow and protocol details Message sequence TR/87(4) is an ECMA Technical Report that describes the use of SIP as a transport of service requests and events defined by the ECMA-269(5) specification as XML bodies within SIP messages. The ECMA-323(6) specification defines the XML format of ECMA-269 services and events.
Call flow 239 Figure 93 SIP INFO message with ECMA-323 content Call flow This section illustrates the call flow sequence for the Telephony Gateway and Services and Remote Call Control with Mediation Server present. Telephony Gateway and Services call flow This section explores dual forking call flows in different scenarios when Mediation Server is present.
Appendix A Call Flow and protocol details Figure 94 Inbound call to OC client with SPS, OC client answers Incoming calls to OC 2007 can originate directly from a phone behind the Communication Server 1000 where the request URI represents the destination. Incoming calls can also come from a PCA , where the Request URI is a service DN used to route the call to OCS 2007, and the actual destination is determined by a special header (x-nt-ocn) that contains the destination DN.
Call flow 241 ATTENTION This scenario would also apply if the inbound call originated from the PSTN. Figure 95 Inbound call to OC client with SRS, phone answers The next scenario as illustrated in Figure 96 "Direct inbound call to OC client, OC client answers" (page 242) depicts a limited deployment configuration where the MCM is pointing directly to the Communication Server 1000. The deployment of SPS or SRS are not present.
Appendix A Call Flow and protocol details Figure 96 Direct inbound call to OC client, OC client answers This scenario as illustrated in Figure 97 "Outbound call from OC client to another client, phone answers" (page 243) depicts the prevention of dual forking in a configuration where both users are registered to the same Communication Server 1000 with the presence of SPS. Joe calls Bob from his OC client. Bob accepts the call from his phone.
Call flow 243 Figure 97 Outbound call from OC client to another client, phone answers This scenario as illustrated in Figure 98 "Outbound call from OC client to another OC client, OC client answers" (page 244) depicts a configuration with a CDP dialing plan and the presence of the SRS component on the network. Joe calls Bob from his OC client. Bob accepts the call from his OC client. ATTENTION For the CDP dialing plan to work, the entire network must be configured with CDP.
Appendix A Call Flow and protocol details Figure 98 Outbound call from OC client to another OC client, OC client answers Call Forward by OC client This scenario depicts a situation where the Communication Server 1000 phone dials the phone number of an OC client Bob and is forwarded to another client Joe. Bob’s twin phone number is x5555 and Joe’s number is X3333. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.
Call flow Figure 99 Call Forward call flow by OC client Remote Call Control Call Flow Figure 100 "Remote Call Control Session Establishment through SRS" (page 246) illustrates the Remote Call Control Session Establishment through SRS. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Appendix A Call Flow and protocol details Figure 100 Remote Call Control Session Establishment through SRS Supported features Table 51 SIP CTI supported features Supported by CS 1000 TR/87 FE Supported by Office Communicator 2007 17.2.3 - Conference X X 17.2.4 - Connection Cleared X X 17.2.5 - Delivered X X 17.2.7 - Diverted X X 17.2.8 - Established X X 17.2.9 - Failed X X 17.2.10 - Held X X 17.2.14 - Originated X X 17.2.16 - Retrieved X X 17.2.
Supported features Feature Supported by CS 1000 TR/87 FE Supported by Office Communicator 2007 X X Call Associated Events 18.2.5 - Service Completion Failure Logical Device Features 22.1.9 - Get Do Not Disturb X (Release 5.0) 22.1.10 - Get Forwarding X X X X 22.1.17 - Set Do Not Disturb 22.1.18 - Set Forwarding Logical Device Feature Event 22.2.12 - Do Not Disturb X 22.2.13 - Forwarding X X X X X X 15.1.2 - Monitor Start X X 15.1.
Appendix A Call Flow and protocol details Feature Supported by CS 1000 TR/87 FE Supported by Office Communicator 2007 17.1.15 - Hold Call X X 17.1.18 - Make Call X X X 17.1.21 - Reconnect Call 17.1.22 - Retrieve Call X X 17.1.25 - Single Step Transfer Call X X 17.1.26 - Transfer Call X X Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.
Appendix B Configuration Examples Contents "Introduction" (page 249) "Standard Edition" (page 249) "Enterprise Edition" (page 275) "Host Authorization" (page 283) "Routing" (page 284) "Configuring DNS" (page 286) "Active Directory configuration" (page 288) "Installing and configuring MCM" (page 289) "Signaling Server checklist" (page 292) "Configuring NRS" (page 293) Introduction As described in the Planning and Engineering chapter, small, medium, and large networks require different editions of Offic
Appendix B Configuration Examples Setting up the lab Follow these steps to ensure the lab is set up correctly: Setting up the lab Step Action 1 Confirm that the CS 1000 server is version 5.0 with the Product Enhancement Package or a later version. 2 Confirm that the Signaling Server is version 5.0 or later with all patches as required in the Product Bulletin 3 Confirm that you have the OCS 2007 Standard Edition server . 4 Confirm that you have MCM 3.0 .
Standard Edition 251 Collecting required data Collect the required data listed in the following three tables before you begin to configure the Converged Office solution. The information entered here can be used to verify configuration settings later on. Table 52 Microsoft Active Directory Required information Record your information For example User SIP URI chris@ocs2007a.corp.nortel.com Server URI sip:2070;phone-context=cdp.udp@test.
Appendix B Configuration Examples SIP URI map, Private/CDP domain name cdp.udp SIP CTI Service, Service enabled Yes SIP CTI Service, Customer Number 0 SIP CTI Service, International Calls As National Yes SIP CTI Service, National Prefix 0 SIP CTI Service, International Prefix 00 SIP CTI Service, Dialing Plan cdp SIP CTI Service, Calling Device URI Format sip:2070;phone-context=cdp.udp@test .
Standard Edition 253 Table 56 LD 22––check for licenses Prompt Response REQ prt TYPE slt Description Screen output: ANALOGUE TELEPHONES 32767 CLASS TELEPHONES 32767 DIGITAL TELEPHONES 32767 DECT USERS 32767 IP USERS 32767 BASIC IP USERS 32767 TEMPORARY IP USERS 32767 DECT VISITOR USER 10000 ACD AGENTS 32767 MOBILE EXTENSIONS 32767 TELEPHONY SERVICES 32767 CONVERGED MOBILE USERS 32767 NORTEL SIP LINES 32767 THIRD PARTY SIP LINES 32767 PCA 32767 LEFT 32762 USED 5 AST 32767 LEFT 32756 USED 11 ITG ISDN
Appendix B Configuration Examples Table 57 LD 22–MS_CONV package Prompt Response REQ prt TYPE pkg 408 Description Screen output: MS_CONV 408 5 Ensure that the VSID and the ELAN ID are greater than or equal to 32 and that the SECU parameter is configured to YES for ELAN and for VAS configuration.
Standard Edition Prompt Response DATE PAGE DES 255 Description Screen output: DES SIP TN 156 0 00 00 VIRTUAL TYPE IPTI CDEN 8D CUST 0 XTRK VTRK ZONE 000 TRK ANLG NCOS 0 RTMB 62 1 CHID 1 TGAR 0 STRI/STRO WNK WNK SUPN YES AST NO IAPG 0 CLS UNR DTN WTA LPR APN THFD XREP P10 NTC TKID AACR NO DATE 5 DEC 2006 7 In LD 21, check that NCNA and NCRD are configured to YES and that SIGO is ESN5 in the SIP Route Configuration.
Appendix B Configuration Examples ESN NO RPA NO CNVT NO SAT NO RCLS EXT VTRK YES ZONE 000 PCID SIP CRID YES NODE 81 DTRK NO ISDN YES MODE ISLD DCH 63 IFC SL1 PNI 00001 NCNA YES NCRD YES TRO YES FALT NO CTYP UKWN INAC YES ISAR NO DAPC NO PTYP ATT … DEXT NO ANTK SIGO ESN5 MFC NO … 8 For TN configuration in LD 11, configure AST, TR87A, PCAM, and CDMR Class of Service. Configure MARP for the telephone. ATTENTION The screen output shown here may differ depending on the setup used.
Standard Edition Prompt Response PAGE DES Description Screen output: DN 2070 CPND CPND_LANG ROMAN XPLN 16 DISPLAY_FMT FIRST,LAST TYPE SL1 TN 100 0 03 04 V KEY 00 MARP DES DLOCS2 3 DEC 2007 (2004P2) TN 152 0 00 30 V KEY 00 DES PCA 12 JUL 2006 (PCA) NACT Table 62 LD 11 Prompt Response REQ prt TYPE tnb TN 152 0 0 14 DATE PAGE DES Description Screen output: DES CDLCS TN 152 0 00 14 VIRTUAL TYPE I2004 CDEN 8D CTYP XDLC CUST 0 ZONE 000 FDN TGAR 0 LDN
Appendix B Configuration Examples XLST 0 SCPW 2070 SFLT NO CAC_MFC 0 CLS CTD FBD WTA LPR MTD FND HTD TDD HFD CRPD MWD LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1 POD DSX VMD CMSD SLKD CCSA-CSI SWD LNA CNDA CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD ICDD CDMD LLCN MCTD CLBD AUTU GPUD DPUD DNDA CFXD ARHD FITD CLTD ASCD CPFA CPTA HSPD ABDD CFHD FICD NAID BUZZ UDI RCC HBTD AHA IPND DDGA NAMA MIND PRSD NRWD NRCD NROD DRDD EXR0 USRD ULAD CCBD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN FDSD NOV
Standard Edition Prompt Response DATE PAGE DES 259 Description The screen output shown here may differ depending on the setup used.
Appendix B Configuration Examples IAPG 0 AACS NO AACS NO ITNA NO DGRP MLWU_LANG 0 MLNG ENG DNDR 0 KEY 00 SCR 2070 0 CPND ANIE 0 01 HOT P 3 888 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 TRN 18 AO6 19 CFW 16 20 RGA 21 PRK 22 RNP 23 24 PRS 25 CHG 26 CPN 27 28 29 30 31 Date 16 APR 2008 Screen output … PCA ON … Screen Output: Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.
Standard Edition 261 …. TYPE UEXT CDEN 8D CTYP XDLC CUST 0 UXTY TLSV …. KEY 00 SCR 2070 0 01 HOT P 3 888 10 Confirm that AST is not configured. 11 Configure TR87D and CDMR Class Of Service. 12 Confirm that this PCA is not configured as MARP. 13 Configure Hot P for SIP Gateway calls. 14 Configure CLS PCAM. 15 Configure DSC for PCA. Create a DSC to route the call to the SIP route using the RL1.
Appendix B Configuration Examples 16 Check LD 21 to confirm that PCA is activated. If not, configure LD 15 to PCA to ON to allow the incoming call to twin the PCA and make the SIP Gateway call work. —End— Signaling Server checklist Use the following procedure to confirm the correct configuration of the Signaling Server. Checking the configuration of the Signaling Server Step Action 1 Confirm that the Signaling Server is version 5.0 or higher.
Standard Edition 263 Figure 102 FQDN of the OCS 2007 Front End server 4 Define the IP address of the server acting as DNS. For example, in Figure 103 "DNS configuration on the Signaling Server" (page 263), the IP address is 47.11.56.114. Figure 103 DNS configuration on the Signaling Server 5 Ensure that the SIP GW settings match the settings as shown in Figure 104 "SIP GW Settings" (page 264).
Appendix B Configuration Examples Figure 104 SIP GW Settings 6 Confirm that the SIP URI Map settings match the settings as shown in Figure 105 "SIP URI Map" (page 265). Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Standard Edition 265 Figure 105 SIP URI Map 7 Confirm that the SIP CTI Services settings match the settings as shown in Figure 106 "SIP CTI Services" (page 266). Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Appendix B Configuration Examples Figure 106 SIP CTI Services —End— Configuring Network Routing Service (NRS) Use the following procedure to check the configuration of NRS. Checking NRS configuration Step Action 1 Check the Signaling Server and MCM Endpoints Status as shown in Figure 107 "Signaling Server and MCM Endpoints status on NRS" (page 267). Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.
Standard Edition 267 Figure 107 Signaling Server and MCM Endpoints status on NRS Ensure that all the endpoints are registered (the endpoints must be listed as "Dynamic Sip" under the Supported Protocols column and have an IP address under the Call Signaling IP column in Figure 107 "Signaling Server and MCM Endpoints status on NRS" (page 267).
Appendix B Configuration Examples Figure 108 Routing Entry 3 Check the OCS 2007 Standard Edition configuration. In Host Authorization for an OCS 2007 Standard Edition, configure the IP Address of the OCS Proxy server. (see Figure 109 "Host Authorization" (page 269). ATTENTION Communication between MCM and the Communication Server 1000 is based on TCP. When using TCP, enter the IP address instead of FQDN.
Standard Edition 269 Figure 109 Host Authorization 4 Check the OCS Proxy server configuration. See Table 53 "Network Routing Service (NRS)" (page 251), the OCS Proxy IP is 47.11.56.54, and the Node IP is 47.11.56.24. —End— Active Directory user configuration Use the following procedure to check the Active Directory user configuration.
Appendix B Configuration Examples a. Compare and match your user properties settings with those in Figure 110 "General user properties" (page 270). The telephone number in the Telephone Number field must be the same as the information recorded in Table 52 "Microsoft Active Directory" (page 251). Figure 110 General user properties b. Click on the Communications tab.
Standard Edition 271 Figure 111 Communications properties c. Click the Communications tab and click the Configure button. Compare and match your settings with those in Figure 112 "User Options" (page 272). The Server URI and the Line URI must be the same as the information recorded in Table 52 "Microsoft Active Directory" (page 251)). Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.
Appendix B Configuration Examples Figure 112 User Options —End— Checking the MCM installation and configuration Check that the MCM is properly installed and configured. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Standard Edition 273 Checking the MCM installation and configuration Step Action 1 On the MCM, check that the user is a member of the RTC Server Applications and RTC Server Local Group. 2 For MCM Application, confirm that MCM running and for the Default OCS applications, confirm that IM URL Filter and Routing Application are running (see Figure 113 "MCM Application" (page 273).
Appendix B Configuration Examples Figure 114 MCM Gateway Endpoint configuration Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Enterprise Edition Figure 115 MCM Configuration screen Enterprise Edition This section describes the configuration of the OCS Enterprise Edition. Overview of general lab set-up Figure 116 "OCS Enterprise Edition General Overview" (page 276), illustrates the lab set-up, which includes: • Call Server version 5.0 • Signaling Server version 5.0 • MCM version 3.
Appendix B Configuration Examples • OCS FE Server with a Pool and a Microsoft Software Load Balancer • 1 OCS Proxy server Figure 116 OCS Enterprise Edition General Overview Collecting Data for Enterprise Edition Collect the required data listed in the following four tables before you begin to configure the Converged Office solution. ATTENTION The FQDN field is case sensitive. Enter the exact FQDN.
Enterprise Edition 277 Server URI sip:2070;phone-context=cdp.udp@te st.com Line URI tel:+16139675000;ext=2070 Telephone number 2070 Table 67 OCS Required information Record your information For example OCS 2007 Proxy server ocs2007a-proxy.ocs2007a.corp.nortel.com 47.11.56.54 Load Balancer Pool ocs2007apool OCS Enterprise Edition Front End server 1 ocs2007a-ocsfe1.ocs2007a.corp.nortel.com 47.11.56.51 OCS Enterprise Edition Front End server 2 ocs2007a-ocsfe1.ocs2007a.corp.nortel.com 47.11.
Appendix B Configuration Examples LAN configuration, IP Address (OCS Proxy and OCS Pool) 47.11.56.54 Communication Server 1000 SIP gateway endpoint name ocs2007_node_A SIP Domain name ocs2007a.corp.nortel.com SIP Gateway Endpoint name ocs2007_node_A SIP URI map, Private/UDP domain name udp SIP URI map, Private/CDP domain name cdp.
Enterprise Edition 279 ATTENTION The OCS GUI is always displayed in lower case. To determine the correct FQDN, right-click on pool, and the correct FQDN displays under Display Name as depicted in Figure 118 "Determining the exact FQDN of the pool" (page 280). Figure 117 OCS Management Console Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Appendix B Configuration Examples Figure 118 Determining the exact FQDN of the pool OCS Default Applications Running Use the following procedure to determine which default applications are running. Identifying the active default applications Step Action 1 To determine the exact FQDN of Pool, confirm that the two default applications, IM URL Filter Application Setting and Routing Application Setting are running. 2 In OCS 2007, click on Applications.
Enterprise Edition 281 Figure 119 Default applications —End— General tab settings Use the following procedure to confirm the correct settings in the General tab. Step Action 1 Right-click on OCS 2007 Front End server and select Properties. 2 Choose the General tab and click the Edit button. Confirm you have the correct settings for the Front End server. For an example, see Figure 120 "General settings" (page 282).
Appendix B Configuration Examples Figure 120 General settings Security/Certificates Prior to the setup of Converged Office, configure certificates. ATTENTION Certificate configuration is not covered in this section. Use the following procedure to check your configuration settings of Certificates. Checking the configuration of Certificates Step Action 1 Right-click on the OCS 2007 Front End server, select Properties. 2 Choose the Certificate tab.
Enterprise Edition 3 283 Click the Select Certificate button to confirm the settings of the Front End server Certificate. Figure 121 Front End server Certificate —End— Host Authorization Use the following procedure to check your configuration settings of Host Authorization. Checking the configuration of Host Authorization Step Action 1 Right-click on the OCS 2007 Front End server and select Properties. 2 Choose the Host Authorization tab.
Appendix B Configuration Examples 3 Click the Edit button to confirm the settings of the Host Authorization for the Front End server (see Figure 122 "Host Authorization for Front End server" (page 284)). Figure 122 Host Authorization for Front End server —End— Routing Use the following procedure to check that Routing is correctly configured. Checking that Routing is correctly configured Step Action 1 Right-click on Front Ends and select Properties.
Enterprise Edition 285 Figure 123 Routing for Enterprise Pool 2 Choose the Routing tab. 3 Click the Edit button to confirm the Matching URI and Next hop settings. (see Figure 124 "Edit Static Route " (page 286)). Forward all requests with the specified Domain. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Appendix B Configuration Examples Figure 124 Edit Static Route —End— Configuring DNS Use the following procedure to check the settings for DNS Configuration. Checking these settings assumes that the DNS service is enabled on the Windows 2003 server. The OCS servers are also using this DNS server. Checking that DNS is correctly configured Step Action 1 On the DNS server, select _tcp. 2 Select _sipinternaltls. 3 Right-click and select Properties. 4 Click on the Service Location (SRV) tab.
Enterprise Edition 287 Figure 125 sipinternaltls SRV records 6 On the DNS server, right-click on ocs2007apool and select Properties. 7 Select the Host (A) tab and check the Host A record for the Pool (see Figure 126 "Host (A) record for the Pool" (page 288)).. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Appendix B Configuration Examples Figure 126 Host (A) record for the Pool For more information on these configurations, see the Microsoft Office Communications Server 2007 Enterprise Edition Deployment Guide . Download Microsoft documentation from the Download Center at www.microsoft.com. —End— Active Directory configuration Step Action 1 On the Active Directory server, right-click on Users and select the name of the user to configure in the right pane. 2 Right-click and select Properties.
Enterprise Edition 4 289 Click the Configure button. —End— See Figure 127 "User Advanced Settings" (page 289) to check the settings for Server URI and Line URI. Figure 127 User Advanced Settings ATTENTION For more information on the user configuration of Active Directory, see the Standard Edition section "Active Directory user configuration" (page 269). Installing and configuring MCM Use the following procedure to check that MCM is correctly installed and configured.
Appendix B Configuration Examples Checking that MCM is correctly installed and configured. Step Action 1 Assign the required Local group to the MCM user. Prior to installation of MCM, an MCM user inside the Active Directory is created and the RTC Server Local Group and RTC Server Application local group is assigned to this user. 2 On the Proxy Server, right-click on My Computer and choose Manage. This assigns the MCM user to the RTC Server Local Group and RTC Server Application.
Enterprise Edition 291 Figure 129 RTC Server Application group ATTENTION 6 • MCM may not run if the MCM user is not configured to belong to the required groups. • MCM may not run if an incorrect password is entered during the MCM installation. On the MCM server, choose the Tools menu and select Configuration. See Figure 130 "MCM configuration" (page 292) for an example.
Appendix B Configuration Examples Figure 130 MCM configuration 7 Ensure that the correct Called Phone Context is entered. The Called Phone Context must correspond to what is configured for the user inside Active Directory and the SIP URI map (Private/CDP or UDP domain name) configured in Element Manager. —End— Signaling Server checklist Use the following procedure to check that the Signaling Server is correctly configured.
Enterprise Edition 293 Checking that the Signaling Server is correctly configured Step Action 1 Check the settings of SIP URI (see Figure 131 "SIP URI" (page 293)). Figure 131 SIP URI —End— Configuring NRS Use the following procedure to check that the NRS is correctly configured. Checking that NRS is correctly configured Step Action 1 Go to Network Routing Service (NRS) and select Endpoints. Confirm that the settings are correct (see Figure 132 "MCM endpoints" (page 294)).
Appendix B Configuration Examples Figure 132 MCM endpoints 2 From the Routing Entries tab, confirm that the settings are correct (see Figure 133 "Routing Entries for Endpoints" (page 295)). Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Enterprise Edition 295 Figure 133 Routing Entries for Endpoints —End— Normalizing Phone Numbers When normalizing phone numbers, the Telephone Number field can be different from what is configured in the OCS user configuration for the Line URI field. However, a corresponding normalization rule should be defined in the "Company_Phone_Number_Normalization_Rules.txt" file to convert the Telephone Number to the Line URI format.
Appendix B Configuration Examples If the Telephone Number is normalized to the Line URI format, you can use the "Click to Call" feature to show the caller’s user name when the Address Book Service is available. Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Appendix C Abbreviations ACD Automatic Call Distribution AD Active Directory AML Application Module Link ATS Activity Tracking System AUX Auxiliary B2BUA Back 2 Back User Agent BCC Basic Client Configuration BRSC Basic Rate Signaling Concentrator CAST Customer Assurance and Serviceability Test CCMS Contact Center Manager Server CCR Customer Controlled Routing Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.
Appendix C Abbreviations CDP Coordinated Dialing Plan CDR Call Detail Recording CS Communication Server CSTA Computer Supported Telecommunications Applications DC Domain Controllers DRAM Dynamic Random Access Memory DN Directory Number DNIS Dialed Number Identification Services EC Enterprise Configurator EMS Enterprise Multimedia Systems EPROM Erasable Programmable Read-Only Memory FS Feature Specification FQDN Fully Qualified Domain Name GC Global Catalog GNTS Global Network Technical Su
Appendix C Abbreviations IP Internet Protocol IPSec Secure Internet Protocol IVR Interactive Voice Response LDAP Lightweight Directory Access Protocol MISP Multipurpose ISDN Signaling Processor MCM Multimedia Convergence Manager MMC Microsoft Management Console MNM Meridian Network Management MSDL Multi-purpose Serial Data Link NAS Nortel Application Switch NCR Number of Call Registers NRS Network Routing Service OC Office Communicator OCS Office Communications Manager P Pentium Nortel Comm
Appendix C Abbreviations PSTN Public Switched Telephone Network PRD Product Requirements Document RCC Remote Call Control Provides full Microsoft Office integration of telephony to control business-grade telephony phones from within Microsoft Office applications, as well as support for a standards-based CTI interface defined by the TR/87 protocol.
Appendix C Abbreviations TN Terminal Number URI Uniform Resource Identifier VIP Virtual Internet Protocol VoIP Voice over Internet Protocol VTRK Virtual Trunk XPEC Expanded Peripheral Equipment Controller Pack Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Appendix C Abbreviations Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 NN43001-121 01.03 Standard Release 5.0 30 April 2008 Copyright © 2005–2008, Nortel Networks .
Nortel Communication Server 1000 Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007 Copyright © 2005–2008 , Nortel Networks All Rights Reserved. Publication: 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.
