Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering Release: 3.0 Document Revision: 03.04 www.nortel.com NN42030-200 .
Nortel Mobile Communication 3100 Release: 3.0 Publication: NN42030-200 Document release date: 17 July 2009 Copyright © 2007-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 MCC 3100 changes 5 MCG 3100 changes 6 Communication server requirements Other changes 6 5 6 Overview References 9 9 Planning 11 MCC 3100 network deployment 11 Data network requirements 12 MCG 3100 network deployment 13 BlackBerry deployment considerations (with BES) 14 BlackBerry (without BES), Nokia, and Windows Mobile deployment considerations 15 Network bandwidth requirements 15 CS 1000 Dialing plans and telephone numbers 16 CS 2100 dialing plans and t
CS 1000 engineering for MC 3100 34 SIP Trunk configuration 37 Device Handoff configuration 39 CS 1000 feature interactions 40 CS 1000 capacity requirements 41 Trunk calculation: Method 1 42 Trunk calculation: Method 2 43 UEXT calculations 46 CS 1000 release and supported MC 3100 features Call Detail Recording 48 Direct outbound call 48 Call-Me-First outbound call 49 Incoming call 49 46 Index Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering NN42030-200 03.
. New in this release The following sections detail what’s new in Nortel Mobile Communication 3100 Planning and Engineering (NN42030-200) for Nortel Mobile Communication 3100 (MC 3100) Release 3.0.
New in this release MCG 3100 changes The Nortel Mobile Communication Gateway 3100 (MCG 3100) in Release 3.0 contains the following planning and engineering changes: • New licenses required to enable features on the Nortel Communication Server 1000 (CS 1000) Release 5.5. MC 3100 Release 3.0 does not support the MC 3100 Release 2.x licences. Communication server requirements MC 3100 Release 3.0 supports CS 1000 Release 5.5. CS 1000 Release 5.
Other changes November 2007 Standard 01.09. This document is up-issued to support the Nortel Mobile Communication 3100 Series Portfolio on Nortel Communication Server 1000 Release 5.0 and Nortel Multimedia Communication Server 5100 Release 4.0. It addresses CR Q01773232 and Q01776937. October 2007 Standard 01.07. This document is up-issued to support the Nortel Mobile Communication 3100 Series Portfolio on Nortel Communication Server 1000 Release 5.
New in this release Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering NN42030-200 03.04 17 July 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved. .
. Overview This document describes the planning and engineering guidelines for the Nortel Mobile Communication 3100 (MC 3100). The MC 3100 is Nortel’s mobility solution for Enterprise networks and consists of a Mobile Communication Gateway 3100 (MCG 3100) server and the Mobile Communications Client 3100 (MCC 3100) application for mobile devices.
Overview Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering NN42030-200 03.04 17 July 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved. .
. Planning This chapter details the planning aspects of the Mobile Communication 3100 (MC 3100).
Planning Figure 1 Typical MC 3100 network architecture The MCC 3100 for Nokia and MCC 3100 for Windows Mobile do not contain integrated virtual private network (VPN) software. Any industry-standard VPN software for the Nokia or Windows Mobile device can be used. The MCC 3100 for Nokia and MCC 3100 for Windows Mobile communicate directly to the MCG 3100. When deployed with the BES, the MCC 3100 for BlackBerry communicates with the BES, which communicates with the MCG 3100.
MCG 3100 network deployment 13 MCC 3100 for BlackBerry (with BES) This section describes the requirements for the MCC 3100 for BlackBerry with the BES. For configurations that do not required the BES, see "MCC 3100 for BlackBerry (without BES), MCC 3100 for Nokia, and MCC 3100 for Windows Mobile" (page 13). The Enterprise-hosted BES defines the data networking requirements between the BlackBerry and the BES.
Planning • access to the ECS Telephony Local Area Network (TLAN), including all SIP infastructure, media gateways, and any IP endpoint that can originate or terminate real-time transport • access to a BlackBerry Enterprise Server (BES) if the MCG 3100 supports the MCC 3100 for BlackBerry with the BES Figure 2 "Data access from devices" (page 14) shows data access from the devices.
MCG 3100 network deployment 15 The BES defines the data networking requirements between the BlackBerry device and the BES. The BES configuration must include the BlackBerry Mobile Data System (MDS) to allow the MCC 3100 for BlackBerry to route HTTP traffic to the BES, and then to the Enterprise MCG 3100. When you deploy the MCG 3100, data originates from the BES for the MCC 3100 for BlackBerry clients.
Planning HTTP Signaling For HTTP signaling, make the following assumptions: • Each mobile client use exchanges approximately 30 megabytes (MB) of signaling data with the MCG 3100 each month. • With 22 business days per month, each mobile user exchanges approximately 1.36 MB of signaling data per day. • • Signaling traffic takes place for 7.5 hours each business day. • In the context of streaming data, 1 MB = 10002 (not 10242 as in the context of computer memory). 1.36 MB/7.
CS 1000 Dialing plans and telephone numbers 17 of Fully Qualified International Numbers include +16131234567 and +31123456789. The dial plan available from MC 3100 should be the same as the dial plan for a desk telephone. That is, if the user has a desk telephone and an MCC 3100 device, the dial plan should be the same. MC 3100 users should use the E.164 Fully Qualified International Numbers for all stored Public Switched Telephone Network (PSTN) numbers in address books and mobile device applications.
Planning CS 1000 digit processing adds to produce 00014161234567 Example 2 (North America) ECS is CS 1000 AC1=6, CNTC=1, NATC=1, INTC=011 Call to a number within North America 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.
Security requirements 19 on the internet to a public FQDN and a public IP address. The figure also shows a sample firewall configuration and policy. For the purposes of this example assume • that the MCC 3100 (in the absence of a BES) requires a public FQDN and IP for the MCG 3100 to be accessible from the internet. This in turn forces the MCG 3100 to be placed in a demilitarized zone (DMZ).
Planning which communicates with the MCG 3100. The MCC 3100 for Nokia and MCC 3100 for Windows Mobile communicates directly with the MCG 3100, as well as the MCC 3100 for BlackBerry when configured without the BES. Access to user records in an active directory server configured against the MCG 3100 uses a tunnel over HTTP or HTTPS. Configure the MCG 3100 to specify the query search base, which limits the search to a subtree of the base.
High availability 21 Figure 4 MCG 3100 high availability configuration A redundant system includes an active server and a standby server. Mobile clients access the active server, while the standby server functions as a backup. The two roles switch freely, based on the following rules: • If the MCG 3100 does not have a configured backup IP address, it starts in active mode. • If the MCG 3100 has a configured backup IP address, it starts in inactive mode and attempts to locate the standby system.
Planning The clients support MCG 3100 redundancy. The Primary MCG 3100 address and Secondary MCG 3100 address fields in the clients contain the active and standby MCG 3100 IP addresses respectively. When the active MCG 3100 stops responding, the clients switch to the other MCG 3100. Attention: The communication link between two MCG 3100 servers in the redundant pair must be highly reliable and available.
High availability Figure 5 Support for multiple call servers using UDP with CS 1000 Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering NN42030-200 03.04 17 July 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved. .
Planning Figure 6 Support for multiple call servers using CDP with CS 1000 In an ECS high availability configuration, the MCG 3100 sends a message to the Primary SPS. If the message • succeeds, the MCG 3100 uses the Primary SPS and sends a message every 20 seconds to check its availability. • fails, the MCG 3100 attempts to connect to the Secondary SPS. — If the Secondary SPS responds, the MCG 3100 connects to the Secondary SPS.
. Engineering This chapter details the engineering aspects of the Mobile Communication 3100 (MC 3100). Navigation • • • "Client device specifications" (page 25) "Gateway specifications" (page 25) "Port tables" (page 25) Client device specifications The Mobile Communication Client 3100 (MCC 3100) application runs on a number of devices. These devices have no special hardware or software requirements. To view the list of supported devices, see the MC 3100 Product Bulletin at www.nortel.com.
Engineering Table 1 MCG 3100 ports Port Protocol Function Applicatio n Configurabl e? Configure in MCG 3100-t o-Enterprise Firewall policy? Configure in Internet-to -MCG 3100 Firewall policy? 21 Transmissi on Control Protocol (TCP) File Transfer Protocol (FTP) Base Linux No No No 22 TCP Secure Shell (SSH) Base Linux No No No 53 (Send only) User Datagr am Protocol (UDP) Domain Name Server (DNS) querie s to external DNS server Base Linux No Yes, assuming DNS is within the Enterpri
Port tables 27 Table 1 MCG 3100 ports (cont’d.
Engineering Table 1 MCG 3100 ports (cont’d.
Port tables 29 In the preceding table, the ranges 26000 to 26999 and 27000 to 27999 depend on the configuration of the Maximum number of DTR ports parameter. The following table lists the ports that are defined by the Enterprise Call Server (ECS). You configure these ports on the ECS. Table 2 ECS ports Protocol Function Application Configure in the MCG 3100-to-E nterprise Firewall policy? Configure in the Inter net-to-MCG 3100 Firewall policy? RTP (UDP ) VoIP send port for the Gateway server.
Engineering Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering NN42030-200 03.04 17 July 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved. .
. License requirements This chapter details the license requirements of the Mobile Communication 3100 (MC 3100).
License requirements The MCG 3100 requires internet access to www199.nortel.com (using port 8008) to validate the client licenses on the clients. During installation, the MCG 3100 stores the site license file. The site license contains the licenses for the clients. The MCG 3100 does not distribute the licenses to the clients. When a user accesses the client application, the client software contacts the MCG 3100.
. Interworking requirements with CS 1000 This chapter details the interworking requirements for the Mobile Communication 3100 (MC 3100) and Nortel Communication Server 1000 (CS 1000), which is a supported Enterprise Call Server (ECS). For information about interworking requirements with the Nortel Communication Server 2100 (CS 2100), see Nortel Mobile Communication 3100 and Communication Server 2100 Solution Integration Guide (NN42200-506).
Interworking requirements with CS 1000 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.
CS 1000 engineering for MC 3100 35 The Direct Inward Dial (DID) number for the Dial in Service DN terminates on the MCG 3100. Configure the CS 1000 with a Mobility Home Location Code (HLOC) to support the client. The UEXT target DN uses the HLOC as a prefix to identify mobile users. The HLOC is a unique digit sequence that does not conflict with the CS 1000 Universal Dialing Plan (UDP), Coordinated Dialing Plan (CDP), and routing configuration.
Interworking requirements with CS 1000 Figure 8 "Client with CS 1000 and CDP" (page 36) shows an example of clients using a CS 1000 CDP. Figure 8 Client with CS 1000 and CDP The UEXT configuration requirements are shown in the following table. Table 3 UEXT configuration parameters Parame ter Description UDP example CDP example Subtype UEXT subtype; must be FMCL FMCL FMCL Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering NN42030-200 03.
CS 1000 engineering for MC 3100 Table 3 UEXT configuration parameters (cont’d.) Parame ter Description UDP example CDP example 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).
Interworking requirements with CS 1000 correct Calling Line ID (CLID) and have the same Network Class of Service (NCOS) as a call from the associated communication server telephone.
CS 1000 engineering for MC 3100 39 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, you must remove all Virtual Trunks before you can change the RDB to ESN5. Device Handoff configuration Device handoff permits the MC 3100 user to hand off an established call between the mobile phone and the desk telephone. The desk telephone must be configured with a handoff key.
Interworking requirements with CS 1000 For more information, see Nortel Mobile Communication 3100 and Communication Server 1000 Solution Integration Guide (NN49000-315) and Features and Services Fundamentals (NN43001-106). CS 1000 feature interactions The clients support a high availability configuration for improved redundancy and failover. Configure the client with primary and secondary proxy addresses that refer to different NRS-SPSs.
CS 1000 capacity requirements 41 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).
Interworking requirements with CS 1000 You can use one of the two following methods to calculate the PSTN trunks and SIP Access Ports: • • "Trunk calculation: Method 1" (page 42) "Trunk calculation: Method 2" (page 43) To calculate the number of UEXTs required, see "UEXT calculations" (page 46). For more information about CS 1000 capacity, see Communication Server 1000E Planning and Engineering (NN43041-220). Trunk calculation: Method 1 Follow these steps: 1. Add the number of client users. 2.
CS 1000 capacity requirements 43 Table 5 Poisson trunk table (cont’d.
Interworking requirements with CS 1000 2. Multiply the total number of users by the desired CCS per User number to obtain a CCS value. 3. Use Table 6 "Trunk traffic Poisson 1 percent blocking" (page 44) to find the CCS value and obtain the number of PSTN trunks (in the cell to the left of the CCS number). If the CCS value is between two values in the trunks column, choose the higher number of trunks. For trunk traffic greater than 6068 CCS, allow 30.34 CCS per trunk. 4.
CS 1000 capacity requirements 45 Table 6 Trunk traffic Poisson 1 percent blocking (cont’d.
Interworking requirements with CS 1000 The number of SIP Access Ports is the number of PSTN trunks multiplied by 2, which is 28 x 2 = 56. UEXT calculations You require one UEXT for each MCC 3100 user. CS 1000 release and supported MC 3100 features The following table describes the MC 3100 call features (provided by the CS 1000). Table 7 MC 3100 call features CS 1000 Release 5.5 Mob ileX MCC 3100 for Window s Mobile MCC 3100 for Black Berry MCC 3100 for Nokia CS 1000 Release 5.
CS 1000 release and supported MC 3100 features 47 Table 7 MC 3100 call features (cont’d.) CS 1000 Release 5.5 Mob ileX MCC 3100 for Window s Mobile MCC 3100 for Black Berry MCC 3100 for Nokia X √ √ √ Over the air download/install of client n/a √ √ √ MC 3100 Release 2.0 User Interface n/a X X √ MC 3100 Release 3.
Interworking requirements with CS 1000 Table 7 MC 3100 call features (cont’d.) CS 1000 Release 5.
Call Detail Recording 49 Call-Me-First outbound call When the user makes a Call-Me-First outbound call, the mobile client user’s home CS 1000 generates two CDR records. • The first CDR record provides details of the call from the MCG 3100 to the mobile phone. In this record, the originator is the username of the mobile client and the destination number is the mobile phone number. • The second CDR record provides details of the outgoing call from the MCG 3100 to the called party.
Interworking requirements with CS 1000 Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering NN42030-200 03.04 17 July 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved. .
. Index B BlackBerry Enterprise Server (BES) 11, 13–15, 18 5, C Communication Server 1000 (CS 1000) PSTN calculations 42–43 SIP Access Ports calculations 42–43 Universal Extension (UEXT) calculations 46 Enterprise Call Server (ECS) 13, 18, 22, 31 High availability 20 Mobile Communication Client 3100. See MCC 3100 for Blackberry, MCC 3100 for Nokia, or MCC 3100 for Windows Mobile Mobile Communication Gateway 3100 .
Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering NN42030-200 03.04 17 July 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved. .
Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering Release: 3.0 Publication: NN42030-200 Document revision: 03.04 Document release date: 17 July 2009 Copyright © 2007-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.
