Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering Release: 3.1 Document Revision: 04.01 www.nortel.com NN42030-200 .
Nortel Mobile Communication 3100 Release: 3.1 Publication: NN42030-200 Document release date: 2 October 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 Communication server requirements Other changes 5 5 5 Overview References 7 7 Planning 9 MCC 3100 and MC 3100 Web UI network deployment 9 Data network requirements 10 MCG 3100 network deployment 12 BlackBerry deployment considerations (with BES) 12 BlackBerry (without BES), Nokia, and Windows Mobile deployment considerations 13 Network bandwidth requirements 13 Dialing plans and telephone numbers 14 Security requirements 16 Password protection 18 High avai
SIP Trunk configuration 35 Device Handoff configuration 37 CS 1000 feature interactions 38 CS 1000 capacity requirements 39 Trunk calculation: Method 1 40 Trunk calculation: Method 2 41 UEXT calculations 44 CS 1000 release and supported MC 3100 features Call Detail Recording 45 Direct outbound call 46 Call-Me-First outbound call 46 Incoming call 46 44 Index Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering NN42030-200 04.
. 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.1.
New in this release Revision history October 2009 Standard 04.01. This document is issued to support Nortel Mobile Communication 3100 Release 3.1. July 2009 Standard 03.04. This document is issued to support Nortel Mobile Communication 3100 Release 3.0 and the Communication Server 2100 (CS 2100). Information regarding the CS 2100 is added. April 2009 Standard 03.03. This document is up-issued to reflect modifications made to support Nortel Mobile Communication 3100 Release 3.0.
. 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 and MC 3100 Web User Interface for mobile devices.
Overview Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering NN42030-200 04.01 2 October 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.
MCC 3100 and MC 3100 Web UI network deployment 11 • • "MCC 3100 for BlackBerry (with BES)" (page 11) "MCC 3100 for BlackBerry (without BES), MCC 3100 for Nokia, and MCC 3100 for Windows Mobile" (page 11) 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 11).
Planning MCG 3100 network deployment The Mobile Communication Gateway 3100 (MCG 3100) requires the following network infrastructure: • access to an Enterprise Call Server (ECS) including a call server, Session Initiation Protocol (SIP) gateway, and SIP Proxy Server (SPS) • 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
MCG 3100 network deployment 13 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.
Dialing plans and telephone numbers 15 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 17 Figure 3 Sample MCG 3100 firewall configuration If a user calls a client, the SIP signaling comes through the SPS. Real Time Protocol (RTP) for announcements or MC 3100 Instant Conference calls takes place between the MCG 3100 and the IP telephone without using the SPS.
Planning The MCG 3100 queries a corporate Lightweight Directory Access Protocol (LDAP) server when the users use the Directory lookup feature on their clients. The MCG 3100 supports the following LDAP servers: • • Active Directory/Exchange Server 2000 or 2003 Nortel Common Network Directory (CND), which is part of Telephony Manager (TM) 3.
High availability 19 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 Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering NN42030-200 04.01 2 October 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved. .
Planning Figure 6 Support for multiple call servers using CDP 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 23) "Gateway specifications" (page 23) "Port tables" (page 23) 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 Application Configurable? Configure in MCG 3100to-Enterpri se 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 Enterprise
Port tables 25 Table 1 MCG 3100 ports (cont’d.
Engineering Table 1 MCG 3100 ports (cont’d.
Port tables Table 2 ECS ports (cont’d.) Protocol Function Applicatio n Configure in the MCG 3100-to-Enter prise Firewall policy? Configure in the Inter net-to-MCG 3100 Firewall policy? RTP (UDP) VoIP send port for the Instant Conference Server. Configured on the MCG 3100. MCG 3100 Yes No RTP (UDP) VoIP send port for the VoIP Conference Media. RTP can be sent to media gateways, IP endpoints, or other SIP User Agents. The range of end point ports defines the ports to which the MCG 3100 sends media.
Engineering Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering NN42030-200 04.01 2 October 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).
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 33 — SIP Access Port license • • SIP Gateway, operating on the VxWorks Signaling Server platform SPS, using the NRS-SPS on the Linux-based NRS. — Configure each MCG 3100 as a Dynamic Gateway Endpoint with an endpoint name. Configure the Dynamic Gateway Endpoint with authentication turned off. — Each client requires the configuration of an NRS-SPS User Endpoint (UE). Clients use the UE for user name and password information, not for SIP routing.
Interworking requirements with CS 1000 Figure 7 Client with CS 1000 and UDP Figure 8 "Client with CS 1000 and CDP" (page 34) 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. Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering NN42030-200 04.01 2 October 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved. .
CS 1000 engineering for MC 3100 Table 3 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).
Interworking requirements with CS 1000 requires these settings so that calls to the Public Network display the 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 37 ZONE 100 PCID SIP ... ANTK SIGO ESN5 STYP SDAT Attention: If the Route Data Block (RDB) already has associated Virtual Trunks and is configured to SIGO STD, 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 39 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 40) "Trunk calculation: Method 2" (page 41) To calculate the number of UEXTs required, see "UEXT calculations" (page 44). 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 41 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 42) 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 43 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).
Call Detail Recording 45 Table 7 MC 3100 call features (cont’d.
Interworking requirements with CS 1000 Direct outbound call When a user makes an outgoing call, the mobile client user’s home CS 1000 generates two CDR records. • The first CDR record provides details of the call from the mobile phone to the service DN. In this record, the originator is the mobile phone number and destination is the service DN. • The second CDR record provides details of the outgoing call to the called party.
Call Detail Recording 47 username of the mobile client, and the destination is the mobile number of the mobile client user. Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering NN42030-200 04.01 2 October 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved. .
Interworking requirements with CS 1000 Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering NN42030-200 04.01 2 October 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved. .
. Index B BlackBerry Enterprise Server (BES) 11–13, 16 9, C Communication Server 1000 (CS 1000) PSTN calculations 40–41 SIP Access Ports calculations 40–41 Universal Extension (UEXT) calculations 44 Enterprise Call Server (ECS) 12, 16, 20, 29 High availability 18 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 04.01 2 October 2009 Copyright © 2007-2009 Nortel Networks. All Rights Reserved. .
Nortel Mobile Communication 3100 Nortel Mobile Communication 3100 Planning and Engineering Release: 3.1 Publication: NN42030-200 Document revision: 04.01 Document release date: 2 October 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.
