Nortel Communication Server 1000 Communication Server 1000 to MCS 5100 Converged Desktop Type 2 Configuration Guide NN43001-321 .
Document status: Standard Document version: 01.05 Document date: 15 February 2008 Copyright © 2005-2008, Nortel Networks All Rights Reserved. Sourced in Canada 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.
Revision history February 2008 Standard 01.05. This document is up-issued to update the instructions for Configuring Meet Me Audio Conferencing in the NRS for CDS. January 2008 Standard 01.04. This document is up-issued to add instructions for Configuring Meet Me Audio Conferencing in the NRS for CDS. December 2007 Standard 01.03. This document is up-issued to update the Converged Desktop Feature installation. June 2007 Standard 01.02.
Revision history CR Q01478214, two options are added to "Configuring MCS 5100 in the NRS for CDS" (page 90). MCS 5100 is configured as a Gateway Endpoint in the first option and as a Collaborative Server in the second. October 2006 Standard 3.00. This document is up-issued for CR Q01412328-01, to add prompt and response to LD-17 Configuration of Value Added Server (VSID) table, to set the VSID security for the SIP CD AML link to No.
Contents How to get help 7 Finding the latest updates on the Nortel Web site 7 Getting help from the Nortel Web site 7 Getting help over the telephone from a Nortel Solutions Center 7 Getting help from a specialist by using an Express Routing Code 8 Getting help through a Nortel distributor or reseller 8 Introduction 9 Subject 9 Applicable systems 9 Intended audience 10 Conventions 10 Related information 10 Converged Desktop Services Contents 13 Introduction 13 How Converged Desktop Services works
Contents Configuring CS 1000 49 Contents 49 Before you begin 49 CS 1000 SIP configuration and UDP location dialing Configuring the Converged Desktop User 66 49 Configuring MCS 5100 67 Contents 67 Before you begin 67 Implementation summary 68 Implementation details 68 Configuring a Converged Desktop user 81 CS 1000 NRS operation 87 Contents 87 Introduction 87 Operation 88 Operational logic 96 Maintenance 99 Contents 99 Introduction 99 CS 1000 CLI commands MCS 5100 tools 101 99 Appendix A Par
How to get help This chapter explains how to get help for Nortel products and services. Finding the latest updates on the Nortel Web site The content of this documentation is current at the time the product is released. To check for updates to the latest documentation for Communication Server (CS) 1000, go to www.nortel.com and navigate to the Technical Documentation page for CS 1000.
How to get help Getting help from a specialist by using an Express Routing Code To access some Nortel Technical Solutions Centers, you can use an Express Routing Code (ERC) to quickly route your call to a specialist in your Nortel product or service. To locate the ERC for your product or service, go to: www.nortel.
Introduction This document is a global document. Contact your system supplier or your Nortel representative to verify that the hardware and software described are supported in your area. Subject This document describes Session Internet Protocol Converged Desktop System (SIP CDS) and its configuration on Communication Server 1000 (CS 1000) and Multimedia Communication Server 5100 (MCS 5100) systems.
Introduction • Meridian 1 PBX 11C Cabinet • Meridian 1 PBX 61C CP PII, CP PIV • Meridian 1 PBX 81C CP PII, CP PIV Note: When upgrading software, memory upgrades may be required on the Signaling Server, the Call Server, or both. Intended audience This document is intended for individuals responsible for administering CS 1000 and Meridian 1 systems.
Related information 11 • Feature Description Guide (NN42020-125) • Interworking Fundamentals (NN42020-127) Online To access Nortel documentation online, click the Technical Documentation link under Support & Training on the Nortel home page: www.nortel.com CD-ROM To obtain Nortel documentation on CD-ROM, contact your Nortel customer representative. Nortel Communication Server 1000 Communication Server 1000 to MCS 5100 Converged Desktop Type 2 Configuration Guide NN43001-321 01.05 Standard Release 5.
Introduction Nortel Communication Server 1000 Communication Server 1000 to MCS 5100 Converged Desktop Type 2 Configuration Guide NN43001-321 01.05 Standard Release 5.0 15 February 2008 Copyright © 2005-2008, Nortel Networks .
Converged Desktop Services Contents This section contains information about the following topics: "Introduction" (page 13) "Scope of this document" (page 14) "How Converged Desktop Services works" (page 14) "Users in a mixed CS 1000/MCS 5100 network" (page 18) "Converged Mode and Unconverged Mode" (page 19) "CDS originating and terminating call handling" (page 19) "AML ELAN numbers and VAS numbers" (page 25) "Click-to-Call" (page 25) "Operating parameters and feature interactions" (page 26) "Call walk-t
Converged Desktop Services Scope of this document This document is intended to assist technical administrators in designing and configuring a Converged Desktop environment between CS 1000 and MCS 5100 systems. The examples provided in this document represent only one example of design and configuration. "Description of the network configured in this document" (page 48) provides the outline of the network used as an example only.
How Converged Desktop Services works 15 In Converged Mode, both the CS 1000 telephone and the MCS 5100 PC Client are integrated to provide both feature sets. In Converged Mode, the CS 1000 telephone effectively becomes the audio device for the MCS 5100 PC Client, so that any audio requirement from the MCS 5100 user (for example, Click-to-Call) is directed to the CS 1000 telephone.
Converged Desktop Services When a call terminates to the CS 1000 telephone, the CDMV or CDMO Class of Service redirects the call to the CSDN defined on the telephone, before ringing the CS 1000 telephone. The CSDN is a CDN used for CDS. This CDN number is also configured on the Signaling Server so that it can be acquired by the CDS application when the Signaling Server starts. When the call terminates to the CDN a message is sent over AML/VAS to the CDS as notification of the incoming call.
How Converged Desktop Services works 17 In Converged Mode, incoming and outgoing calls to and from a converged telephone notify the MCS 5100. Upon notification, the MCS 5100 then provides different SIP services and features to the user. The features include the following, depending on where the call is destined, or from where it originated. All calls to or from a Converged Desktop user receive: • Call log — Allows a user to see who has called and when the call occurred.
Converged Desktop Services • Web co-browsing — Allows users to share a web browser. If both users have the web co-browsing feature, then one user can automatically control (or drive) the other user’s web browser. All of these features are achieved by sending originating and terminating call notifications to the MCS 5100. Users in a mixed CS 1000/MCS 5100 network CS 1000 and MCS 5100 systems can interoperate directly using SIP. Both systems can be deployed in a single mixed customer network.
How Converged Desktop Services works 19 Note: When a Converged Desktop user is not in a converged state, the user effectively becomes an MCS 5100 user and the CS 1000 device becomes a stand-alone voice device. Converged Mode and Unconverged Mode An MCS 5100 client can be in one of the two following modes: • Converged Mode — The MCS 5100 client uses the CS 1000 voice path. It also uses the AML link for CDS signaling. • Unconverged Mode — The MCS 5100 client uses the MCS 5100 voice path.
Converged Desktop Services — Select from a Friends list or Directory book. In both instances the following functionality is automatically provided: • The Call Log is updated after the call. • A pop-up window is generated if another CD user or SIP user was called. • The users’ Presences are updated after the call is answered.
How Converged Desktop Services works 9 Converged user A releases. 10 Call disconnected; Disconnect message sent. 11 Release message sent. 12 Call timer stopped, Call Log updated. Figure 3 "Call flow: Click-to-Call" (page 21) shows the call flow and messaging that occurs during a Click-to-Call session. Figure 3 Call flow: Click-to-Call Legend: 1 Click-to-Call action initiated. 2 Click-to-Call Invite message sent. 3 One idle PCA selected to call own phone. 4 Converged user A rings.
Converged Desktop Services 9 Call between PCA and converged user A disconnected; call made from converged user A to user B. 10 Call placed to user B. Receiving a call Depending on the Class of Service (CDMV or CDMO) of the converged user, the call flow will differ slightly. To receive a call, note the following: • A CD user in CS 1000 can be defined as Multimedia Only user or Multimedia and Voice user. • All calls to CD users are sent first to a predefined CDN queue.
How Converged Desktop Services works 23 Legend: 1 User A dials user B; call is forwarded to CDN. 2 Incoming call to CDMV user sent to CDS. 3 PCA selected; call made to Service DN to select a Virtual Trunk. 4 Virtual Trunk reserved. 5 INVITE message sent to CDS URL. 6 INVITE PC Client • Call Forking based on PA route • Call Log updated • Pop-up window generated If PA settings allow a call to converged user B, then: 7 INVITE message sent to converged user B.
Converged Desktop Services Figure 5 Call flow: call terminating to a user with a CDMO Class of Service Legend: 1 User A dials user B; call is forwarded to CDN. 2 Incoming call to CDMO user sent to CDS. 3 PCA selected; call made to Service DN to select a Virtual Trunk. 4 Virtual Trunk reserved. 5 INVITE message sent to CDS URL. 6 INVITE PC Client • No Call Forking • Call Log updated • Pop-up window generated 7 302 Moved Temporarily message sent to CDS.
How Converged Desktop Services works 25 When receiving a call, the functionality of the PC Client is different from that when making a call. With CDMO, a call to a converged telephone always rings the converged telephone. It does not invoke PA routing. But with CDMV, a call to a converged telephone on MCS 5100 invokes PA routing to determine if it is to ring the converged telephone or another telephone.
Converged Desktop Services The following steps must be performed when using Click-to-Call: • The caller makes a call from the PC Client software and the caller’s telephone rings. • The caller must answer their telephone when it rings if the desktop telephone is an analog (500/2500-type) telephone or is part of a Multiple Appearance DN (MADN) group. Answering the telephone then directs the call to the called party.
Call walk-throughs • 27 In the Converged Desktop Environment, voice mail is supported only on the CS 1000 telephone, not the MCS 5100 Client. Call walk-throughs The figures in this section show messages exchanged between a CS 1000 system and an MCS 5100 system with different configurations. Although two CS 1000 systems appear in the figures, they collapse into one if the call is internal.
Converged Desktop Services Figure 7 Incoming call to CDMV user with forking Figure 8 Incoming call to CDMV user with NO forking Figure 9 Incoming call to CDMO user Nortel Communication Server 1000 Communication Server 1000 to MCS 5100 Converged Desktop Type 2 Configuration Guide NN43001-321 01.05 Standard Release 5.0 15 February 2008 Copyright © 2005-2008, Nortel Networks .
Feature requirements 29 Figure 10 Combined incoming and outgoing Converged Desktop call Feature requirements CS 1000 systems CS 1000 systems require: • CS 1000 Release 4.
Converged Desktop Services Feature implementation For CDS to operate, you must have the following conditions in place: • MCS 5100 clients must assume the location identifier (LOC) of a CS 1000 system. This enables one MCS 5100 system to provide CDS to many CS 1000 systems, having the MCS 5100 clients assume the location identifier (LOC) of each CS 1000 system. • The dialing plan and numbering plan between the CS 1000 systems and the MCS 5100 system must be compatible.
Dialing and numbering plan issues for the mixed network 31 ATTENTION Rule 1: All users in a mixed CS 1000/MCS 5100 network must be accessible by all systems through a digit-based address. On the MCS 5100 system, each username must have an alias that is all digits, or each username must be all digits. Dialing plan issues The term "dialing plan" is used in a very broad sense in this context.
Converged Desktop Services Rule 2 is important for a CD user. Although a CD user can enter a destination number on the Multimedia PC Client, the call itself is originated under CS 1000 control. DNs as MCS aliases versus DNs as MCS usernames This section describes how to assign a digit-based address (that is, directory number [DN]) to an MCS 5100 user. The following options are available to associate a DN with an MCS user: • Provision the user’s username in the form of a DN.
Dialing and numbering plan issues for the mixed network 33 — Local numbers — National numbers — International numbers — Special numbers • Private address space — which is subdivided into the following categories: — Level 0 regional numbers (in CS 1000, these are known as Coordinated Dialing Plan [CDP] numbers) — Level 1 regional numbers (in CS 1000, these are known as Universal Dialing Plan [UDP] numbers) To be useful, a DN must be scoped within an appropriate address space.
Converged Desktop Services Non-telephony-based SIP URIs In accordance with the preceding Rule 4, non-telephony-based, or regular, SIP URIs must not be passed between systems in a mixed CS 1000/MCS 5100 network. There is one exception to this rule — regular SIP URIs can be passed between systems in the Refer-to header. ATTENTION Rule 5: In a mixed CS 1000/MCS 5100 network, for routing purposes, regular SIP URIs can be passed between the two systems only within a Refer-to header.
Dialing and numbering plan issues for the mixed network 35 The converged Multimedia PC Client provides several ways for a user to initiate Click-to-Call, including: • using the Directory window • using the Friends Online window • using the Call Logs window (Outbox and Inbox tabs) • using the Make a Call window (Dialpad, Recent, and Directory tabs) These four user interfaces retrieve an address.
Converged Desktop Services Nortel Communication Server 1000 Communication Server 1000 to MCS 5100 Converged Desktop Type 2 Configuration Guide NN43001-321 01.05 Standard Release 5.0 15 February 2008 Copyright © 2005-2008, Nortel Networks .
Examples of dialing and numbering plan configuration for mixed networks Contents This section contains information about the following topics: "Introduction" (page 37) "Mixed network example: UDP" (page 37) "Sample network" (page 38) "CS 1000 setup" (page 39) "MCS 5100 setup" (page 40) "Mixed network example: CDP" (page 42) "Sample network" (page 42) "CS 1000 setup" (page 43) "MCS 5100 setup" (page 40) Introduction This section provides examples of a dialing plan setup for a mixed CS 1000/MCS 5100 netw
Examples of dialing and numbering plan configuration for mixed networks Sample network The sample network has the following characteristics: • The network includes several sites. • Each site has a mixture of CS 1000 users, MCS 5100 users, and Converged Desktop users. • Dialing within a site is done using CDP numbers (no access code, 4-digit numbers). • Dialing among the sites is done by dialing 6 + 7-digit UDP number. • Local PSTN hop-off is done by dialing 9 + local number.
Mixed network example: UDP 39 CS 1000 setup The CS 1000 setup includes both a user setup and translation setup. User setup The CS 1000 user setup involves both the general user setup and the Converged Desktop user setup. General user setup The general user setup applies to both stand-alone and Converged Desktop users. The general user setup involves the following: • Configure the user’s extension as a 4-digit number.
Examples of dialing and numbering plan configuration for mixed networks — UDP phone-context For example: phone-context="udp" — CDP phone-context For example: phone-context="cdp.udp" — Public/Local phone-context For example: phone-context="+1613" — Public/National phone-context For example: phone-context="+1" MCS 5100 setup The MCS 5100 setup involves includes both a user setup and translation setup.
Mixed network example: UDP 41 number. For example: PAD = 63345573 The number 6 is the access code configured for UDP calls as configured on CS 1000. The configured values must match in both configurations. Translation setup The MCS 5100 translation setup includes pretranslation setup, private telephony routes setup, and gateway telephony routes setup.
Examples of dialing and numbering plan configuration for mixed networks Mixed network example: CDP The following is an example of a dialing plan setup for a mixed CS 1000/MCS 5100 network. CDP numbers are used to dial among sites. Sample network The sample network has the following characteristics: • The network includes several sites. • Each site has a mixture of CS 1000 users, MCS 5100 users, and Converged Desktop users.
Mixed network example: CDP 43 Figure 12 Network diagram: mixed CDP CS 1000 setup The CS 1000 setup includes both a user setup and translation setup. User setup The CS 1000 user setup involves both the general user setup and the Converged Desktop user setup. General user setup The general user setup applies to both stand-alone and Converged Desktop users. The general user setup involves the following: • Configure the user’s extension as a 5-digit number.
Examples of dialing and numbering plan configuration for mixed networks Note: Although the network is CDP-only, some UDP configuration is necessary to support MCS 5100 private charge ID, which is always presented as a UDP number. • Configure the Private Network Identifier (PNI) for user groups (that is, customers). For example: PNI = 00002 • PNI, HLOC, and the user’s extension create the Global user ID that is globally unique: PNI + HLOC + Extension.
Mixed network example: CDP 45 User setup The MCS 5100 user setup involves both the general user setup, stand-alone user setup, and the Converged Desktop user setup. General user setup The general user setup applies to both stand-alone and Converged Desktop users. The general user setup involves the following: • Configure the user’s username as an alphanumeric address. For example: Username = asmith • Configure the user’s private charge ID as the UDP number.
Examples of dialing and numbering plan configuration for mixed networks • If the Public/International number is received, insert 9011. For example, DN starts with a plus sign (+), insert 9011.
CDS configuration: overview Contents This section contains information about the following topics: "Introduction" (page 47) "Configuration notes" (page 47) "Description of the network configured in this document" (page 48) Introduction In order to use SIP Converged Desktop Services, the SIP Trunk Gateway must first be configured. See IP Peer Networking Installation and Commissioning (NN43001-313) for detailed instructions.
CDS configuration: overview Description of the network configured in this document The user will encounter one of many CDS configuration situations. This section describes the basic characteristics of the network to which the configuration described in the rest of this document applies. The intent is to provide a configuration example which the user can then adapt to their particular situation.
Configuring CS 1000 Contents This section contains information about the following topics: "Before you begin" (page 49) "CS 1000 SIP configuration and UDP location dialing" (page 49) "Configuring the Call Server" (page 49) "Configure the Signaling Server usingCS 1000 Element Manager" (page 57) "Verifying configuration" (page 64) "Configuring the Converged Desktop User" (page 66) Before you begin ATTENTION Some values in these instructions are taken from the values in "Description of the network configu
Configuring CS 1000 2. "LD 17 Configure the Application Module Link (AML)." (page 51). 3. "LD 17 Configure Value Added Server (VAS)." (page 51). 4. "LD 23 Configure Automatic Call Distribution (ACD) Directory Number (DN)." (page 52). 5. "LD 23 Configure Control Directory Number (CDN)." (page 52). 6. "LD 86 Configure ESN Data Block with AC1 and AC2 (if not already defined)." (page 52). 7. "LD 90 Configure Home Location Code (HLOC)." (page 53). 8. "LD 86 Configure Access Code (AC1 or AC2)." (page 53). 9.
CS 1000 SIP configuration and UDP location dialing Prompt Response Description -PFX1 613 Prefix 1 -PFX2 962 Prefix 2 DITI Yes DID to TIE connections allowed. 51 To connect external DID and internal network TIE trunks for the customer (which allows an external trunk to be transferred across an internal network TIE trunk), set DITI=YES. LD 17 Configure the Application Module Link (AML). Prompt Response Description REQ CHG Change existing data.
Configuring CS 1000 LD 23 Configure Automatic Call Distribution (ACD) Directory Number (DN). Prompt Response Description REQ NEW Add new data. TYPE ACD Automatic Call Distribution data block CUST xx Customer number as defined in LD 15. (Customer number associated with this data block.) ACDN 5300 ACD Directory Number LD 23 Configure Control Directory Number (CDN). Prompt Response Description REQ NEW Add new data.
CS 1000 SIP configuration and UDP location dialing 53 Configuring HLOC is necessary to properly handle a UDP number sent by the MCS 5100 based on the Private Charge ID of the MCS 5100 user profile. The MCS 5100 always qualifies this number as a UDP number. HLOC will already have been configured if UDP is used. Even if only CDP is used, you must still configure HLOC. LD 90 Configure Home Location Code (HLOC). Prompt Response Description REQ NEW Add new data.
Configuring CS 1000 Prompt Response Description xxxx 1-4 digit Flexible Numbering Plan Access Code 1. ... AC1 or The access code cannot conflict with the numbering plan. AC2 Removal of the HLOC digits is necessary so that local termination is possible. Configuring digit manipulation is necessary to properly handle a UDP number sent by the MCS 5100 based on the Private Charge ID of the MCS 5100 user profile. The MCS 5100 always qualifies this number as a UDP number.
CS 1000 SIP configuration and UDP location dialing Prompt Response 55 Description AC1 = NARS/BARS AC2 = NARS TYPE: SPN Special Number translation (Special code translation block) Configure the CDS Service DN as an SPN, and point it to the SIP trunk. This number is only internal between the Call Server and the Signaling Server for reserving the Virtual Trunk when routing the terminating CD call out to the MCS 5100. SPN 5100 Special Number. The same DN must be used in the config.
Configuring CS 1000 Prompt Response Description Flexible length is the exact number of digits the system expects to receive before accessing a trunk and outpulsing those digits. -DSP aaa Display, where aaa = LSC, LOC, DN. -RRPA (NO) YES Remote Radio Paging Access -RLI xxx Route List to be accessed for Distant Steering Code. Virtual Route RLI with no DMI changes.
CS 1000 SIP configuration and UDP location dialing Prompt Response 57 Description zzzz = agent’s position ID (zzzz can be up to 4 digits; up to 7 digits with Directory Number Expansion [DNXP] package 150). 2 MCN 3604 Multiple Call Non-Ringing key Where yyyy = DN The DN can be up to 4 digits; up to 7 digits with Directory Number Expansion (DNXP) package 150. Once the MCN key has been defined, the MARP prompt appears.
Configuring CS 1000 3 Click Edit next to the node for which SIP CDS is to be configured. The Edit web page opens, as shown in Figure 14 "Edit web page" (page 58). Figure 14 Edit web page 4 Select SIP CD Services to expand the section, as shown in Figure 15 "SIP CD Services" (page 59). Nortel Communication Server 1000 Communication Server 1000 to MCS 5100 Converged Desktop Type 2 Configuration Guide NN43001-321 01.05 Standard Release 5.0 15 February 2008 Copyright © 2005-2008, Nortel Networks .
CS 1000 SIP configuration and UDP location dialing 59 Figure 15 SIP CD Services 5 Enter the necessary information in the following fields: a. Service Enabled: Select whether the Converged Desktop Service application is enabled or disabled for this node. CDS is enabled by default (the check box is selected). Note: If CDS is not enabled, no calls are sent to the MCS 5100, including both originating and terminating calls either to or from the Converged Desktop telephone. b.
Configuring CS 1000 Virtual Trunk route based on translations. The CDS answers and reserves the Virtual Trunk in case it is needed to terminate the incoming call. The example shown uses an SPN and is defined as follows: Service DN = AC1 (from LD 86) + SPN (from LD 90) For example, the value entered for the Service DN is 65100, where 6 is Access Code 1 (AC1) (configured in LD 86 on "LD 86 Configure Access Code (AC1 or AC2).
CS 1000 SIP configuration and UDP location dialing 61 sip:convergeddesktop@SIPdomainname;nortelconverged= conditionalfork Ensure that the SIPdomainname is part of the string. The SIP Domain name should have been configured during the SIP Trunk Gateway configuration. If the string is missing the SIP Domain name (that is, the string is sip:convergeddesktop@;nortelconverged=conditionalfork), then the SIP Domain name was not configured during the SIP Trunk Gateway configuration.
Configuring CS 1000 user can be directed to RAN. The RAN typically will say, for example, "Your call is proceeding, please wait..." h. Wait time before a caller is sent to RAN Queue: Enter the time (in seconds) that the caller waits before the called is directed to the RAN queue. The range is -1 to +32767 seconds, where: Value Meaning -1 Never send to RAN queue. This is the default. 0 Immediately send to RAN queue. +1 to +32767 Wait n seconds before sending to RAN queue. i.
CS 1000 SIP configuration and UDP location dialing 63 Note: The fields require a character string that is less than 128 characters in length. The valid characters include: alphanumeric (a-z, 0-9), period (.), dash (-), underscore (_), and plus sign (+). These fields must be completed if the SIP Trunk Gateway application is enabled. Figure 16 CS 1000 SIP URI Map 7 Fill in the fields as follows: a. Type +1 in the Public E.164/National domain name text box. b. Type +1613 in the Public E.
Configuring CS 1000 8 Click Save and Transfer. —End— Verifying configuration After configuring the Virtual IP D-channel, SIP Route, Converged Desktop AML, and the other elements, log in to the Leader Signaling Server of the node. At the Command Line Interface (CLI), use the commands cdsShow and cdsAgentShow to verify the configuration.
CS 1000 SIP configuration and UDP location dialing Figure 17 Verifying configuration: cdsShow Figure 18 Verifying configuration: cdsAgentShow Nortel Communication Server 1000 Communication Server 1000 to MCS 5100 Converged Desktop Type 2 Configuration Guide NN43001-321 01.05 Standard Release 5.0 15 February 2008 Copyright © 2005-2008, Nortel Networks .
Configuring CS 1000 Note: If your Agents do not show Up, you may not have Nortel Symposium Call Center (NGCC) package 311 equipped. You need CS 1000 PEP MPLR19786 if the package is not equipped and you are using CS 1000 Release 4.0 software. This PEP is not required on CS 1000 Release 4.5 or later software. Configuring the Converged Desktop User The Converged Desktop user is configured in LD 10 for analog (500/2500-type) telephones or LD 11 for digital telephones.
Configuring MCS 5100 Contents This section contains information about the following topics: "Before you begin" (page 67) "Implementation summary" (page 68) "Implementation details" (page 68) "Add IP address of IP Telephony node as an Authenticated Server" (page 68) "Configure the SIP Gateway, trunk, and trunk group" (page 69) "Configure number qualifiers" (page 72) "Configure a route list" (page 75) "Configure routes for each dialing plan entry" (page 77) "Configuring a Converged Desktop user" (page 81)
Configuring MCS 5100 Implementation summary The following is a summary of the tasks in this section: • "Add IP address of IP Telephony node as an Authenticated Server" (page 68). • "Configure the SIP Gateway, trunk, and trunk group" (page 69). • "Configure number qualifiers" (page 72). • "Configure a route list" (page 75). • "Configure routes for each dialing plan entry" (page 77).
Implementation details 7 69 Verify the address appears in the list under the Authentication tab, as shown in Figure 19 "IP address of IP Telephony node added as an Authenticated Server" (page 69): a. Right-click on the application server. b. Select Query.
Configuring MCS 5100 Figure 20 Provisioning Client Login 2 Enter your Username and Password. The Provisioning Client web page opens, as shown in Figure 21 "Provisioning Client" (page 70). The Provisioning Client navigator is in the section on the left of the web page. Figure 21 Provisioning Client 3 Add a new gateway, as follows: a. Select Provisioning > Gateways > Add Gateway in the Provisioning Client navigator.
Implementation details Figure 22 Provisioning Client: Add a new gateway b. Enter mydomain.com:maddr=12.123.1.123 in the Gateway host text box. c. Select CS 1000 in the Gateway type drop-down list. d. Select Other from the Location drop-down list. e. Select TRUE for Trusted Node. f. Select TRUE for Is Gateway. g. Click Submit. 4 Add a new route, as follows: a. Select Provisioning > Gateways > Add Route in the Provisioning Client navigator.
Configuring MCS 5100 c. Select mydomain.com in the Domain drop-down list. d. Click Save. 5 Add a trunk group directed to the gateway and route just created, as follows: a. Select Provisioning > Gateways > Add TrunkGroup in the Provisioning Client navigator. The Trunkgroup Provisioning web page opens, as shown in Figure 24 "Provisioning Client: Trunkgroup Provisioning" (page 72). Figure 24 Provisioning Client: Trunkgroup Provisioning b. Select mydomain.com:maddr=12.123.1.
Implementation details • CS 1000 NRS SIP URI phone-context in the Endpoint Routes (see Figure 26 "CS 1000 NRS Endpoint Routing Entries" (page 73)). • MCS 5100 Telephony Routes Number Qualifiers (see Figure 27 "MCS 5100 Number Qualifiers" (page 74)). where: • cdp.
Configuring MCS 5100 Figure 27 MCS 5100 Number Qualifiers Procedure 4 Configuring number qualifiers Step Action 1 Enter the IP address of the MCS Provisioning Client in a web browser. The Provisioning Client Login web page opens, as shown in Figure 20 "Provisioning Client Login" (page 70). 2 Enter your Username and Password. The Provisioning Client web page opens, as shown in Figure 21 "Provisioning Client" (page 70). 3 Add a new gateway, as follows: a. Select Provisioning > Domains > mydomain.
Implementation details 4 75 Add a number qualifier for each entry in the SIP URI map (shown in Figure 25 "CS 1000 SIP URI Map" (page 73)) as follows: a. Enter the name in the Name text box, for example cdp.udp. b. Enter a description in the Description text box, for example My CDP phone context. c. Click Add. Figure 28 Provisioning Client: Number Qualifiers —End— Configure a route list Use Procedure 5 "Configuring a route list" (page 75) to add a route list.
Configuring MCS 5100 The Provisioning Client Login web page opens, as shown in Figure 20 "Provisioning Client Login" (page 70). 2 Enter your Username and Password. The Provisioning Client web page opens, as shown in Figure 21 "Provisioning Client" (page 70). 3 Configure the Class of Service, as follows: a. Select Provisioning > Domains > mydomain.com > Telephony Routes > Routing COS in the Provisioning Client navigator.
Implementation details 77 a. Select Provisioning > Domains > mydomain.com > Telephony Routes > Add RouteList in the Provisioning Client navigator. The Create a New Route List web page opens, as shown in Figure 30 "Provisioning Client: Create a New Route List" (page 77). Figure 30 Provisioning Client: Create a New Route List b. Enter a list name, such as myRouteList, in the Name text box. c. Enter a list description, such as myRouteList, in the Description text box. d.
Configuring MCS 5100 • Gateway UDP route • private PSTN route • route for local Dial-9 National (NPA) dialing using the Gateway CS 1000 PSTN • route for national Dial-9 National (NPA) dialing using the Gateway CS 1000 PSTN Use Procedure 6 "Configuring routes for each dialing plan entry" (page 78) to configure these routes. Procedure 6 Configuring routes for each dialing plan entry Step Action 1 Enter the IP address of the MCS Provisioning Client in a web browser.
Implementation details 79 Figure 31 Provisioning Client: Create New Telephony Route b. Configure each new route, as follows: 1. Enter the values for the appropriate fields, as listed in Table 2 "Values for configuring Routes" (page 79). Do not use blank spaces in text fields. Note: In the Name field, only the following characters are valid: A-Z, a-z, 0-9, comma (,), period (.), hyphen (-), and underscore (_). Any other character in the route Name causes an error message. 2. Click Save.
Configuring MCS 5100 Route Type Entry Field Private CDP Private UDP Private PSTN Gateway CDP Gateway UDP Public Local Public National From Digits 7100 6334 9 7100 6334 9 9961 To Digits 7199 6334 9 7199 6334 9 9969 Min Numbe r of Digits 4 8 8 4 8 11 8 Max Numb er of Digits 4 8 22 4 8 22 8 Route Type Private Private Private Gateway Gateway Gateway Gateway Remove 0 1 1 0 1 1 1 Prefix 0000233 4 00002 Not applicable Recursive No No Not applicable
Configuring a Converged Desktop user 81 Figure 32 Provisioning Client: Pre translations b. Configure pretranslations for each of the number qualifiers in the Add New Pretranslations section, as follows: 1. Select the appropriate number qualifier from the Number Qualifier drop-down list. 2. Enter a number in the Length text box. 3. Enter a prefix in the Prefix text box. 4. Click Add.
Configuring MCS 5100 Procedure 7 Configuring a Service Package Step Action 1 Select Provisioning > Domains > mydomain.com > Service Package > Create Package in the Provisioning Client navigator. The Create new package web page opens, as shown in Figure 33 "Provisioning Client: Create new package" (page 82). 2 Enter a package name in the Name of the Packages text box. 3 Select services and their appropriate parameters as appropriate, including the following: a. Select Converged Desktop. b.
Configuring a Converged Desktop user 83 —End— Configuring the Converged User on the MCS 5100 Use Procedure 8 "Configuring a Converged Desktop User in MCS 5100" (page 83) to configure each Converged Desktop user in MCS 5100. Procedure 8 Configuring a Converged Desktop User in MCS 5100 Step Action 1 Select Provisioning > Domains > mydomain.com > Users > Add Users in the Provisioning Client navigator.
Configuring MCS 5100 This is the HLOC + DN of the converged telephone. This number is used for Click-to-Call in Converged Mode, and must be a UDP number. b. Enter 6139625573 in the Public Charge ID text box. This is the NPA + NXX + DN of the converged telephone. It is the caller identification information sent on a public call. This value is required, and may be need even in Unconverged Mode. c. Select cdCOS from the Class of Service drop-down list.
Configuring a Converged Desktop user • If you are configuring CDP, enter the CDP number. d. Select Enterprise Converged User from the Converged Desktop User Type drop-down list. —End— Nortel Communication Server 1000 Communication Server 1000 to MCS 5100 Converged Desktop Type 2 Configuration Guide NN43001-321 01.05 Standard Release 5.0 15 February 2008 Copyright © 2005-2008, Nortel Networks .
Configuring MCS 5100 Nortel Communication Server 1000 Communication Server 1000 to MCS 5100 Converged Desktop Type 2 Configuration Guide NN43001-321 01.05 Standard Release 5.0 15 February 2008 Copyright © 2005-2008, Nortel Networks .
CS 1000 NRS operation Contents This section contains information about the following topics: "Introduction" (page 87) "Operation" (page 88) "Domains" (page 88) "Gateway Endpoints" (page 89) "Routing entries" (page 90) "Configuring MCS 5100 in the NRS for CDS" (page 90) "Configuring Meet Me Audio Conferencing in the NRS for CDS" (page 94) "Operational logic" (page 96) Introduction In a mixed CS 1000/MCS 5100 network, the following is expected to occur: • The CS 1000 SIP Redirect Server routes calls to
CS 1000 NRS operation This network configuration requires the CS 1000 SIP Redirect Server and MCS 5100 to interwork seamlessly. Therefore, this section describes the basics of the redirect server logic. Operation Note: Some values in these instructions are taken from the example numbering plans described "Examples of dialing and numbering plan configuration for mixed networks" (page 37). Note that actual values may differ between applications.
Operation Figure 38 Level0 Domain Gateway Endpoints The Gateway endpoint is configured with the following properties: • ID — Node134Loc334 This matches the SIP Endpoint name configured in CS 1000. • Call Signaling IP address — 12.123.1.123 This is the IP address of the CS 1000 IP Telephony node. • SIP Support — Dynamic SIP endpoint • SIP Transport Protocol — UDP • SIP port — 5060 This effectively configures the CS 1000 as an NRS endpoint. See Figure 39 "Gateway Endpoints" (page 89).
CS 1000 NRS operation Routing entries The routing entries configured in CS 1000 NRS for Gateway Endpoint Node134Loc334 are shown in Figure 40 "Routing Entries" (page 90). Note: SIP URI phone-contexts are configured in CS 1000 NRS as part of the Level1 Domain (udp). Figure 40 Routing Entries Configuring MCS 5100 in the NRS for CDS To implement CDS in the NRS, configure the MCS 5100 system in one of two ways: • Configure the MCS 5100 as a Gateway Endpoint.
Operation 91 Configure at least two routing entries against this Gateway Endpoint, so the Gateway Endpoint can be added to the lookup table. • Configure the MCS 5100 as a Collaborative Server. See Figure 41 "MCS 5100 configured as a Collaborative Server" (page 92). Note: This option is not recommended and can only be used when no other Collaborative Servers exist in the system. When you configure the MCS 5100 system in the NRS, note the following requirements: — domain = 12.234.3.
CS 1000 NRS operation Figure 41 MCS 5100 configured as a Collaborative Server To route calls from MCS 5100 to CS 1000 when MCS is configured as a Collaborative Server, choose one of two configuration options: 1. Configure MCS 5100 as a Gateway Endpoint for the NRS without routing entries for calls from CS 1000 to MCS 5100. See Figure 42 "MCS 5100 configured as a Gateway Endpoint without routing entries" (page 93).
Operation 93 Figure 42 MCS 5100 configured as a Gateway Endpoint without routing entries 2. Configure telephony routes on MCS 5100 to contact the CS 1000 SIP Gateway directly (not through NRS). See Figure 43 "Configure telephony routes on MCS 5100" (page 94). For more information about configuring MCS 5100, see "Configuring MCS 5100" (page 67). Nortel Communication Server 1000 Communication Server 1000 to MCS 5100 Converged Desktop Type 2 Configuration Guide NN43001-321 01.05 Standard Release 5.
CS 1000 NRS operation Figure 43 Configure telephony routes on MCS 5100 Configuring Meet Me Audio Conferencing in the NRS for CDS To configure Meet Me Audio Conferencing for CDS, you must point the meetme DID to the convergeddesktop gateway end point as a CDP entry. Note: You must create the convergeddesktop endpoint before beginning this procedure. For more information, see "Gateway Endpoints" (page 89).
Operation 7 Click Add. 8 Enter the DN Type, DN Prefix, and Route Cost. 9 Click Save. 10 Navigate to Tools > Database Actions. 11 Under Select database action, choose Cut over & Commit. Nortel Communication Server 1000 Communication Server 1000 to MCS 5100 Converged Desktop Type 2 Configuration Guide NN43001-321 01.05 Standard Release 5.0 15 February 2008 Copyright © 2005-2008, Nortel Networks .
CS 1000 NRS operation 12 Click Submit. —End— Operational logic The following items describe the operational logic of the CS 1000 SIP Redirect Server: • When an INVITE is received, the Public Address is extracted from the request URI. For example: INVITE SIP/2.0 • When the SIP Redirect Server searches the location database, it tries to find all the endpoints that meet the following requirements: — The endpoint belongs to the specified domain.
Operational logic 97 Table 3 Search results of location database If... Then... The resolution fails (that is, no endpoints are found), the SIP Redirect Server redirects to a collaborating server. • Send the 302 response (Moved Temporarily) • Build the Contact Address of the 302 response to include the collaborating servers IP address Note: For the purpose of this discussion, the collaborating server can be an MCS 5100 Session Manager. A single endpoint is found.
CS 1000 NRS operation Nortel Communication Server 1000 Communication Server 1000 to MCS 5100 Converged Desktop Type 2 Configuration Guide NN43001-321 01.05 Standard Release 5.0 15 February 2008 Copyright © 2005-2008, Nortel Networks .
Maintenance Contents This section contains information about the following topics: "Introduction" (page 99) "CS 1000 CLI commands" (page 99) "MCS 5100 tools" (page 101) "Translation Verification tool" (page 101) Introduction This section contains CS 1000 Command Line Interface (CLI) commands that can be used with CDS. The CS 1000 CLI commands are used from the Signaling Server CLI. This section also contains a diagnostic tool available on MCS 5100 for verifying translations.
Maintenance You must log in to the Signaling Server to use the CLI commands. Refer to Signaling Server Installation and Commissioning (NN43001-312) for this procedure. Table 4 "CDS OAM commands" (page 100) shows the Converged Desktop CLI commands available on the Signaling Server from the OAM shell. Table 4 CDS OAM commands Command Description cdsShow Displays the current Converged Desktop configuration. The command is used to check the basic Converged Desktop application status.
MCS 5100 tools Command Description cdsCallTraceSetAll Enables CDS call trace for all calls. 101 All messages to or from the Call Server and to or from the Signaling Server that relate to a Converged Desktop call are traced. cdsCallTraceOff Turns off CDS call trace for all calls. cdsCallTraceSetDN "callingNum", "calledNum" Sets CDS call trace for a particular calling party or called party DN. Where: • "callingNum" is the calling party DN. If set to 0, it traces all calls to a non-zero "calledNum".
Maintenance Figure 44 Provisioning Client: Translation Verification Tool 4 Enter the SIP URI to be traced in the Request URI text box. 5 Enter the destination DN in the To text box. 6 Enter the originating DN in the From text box. 7 Click Execute. —End— Nortel Communication Server 1000 Communication Server 1000 to MCS 5100 Converged Desktop Type 2 Configuration Guide NN43001-321 01.05 Standard Release 5.0 15 February 2008 Copyright © 2005-2008, Nortel Networks .
Appendix A Parameter configuration for a SIP URI Contents This section contains information about the following topics: "Introduction" (page 103) "Example" (page 103) "Phone-context strings" (page 104) "Phone-context strings for public numbers" (page 104) "Phone-context strings for unknown numbers" (page 105) "Phone-context strings for private numbers" (page 105) Introduction The SIP phone-context parameter qualifies a DN beyond the usual Numbering Plan Identifier (NPI) and Type of Number (TON).
Appendix A Parameter configuration for a SIP URI Global uniqueness of phone-context strings is a prerequisite for being able to serve a domain (for example, CDP-domain or an area code) by several systems (such as CS 1000 and MCS 5100). If the Site1 CDP domain is divided between a CS 1000 and an MCS 5100 system, then a globally unique phone-context for Site1 CDP domain must be defined and recognized by both systems.
Phone-context strings NPI/TON Scope NPI=Public, TON=Special Area within nation 105 Global prefixed-base d schema CS 1000 SIP Redirect Server implementation myarea.mynation. special.e164.myroot domain Not supported Not supported myarea.mynation. unknown.e164.
Appendix A Parameter configuration for a SIP URI Table 8 Phone-context strings for private numbers (example) NPI/TON Scope NPI=Private, TON=Level 1 Regional (UDP) Enterprise Hierarchical domain-based schema Global prefixed-base d schema level1.private. myenterprise +1-800-466-78 35 For example, myenterprise NPI=Private, TON=Level 0 Regional (CDP) Location withi n Enterprise NPI=Private, TON=Special Location withi n Enterprise mylocation.level0. private.
Appendix B PC Client windows Table 9 "PC Client: user expectations" (page 107) describes pop-up and other windows that may open and close on the PC Client when two users make a call on an Enterprise switch.
Appendix B PC Client windows Originating PCC’s call window closes when terminating PCC closes call window Network Call Log Popup Window CD2 to PSTN CD2 yes PSTN n/a CD2 no PSTN n/a No CD2 yes PSTN n/a N/A N/A PSTN to CD2 PSTN n/a CD2 yes PSTN n/a CD2 yes No PSTN n/a CD2 yes N/A N/A Video PCC Call Log/ Auto Presence Terminating PCC’s call window closes when originating PCC closes call window Nortel Communication Server 1000 Communication Server 1000 to MCS 5100 Converged Desktop Type
Nortel Communication Server 1000 Communication Server 1000 to MCS 5100 Converged Desktop Type 2 Configuration Guide Copyright © 2005-2008, Nortel Networks All Rights Reserved. Publication: NN43001-321 Document status: Standard Document version: 01.05 Document date: 15 February 2008 To provide feedback or report a problem in the document, go to www.nortel.
