Nortel Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide Release: 3.1 Document Revision: 02.01 www.nortel.com NN49000-315 .
Nortel Mobile Communication 3100 Release: 3.1 Publication: NN49000-315 Document release date: 2 October 2009 Copyright © 2008-2009 Nortel Networks. All Rights Reserved. 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 Features 5 Other changes 5 5 Introduction 7 MC 3100 and CS 1000 deployment overview 9 CS 1000 engineering for MC 3100 9 CS 1000 Source Based Routing 13 SIP Gateway CLID Parameters configuration 13 Mobile prefix 15 Data Access Planning 15 CS 1000 data access considerations 16 Licensing requirements 16 Dialing plans and telephone numbers 17 Service DN 18 Universal Extensions 19 Caller ID table 19 Device Handoff key configuration in PBX telephones 20 CallPilot MWI Co
Configuring ISM requirements 43 Printing system license limits 43 NRS configuration Configuring gateway endpoints on the NRS Adding an NRS Routing rule 47 Adding a User Endpoint 49 45 46 CS 1000 configuration for client support Configuring Configuring Configuring Configuring Configuring Configuring Configuring 53 features and keys 54 the Device Handoff key 55 the TSC steering codes 56 dial plan parameters 56 the Digit Manipulation Index 58 a Route List Index 59 Call Forward No Answer 59 MCC 3100 con
. New in this release The following sections detail what’s new in Nortel Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide (NN49000-315) for Mobile Communication 3100 (MC 3100) Release 3.1. • • "Features" (page 5) "Other changes" (page 5) Features For information on the features, see Nortel Mobile Communication 3100 Fundamentals (NN42030-109). Other changes The following changes were made for MC 3100 Release 3.
New in this release April 2009 Standard 01.03. This document is up-issued to add a new section called "CallPilot MWI Configuration" and to delete the following sections: • • • • Installing the ECM MCG 3100 software Adding the MCG 3100 as an element from the primary ECM Upgrading to a different network framework Accessing the MC 3100 Web Console from the ECM January 2009 Standard 01.02. This document is up-issued to add a new section called "SIP Gateway CLID Parameters configuration".
. Introduction This document describes the interworking of the Mobile Communication 3100 (MC 3100) and Communication Server 1000 (CS 1000). The MC 3100 consists of the Mobile Communication Gateway 3100 (MCG 3100), the MC 3100 Web User Interface (MC 3100 Web UI), and the clients: Nortel Mobile Communication Client 3100 (MCC 3100) for BlackBerry, MCC 3100 for Nokia, and MCC 3100 for Windows Mobile.
Introduction Nortel Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide NN49000-315 02.01 2 October 2009 Copyright © 2008-2009 Nortel Networks. All Rights Reserved. .
. MC 3100 and CS 1000 deployment overview This section describes the deployment of the Mobile Communication 3100 (MC 3100) with the Communication Server 1000 (CS 1000).
MC 3100 and CS 1000 deployment overview — Each user requires one Universal Extension (UEXT). Each UEXT supports the SIP interface on the client. Configure the UEXT with the Fixed Mobile Convergence Line (FMCL) subtype.The FMCL subtype requires an Incremental Software Management (ISM) independent of the Mobile Extension (MOBX) subtype. — SIP Access Port license • • SIP Gateway, operating on the VxWorks Signaling Server platform SPS, using the NRS-SPS on the Linux-based NRS.
CS 1000 engineering for MC 3100 Figure 1 Client with CS 1000 and UDP Figure 2 "Client with CS 1000 and CDP" (page 11) shows an example of clients using a CS 1000 CDP. Figure 2 Client with CS 1000 and CDP The UEXT configuration requirements are shown in the following table. Nortel Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide NN49000-315 02.01 2 October 2009 Copyright © 2008-2009 Nortel Networks. All Rights Reserved. .
MC 3100 and CS 1000 deployment overview Table 1 UEXT configuration parameters Parame ter Description UDP example CDP example Subtype UEXT subtype; must be FMCL FMCL FMCL primary DN On key 0; this determines the user’s published addresses for both private electronic switched network (ESN) and public direct inward dial (DID).
CS 1000 engineering for MC 3100 13 CS 1000 Source Based Routing CS 1000 Source Based Routing (SBR) occurs when the request Uniform Resource Indicator (URI) of the INVITE message sent from the Mobile Communication Client 3100 (MCC 3100) or the MCG 3100 contains the tag x-nt-net-feature=x-nt-home. For example, the following request URI triggers SBR: INVITE sip:+16131234567@nortel.com;x-nt-sip-line-service;x-nt-net-featur e=x-nt-home SIP/2.
MC 3100 and CS 1000 deployment overview For all public calls (subscriber [for example, NXX in North America], national [for example, NPA in North America], or international) E.164 fully qualified numbers are used to represent the caller. This is made possible through the use of the following parameters: • • • • • • Country Code Area Code Subscriber/Number of Digits to strip Subscriber/Prefix to insert National/Number of Digits to strip National/Prefix to insert The E.
Data Access Planning 15 Parameter: National/Number of Digits to strip For incoming national (NPA) calls this parameter defines the number of digits to strip from the incoming phone number prior to conversion to E.164 format. Parameter: National / Prefix to insert For incoming national (NPA) calls this parameter defines the prefix to insert after stripping any digits necessary from the incoming phone number prior to conversion to E.164 format.
MC 3100 and CS 1000 deployment overview CS 1000 data access considerations The MCG 3100 requires data access to the TLAN of the CS 1000. The MCG 3100 uses the CS 1000 SPS as the SIP Signaling Proxy. The media for all calls to and from MCC 3100 clients is anchored on the MCG 3100. The MCG 3100 will accept or transmit RTP to any IP endpoint within the enterprise (e.g. Media Cards, Other SIP clients, IP sets).
Dialing plans and telephone numbers 17 Dialing plans and telephone numbers MC 3100 supports telephone numbers in the following formats • Dial strings, where the user enters all the digits to be dialed. Examples of dial strings include 2356, 63432356, 93432356 and 3432356. • E.164 Fully Qualified International Numbers, where telephone numbers start with the plus (+) symbol. E.164 Fully Qualified International Numbers are also known as "plus numbers".
MC 3100 and CS 1000 deployment overview produce 00123456789 Call to a number outside Switzerland A user initiates a call to a contact with the phone number +14161234567. The URI incoming for the SIP INVITE for the call is sip:+14161234567@domain.
Universal Extensions 19 Configure the mobile prefix on the MCG 3100 gateway configuration tab as the incoming prefix for call termination. Configure the Service DN field on the MCG 3100 gateway configuration with the service DN. Universal Extensions A CS 1000 Universal Extension (UEXT) represents each mobile client instance.
MC 3100 and CS 1000 deployment overview Device Handoff key configuration in PBX telephones To allow an MCC 3100 user to perform Device Handoff between the MCC 3100 and PBX telephone, a Handoff key must be configured on the desktop telephone. The MCC 3100 uses the same configuration and same user interface for device handoff as the Mobile Extension feature introduced in CS 1000 Release 5.5. Only one handoff key can be configured for a desktop telephone.
Device Handoff key configuration in PBX telephones 21 CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD ICDD CDMD LLCN MCTD CLBD AUTU GPUD DPUD DNDA CFXA ARHD CLTD ASCD CPFA CPTA ABDD CFHD FICD NAID DNAA BUZZ UDI RCC HBTD AHD IPND DDGA NAMA MIND PRSD NRWD NRCD NROD DRDD EXR0 USMD USRD ULAD CCBD RTDD RBDD RBHD PGND FLXD FTTC DNDY DNO3 MCBN FDSD NOVD CDMR MCDD T87D PKCH CPND_LANG ENG HUNT PLEV 02 DANI NO AST IAPG 0 AACS NO ITNA NO DGRP MLWU_LANG 0 MLNG ENG DNDR 0 KEY 00 SCR 7771 0 MARP ANIE 0 01 HNDO 02 03 04 0
MC 3100 and CS 1000 deployment overview 25 CHG 26 CPN 27 CLT 28 RLT 29 30 31 DATE 25 MAR 2008 Nortel Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide NN49000-315 02.01 2 October 2009 Copyright © 2008-2009 Nortel Networks. All Rights Reserved. .
. CallPilot MWI Configuration For CallPilot to send message waiting indicator (MWI) notifications to the mobile clients, you must configure CallPilot with an alternate DN against the primary DN for the user. The alternate DN must be equal to the UEXT target DN used to extend SIP calls to the mobile clients. The format is: Example: 888881234567 When CallPilot sends the Message Waiting Indicator (MWI) notification, the following series of events occurs: 1.
CallPilot MWI Configuration Nortel Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide NN49000-315 02.01 2 October 2009 Copyright © 2008-2009 Nortel Networks. All Rights Reserved. .
. MC 3100 and CS 1000 integration This section describes the tasks required to get the Nortel Mobile Communication 3100 (MC 3100) working with Communication Server 1000 (CS 1000). MC 3100 and CS 1000 integration workflow Figure 4 "MC 3100 and CS 1000 integration workflow" (page 25) shows the steps required to integrate the MC 3100 and CS 1000.
MC 3100 and CS 1000 integration Work flow navigation • "Prerequisites" (page 27) • "MCG 3100 configuration" (page 37) • "CS 1000 configuration" (page 39) • "MCC 3100 configuration" (page 61) • "Validate deployment" (page 63) Nortel Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide NN49000-315 02.01 2 October 2009 Copyright © 2008-2009 Nortel Networks. All Rights Reserved. .
. Prerequisites This section describes the prerequisites for Mobile Communication 3100 (MC 3100) and Communication Server 1000 (CS 1000) integration. Navigation • • "Establishing the system baseline" (page 27) "Integration worksheet" (page 30) Establishing the system baseline To successfully integrate voice services, you must first establish the system baseline for the CS 1000 and MC 3100 systems so that the systems are configured and working in a stand-alone environment.
Prerequisites Task Reference The CS 1000 must have the latest DEP List loaded. Nortel Mobile Communication 3100 Release Notes (NN42030-404) (Updates through Product Bulletins) Comments SIP Proxy Server (SPS) SPS software is CS 1000 Release 5.5. SPS must have the latest SU loaded Nortel Mobile Communication 3100 Release Notes (NN42030-404) (Updates through Product Bulletins) MC 3100 Mobile Communication 3100 is Release 3.0.
Establishing the system baseline 29 Checking the CS 1000 release from Element Manager Use this procedure to check the version of the CS 1000 using Element Manager. Procedure steps Step Action 1 Log on to Element Manager. 2 On the left navigation pane, select Home. The Home System View page appears. 3 In the Call Server section, the software release is referred to as Release.
Prerequisites Figure 5 swVersionShow example --End-- Integration worksheet Use the following worksheet to capture values that you require during the integration of MC 3100 and CS 1000. Some of these values will not be applicable to your system, depending on your CS 1000 dialing plan. Table 3 Integration worksheet Related to Dial plan type Parameter Example CS 1000 UDP SIP Domain nortel.com L0 Domain CDP L1 Domain UDP ESN mobile prefix 343 ESN AC 6 ESN LOC 555 FLEN 10 DSC 2200 E.
Integration worksheet Related to Dial plan type NRS NRS—UDP Route NRS—CDP Route User Endpoint—U DP User Endpoint—C DP Value Parameter Example Description TSC 88888 FLEN 9 E.164 1-613 DSC 2200 Service DN 1.614E+10 Gateway Endpoint Id MCG3100 Add a gateway endpoint Call Signaling IP 192.167.13 0.75 This should be the IP of the MCG once it registers as a Dynamic Endpoint.
Prerequisites Related to MCG 3100 MCG 3100 (continued) Dial plan type Parameter Example Value Description Primary Gateway Address 192.167.13 0.75 The IP address that the local MCG 3100 uses for SIP traffic. This parameter is unique to the local server. Secondary Gateway Address (if applicable) 192.167.13 0.76 The IP address that the local MCG 3100 uses for SIP traffic. This parameter is unique to the local server. Primary and Secondary Gateway SIP Port 5060 The SIP server port.
Integration worksheet Related to MCG 3100 (continued) Dial plan type Parameter Example User Prefix / Phone-context for Call Origination CDP: None User Prefix for Call Termination MCG 3100 (continued) Dial-In Service DN UDP: udp CDP: 8888 8 UDP: 555 CDP: 2200 Value Description The user name prefix or phone context for call origination. This prefix applies to calls originated by the MCG 3100 server and to the calling address. The user name prefix for call termination.
Prerequisites Related to Dial plan type Parameter Example Value Description Mobility Prefix 555 Username 343XXXX The account use name on the enterprise network. Password XXXXXXX The account password on the enterprise network Outgoing Call Service DN +41123456 789 The mobile phone will dial +41123456789 for direct outbound calls. This PSTN number will be routed to the enterprise as a DID number.
Integration worksheet Related to MCC 3100 Dial plan type Value Parameter Example Description Mobile Contac t +41123456 789 Connection details for the primary Enterprise mobility gateway (EMG). Username 3435335 The account use name on the enterprise network. Password XXXXXXX The account password on the enterprise network. Outgoing Call Service DN +1 (613) 957-2200 The service directory number that enables you to place calls in Direct Outbound mode.
Prerequisites Nortel Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide NN49000-315 02.01 2 October 2009 Copyright © 2008-2009 Nortel Networks. All Rights Reserved. .
. MCG 3100 configuration Install the MCG 3100 as described in Nortel Mobile Communication 3100 Installation and Commissioning (NN42030-300), taking into consideration the following configuration requirements: • When configuring the Gateway Settings: — The User Prefix for Call Termination field which is related to the mobile prefix. For more information, see "Mobile prefix" (page 15). — The Dial-In Service DN field must be configured.
MCG 3100 configuration Nortel Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide NN49000-315 02.01 2 October 2009 Copyright © 2008-2009 Nortel Networks. All Rights Reserved. .
. CS 1000 configuration This section describes the configuration required on the Communication Server 1000 (CS 1000). CS 1000 configuration workflow CS 1000 configuration requires a number of tasks to be completed, as shown in the following figure.
CS 1000 configuration Nortel Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide NN49000-315 02.01 2 October 2009 Copyright © 2008-2009 Nortel Networks. All Rights Reserved. .
. CS 1000 licensing This section describes the tasks required for Communication Server 1000 (CS 1000) licensing.
CS 1000 licensing Procedure steps Step Action 1 Connect to your call server. 2 Press enter. 3 Enter the following command to log in to the system. LOGI admin2 4 Enter the Level 2 password. 5 Enter the following command. LD 22 6 At the REQ prompt, enter PRT 7 At the TYPE prompt, enter PKG 8 From the results, ensure that Packages 414, 412, 398, and 145 are listed. --End-- Verifying PCA requirements Use this procedure to verify that the PCA feature is enabled.
Printing system license limits 43 Configuring ISM requirements ISM counts are created for each of the Universal Extension subtypes, according to the following table.
CS 1000 licensing 5 Enter the following command: LD 22 6 At the REQ prompt, enter SLT 7 From the results, ensure from the LEFT parameter that you have the necessary ISMs available. --End-- Nortel Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide NN49000-315 02.01 2 October 2009 Copyright © 2008-2009 Nortel Networks. All Rights Reserved. .
. NRS configuration The Mobile Communication Gateway 3100 (MCG 3100) is defined as a Dynamic Gateway Endpoint on the Network Routing Server (NRS) SIP Proxy Server (SPS) and is assigned an endpoint name. Authentication is turned off. The endpoint name is configured on the MCG 3100 as the gateway name under the list of gateway configuration parameters. Each Mobile Communication Client 3100 (MCC 3100) or MC 3100 Web User Interface user is represented by an NRS-SPS User Endpoint (UE).
NRS configuration Figure 8 NRS configuration task flow Task flow navigation • "Configuring gateway endpoints on the NRS" (page 46) • "Adding an NRS Routing rule" (page 47) • "Adding a User Endpoint" (page 49) Configuring gateway endpoints on the NRS Perform the following procedure to configure the MCG gateway endpoints on the Network Routing Service (NRS). You must perform this procedure for each MCG node on the system. On NRS redundant systems, perform all configuration on the primary NRS.
Adding an NRS Routing rule 5 47 Ensure that the correct service domain, L1 domain, and L0 domain are selected and click Add. The View Gateway Endpoint Property page appears. 6 For Endpoint name, type a relevant endpoint name. Example: MCG3100 7 For Endpoint description, type a relevant endpoint description. 8 Clear the Trust Node check box. 9 Ensure that Tandem Gateway Endpoint name is configured to Not Configured.
NRS configuration 3 In the NRS Manager Navigator, select Numbering Plans, Routes. The Routes web page opens. 4 Ensure Standby database is selected. 5 The Limit results to Domain drop-down lists, in the Search for Routing Entries pane, contain configured Service Domains, L1 Domains and L0 Domains. Select a Service Domain, an L1 Domain and an L0 Domain from the respective drop-down lists. 6 Select a Gateway Endpoint from the Endpoint Name drop-down list in the Search for Routing Entries pane.
Adding a User Endpoint 49 The Commit command is issued, and the database is placed into a Committed state. --End-- Adding a User Endpoint Use this procedure to add a user endpoint to the NRS. Each mobile client instance is represented by a User Endpoint (UE). Create the UE in the L0 domain that corresponds to the PBX that hosts the user.
NRS configuration The standby database is updated. The Endpoints Web page opens, showing the newly added User Endpoint in the User Endpoints pane. 8 If required, click Add to add additional User Endpoints. The User Endpoints Web page displays any new endpoints. Attention: A maximum of 100 user endpoints can be displayed on the User Endpoints Web page. Attention: On login, the MCC 3100 users validate their password against the NRS; however they never will show as registered against the NRS.
Adding a User Endpoint Field Description User endpoint description The endpoint’s description can use most keyboard characters (except single quotes) and can be up to 120 characters in length. 51 Frequently, this field is configured with the user’s name. Example John Smith Trust Node The checkbox should be cleared. Tandem gateway endpoint name Configure the field to Not Configured. L0 directory number (DN) This field is a number that is based on the user’s directory number.
NRS configuration Nortel Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide NN49000-315 02.01 2 October 2009 Copyright © 2008-2009 Nortel Networks. All Rights Reserved. .
. CS 1000 configuration for client support This section describes the configuration required on the Communication Server 1000 (CS 1000) to support the individual Mobile Communication Client 3100 (MCC 3100) users. CS 1000 configuration for client support task flow Configuring the CS 1000 for client support requires the following procedures.
CS 1000 configuration for client support Task flow navigation • "Configuring features and keys" (page 54) • "Configuring the Device Handoff key" (page 55) • "Configuring the TSC steering codes" (page 56) • "Configuring dial plan parameters" (page 56) • "Configuring the Digit Manipulation Index" (page 58) • "Configuring a Route List Index" (page 59) • "Configuring Call Forward No Answer" (page 59) Configuring features and keys Use this procedure to configure the features and keys on the CS 1000.
Configuring the Device Handoff key 7 55 Navigate to the Keys section of the Phone Details page. • • Key 0 is configured with the SCR DN. Key 1 is configured as a HOT_P key containing the mobile DN. 8 Enter the required details for Key 0 and Key 1 and click Validate to perform validation of general properties, features, and keys. For more information, see the following Job aid. 9 Click Finish.
CS 1000 configuration for client support Example: 100 0 0 29 9 At the KEY prompt, enter 01 HNDO to program the Handoff feature on key 01 of the device. --End-- Configuring the TSC steering codes Perform this procedure if you require TSC steering codes. Procedure steps Step Action 1 Connect to your call server. 2 Press enter. 3 Enter the following command to log in to the system: LOGI admin2 4 Enter the Level 2 password.
Configuring dial plan parameters 57 Use your CS 1000 documentation and your existing dial plan to configure the parameters in the following job aids.
CS 1000 configuration for client support Table 5 CDP parameters (cont’d.) Parameter Description Example Mobility mobile prefix Configured in MCG 3100 Call termination field Mobility mobile prefix configured in NRS Routing rule as 88888. UEXT 88888 5535 LD 11 - KEY Configuring the Digit Manipulation Index Create a Digit Manipulation Index (DMI) to take calls from the PSTN, route it to the SIP Gateway, through the SRS, and finally to the MCG 3100.
Configuring Call Forward No Answer 59 Configuring a Route List Index The Route List Index (RLI) defines the trunk characteristics. The RLI is used to steer calls to the MCG 3100. Procedure steps Step Action 1 Connect to your call server. 2 Press enter. 3 Enter the following command to log in to the system: LOGI admin2 4 Enter the Level 2 password.
CS 1000 configuration for client support FNAL CFTA CCFWDN CFN0 CFN1 6 CFN2 DFN0 DFN1 DFN2 MDID NDID MWFB TRCL CRTOD CRDAY CRHOL LD 11 configures the number of ringing cycles for CFNA. Configure the CFN index that corresponds to the RCO entry configured in LD 15 (for example, RCO 1 uses CFN 1). LD 11 REQ: chg TYPE: 1140 TN 100 0 8 23 ECHG yes ITEM rco 1 ITEM HNT FNA HNT FNA Nortel Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide NN49000-315 02.
. MCC 3100 configuration On the first login attempt, Mobile Communication Client 3100 (MCC 3100) users have a minimal set of parameters to configure. • Server Address—The Fully Qualified Domain Name (FQDN) or IP address of the MCG 3100 • • • Login Name—The user’s account username on the network. Login Password—The user’s login password on the network. Mobile Phone Number Attention: Configure the mobile telephone number using the format +1XXXXXXXXXX .
MCC 3100 configuration Autoconfiguration settings Autoconfiguration allows a number of the client configuration parameters to be preset on the MCG 3100 and downloaded to the client during the first login to the MCG 3100. The automatically-downloaded fields appear as grey text on the interface unless the administrator allows the user to override the configuration. Autoconfiguration insures that all clients registered to each MCG 3100 receive the same configuration.
. Validate deployment This section describes how to validate that the Mobile Communication 3100 (MC 3100) components and the Communication Server 1000 (CS 1000) integration is correct.
Validate deployment Procedure steps Step Action 1 Login to the NRS. 2 Select Endpoints under the Numbering Plan menu on the left hand side. 3 Ensure that you are managing the Active Database. 4 Select the Gateway Endpoints tab. 5 In the results pane, locate the MCG3100 endpoint ID. 6 Verify that the Call Signaling IP is the IP address of the MCG3100 gateway. If the Call Signaling IP field shows Not Registered, then the MCG3100 gateway is not currently registered.
Validating MC 3100 and CS 1000 deployment 65 Prerequisites • • • • MCG 3100 has been installed and configured. MCC 3100 has been installed and configured on a number of devices. CS 1000 has been configured to support MC 3100. LDAP server is accessible. Procedure steps Step Action 1 Configure the MCG 3100 to not require encryption. 2 Configure the MCC 3100 for BlackBerry to not require encryption. 3 Log in to the MCC 3100 for BlackBerry (uses HTTP).
Validate deployment 13 Perform a corporate directory search from the client for a known user. Verifies that the LDAP to MCG 3100 connections and data mapping are correct. 14 Add a user from the corporate directory search to the buddy list. 15 Send an instant message to the added user. Validates the LDAP field mapping and instant message functionality. 16 Check that you can see the presence status of the user. Validates the LDAP field mapping and presence.
Nortel Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide Release: 3.1 Publication: NN49000-315 Document revision: 02.01 Document release date: 2 October 2009 Copyright © 2008-2009 Nortel Networks. All Rights Reserved.
