Page 3 - Contents; New in this release
3 . Contents New in this release 5 Features 5 Other changes 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 considera...
Page 5 - Features; Revision history
5 . New in this release The following sections detail what’s new in Nortel Mobile Communication3100 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...
Page 7 - Introduction; Navigation
7 . Introduction This document describes the interworking of the Mobile Communication3100 (MC 3100) and Communication Server 1000 (CS 1000). TheMC 3100 consists of the Mobile Communication Gateway 3100(MCG 3100), the MC 3100 Web User Interface (MC 3100 Web UI), andthe clients: Nortel Mobile Communic...
Page 15 - Parameter: National/Number of Digits to strip; Mobile prefix
Data Access Planning 15 Parameter: National/Number of Digits to strip For incoming national (NPA) calls this parameter defines the number ofdigits to strip from the incoming phone number prior to conversion to E.164format. Parameter: National / Prefix to insert For incoming national (NPA) calls this...
Page 16 - CS 1000 data access considerations; Example; Licensing requirements
16 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. TheMCG 3100 uses the CS 1000 SPS as the SIP Signaling Proxy. The mediafor all calls to and from MCC 3100 clients is anchored on the MCG 3100.The MCG 3100 will a...
Page 17 - Dialing plans and telephone numbers
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. Examplesof dial strings include 2356, 63432356, 93432356 and 3432356. • E.164 Fully Qualified Inte...
Page 18 - Service DN
18 MC 3100 and CS 1000 deployment overview produce 00123456789 Call to a number outside SwitzerlandA user initiates a call to a contact with the phone number +14161234567. The URI incoming for the SIP INVITE for the call issip:[email protected];user=phone CS 1000 digit processing adds <AC1 ...
Page 19 - Universal Extensions; Caller ID table
Universal Extensions 19 Configure the mobile prefix on the MCG 3100 gateway configuration tab asthe incoming prefix for call termination. Configure the Service DN field onthe MCG 3100 gateway configuration with the service DN. Universal Extensions A CS 1000 Universal Extension (UEXT) represents each...
Page 20 - Device Handoff key configuration in PBX telephones
20 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 theMCC 3100 and PBX telephone, a Handoff key must be configured onthe desktop telephone. The MCC 3100 uses the same configuration andsame user int...
Page 23 - CallPilot MWI Configuration
23 . CallPilot MWI Configuration For CallPilot to send message waiting indicator (MWI) notifications to themobile clients, you must configure CallPilot with an alternate DN againstthe primary DN for the user. The alternate DN must be equal to the UEXTtarget DN used to extend SIP calls to the mobile ...
Page 26 - Work flow navigation
26 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...
Page 27 - Prerequisites
27 . 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 su...
Page 29 - Checking the CS 1000 release from Element Manager; Checking the CS 1000 release from the command line; Step; swVersionShow
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 ElementManager. 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...
Page 30 - Integration worksheet
30 Prerequisites Figure 5swVersionShow example --End-- Integration worksheet Use the following worksheet to capture values that you require during theintegration of MC 3100 and CS 1000. Some of these values will not beapplicable to your system, depending on your CS 1000 dialing plan. Table 3Integrat...
Page 42 - Verifying PCA requirements; Procedure steps
42 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 t...
Page 43 - Configuring ISM requirements; Printing system license limits; LOGI admin2
Printing system license limits 43 Configuring ISM requirements ISM counts are created for each of the Universal Extension subtypes,according to the following table. Universal Extension UXTY ISM Description MOBX Mobile Extensions Implemented by this feature TLSV Telephony Services Microsoft OCS 2007 ...
Page 44 - REQ
44 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 havethe necessary ISMs available. --End-- Nortel Mobile Communication 3100 Mobile Communication 3100 and Communication Server 1000 Solution Integration...
Page 45 - NRS configuration; NRS configuration task flow
45 . NRS configuration The Mobile Communication Gateway 3100 (MCG 3100) is defined as aDynamic Gateway Endpoint on the Network Routing Server (NRS) SIPProxy Server (SPS) and is assigned an endpoint name. Authenticationis turned off. The endpoint name is configured on the MCG 3100 as thegateway name ...
Page 46 - Task flow navigation
46 NRS configuration Figure 8NRS 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 pr...
Page 47 - Adding an NRS Routing rule
Adding an NRS Routing rule 47 5 Ensure that the correct service domain, L1 domain, and L0domain 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 descr...
Page 49 - Adding a User Endpoint
Adding a User Endpoint 49 The Commit command is issued, and the database is placed intoa 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 corres...
Page 50 - Select the Commit button.; Job Aid
50 NRS configuration The standby database is updated. The Endpoints Web pageopens, showing the newly added User Endpoint in the UserEndpoints pane. 8 If required, click Add to add additional User Endpoints. The UserEndpoints Web page displays any new endpoints. Attention: A maximum of 100 user endpo...
Page 53 - CS 1000 configuration for client support task flow
53 . CS 1000 configuration for clientsupport This section describes the configuration required on the CommunicationServer 1000 (CS 1000) to support the individual Mobile CommunicationClient 3100 (MCC 3100) users. CS 1000 configuration for client support task flow Configuring the CS 1000 for client s...
Page 55 - Job aid; Configuring the Device Handoff key
Configuring the Device Handoff key 55 7 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 mobileDN. 8 Enter the required details for Key 0 and Key 1 and click Validateto perform validation of general pro...
Page 56 - Configuring the TSC steering codes; Configuring dial plan parameters
56 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 you...
Page 57 - UDP Job Aid
Configuring dial plan parameters 57 Use your CS 1000 documentation and your existing dial plan to configurethe parameters in the following job aids. UDP Job Aid Table 4UDP parameters Parameter Description Example ESN AC The Access code can beconfigured in LD 15 whileconfiguring the CDB AC2 : 6 mobil...
Page 58 - Configuring the Digit Manipulation Index
58 CS 1000 configuration for client support Table 5CDP parameters (cont’d.) Parameter Description Example Mobility mobile prefix Configured in MCG 3100 Calltermination field Mobility mobile prefixconfigured in NRS Routingrule as 88888. UEXT LD 11 - KEY <mobileprefix><DN> 88888 5535 Confi...
Page 59 - Configuring a Route List Index; Configuring Call Forward No Answer
Configuring Call Forward No Answer 59 Configuring a Route List Index The Route List Index (RLI) defines the trunk characteristics. The RLI isused 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 s...
Page 62 - Autoconfiguration settings
62 MCC 3100 configuration Autoconfiguration settings Autoconfiguration allows a number of the client configuration parametersto be preset on the MCG 3100 and downloaded to the client during thefirst login to the MCG 3100. The automatically-downloaded fields appearas grey text on the interface unless...
Page 63 - Validate deployment; Validating deployment task flow
63 . Validate deployment This section describes how to validate that the Mobile Communication3100 (MC 3100) components and the Communication Server 1000(CS 1000) integration is correct. Validating deployment task flow Validating deployment task flow navigation • "Validating MCG 3100 registration...
Page 64 - Validating MCC 3100 for BlackBerry communication
64 Validate deployment Procedure steps Step Action 1 Login to the NRS. 2 Select Endpoints under the Numbering Plan menu on the lefthand 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 t...