Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 .
Document status: Standard Document version: 01.02 Document date: 20 June 2007 Copyright © 2007, Nortel Networks All Rights Reserved. Sourced in Canada. The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document.
Revision history June 2007 This document has been up-issued to reflect changes in technical content for CR Q01514742. May 2007 Standard 01.01. This document is issued to support Communication Server 1000 Release 5.0. This document contains information previously contained in the following legacy document, now retired: (553-3001-314). September 2006 Standard 5.00. This document is up-issued for CR Q0143871, with an update to Procedure 23, which resulted in no remote access over IP Network to CS.
Revision history Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Contents New in this release MG 1000B hardware platform 17 Media Card MC32S 18 Main and Branch Office running different releases Main Office and Branch Office Migration 18 17 18 How to get help 19 Getting help from the Nortel web site 19 Getting help over the telephone from a Nortel Solutions Center 19 Getting help from a specialist by using an Express Routing Code 19 Getting help through a Nortel distributor or re-seller 20 Overview Contents 21 What is Branch Office? 22 Main Office and Branch Offi
Contents MG 1000B with MGC Data Networking 38 MGC Network Connections 40 MG 1000B platform configuration overview 44 MG 1000B platform without an MG 1000B Expander 45 MG 1000B platform with an MG 1000B Expander 46 Capacity 47 Media Card DSP capacity 47 Software requirements 47 Main and Branch Office running the same release 47 Main and Branch Office running different releases 48 Package Combinations 50 Supported applications 50 Survivability 50 Active Call Failover 52 Configuring S2 IP Address to point to
Contents 7 Every Branch Office HLOC is shared with the main office 96 No Branch Office HLOC is shared with the main office, but can be shared with another Branch Office 97 No Branch Office HLOC is shared with the main office or another Branch Office 98 Call between branch offices associated with different main office 99 Every Branch Office HLOC is shared with the main office 99 No Branch Office HLOC is shared with the main office or another Branch Office 102 Summary of provisioning procedures for Tandem Ban
Contents Network Class of Service 144 Network Routing Service (NRS) 145 Trunk Route Optimization (TRO) 145 Virtual Office 145 Feature packaging 145 Feature implementation using Command Line Interface 145 Task summary list 145 Sample printout 146 Feature implementation using Element Manager 147 Zone configuration 147 Diagnostics 149 Maintenance 155 Command Line Interface maintenance 155 Element Manager maintenance 155 Feature operation 158 How the Branch Office feature works Contents 159 Introduction 160
Contents 9 Planning and management 179 Contents 179 Data network planning 179 LAN/WAN bandwidth requirements 180 Branch Office dialing plan 181 Emergency Services 182 Zones 182 Music on Hold 182 ESN Access Codes 182 Provisioning the IP Phones 182 Configuration example for PSTN resources at the Branch Office 183 Management 185 Remote Access 185 Element Manager 185 Telephony Manger 3.
Contents Main office configuration 209 Contents 209 Introduction 209 Zone parameters 210 Element Manager zone configuration 213 IP Phone passwords and parameters 215 MG 1000B IP Phone configuration 218 MG 1000B IP Phone configuration using TM 3.
Contents 11 Summary of steps 255 Configuring the Media Cards 256 Configuring the trunks and lines 256 Zone parameters 256 Element Manager Branch Office zone configuration 260 Adding the Branch Office endpoints to the NRS database 260 MG 1000B telephones 263 Contents 263 Overview 263 Installing and configuring IP Phones 264 Password requirements 265 Installing an IP Phone using the keypad 265 Branch User Config 270 Transferring IP Phone data using TM 3.
Contents Emergency Services configuration 315 Contents 315 Overview 315 Emergency Services Access (ESA) 316 Routing ESA calls 316 Configuring ESA for the Branch Office 317 Element Manager ESA configuration 326 Emergency Service using Special Numbers (SPN) 327 CLID verification (CLIDVER) 328 Networked M911 328 Basic Emergency Services When VO Logged Out Contents 329 Overview 329 Configure ESA Data Block 333 Warm Start 333 Emergency Services For Client Mobility Active Call Fail Over 334 Context Sensiti
Contents 13 Appendix A Preprogrammed data Contents 361 Introduction 361 Passwords and codes 362 Default numbering plan 362 First digits 363 Important extension numbers Flexible Feature Codes 364 SDI ports 364 Modem port 365 ESDI settings 365 Telephone tones 366 Trunk routes 366 System parameters 367 Customer data 367 Trunk models 367 Telephone models 370 361 363 Appendix B Branch Office engineering example Contents 371 Introduction 371 Assumptions 372 Calculations 373 Traffic 373 MG 1000B Core and MG 10
Contents Provisioning 406 Main office 406 NRS 408 Branch Office 409 Call example 409 Main office 410 NRS 410 Branch Office 410 List of terms 411 Procedures Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure 1 2 3 4 5 6 7 8 9 10 11 Procedure 12 Procedure 13 Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedur
Contents 15 Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 Procedure 51 Procedure 52 Procedure 53 Using the Test Local Mode feature 286 Using the Set-Based Removal feature 288 Configuring the main office 299 Configuring the NRS database 306 Configuring the Branch Office 308 Testing PSTN access u
Contents Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
New in this release 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. This document describes the Branch Office feature and contains information on planning, installation, configuration, and maintenance. Information in this document complements information found in documents in the Communication Server 1000 documentation suite, as listed in Related information.
New in this release Media Card MC32S For CS 1000 Release 5.0, the new Media Card 32S (MC32S) fully replaces the functionality of the current VGMV pack NTVQ01BB. You can use the new pack in both large and small systems, and anywhere you can use the current NTVQ01BB pack. The MC32S also adds SRTP security. For an MGC-based MG 1000B, the sets are configured in four-field format. As there are new conference capabilities on the MGC, the Group Call feature available in CS 1000 Release 5.
How to get help This chapter explains how to get help for Nortel products and services. Getting help from the Nortel web site The best way to get technical support for Nortel products is from the Nortel Technical Support web site: http://www.nortel.com/support This site provides quick access to software, documentation, bulletins, and tools to address issues with Nortel products.
How to get help http://www.nortel.com/erc Getting help through a Nortel distributor or re-seller If you purchased a service contract for your Nortel product from a distributor or authorized re-seller, contact the technical support staff for that distributor or re-seller. Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Overview Contents This section contains information on the following topics: "What is Branch Office?" (page 22) "Main Office and Branch Office Migration" (page 24) "MG 1000B (MGC) compared to the MG 1000B (SSC)" (page 24) "MGC Serial Ports" (page 26) "Single CPU Implications" (page 26) "Dual CPU Implications" (page 26) "Terminal Server Support" (page 26) "MGC serial port default configuration" (page 27) "MGC serial ports configuration change in Overly 17" (page 27) Table 2 "CEMux Packs and daughter boar
Overview "MGC Network Connections" (page 40) "MG 1000B platform configuration overview" (page 44) "MG 1000B platform without an MG 1000B Expander" (page 45) "MG 1000B platform with an MG 1000B Expander" (page 46) "Capacity" (page 47) "Media Card DSP capacity" (page 47) "Software requirements" (page 47) "Main and Branch Office running the same release" (page 47) "Main and Branch Office running different releases" (page 48) "Package Combinations" (page 50) "Supported applications" (page 50) "Survivability
What is Branch Office? 23 for large systems to be supported as a Branch Office. A mixture of pre CS 1000 Release 5.0 branches are supported with CS 1000 Release 5.0 branches as long as the main office is running the latest software. The Branch Office feature does not change with the addition of large system based branches. The Branch Office feature is ported to a large system.
Overview Figure 1 Branch Office associated with a CS 1000E main office Main Office and Branch Office Migration All Main Office call servers in CS 1000 Release 5.0 are large system based. A CS 1000 Small System Main Office is no longer supported. Since all CS 1000 Release 5.0 Small System Controller (SSC) based Main Offices have been migrated to Call Processor Pentium Mobile (CP-PM) Call Servers, the Main Office TN (MOTN) Type in a Branch Office will always be set to the large system MOTN Type.
MG 1000B (MGC) compared to the MG 1000B (SSC) 25 mgcsetup command. With a properly designed data network, the multiple ELAN and TLAN interfaces can be used to implement a dual homed configuration for the MG 1000B with MGC. Four of these interfaces are accessed by using RJ45 connectors on the faceplate. Two are reserved for ELAN and two are reserved for TLAN. Two additional Ethernet connections are available if an Option 11C cabinet is used. One is reserved for ELAN and one is reserved for TLAN.
Overview tolerance, the MGC is equipped with a clock reference input/output. The clock reference input and output connections and cable detect are provided through a 15-pin DSUB connector. MGC Serial Ports Each MGC installed in a CS 1000B provides the opportunity for 3 remote SDIs. The maximum number of TTYs does not change. Therefore, after you configure the maximum TTYs , no additional TTYs are supported. The MGC has three serial ports SDI0, SDI1, and SDI2.
MGC Serial Ports 27 MGC serial port default configuration The default settings for the serial ports are • Baud rate = 9600 • Number of data bits = 8 • Number of stop bits = 1 • Parity = none • Flow control = none MGC serial ports configuration change in Overly 17 If you configure the serial ports on an MG 1000B with MGC as SL1 terminals on the Call Server, then the baud rate, number of data bits, number of stop bits, parity, and flow control are configured in LD 17.
Overview SSTD (NTAK03) not supported n/a n/a Card Option Mail not supported n/a n/a Standard Option 11C minimum vintages apply to all packs and daughter boards. Attempts to install unsupported CEMux packs or to configure an unsupported application are blocked. Support of CEMux requires CS 1000 Release 5.0 Softswitch software and a Media Gateway Controller Card (MGC). It is supported by all MG 1000B systems.
MG 1000B platform hardware description 29 The diagrams throughout this document show a CS 1000E main office. All of the systems appearing in the list perform identical main office functions as far as the Branch Office feature is concerned. MG 1000B platform hardware description The MG 1000B system has been enhanced for CS 1000 Release 5.0 Branch Office. The CP-PM Call Server and MGC replace the SSC (Motorola) used in the Release 4.0/4.5 MG 1000B.
Overview Figure 2 CS 1000 Release 5.0 MG 1000B System CS 1000 Release 5.0 continues to support the existing Branch Office configuration that uses the SSC processor, but Nortel no longer offers sales of the SSC based Branch Office. CS 1000 Release 5.0 provides various hardware versions of the Signaling Server, the existing ISP1100 signaling servers, or the new CP-PM Signaling Server. With CS 1000 Release 5.
MG 1000B platform hardware description 31 MG 1000B Core, and the optional chassis expander performs the same functionality as the MG 1000B Expander. Refer to "Converting a Small System to a Branch Office" (page 201) for more information. After conversion to an MG 1000B platform, the Small System cabinet or chassis is referred to as an "MG 1000B Cabinet" or "MG 1000B Chassis", as applicable. The optional chassis expander is referred to as the "MG 1000B Chassis Expander".
Overview Figure 3 MG 1000B Core/MG 1000B Expander MG 1000B Chassis CEMux packs are supported in card positions 1 to 4 of an MG 1000B chassis. They are not supported in the MG 1000B expander chassis, similar to what is the support in the Option 11C SIPE system. Card slots Table 3 "Card slots for MG 1000B Core and MG 1000B Expander" (page 32) shows the card slot assignments for all configurations of the MG 1000B Core and MG 1000B Expander (discussed on "MG 1000B Expander" (page 33)).
MG 1000B platform hardware description slots 33 MGC DLC slot #s slot s slot #s MG 1000B Core 5 0 Not used 1-4 4 7-10 MG 1000B Cabinet 11 0 Not used 1-10 (see Note 1) N/A N/A MG 1000B Chassis 5 0 4 (see Note 2) 1-3 4 7-10 (see Note 1) For converted Small Systems only, the Meridian Mail card must be installed in slot 10 if Meridian Mail is to be supported. If the 48-port Digital Line Card (DLC) is not used, slot 4 must remain unused.
Overview • The MG 1000B Expander is connected to the MG 1000B Core with copper wire. Therefore, the back of the MG 1000B Expander does not have an Ethernet port. Figure 3 "MG 1000B Core/MG 1000B Expander" (page 32) shows the MG 1000B Expander. Table 3 "Card slots for MG 1000B Core and MG 1000B Expander" (page 32) gives the card slots for the MG 1000B Expander. Signaling Server The Signaling Server is required for the Branch Office feature.
MG 1000B platform hardware description 35 For more information on the Signaling Server, refer to Signaling Server Installation and Commissioning (NN43001-312). For more information on SIP, H.323, and overlap signaling, refer to IP Peer Networking Installation and Commissioning (NN43001-313) . The NCS is required to provide the Main Office Node IP’s actual status. The redirection procedure cannot be performed without the NCS. Interaction with the NCS Branch Office requires the same H.
Overview When configuring the NRS it is necessary to enable the NCS. Ensure the check box "Network Connection Server enabled" is checked in the NRS configuration window of CS 1000 Element Manager. For information on configuring the NRS, refer to IP Peer Networking Installation and Commissioning (NN43001-313) .
MG 1000B platform hardware description IP Audio Conference Phone 2033 i2001 2033 IP Softphone 2050 i2050 2050PC Mobile Voice Client 2050 i2050 2050MC WLAN Handset 2210 i2004 2210 WLAN Handset 2211 i2004 2211 WLAN Handset 2212 i2004 2212 IP Phone 1110 i2001 1110 IP Phone 2007 i2004 2007 IP Phone 1120E i2004 1120 IP Phone 1140E i2004 1140 IP Phone 1150E iPACD 1150 37 Throughout this document, the telephones in this list are referred to collectively as "IP Phones.
Overview (500/2500-type) or digital telephone or the PSTN uses one DSP port. Calls between two IP Phones do not require any DSP ports, as there is no need for IP-to-circuit-switched transcoding. Media Cards provide echo cancellation, compression, and decompression of voice streams.For more information about DSP resources residing on the MGC that are configured with DSP Daughterboards, see the CS 1000E Installation and Configuration NTP.
MG 1000B with MGC Data Networking 39 You can connect the MGC to a Layer 2 switch to handle signaling between the Call Server and the MG 1000Bs. If two of the MGC ELAN ports connect to separate Layer 2 switches, the MG 1000B can remain operational if one of the Layer 2 switches fails. MG 1000B shelves must have a data network connectivity to the ELAN port of the Call Server. The design of the data networking configuration is outside the scope of this document.
Overview MGC Network Connections In the following diagrams, two connections are shown to the external data equipment for the dual-homing feature, distributed and nondistributed. Nondistributed means that both Ethernet ports (TLAN or ELAN) of the dual-homing feature connect to a single Layer 2 switch, thus providing a single point of failure if that switch goes out of service.
MG 1000B with MGC Data Networking 41 The following figure illustrates a typical network configuration that supports dual homing of both the ELAN and TLAN. With this configuration, however, a single Layer 2 switch remains a single point of failure. Figure 6 Single server port network connections (dual-homing - non distributed) The following figure illustrates a typical network configuration that supports dual homing of both the ELAN and TLAN.
Overview Figure 7 Single server port network connections (dual-homing - distributed) The following figure illustrates a typical network configuration for a dual CPU Call Server configuration that supports dual homing of both the ELAN and TLAN. Multiple Layer 2 switches ensure there isn’t a single point of failure. Nortel recommends this configuration in a dual CPU Call Server configuration.
MG 1000B with MGC Data Networking 43 Figure 8 Multi server port network configuration (dual-homing - distributed) Cascading can occur for the MGC network connections for up to a maximum of 2 cabinets. You can directly cable the MGCs , without the need for external Layer 2 switches. Nortel recommends this type of configuration for a pure TDM solution. Figure 9 Single server port network connections - cascading Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.
Overview Multi Server (CP-P4) Port Network Configuration (Dual-homing Distributed), shows a configuration with a Call Server platform that does not reside in a MG 1000B cabinet and chassis; therefore no direct connection exists to the MGC.
MG 1000B platform configuration overview 45 MG 1000B platform without an MG 1000B Expander Figure 11 "MG 1000B platform without MG 1000B Expander" (page 45) shows an MG 1000B platform configured without an MG 1000B Expander. This configuration has a single MG 1000B Core. Figure 11 MG 1000B platform without MG 1000B Expander This MG 1000B platform configuration requires at least one Voice Gateway Media Card.
Overview For more information on the Voice Gateway Media Card configuration, refer to IP Line Fundamentals (NN43100-500). For more information on Integrated Conference Bridge, refer to Integrated Conference Bridge Service Implementation Guide (NN43001-558). MG 1000B platform with an MG 1000B Expander Figure 12 "MG 1000B platform with MG 1000B Expander" (page 46) shows an MG 1000B platform configured with an MG 1000B Expander. With the addition of an MG 1000B Expander, you have additional usable slots.
Software requirements 47 Capacity Each CS 1000 main office can support up to 255 branch offices. Each Branch Office supports up to 400 IP Phone users. However, since all IP Phones register with the main office, the governing factor is the maximum number of IP Phones that can be supported at the main office.
Overview Main and Branch Office running different releases The Main Office Call Server and the Branch Office can have different software releases, as long as the Main Office runs at the highest release. With the introduction of CS 1000 Release 5.0 program, Nortel’s policy will be if the main office Call Server is running CS 1000 Release 5.0, the Branch Office can run on CS 1000 Release 5.0, CS 1000 Release 4.5, or CS 1000 Release 4.0. Some functionality found in CS 1000 Release 5.
Software requirements 49 Features in mixed-software configurations Feature operation of IP Phone users in Normal Mode is the feature set on the main office. IP Phone users in Local Mode use the feature set on the Branch Office. Users of analog and digital devices always use the feature set on the Branch Office.
Overview Refer to "Firmware downloads" (page 345) for more information on upgrading firmware for the IP Phone 2001, IP Phone 2002, IP Phone 2004, and IP Phone 2007. Package Combinations The MG 1000B with MGC requires existing packages 402 SOFTSWITCH and 403 IPMG that were introduced in Rls 4.0. Package combinations supported using the Rls 4.5 MG 1000B are supported by the MG 1000B with MGC. For MG 1000B with MGCs, the Branch Office package 390 and IPMG package 403 are required.
Survivability 51 If the main office Call Server fails and call processing services are provided by an alternate Call Server, the MG 1000B IP Phones register with the alternate Call Server and receive call processing services from it. If no alternate Call Server is available, the MG 1000B IP Phones stay registered with the main office TPS for ten minutes. At the end of the ten minutes, the IP Phones reset and register with the call server.
Overview Local Mode at the Branch Office, the MG 1000B telephones remain in Local Mode, displaying aServer Unreachable (1) message and receives all call processing services from the CP PM in the MG 1000B Core. MG 1000B IP Phones in Normal Mode remain registered with the main office when the Primary NRS fails and no Alternate or Failsafe NRS is available. They can call any main office telephone or IP Phones in Normal Mode in other branch offices.
Survivability 53 ACF mode The ACF feature for IP Phones enables an IP Phone to reregister in the ACF mode during a supported system failure. The ACF mode preserves the following: • active media session • LED states of the Mute, Handsfree, and Headset keys • DRAM content All other elements (the feature keys, soft keys and text areas) are retained until the user presses a key or the connection with the Call Server is resumed.
Overview For further information on this configuration and its limitations, see "Configuring non-zero S2 IP Addresses" (page 169). Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Bandwidth Management Contents This section contains information on the following topics: "Introduction" (page 55) "Codec negotiation" (page 56) "Codec selection" (page 59) "Codec selection algorithms" (page 59) "Configuring Bandwidth Management parameters" (page 62) "Zones" (page 62) "Configuration rules" (page 62) "Network Planning" (page 62) "Enabling codecs" (page 63) "Configuring Bandwidth Management" (page 64) "Maintenance commands" (page 67) "Adaptive Network Bandwidth Management" (page 70) "Descr
Bandwidth Management With the Network Bandwidth Management feature, you can configure bandwidth zones on a network basis so that codec selection and bandwidth allocation software can identify whether Internet Telephones or gateways are physically co-located (in the same bandwidth zone) even though they are controlled by different Call Servers.
Codec negotiation 57 Nortel recommends configuring the same payload size for all codecs in the same node. SIP example If a G.711 20ms codec and G.729 30ms codec are configured, then codec negotiation uses the minimum payload size of 20 ms. That is, the G.711 20ms codec and the G.729 20ms codec are used. Instead, Nortel recommends that both G.711 and G.729 codecs be configured as 20ms. When a G.729 30ms codec is configured, then the G.729 10ms/20ms/30ms codecs are supported.
Bandwidth Management G.711 A-law and mu-law interworking In case the far end uses a different Pulse Code Modulation (PCM) encoding law for its G.711 codec, systems that are configured as G.711 A-law also include G.711 mu-law on their codec preferences list. Systems configured as G.711 mu-law include G.711 A-law as their last choice. Therefore, encoding law conversion is performed between systems with different laws.
Codec negotiation 59 Codec selection For every Virtual Trunk call, a codec must be selected before the media path can be opened. When a call is set up or modified (that is, media redirection), one of two processes occurs: • The terminating node selects a common codec and sends the selected codec to the originating node. • The codec selection occurs on both nodes. Each node has two codec lists: its own list and the far end’s list.
Bandwidth Management Algorithm details following manner: The H.323 Master/Slave algorithm operates in the • The Master node uses its own codec list as the preferred one and finds a common codec in the far end’s list. In other words, the Master gets the first codec in its list (for example, C1), checks in the far end’s list if it is a common codec; if it is, C1 is the selected codec. Otherwise, it gets the second codec in its list and verifies it against the far end, and so on.
Codec negotiation 61 This is the preferred method of operation. • The calling user agent sends an SDP offer with its codec list in the INVITE message with a "sendrecv" attribute. The called user agent returns more than one codec in the SDP answer. In the case that many codecs are included in the response, the calling user agent picks the first compatible codec from the called user agent’s list, and sends a new SDP offer with a single codec to lock it in.
Bandwidth Management Configuring Bandwidth Management parameters The following sections describe how to configure Bandwidth Management in a CS 1000 network. Nortel recommends that you read the Bandwidth Management section in Converging the Data Network with VoIP (NN43001-260) before using the following configuration information. Zones Bandwidth Management Zones are configured for each endpoint on a Call Server.
Configuring Bandwidth Management parameters 63 3 Choose unique Bandwidth Zone numbers for the Virtual Trunks in the network. 4 Choose the codecs that will be enabled on each Call Server. 5 Identify what the interzone codec strategy will be (BB-Best Bandwidth or BQ-Best Quality) for each zone in the network. 6 Identify what the intrazone codec strategy will be (BB-Best Bandwidth or BQ-Best Quality) for each zone in the network.
Bandwidth Management Figure 13 Configuring a codec Configuring Bandwidth Management The steps to configure Bandwidth Management on the Call Server are as follows: Step Action 1 Define a VPNI number in LD 15.
Configuring Bandwidth Management parameters 65 — Interzone Bandwidth = maximum bandwidth usage allowed between peer Call Servers • Call Server zones that will be used for Virtual Trunks with the following properties: — Intrazone Preferred Strategy = Best Quality (BQ) — Intrazone Bandwidth = default (1000000) — Interzone Preferred Strategy = Best Bandwidth (BQ) — Interzone Bandwidth = default (1000000) 3 Configure the IP Phone, DSP and Virtual Trunk data with the corresponding zone numbers.
Bandwidth Management Figure 14 Zones web page Configuration using LD 117 A new Bandwidth Management zone is configured in LD 117 using the NEW ZONE command. An existing zone can be modified using the CHG ZONE command. LD 117 Configure a new or existing Bandwidth Management zone.
Configuring Bandwidth Management parameters 67 Description Command • interZoneStrategy = BB (Best Bandwidth) or BQ (Best Quality); Nortel recommends this value be set to BB to conserve interzone bandwidth.
Bandwidth Management Figure 15 Maintenance Commands for Zones web page 3 Do one of the following: • To display intrazone statistics: 1. Select Print Interzone Statistics (PRT INTERZONE) from the Action drop-down list. 2. Select a zone from the Zone Number drop-down list, by doing of the following: • • Select ALL to print statistics for all zones. • Select a specific zone number to display statistics for a specific zone. To display interzone statistics: 1.
Configuring Bandwidth Management parameters 69 The Maintenance Commands for Zones web page reopens, displaying the statistics for the specified zone or zones. A blank field indicates that statistic is either not available or not applicable to that zone. Figure 16 "Element Manager - intrazone statistics" (page 69) shows an example of intrazone statistics for a sample Zone 2.
Bandwidth Management Description Command Print intrazone statistics for the identified zones, where: • zone = ALL or 0-255 The output of this command displays the following information: • Zone • Type = PRIVATE/SHARED • Strategy = BB/BQ • ZoneIntent = MO/BMG/VTRK • Bandwidth = number of Kbps • Usage = number of Kbps • Peak = % PRT INTERZONE [] [] [] [] Print interzone statistics for the specific VPNI zone; where: • nearZone = ALL or 0-255 The outp
Adaptive Network Bandwidth Management 71 to another Call Server, the available bandwidth is reduced automatically between those two zones. When the QoS between the two zones improves, then the bandwidth limit is allowed to return to normal. When an IP Phone encounters degradation of the network, it informs the Call Server through various QoS alarms. These QoS alarms (packet loss, jitter, delay, and, for phase 2 IP Phones, R value) get reported to the Call Server.
Bandwidth Management Call scenario A call is requested from a telephone in VPNI 1/Zone 2 on Call Server A to a telephone in VPNI 3/Zone 3 on Call Server B. Both zones have Adaptive Network Bandwidth Management enabled. 1. Call Server A contacts the Network Redirect Server to obtain the address of Call Server B. 2. Call Server A sends a call setup message to Call Server B, identifying the calling telephone’s VPNI and zone. 3.
Adaptive Network Bandwidth Management 73 Figure 17 Call Progress with Adaptive Network Bandwidth Management Zone bandwidth management and Adaptive Network Bandwidth Management Using Element Manager or the Command Line Interface (CLI), previously configured zones (except Zone 0) can have the Adaptive Network Bandwidth Management feature turned on or off. Once turned on, alarm threshold levels and the QoS coefficients can be adjusted from the default values.
Bandwidth Management When a call is made from a zone with Adaptive Network Bandwidth Management enabled, to a third party gateway, which has no zone, then the zone of the Virtual Trunk (VTRK) is used and appears in the zone table. Figure 18 "Adaptive Network Bandwidth Management graph" (page 74) shows an example of the bandwidth changes. Figure 18 Adaptive Network Bandwidth Management graph When a Call Server receives a QoS alarm, the two zones that originated the alarm are determined.
Adaptive Network Bandwidth Management 75 Multiple Appearance Directory Numbers (MADN) can exist on different zones. Calls to an MADN are handled the same as other IP Phone calls, and are subject to the same bandwidth limitations. New SNMP alarms are provided to monitor the system. When the bandwidth limit between zones is reduced below configured levels, an alarm is raised. A Warning alarm and an Unacceptable alarm, each corresponding to a drop below a configured threshold, are used.
Bandwidth Management Figure 20 Effect of a higher CQoS Coefficient Other configurable coefficients used in the calculation are the QoS Coefficient (CQoS), QoS Response Time Increase (ZQRT), and QoS Response Time Interval (ZQRTI). CQoS, Cr, Cd, Cpl, and Cj control the rate of bandwidth decrease, while ZQRT and ZQRTI control the rate of bandwidth increase.
Adaptive Network Bandwidth Management 77 Configuration rules The configuration rules for Adaptive Network Bandwidth Management are as follows: • Each main office Call Server in a network must have a unique non-zero VPNI. • All branch offices(MG1000B or SRG) associated with a particular main office must have the same VPNI as the main office Call Server. • All IP Phones (other than specific IP SoftPhone 2050s) and DSP endpoints on a Call Server must be configured for the same zone.
Bandwidth Management 4. Tandem the inbound Branch Office calls by creating a dialing plan which routes all calls destined for the Branch Office through the main office. Advanced Configuration Notes 1. The default values for Cpl, Cj, Cd, Cr and CQos can be increased to increase the response time for Sliding Maximum changes. However, increasing them can cause the Sliding Maximum to temporarily decrease to a lower value then necessary, resulting in the needless blocking of interzone calls. 2.
Adaptive Network Bandwidth Management 79 Figure 21 Adaptive Network Bandwidth Management and CAC web page If the Adaptive Network Bandwidth Management feature is enabled using the Enable Call Admission Control feature (ZCAC) check box, then the other parameters can be adjusted as required. Table 6 "Adaptive Network Bandwidth Management and CAC fields" (page 79) shows the fields in the Adaptive Network Bandwidth Management and CAC web page, the field definitions, and their LD 117 command equivalent.
Bandwidth Management LD 117 equivalents Field Title Field Definition QoS Response Time Increase (ZQRT) Bandwidth limit increment, as a percentage of the QoS factor for the zone CHG ZQRT QoS Response Time Interval (ZQRTI) Time (in minutes) between bandwidth limit increments CHG ZQRTI Warning Alarm Threshold (ZQWAT) A QoS value, which is lower than this value, but higher than the Critical (Unacceptable) Alarm Threshold, triggers a Major Alarm.
Adaptive Network Bandwidth Management Command 81 Description Change the Cd coefficient in the formula that determines how quickly an alarm reduces the Sliding Maximum bandwidth for the identified zone, where: • Zone = 1-255 • Cd = Cd coefficient = 1-(50)-100 CHG CPL Change the Cpl coefficient in the formula that determines how quickly an alarm reduces the Sliding Maximum bandwidth for the identified zone, where: • Zone = 1-255 • Cpl = Cpl coefficient = 1-(50)-100 CHG CJ
Bandwidth Management Command Description Change the parameters of an existing zone, where: • zoneNumber = 1-255 • intraZoneBandwidth = 1000000 (Mbit/s) • intraZoneStrategy = intrazone preferred strategy — Best Quality = BQ — Best Bandwidth = BB • interZoneBandwidth = 1000000 (Mbit/s) • interZoneStrategy = intrazone preferred strategy — Best Quality = BQ — Best Bandwidth = BB • zoneIntent = type of zone, where: — MO = Main office zone — BMG = Branch Media Gateway (Branch Office) zone — VTRK
Adaptive Network Bandwidth Management Command 83 Description Change the QoS Response Time Interval while alarms are not coming, to increase the Sliding Maximum for the identified zone, where: • Zone = 1-255 • Interval = interval in minutes = 1-(5)-120 CHG ZQUAT Change the QoS Unacceptable Alarm Threshold value for the identified zone, where: • Zone = 1-255 • Thres = threshold value = 1-(75)-99 When the zone-to-zone QoS value drops below the threshold value, the alarm is presented
Bandwidth Management Description Command — BMG = Branch Media Gateway (Branch Office) zone — VTRK = Virtual Trunk zone • zoneResourceType = resource intrazone preferred strategy — shared DSP channels (default) = shared — private DSP channels = private DIS ZCAC Disables the Call Admission Control (CAC) feature for the specified zone, where: • Zone = 1-255 Disables the feature on a zone-by-zone basis.
Adaptive Network Bandwidth Management 85 Procedure 2 Displaying CAC parameters for one or more zones Step Action 1 Select IP Network > Zones from the navigator. The Zones web page opens (see Figure 14 "Zones web page" (page 66)). 2 Click Maintenance Commands for Zones (LD 117). The Maintenance Commands for Zones web page opens, as shown in Figure 15 "Maintenance Commands for Zones web page" (page 68). This page lists all the configured zones and their intrazone statistics by default.
Bandwidth Management Figure 22 Element Manager - CAC parameters Maintenance using LD 117 The same information can be displayed using commands in LD 117.
Adaptive Network Bandwidth Management Command Description Print intrazone statistics for the identified zones, where: • zone = ALL or 1-255 The output of this command displays the following information: • Zone • State = ENL/DIS • Type = PRIVATE/SHARED • Strategy = BB/BQ • MO/VTRK/BMG = zoneIntent • Bandwidth = Kbps • Usage = Kbps • Peak = % Figure 23 "Sample output for PRT INTRAZONE command" (page 89) shows an example of the output for this command.
Bandwidth Management Command Description • Strategy = BB/BQ • MO/VTRK /BMG= zoneIntent • QoS factor = % • Bandwidth configured = Kbps • Sliding max = Kbps • Usage = Kbps • Peak = % • Call = Cph • Alarm = Aph The report rows are grouped as: • First row = summary bandwidth usage per near zone • Next rows = bandwidth usage per near (VPNI- Zone) and far (VPNI - Zone) Figure 24 "Sample output for PRT INTERZONE command" (page 90) shows an example of the output for this command.
Adaptive Network Bandwidth Management Command 89 Description • ZQRTI = 10-120 • ZQUAT = 1-99 • ZQWAT =1-99 • CACVT = 1-255 Sample outputs for PRT commands Figure 23 "Sample output for PRT INTRAZONE command" (page 89) shows an example of the output of the PRT INTRAZONE command. Figure 24 "Sample output for PRT INTERZONE command" (page 90) shows an example of the output of the PRT INTERZONE command.
Bandwidth Management Figure 24 Sample output for PRT INTERZONE command Tandem Bandwidth Management overview In order for the main office to correctly keep track of all the bandwidth being used to and from a Branch Office the call must be tandemed through the main office. When calls are tandemed through the main office only the signaling is tandemed, the actual voice bandwidth travels directly between the source and destination.
Dialing Plan Overview 91 Bandwidth utilization for the Branch Office is tracked at the main office and can be displayed in LD 117 using the PRT INTERZONE command. To provide the correct bandwidth utilization to the main office Call Server, when a Branch Office is calling another node in the network, the calls must be tandemed through the main office Call Server in both the inbound and outbound direction.
Bandwidth Management Figure 25 A call between two branch offices tandems through the main office Figure 26 "General legend" (page 93) on Figure 26 "General legend" (page 93) shows a general legend for the figures in the following section. Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Network using Uniform Dialing Plan 93 Figure 26 General legend Network using Uniform Dialing Plan The following section provides general network configuration for a network using UDP only. Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Bandwidth Management Figure 27 "Scenario 1: UDP throughout the network" (page 94) shows two or more main offices with their branch offices, within a larger network. Callers within each main office/Branch Office "region" use UDP to place calls between systems. Callers also use UDP to place calls across the IP network to the other main office(s) and its (their) branch offices. In a typical network, a full region uses a single Home Location Code (HLOC).
Network using Uniform Dialing Plan 95 Table 7 "Configuration details for the general case" (page 95) describes the network configuration and the steps that a call takes during its setup. Table 7 Configuration details for the general case Call progress steps Region Configuration detail and call progress during call setup 1, 2, 3 UDP used for all calls within the region. 1, 2, 3 UDP used for region to region calls.
Bandwidth Management Region Provisioning detail 1 The DMI for the Branch Office "LOC" inserts a gateway routing prefix in front of the number. 2,3 Similar configuration, as above, applies to regions 2 and 3. Call between two branch offices associated with the same main office The following scenarios describe calls between two branch offices that belong to the same main office.
Network using Uniform Dialing Plan 97 2. The Branch Office sends the call to 395-3456 to the main office. 3. The main office determines that this is LOC 39534, to another Branch Office, with gateway routing prefix 552. The system inserts the prefix and transmits 552-395-3456 to the NRS. The NRS checks its provisioning, and determines that all calls to prefix 552 are to be sent to Branch Office A2; it directs the call to the Branch Office. 4.
Bandwidth Management 3. The main office determines that this is LOC 39534 to another Branch Office, with gateway routing prefix 552. The system inserts the prefix and transmits 552-395-3456 to the NRS. The NRS checks its provisioning, and determines that all calls to prefix 552 are to be sent to Branch Office A2; it directs the call to the Branch Office. 4. The main office sends the call to 552-395-3456 to the Branch Office. The Branch Office deletes the prefix and the HLOC and rings set 3456.
Network using Uniform Dialing Plan 99 determines that all calls to prefix 552 are to be sent to Branch Office A2; it directs the call to the Branch Office. 4. The main office sends the call to 552-399-3456 to the Branch Office. The Branch Office deletes the prefix and the HLOC, and rings set 3456. Call between branch offices associated with different main office The following scenarios describe calls between two branch offices that belong to different main offices.
Bandwidth Management that all calls are to be sent to the main office; it directs the call to the main office. 2. The Branch Office sends the call to 444-3456 to the main office. 3. The main office determines that this is to another main office. The system transmits 444-3456 to the NRS. The NRS checks its provisioning, and determines that this call goes to main office B. Figure 32 Call flow for Scenario 1 - call to remote Branch Office (destination side) 1.
Network using Uniform Dialing Plan 101 Figure 33 Call flow for Scenario 1 - call to remote Branch Office (originator side) 1. The Branch Office user dials 6-444-3456. The system transmits 444-3456 to the NRS. The NRS checks its provisioning, and determines that all calls are to be sent to the main office; it directs the call to the main office. 2. The Branch Office sends the call to 444-3456 to the main office. 3. The main office determines that this is to another main office.
Bandwidth Management Figure 34 Call flow for Scenario 1 - call to remote Branch Office (destination side) 1. Main office B determines that this LOC plus digits is to a local Branch Office with prefix 225. (If sharing this LOC with another Branch Office, the extended LOC is 44434.) The system transmits 225-444-3456 to the NRS. The NRS checks its provisioning, and determines that this call goes to Branch Office B1. 2. The main office sends the call to 225-444-3456 to the Branch Office.
Network using Uniform Dialing Plan 103 Figure 35 Call flow for Scenario 1 - call to remote Branch Office (originator side) 1. The Branch Office user dials 6-444-3456. The system transmits 444-3456 to the NRS. The NRS checks its provisioning, and determines that all calls are to be sent to the main office; it directs the call to the main office. 2. The Branch Office sends the call to 444-3456 to the main office. 3. The main office determines that this is to another main office.
Bandwidth Management Figure 36 Call flow for Scenario 1 - call to remote Branch Office (destination side) 1. Main office B determines that LOC 444 is to a local Branch Office with prefix 225. The system transmits 225-444-3456 to the NRS. The NRS checks its provisioning, and determines that this call goes to Branch Office B1. 2. The main office sends the call to 225-444-3456 to the Branch Office.
Network using Uniform Dialing Plan 105 which provides service for the Branch Office using the LOC. See step 3. 4 Provision the NRS to send all calls to a LOC with a gateway routing prefix to the Branch Office directly. Using the gateway routing prefix and the Type of Number of SPN, the entries can be differentiated from the normal LOCs easily. See step 4. 5 Provision the main office with the DGT table DMIs to insert the prefixes and set the Type of Number correctly.
Bandwidth Management Figure 37 Provisioning example Procedure 3 Provisioning Tandem Bandwidth Management Step Action 1 Enter the main office Gateway endpoint identifier in the Tandem Endpoint field for each Branch Office GW configured on the NRS.This provides tandeming for outbound calls from a Branch Office through its main office. Figure 38 "Tandem endpoint configuration in Element Manager" (page 107) shows the tandem endpoint configuration in Element Manager.
Network using Uniform Dialing Plan 107 Figure 38 Tandem endpoint configuration in Element Manager 2 Plan the gateway routing prefixes. At least one prefix is needed per Branch Office, although any branch offices that have a prefix for ESA "911" calls does not necessarily require another. (These prefixes will be SPN - Special Number - entries if you are using ESA 911. In the example these are LOC codes because network 911 is not being used.
Bandwidth Management Table 9 "Main office B DMI and RLI provisioning (for calls in Branch Office B)" (page 108) lists main office B DMI and RLI provisioning.
Network using Uniform Dialing Plan 109 7 Provision the main office and Branch Office with a home location code (HLOC) or multiple codes to terminate all calls that should terminate on this system. Table 11 "Main office and Branch Office HLOC provisioning - Main office B and Branch Office B" (page 109) lists main office and Branch Office HLOC provisioning.
Bandwidth Management Create an RLI Create a LOC ROUT 71 FLEN 7 RLI 51 Table 13 "Main office A LOC provisioning for LOC to remote main office systems - main office B is LOC 841" (page 110) lists main office A LOC provisioning for LOC to the remote office.
Network using Uniform Dialing Plan 111 Network using mixed Coordinated Dialing Plan and Uniform Dialing Plan The following section provides general details of the network setup. Figure 39 "Scenario 2 - UDP between main offices, CDP inside the main office region" (page 111) shows an example of a mixed network configuration.
Bandwidth Management Region Provisioning detail 1, 2, 3 Prefixes for branch offices for regular calls not required. May still have prefixes for E-911 calls, if required. 1 All branch offices are provisioned at the NRS to route all calls through the main office. 1 Main office sends all UDP calls to destinations that are not its own Branch Office to the NRS with unchanged dialled digits.
Network using Uniform Dialing Plan 113 4. The main office sends the call to 3456 to the Branch Office. The Branch Office rings set 3456. Abnormal case - calls originating using UDP, but terminating using CDP Figure 41 Call flow for Scenario 2 - local call dial UDP 1. The Branch Office user dials 6-395-3456. The system transmits 395-3456 to the NRS. The NRS checks its provisioning, and determines that all calls are to be sent to the main office; it directs the call to the main office. 2.
Bandwidth Management Figure 42 Call flow for Scenario 2 - local call to remote Branch Office (originator side) 1. The Branch Office user dials 6-444-3456. The system transmits 444-3456 to the NRS. The NRS checks its provisioning, and determines that all calls are to be sent to the main office; it directs the call to the main office. 2. The Branch Office sends the call to 444-3456 to the main office.The main office determines that this is to another main office. The system transmits 444-3456 to the NRS.
Network using CDP only 115 Figure 43 Call flow for Scenario 2 - call to remote Branch Office (destination side) 1. The main office B deletes the HLOC, and determines that this is to a local Branch Office. The system transmits 3456 to the NRS. The NRS checks its provisioning, and determines that for this CDP region this call goes to Branch Office B1. 2. The main office sends the call to 3456 to the Branch Office. The Branch Office rings set 3456.
Bandwidth Management Figure 44 Scenario 3 - full CDP network Table 16 "Provisioning details for this case" (page 116) lists the provisioning details for a full CDP network. Table 16 Provisioning details for this case Region Provisioning detail 1, 2, 3 CDP used for all calls within the region. 1, 2, 3 CDP used for region to region calls. 1, 2, 3 All CDP numbers must be sufficiently long to allow unique termination of the calls.
Network using CDP only 117 Region Provisioning detail 1 All branch offices are provisioned at the NRS to route all calls through the main office. 1 Main office sends all CDP calls to destinations that are not its own Branch Office to the NRS with unchanged dialled digits. 1 Main office sends all CDP calls to destinations that are its own Branch Office to the NRS with a specific gateway prefix in front of the dialled digits. 1 All branch offices delete the prefix and terminate the calls.
Bandwidth Management to the NRS. The NRS checks its provisioning, and determines that all calls to prefix 552 are to be sent to Branch Office A2; it directs the call to the Branch Office. 4. The main office sends the call to 552-43456 to the Branch Office. The Branch Office deletes the prefix and LSC "4", and rings set 3456.
Network using CDP only 119 Figure 47 Call flow for Scenario 3- calls to remote Branch Office (destination side) 1. Main office B determines that this is to a local Branch Office with prefix 225. The system transmits 225-53456 to the NRS. The NRS checks its provisioning, and determines that this call goes to Branch Office B1. 2. The main office sends the call to 225-53456 to the Branch Office. The Branch Office deletes the prefix and LSC, and rings set 3456.
Bandwidth Management Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Bandwidth Management Support for Network Wide Virtual Office Contents This section contains information on the following topics: • Section "Feature description" (page 121) • Section "Feature interactions" (page 122) • Section "Feature packaging" (page 123) • Section "Feature implementation" (page 123) • Section "Feature operation" (page 125) Feature description Bandwidth Management Support for Network Wide Virtual Office (NWVO) allows the assignment of the same Virtual Private Network Identif
Bandwidth Management Support for Network Wide Virtual Office The customer can check the value of the Current Zone for IP sets using LD 20, PRT command - as this value is not configurable, no changes are made to LD 11.
Feature implementation 123 Interaction with Zone-based Digit Manipulation A new prompt is added to the Customer Data Block (CDB) to configure the zone (Current or Configured) to be used for Zone-based Digit Manipulation feature. It allows VO users to use either local PSTN connections of the CS were they are physically located (Current Zone), or remote PSTN connections of the CS were their VO TNs are configured (Configured Zone) depending on customers’ preferences.
Bandwidth Management Support for Network Wide Virtual Office Prompt Response Description TYPE: NET_DATA Networking. -VPNI 1-16283 Virtual private network identifier. LD 117 Define Zone Data Command Description NEW ZONE [ ] Define a new Zone with parameters. All parameters must be entered: - zoneNumber from 0 to 255. - intraZoneBandwidth from 0 to 0.1Mbps.
Feature operation 125 Prompt Response Description ZONE Zone Number which Nortel Networks IP Phone set belongs. CLS VOLA Allow/deny Virtual Office operation from this TN. VOUA Allow/deny Virtual Office login onto this TN using other phone (destination of Virtual Office login). LD 15 - Choose zone (Current or Configured) to be used for zone-based digit manipulation feature. Prompt Response Description REQ CHG Change existing data block. TYPE: FTR_DATA Features and options.
Bandwidth Management Support for Network Wide Virtual Office Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Alternative Call Routing for Network Bandwidth Management Contents This section contains information on the following topics: "Description" (page 127) "Operating parameters" (page 143) "Feature interactions" (page 144) "Feature packaging" (page 145) "Feature implementation using Command Line Interface" (page 145) "Feature implementation using Element Manager" (page 147) "Diagnostics" (page 149) "Maintenance" (page 155) "Feature operation" (page 158) Description Alternative Call Routing for Network Ban
Alternative Call Routing for Network Bandwidth Management Figure 48 "Example of Alternative Call Routing for NBWM in operation" (page 128) shows a diagram of a typical network where Alternative Call Routing for NBWM can be used. It illustrates the sequence of events that are explained in the information following the diagram. Event number 1 pertains to the originally dialed call that experiences low bandwidth or unacceptable QoS conditions. Event number 2 pertains to the alternately routed call.
Description • 129 Branch Office calls to or from another Branch Office controlled by the same main office The term "Branch Office" refers to Media Gateway 1000B (MG1000B) and Survivable Remote Gateway (SRG) systems in this document. This feature enables alternate routing to occur for Branch Office users registered to the main office, when they place inter-zone, station-to-station calls to main office stations or Branch Office stations.
Alternative Call Routing for Network Bandwidth Management The ALTPrefix applies to the zone in which the call originates. There is one ALTPrefix for each zone that requires alternate routing. All Call Servers must be able to translate the ALTPrefixes for all zones that require Alternative Call Routing for NBWM.
Description 131 5. The call is routed over the PSTN/MCDN to the telephone at the Branch Office. With the ALTPrefix digits inserted, the resulting number must be one that CDP or VNR software can process as a steering code. For SRGs, the main office manipulates the digits in the call into a format appropriate for routing from the SRG on PSTN/MCDN trunks. For more information on SRG, refer to Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide (NN43001-307).
Alternative Call Routing for Network Bandwidth Management Calls preceded by the ALTPrefix can be handled by the Vacant Number Routing (VNR) feature. Use Flexible Numbering Plan (FNP) software for this type of routing. Examples of Alternative Call Routing for NBWM in operation The main office systems shown in the diagrams in this chapter are CS 1000E systems. However, this feature is supported on any CS 1000 system.
Description Configuration required 133 Configure the following: At the main office: • Use one of the dialing plan software packages to process the call, such as CDP or NARS. • Provision an ALTPrefix for the BO2 zone. • Provision the ALTPrefix as a Steering Code at the main office. Build a Route List Index (RLI) so these calls go to the virtual trunk or configure the Vacant Number Routing feature to do the same. At the Branch Office: • Provision the ALTPrefix as a steering code.
Alternative Call Routing for Network Bandwidth Management Figure 50 Illustration showing digits dialed and outpulsed with Alternative Call Routing for NBWM 1. IP Phone User B in the BO2 zone dials IP Phone A in the main office zone (DN 5262) (action labeled 1 in Figure 49 "Example of an alternately routed call between a Branch Office telephone in Normal Mode and a main of" (page 132)). 2. The main office Call Server determines there is insufficient bandwidth between the two zones. 3.
Description 135 4. The call is routed to the virtual trunk by CDP or VNR. The virtual trunk sends a request to the NRS for address resolution. The digit string sent to the NRS contains the ALTPrefix. The NRS returns the IP address of the Branch Office endpoint to the virtual trunk. 5. The virtual trunk places the call to the Branch Office. 6. The Branch Office receives the call and recognizes the first part of the number as a Steering Code. The call is steered to an RLI.
Alternative Call Routing for Network Bandwidth Management gatekeeper/Network Routing Service (NRS) that can be co-resident with a Signaling Server. IP Phones are also shown associated with each system. Telephone A belongs to the main office. Telephone B is a telephone at the Branch Office registered to the main office. There are two bandwidth zones indicated by the dashed line (main office zone [MO zone] and Branch Office zone [BO2 zone]). Telephone A and the Media Gateway belong to the MO zone.
Description • 137 Set up a DMI to outpulse the correct digits to the Branch Office telephone. At the Branch Office: • No provisioning required. At the NRS: • No provisioning required. Sequence of events in the call The information that follows refers to Figure 51 "Example of an alternately routed call between a main office telephone and a Branch Office telephone" (page 136) and Figure 52 "Illustration showing digits dialed and outpulsed with Alternative Call Routing for NBWM" (page 137).
Alternative Call Routing for Network Bandwidth Management Example: ALTPrefix assigned is 777. The dialed number becomes 777 3121. 4. The call is routed by CDP or VNR to the outgoing route using an RLI. Example: 7773 is a steering code, translated to go to an RLI where there is one entry, a PSTN trunk route. 5.
Description 139 Figure 53 Example of an alternately routed call between a Branch Office telephone and another Branch Office telephone Telephone B in the BO2 zone calls Telephone F in the BO1 zone (the user dials 6020). In this example, the call alternately routes to the PSTN. (The PSTN telephone number of Telephone F is 506-348-6020.) Configuration required Configure the following: At the main office: • Use one of the dialing plan software packages to process the call, such as CDP or NARS.
Alternative Call Routing for Network Bandwidth Management At the NRS: • Create a CDP entry for the ALTPrefix in the Branch Office gateway. Sequence of events in the call The information that follows refers to Figure 53 "Example of an alternately routed call between a Branch Office telephone and another Branch Office te" (page 139) and Figure 54 "Illustration showing digits dialed and outpulsed with Alternative Call Routing for NBWM" (page 141).
Description 141 Figure 54 Illustration showing digits dialed and outpulsed with Alternative Call Routing for NBWM 1. The user of IP Phone B in the BO2 zone dials IP Phone F in the BO1 zone (DN 6020) (action labeled 1 in Figure 53 "Example of an alternately routed call between a Branch Office telephone and another Branch Office te" (page 139)). Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.
Alternative Call Routing for Network Bandwidth Management 2. The main office Call Server determines there is insufficient bandwidth between the BO2 and BO1 zones. 3. The Call Server inserts the ALTPrefix configured for the BO2 zone prior to IP Phone F’s telephone number, dialed by the user. Example: ALTPrefix assigned is 222.The dialed number becomes 222 6020. 4. The call is routed to the virtual trunk by CDP or VNR. The virtual trunk sends a request to the NRS for address resolution.
Operating parameters 143 The configuration and provisioning for the All Calls mode is exactly the same as the regular Alternative Call Routing for NBWM feature except that the Alternate Routing for All Calls option is selected in LD 117 or Element Manager. Operating parameters This feature applies to all CS 1000 systems. This feature applies to station-to-station, interzone calls. The call can be between IP Phones or a TDM telephone at the main office and an IP Phone at the Branch Office.
Alternative Call Routing for Network Bandwidth Management This feature does not apply to virtual trunk calls. It only applies to station-to-station calls, and routes them over the PSTN or MCDN network. Virtual Trunk calls already have this feature and can be alternately routed using traditional methods (such as NARS), which are outside the scope of this feature. Alternative Call Routing for NBWM does not apply to users who are registered in local mode to the Branch Office.
Feature implementation using Command Line Interface 145 Network Routing Service (NRS) Both the main office and Branch Office must be registered on the Nortel NRS for tandem routing to work for main office to Branch Office tandeming. Trunk Route Optimization (TRO) Disable Trunk Route Optimization between the Branch Office (or SRG) and the main office to allow the tandeming required for the feature to work.
Alternative Call Routing for Network Bandwidth Management Description Command Enable Alternative Call Routing for NBWM, where: Input zone number (0-255). Configure the Branch Office zone using LD 117 at the main office. LD 117 - Configure Alternate Prefix number for a particular zone and the All Calls option, if desired. Description Command CHG ZALT [] Change ALTPrefix number for zone, where: Input zone number (0-255).
Feature implementation using Element Manager 147 Feature implementation using Element Manager Zone configuration Use Element Manager to configure the specific zone properties. 1. Access the Zones web page to select Alternate Routing for Calls between IP Stations. 2. Access the Alternate Routing for Calls between IP Stations web page to configure the feature. Accessing the Zones web page Procedure 4 Accessing the Zones web page Step Action 1 From the navigator, click IP Network > Zones.
Alternative Call Routing for Network Bandwidth Management Figure 56 Access the Zones web page to select Alternate Routing for Calls between IP Stations 2 Under Configuration click beside the Zone, or click the Zone you are programming, to expand the choices under it. 3 Click Alternate Routing for Calls between IP Stations. A web page appears that displays the configuration parameters related to the Alternative Call Routing for NBWM feature.
Diagnostics 149 Figure 57 Access the Alternate Routing for Calls between IP Stations web page to configure the feature The Zone Number for the zone you selected in step 3 is displayed. 4 Select the Enable Alternate Routing feature (ENL_ZALT) check box to enable the Alternative Call Routing for NBWM feature. 5 Enter a maximum of 7 digits in Alternate Routing Prefix Digits (ALTPrefix). 6 Select the Re-route for All Calls (ALL_CALLS) check box to enable the feature for all calls.
Alternative Call Routing for Network Bandwidth Management The printout for all configured zones appears as follows: # Alternate Routing Status 10 ENL 11 DIS 12 DIS LD 117 - Obtain status for a Branch Office zone(s). Command Description STAT ZBR Show status of specified Branch Office zone, where: zone = bandwidth zone If you do not enter a value in the zone field, you obtain a printout of the status of all configured Branch Office zones.
Diagnostics 151 Figure 58 System Maintenance web page 2 Click Select by Functionality. The Select by Functionality web page appears. (See Figure 59 "Maintenance web page showing Select by Functionality" (page 152).) Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Alternative Call Routing for Network Bandwidth Management Figure 59 Maintenance web page showing Select by Functionality 3 Click Zone diagnostics. The Maintenance Commands for Zones web page appears. (See Figure 60 "The Maintenance Commands for Zones web page with PRT ZALT results" (page 153).) You can also access this page if you click on Zones, as you see in Figure 56 "Access the Zones web page to select Alternate Routing for Calls between IP Stations" (page 148).
Diagnostics 153 Figure 60 The Maintenance Commands for Zones web page with PRT ZALT results 4 Select Print Zone Alternate Prefix Information (PRT ZALT) from the the drop-down list beside Action. 5 Select ALL or a zone number from the Zone Number drop-down list. 6 Click Submit. Figure 60 "The Maintenance Commands for Zones web page with PRT ZALT results" (page 153) shows a typical example of the results.
Alternative Call Routing for Network Bandwidth Management 3 Click Zone diagnostics. The Maintenance Commands for Zones web page appears. (See Figure 61 "Show the status of the Alternative Call Routing feature for the Branch Office zone" (page 154).) 4 Select Show Alternate Routing Status (STAT ZALT) from the drop-down list beside Action. (See Figure 61 "Show the status of the Alternative Call Routing feature for the Branch Office zone" (page 154).
Maintenance 155 Maintenance Command Line Interface maintenance LD 117 - Enable and disable Alternative Call Routing for NBWM for a zone. Command Description ENL ZALT Enable Alternative Call Routing for Bandwidth Management for zone specified. DIS ZALT Disable Alternative Call Routing for Bandwidth Management for zone specified. ENL ZBR [ALL] [LOC][ESA][TIM][ALT] Enable features for the Branch Office zone. If you do not input features, then all are enabled.
Alternative Call Routing for Network Bandwidth Management Procedure 7 Enabling a zones Branch Office behavior Step Action 1 From the navigator, click System > Maintenance. The Maintenance web page appears. (See Figure 58 "System Maintenance web page" (page 151).) 2 Click Select by Functionality. The Select by Functionality web page appears. (See Figure 59 "Maintenance web page showing Select by Functionality" (page 152).) 3 Click Zone diagnostics.
Maintenance 7 157 Click Submit. The display updates with new configuration data for the zone you specified. —End— Suppress alarms Procedure 8 Suppress Alternative Call Routing for NBWM alarms Step Action You can suppress alarms QoS0038 and QoS0039 for a configurable amount of time (0 - 3600 seconds). 1 Click IP Network > Zones 2 Click beside the Zone, or click the Zone you are programming, to expand the choices under it.
Alternative Call Routing for Network Bandwidth Management —End— Feature operation No specific operating procedures are required to use this feature. Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
How the Branch Office feature works Contents This section contains information on the following topics: "Introduction" (page 160) "Normal Mode and Local Mode operation" (page 160) "Normal Mode" (page 160) "Local Mode" (page 160) "Virtual Trunks" (page 164) "IP Phone calls" (page 165) "Zones" (page 165) "Vacant Number Routing" (page 165) "Time of Day" (page 166) "MG 1000B IP Phone to local PSTN calls" (page 166) "IP Phone to analog (500/2500-type) or digital telephone calls" (page 167) "Conference calls
How the Branch Office feature works "MG 1000B Core interoperability" (page 176) "Network Wide Redundancy Phase II and Network Music" (page 176) Introduction The Branch Office connects to the main office using Virtual Trunks over the LAN or WAN. Virtual Trunks are software components that provide the trunking features of the Meridian Customer-Defined Networking (MCDN) feature set.
Normal Mode and Local Mode operation 161 An IP Phone at the Branch Office may be in Local Mode for two different reasons: • IP Phone may have just booted up • IP Phone cannot communicate to the main office because of a WAN failure or a failure of the main office components. In the event of a WAN failure, the Branch Office IP Phones lose communication with the main office. This causes the Branch Office IP Phones to reset and reregister with the Branch Office. The IP Phones then operate in Local Mode.
How the Branch Office feature works Before the Branch Office IP Phone attempts to register with the main office, the MG 1000B first queries the Primary NRS (NCS) fro the main office for the Virtual Trunk node IP address to redirect the IP Phone. If the Primary NRS (NCS) is down or unreachable, the MG 1000B queries the Alternate NRS, if one is specified. If it receives a positive response, the MG 1000B is redirected to the specified main office.
Normal Mode and Local Mode operation 163 After Virtual Office login, the Branch Office does not start the redirection procedure to the Main Office for a logged in set immediately. The Main Office can accept only an IP Phone 2004 compatible phone following a Branch Office redirection. If the redirected phone is not 2004 compatible (such as 2007 or 1140), an Invalid Set Type message is displayed.
How the Branch Office feature works The licensing feature applies only if more than four IP Phones are in Local Mode at the same time. If four or fewer phones are in Local Mode simultaneously, the licensing feature is not activated. Testing the telephone in Local Mode From Normal Mode, a Branch Office user can use Test Local Mode to test telephone functionality in Local Mode. The user can perform the test at any time and does not require a password. This test is invoked from the Internet Telephone.
Normal Mode and Local Mode operation 165 IP Phone calls When an IP Phone calls another IP Phone, each telephone receives the address of the other to exchange media directly between the telephones. Also note that when in Normal Mode, an MG 1000B IP Phone calling a main office IP Phone does not require any trunking to setup the call. However, LAN/WAN bandwidth is used to provide a media path for the call.
How the Branch Office feature works Vacant Number Routing (VNR) is mandatory in a Branch Office. It enables a Branch Office to route calls through the NRS, or other alternate routes if configured, with minimal configuration. Instead of changing the numbering trees and steering codes at each location, all the routing information can be kept at one central location. At the Branch Office, VNR is normally routed first to the Virtual Trunk.
Normal Mode and Local Mode operation 167 ATTENTION IMPORTANT! If you are using one Access Code for both local and long-distance calls, and that Access Code is associated with a Branch Office zone, all calls (local and long-distance) are routed through that Branch Office. For more information, see "Dialing plan configuration" (page 291).
How the Branch Office feature works The conferencing feature for MG 1000B systems supports up to 30 parties with the addition of the MGC as the gateway controller for the MG 1000B. In a CS 1000E system, the MGC acts as the controllers for the MG 1000Bs: • If you configure a conference loop in LD 17 on any MGC-based MG 1000Bs, the maximum number of parties for any conference on the system is six. This is the CS 1000 Release 5.0 limit due to the Call Server hardware.
Configuring non-zero S2 IP Addresses 169 When the telephone detects that it has lost communication with the main office, it reboots and registers to the MG 1000B TPS. This means that, depending on the network configuration (or the point of failure in the network), not all MG 1000B IP Phones go into Local Mode at the same time. Calls are not maintained during switchover from Normal Mode to Local Mode.
How the Branch Office feature works Figure 64 Configuration using S2 IP Address Points to remember When an IP set registers to the main office using S2, remember the following important points: • An IP Phone registered to the main office using S2 appears in the main office TPS as a "regular online" user. Normally, an MG 1000B IP Phone registered to the main office Call Server appears as a "branch online" user. Commands can be executed on the main office Signaling Server to verify this operation.
Configuring non-zero S2 IP Addresses 171 System or a CS 1000E, a TN mismatch occurs and redirection from Branch Office to main office is not successful. • If the MG 1000B TPS is unavailable, IP Phones at the main office or Branch Office have no access to TDM resources (digital and analog telephones or PSTN trunks) at the Branch Office, whether the IP Phones are registered using S1 or S2.
How the Branch Office feature works 3 Program the IP address, subnet mask, and gateway addresses for the MG 1000B IP Phone. 4 Program the S1 IP Address, action, and retry parameters. The S1 IP Address is the MG 1000B Node IP Address. 5 Program the S2 IP Address, action, and retry parameters. The S2 IP Address is the main office Node IP Address. 6 Program the remaining parameters. The IP Phone reboots again.
Emergency services 173 The key difference between the main office user and the Branch User is the route selected for the emergency call. An emergency call must be handed off to the PSTN over a trunk at the central office that is geographically closest to the caller — this means that there is normally an emergency trunk in the main office, and one in each of the branch offices.
How the Branch Office feature works With all sites using the same ESDN, a conflict occurs in the NRS. The conflict is resolved by using a unique prefix for each site, which the main office adds as it routes the call. The suggested prefix is the ESN home location code of the MG 1000B CP PM, or alternately, the Number Plan Area (NPA) code of the MG 1000B CP PM if there is not more than one Call Server in the NPA.
Abbreviated Dialing 175 This feature is implemented with a pre-translation group assigned to every telephone. All IP Phones in the same bandwidth management zone use the same pre-translation group. TDM telephones, which share the same dialing plan with IP Phones in a bandwidth management zone, also use the same pre-translation group. The pre-translation group assignment is more easily and quickly done using the TM 3.01 global change functionality.
How the Branch Office feature works • Calling Line Identification (CLID) on outgoing PSTN calls from the main office or the Branch Office are modified from four to six digits. Additional digits can be added using the capabilities of CLID. • The calling party display always shows the full-length DN of the originating party. • The display on the calling telephone shows the called DN as dialed. After the call is established or modified, the display changes in accordance with existing features.
Network Wide Redundancy Phase II and Network Music 177 or the CS 1000/2100 itself is down. When the link to the remote 2100/CS 1000 or to the remote CS 1000/2100 itself is restored, the IP telephones are automatically redirected back to the remote CS 1000/2100 to receive telephony services. Support for this feature is available in the MG 1000B to provide survivability to IP telephones normally registered with a CS 2100/CS 1000.
How the Branch Office feature works Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Planning and management Contents This section contains information on the following topics: "Data network planning" (page 179) "LAN/WAN bandwidth requirements" (page 180) "Branch Office dialing plan" (page 181) "Emergency Services" (page 182) "Zones" (page 182) "Music on Hold" (page 182) "ESN Access Codes" (page 182) "Provisioning the IP Phones" (page 182) "Configuration example for PSTN resources at the Branch Office" (page 183) "Management" (page 185) "Remote Access" (page 185) "Element Manager" (pag
Planning and management • jitter CAUTION Service Interruption If the network is planned so IP Phones use a different route to the main office than the MG 1000B TPS, a fault condition can occur. When the MG 1000B TPS can "ping" the main office but the IP Phone cannot "ping" the main office due to a network outage, an IP Phone registration can force the telephone into a cycle of registering locally, being redirected to the main office, rebooting and then registering locally again.
Branch Office dialing plan 181 The maximum bandwidth required for these activities is approximately 13 Kbps. This is insignificant when compared to the bandwidth requirement for the expected voice traffic. Therefore, when determining the LAN/WAN bandwidth requirement for a Branch Office, expected voice traffic should be the major factor.
Planning and management For more information about CDP, refer to Dialing Plans Reference (NN43001-283). For details on other Numbering Plan options, refer to Communication Server 1000S: Overview (NN43031-110). For more information on ESN, refer to "ESN Access Codes" (page 182). Emergency Services To understand Emergency Service Access (ESA), see "Emergency services" (page 172). The main office Call Server supports only one Emergency Service DN (ESDN).
Branch Office dialing plan 183 Configuration example for PSTN resources at the Branch Office IP Phones registered to the main office Call Server can be grouped into one of two categories: • those configured with a main office dialing plan, similar to any other non-IP Phone at the main office • those configured with a Branch Office dialing plan because the telephone is physically located in a Branch Office Customer data must first be configured to recognize numbers that are local to each location (a st
Planning and management • All other long-distance numbers have other routing as appropriate (1-NPA-NXX-XXXX). At the Branch Office, the following items must be configured: • Long-distance numbers in the same area code, such as 1-506-234-1234 or 1-506-675-1234. • Long-distance numbers at the main office are configured to go over the Virtual Trunk and use PSTN trunks at the main office, such as 1-613-967-1111 or 1-613-555-1212.
Management 185 Description Command Tells the system the NARS Access Codes for local dialing and the NARS Access Code to convert the call into a long-distance call, to route the call to the Branch Office. In this case we are converting a call, such as "9 555-1212" into the call "6 1 506 555-1212", a conversion from AC2 to AC1. CHG ZDP 10 1 506 Specifies the additional digits needed to convert a local call to a long-distance call.
Planning and management — trunks — the IP telephony node — Electronic Switched Network (ESN) data — Digital Signal Processing (DSP) channels — Branch Office zone features — Emergency Services Access at the Branch Office — Daylight Savings Time at the Branch Office Telephony Manger 3.1 TM 3.1 supports all Windows and web-based applications for the Branch Office feature, similar to the CS 1000E and CS 1000M systems. TM 3.01 allows customers to configure IP Phone data for use in survivable mode.
Management 187 office, or any other Branch Office in the network. However, IP Phone calls to devices or local trunks at the Branch Office are counted as incoming Virtual Trunk calls to the analog or digital devices or local trunks. When an IP Phone is in Local Mode, any calls to or from the IP Phone are included in the traffic measurement at the Branch Office. Call Detail Recording (CDR) The format of CDR output for the Branch Office feature is no different from the existing CDR format.
Planning and management The identifying digits in the main office Call Server’s CDR log are the manipulated string as specified by the Branch Office zone. For example, the Branch Office user dialed "9, 555-1212", but the main office Call Server changes it to "6, 1-613-555-1212". CDR records the dial string as "1-613-555-1212".
Management 189 ATTENTION IMPORTANT! The notification level for a Branch Office zone must be configured exactly the same in the main office and the Branch Office. System security CS 1000E and CS 1000M (Large System) system security is explained in detail in System Management Reference (NN43001-600). This is required reading for any Branch Office administrator. Refer to Access Control Management Reference (NN43001-602) for additional information.
Planning and management Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Adding a Branch Office Contents This section contains information on the following topics: "Introduction" (page 191) "Main office requirements" (page 192) "Branch Office requirements" (page 193) "Implementation summary" (page 194) "Adding a CS 1000 Release 5.0 Branch Office to a Branch Office network with previous releases of soft" (page 196) "Upgrade the entire network to CS 1000 Release 5.0" (page 197) "Upgrade only the main office to CS 1000 Release 5.
Adding a Branch Office firmware for the existing branch offices. You can choose not to upgrade the firmware at the existing branch offices only if the IP Phones in those branch offices are running at least the minimum version of firmware as specified in "Telephones" (page 36). If you choose to upgrade the firmware, you must upgrade the firmware at the existing branch offices first. The main office may not require a firmware upgrade, depending on its current version.
Main office requirements 193 share the voicemail system in the main office. For any configurations using centralized Call Pilot on the main office with one or more branch offices in separate time zones, the NMS package is required at the main office for the branch IP Phones. Optional features • Network Alternate Route Selection (NARS) package 58. Refer to Basic Network Feature Fundamentals (NN43001-579). • Overlap Signaling (OVLP) package 184.
Adding a Branch Office • Emergency Services Access (ESA) package 329 • Virtual Office (VIRTUAL_OFFICE) package 382 and M3900 Phase III Virtual Office Enhancement (VIR_OFF_ENH) package 387. These packages are optional; they are required only for Virtual Office functionality. • BMG package 390 • IP Peer H.323 Trunk (H323_VTRK) package 399. This package is optional; it is required for H.323 functionality. The packaging for package 399 also includes package 184.
Implementation summary 195 a. Upgrade the main office software to CS 1000 Release 5.0. Refer to , Communication Server 1000E Upgrades (NN43041-458) orCS 1000M and Meridian 1 Large System Upgrades Overview (NN43021-458). b. If not already implemented, implement IP Peer Networking as part of a system installation or upgrade. Refer to IP Peer Networking Installation and Commissioning (NN43001-313) . c. Configure the Branch Office zones. See Procedure 9 "Configuring ESN and MG 1000B zones" (page 210). d.
Adding a Branch Office g. Install and provision the local trunks (the XUT, PRI, and DTI cards). h. If applicable, configure Abbreviated Dialing. See "Abbreviated Dialing configuration" (page 337). i. Provision the Virtual Trunks. Refer to IP Peer Networking Installation and Commissioning (NN43001-313) . When configuring NRS, enable the Network Connection Service (NCS). Ensure that each Branch User ID (BUID) is entered in the Branch Office numbering plan so it points to the main office.
Adding a CS 1000 Release 5.0 Branch Office to a Branch Office with a previous software release 197 For further information on upgrading the IP Phone firmware, refer to IP Line Fundamentals (NN43100-500). For information on upgrading and reconfiguring the Signaling Server software, refer to Signaling Server Installation and Commissioning (NN43001-312). Upgrade the entire network to CS 1000 Release 5.0 To upgrade the entire network to CS 1000 Release 5.0: Step Action 1 At the main office: a.
Adding a Branch Office Upgrade only the main office to CS 1000 Release 5.0 ATTENTION IMPORTANT! A mixed software configuration between the main office and branch offices running , CS 1000 4.0, CS 1000 Release 4.5 or CS 1000 Release 5.0, is permitted. In this case, indefinite operation with a mixed software configuration is supported. If you choose to upgrade only the main office to CS 1000 Release 5.0, you have the option of upgrading the IP Phone firmware. Specifically, the options are: 1.
Adding a CS 1000 Release 5.0 Branch Office to a Branch Office with a previous software release 199 4 Install the new CS 1000 Release 5.0 Branch Office as described in "Implementation summary" (page 194). —End— Upgrade main office without IP Phone firmware upgrade To upgrade the main office to CS 1000 Release 5.0 without upgrading the IP Phone firmware in the existing CS 1000 4.0 or CS 1000 4.5 branch offices: Step Action 1 At the main office: a. Upgrade the Call Server software to CS 1000 Release 5.0.
Adding a Branch Office Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Converting a Small System to a Branch Office Contents This section contains information on the following topics: "Introduction" (page 201) "Requirements" (page 201) "Conversion" (page 202) "Implementation summary" (page 203) Introduction Customers with a CS 1000M installed base can re-configure existing satellite Small System to function as Branch Offices. This configuration allows customers to incorporate systems that were previously stand-alone into a Branch Office network.
Converting a Small System to a Branch Office • single-chassis Meridian 1 Option 11C Mini/Meridian 1 PBX 11C Chassis with or without a chassis expander • single-cabinet CS 1000M Cabinet • single-cabinet CS 1000M Chassis with or without a chassis expander Only single-cabinet and single-chassis systems (with or without a chassis expander) can be converted. Multiple-cabinet and multiple-chassis Small Systems must first be reduced to single cabinets or chassis.
Conversion 203 on upgrading an existing system to CS 1000 Release 5.0 software. Refer to Signaling Server Installation and Commissioning (NN43001-312) for instructions on installing a Signaling Server on a Meridian 1 system. If a Signaling Server is added to a previously CISPR Class B system (previously used in some specific countries), the system is now compliant to Class A, as noted in the front and back pages of this document.
Converting a Small System to a Branch Office 2 For each Small System that is to be converted to a Branch Office: a. Power down the system, including reserve power if so equipped. b. Upgrade the system controller card if required. Refer to Meridian 1 Small System Software -only Upgrade (NN43011-459). c. Install a Voice Gateway Media Card if required. Refer to IP Line Fundamentals (NN43100-500). If the Small System already has a Voice Gateway Media Card, upgrade it to IP Line 4.5.
Conversion i. 205 Configure the Voice Gateway Media Cards. Refer to IP Line Fundamentals (NN43100-500). Use the same zone for DSP physical TNs and IP Phone TNs. The zone number must match that at the main office. Refer to IP Line Fundamentals (NN43100-500). j. Install and provision the local trunks (the XUT, PRI, and DTI cards). Refer to Communication Server 1000M and Meridian 1 Small System Installation and Commissioning (NN43011-310). k. If applicable, configure Abbreviated Dialing.
Converting a Small System to a Branch Office Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Upgrading to CS 1000 Release 5.0 Contents This section contains information on the following topics: "Introduction" (page 207) "Upgrading to CS 1000 Release 5.0" (page 208) Introduction This chapter describes upgrading an existing main office and its associated branch offices from CS 1000 4.0 or CS 1000 4.5 to CS 1000 Release 5.0. If, in a given network, there is one or more CS 1000 4.0 Branch Offices, or one or more CS 1000 4.5 Branch Offices, all Branch Offices must be upgraded to Succession 4.
Upgrading to CS 1000 Release 5.0 Upgrading to CS 1000 Release 5.0 If the main office has not already been upgraded to CS 1000 Release 5.0, begin with step 1. If the main office has been upgraded to CS 1000 Release 5.0, skip to step 2. Step Action 1 At the main office: a. Upgrade the Call Server software to CS 1000 Release 5.0. b. Upgrade the main office Signaling Server(s) software to CS 1000 Release 5.0 with the Automatic Firmware Upgrade set. c.
Main office configuration Contents This section contains information on the following topics: "Introduction" (page 209) "Zone parameters" (page 210) "Element Manager zone configuration" (page 213) "IP Phone passwords and parameters" (page 215) "MG 1000B IP Phone configuration" (page 218) Introduction This section describes the configuration of zones, IP Phone passwords and parameters, and MG 1000B IP Phones at the main office.
Main office configuration Zone parameters Zone parameters must be configured at both the main office Call Server and MG 1000B Call Server. The main office procedure is similar to an IP Peer Network configuration with the Branch Office-specific configuration outlined in this chapter.
Zone parameters 211 Prompt Response Description - VPNI (0)-16283 Virtual Private Network Identifier for Bandwidth Management feature 0 or X = Disables feature 1-16383 = Enables feature = No Change 2 Configure the Branch Office zone. Configure the zone properties for IP telephony bandwidth management. Use LD 117 or Element Manager. Refer to IP Peer Networking Installation and Commissioning (NN43001-313) .
Main office configuration Description Command • interZoneBandwidth = Interzone available bandwidth (see Note Note 1:) 0-1000000 Kbps • interZoneStrategy = Interzone preferred strategy (BQ for Best Quality or BB for Best Bandwidth) (see Note Note 2:) • zoneResourceType = zone resource type (shared or private), where — shared = Current default zone type. The IP Phones configured in shared zones use DSP resources configured in shared zones.
Zone parameters 213 Description Command If the Branch Office observes Daylight Savings Time (DST), these parameters specify the start and end of DST. During DST, the clock automatically advances one hour forward. CHG ZTDF Specified in minutes, the time difference between main office and Branch Office when both are not in DST. CHG ZDES
Main office configuration Figure 67 Branch Office-specific Zone Basic Property and Bandwidth Management Figure 68 Zone Time Difference and time zone Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
IP Phone passwords and parameters Step Action 1 Select IP Network > Zones in Element Manager navigator. 215 The Zones window opens (Figure 66 "Branch Office-specific zone configuration" (page 213)). The zone list is the main window used for zone configuration. In the Zone List window, select the zone to be configured.
Main office configuration related commands, and explanations are given in Table 19 "IP Phone node passwords" (page 216). Table 19 IP Phone node passwords Command Description nodePwdSet Sets the node password. If a non-zero length password is configured, all IP Phones that attempt to register after this command is entered display a prompt for node password before the TN can be modified. nodePwdShow Shows the node password settings. nodePwdEnable Enables node password checking.
IP Phone passwords and parameters 1 217 Configure the length of the password, SCPL, to be of non-zero length in LD 15. LD 15 Configure the SCPW length in the Customer Data Block. Prompt Response Description REQ: CHG Change existing data. TYPE: FFC Flexible Feature Code SCPL 0-8 Length of SCPW, minimum recommended is 4 digits 2 Assign the Automatic Set Relocation security code. LD 15 Assign Automatic Set Relocation security code.
Main office configuration 3.01" (page 218)) or overlays (see Procedure 12 "Configuring MG 1000B IP Phones at the main office using LD 11" (page 218)). —End— MG 1000B IP Phone configuration After the Branch Office zones and passwords are provisioned, provision the MG 1000B IP Phones at the main office. These can be provisioned using TM 3.01 (see "MG 1000B IP Phone configuration using TM 3.
MG 1000B IP Phone configuration 2 219 Configure the following telephone data in LD 11: • Terminal type • Customer Number • TN • Zone • Prime DN to correspond to BUID LD 11 Provision Branch User and SCPW at the main office Prompt Response Description REQ: NEW CHG Add new data, or change existing data. TYPE: a...a Terminal type. Type ? for a list of possible responses. CUST xx Customer number as defined in LD 15. ZONE 0-255 Zone Number to which the IP Phone belongs.
Main office configuration Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
MG 1000B platform hardware installation Contents This section contains information on the following topics: "Installing an MG 1000B Core" (page 221) "Readiness checklist" (page 222) "Tools checklist" (page 223) "Rack-mounting an MG 1000B Core or MG 1000B Expander" (page 223) "Installing cards" (page 227) "Installing a Signaling Server" (page 228) "Materials required" (page 228) "Preparing for rack-mounting" (page 230) "Rack-mounting" (page 232) "Connecting and powering up the Signaling Server" (page 23
MG 1000B platform hardware installation To connect to the PSTN, use one of the following interface cards: • 1.5 Mb T1 Multi-functional Digital Interface • Extended Universal Trunk (analog) • 2.0 Mb Digital Trunk Interface (DTI) • 2.0 Mb Primary Rate Interface (PRI) The MG 1000B Expander will support digital trunks if configured with a media gateway controller. Each MG 1000B Core with a digital trunk card must have a clock controller. See Circuit Card Reference(NN43001-311).
Installing an MG 1000B Core 223 Tools checklist To install the system correctly, make sure that the tools listed in Table 21 "Tools checklist" (page 223) are available before assembling the components.
MG 1000B platform hardware installation 1 Fasten the right guide bracket to the right rack support. a. Insert two #12-24 self-tapping screws into the two middle slots in the guide bracket and into the respective holes in the right rack support. b. Tighten the screws. See Figure 69 "Guide bracket installed in a rack" (page 224). Figure 69 Guide bracket installed in a rack The guide brackets guide the MG 1000B Core into place and enable one person to install the MG 1000B Core in the rack.
Installing an MG 1000B Core 225 be at the top of the bracket and must face to the front of the MG 1000B Core. Figure 70 Right ear bracket installed on the MG 1000B Core 4 Attach the left ear bracket (marked with an "L") to the holes on the left side of the MG 1000B Core (near the front). a. Use two #8-32 machine screws. b. Position the ear bracket so that the four holes on the bracket flange are nearer to the back of the MG 1000B Core. To determine the front of the bracket, locate the "L".
MG 1000B platform hardware installation 5 Place the MG 1000B Core on the guide brackets. Carefully slide the MG 1000B Core into the rack until the ear brackets come to rest against the rack support. 6 Use the four remaining #12-24 self-tapping screws to fasten the MG 1000B Core to the rack supports (two screws on each side). 7 Make sure that the back of the MG 1000B Core is on the guide brackets. See Figure 71 "MG 1000B Core and MG 1000B Expander installed in a rack" (page 226).
Installing an MG 1000B Core 227 b. Follow the instructions in Telephony Manager 3.1 Installation and Commissioning (NN43050-300). A sample printout of the Ethernet configuration is provided. Do not connect a serial port to the AUX connector. It can damage the port. 13 Set DIP switches on the power supply for the desired ringing voltage, ringing frequency, and message waiting voltage. These procedures are in Communication Server 1000S: Installation and Configuration (NN43031-310).
MG 1000B platform hardware installation Figure 73 Media Card Install a trunk card to connect with the PSTN and an analog or digital line card to connect with local resources.
Installing a Signaling Server 229 3. The power cable for the Signaling Server. Check that the power cord is the exact type required in the host region. Do not modify or use the supplied AC power cord if it is not the correct type. 4. The serial cable for the Signaling Server. 5. The CAT5 cables for networking. 6. The contents of the accessories pouch to install the Signaling Server. The accessories pouch should contain the following items: a. Two support brackets (A) b. Two rack-mounting brackets (B) c.
MG 1000B platform hardware installation Preparing for rack-mounting Procedure 14 Preparing the Signaling Server for rack-mounting Step Action The Front Mount Bracket assembly is not intended for use as a slide rail system. The Signaling Server must be firmly attached to the rack. 1 Make sure the Signaling Server is not plugged into an electrical outlet.
Installing a Signaling Server Figure 77 Left hinge mount Figure 78 Right hinge mount Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
MG 1000B platform hardware installation When the door is attached to the Signaling Server and rack-mount apparatus, it appears as shown in Figure 79 "Snapped-in bezel door" (page 232). Figure 79 Snapped-in bezel door —End— Rack-mounting Read the following warnings carefully before installing the Signaling Server in the rack. DANGER DANGER OF ELECTRIC SHOCK DISCONNECT AC POWER: Completely disconnect the the Signaling Server from any AC power source before performing this procedure.
Installing a Signaling Server 233 WARNING MAIN AC POWER DISCONNECT: You must install an AC power disconnect for the entire rack unit. This main disconnect must be readily accessible, and it must be labeled as controlling power to the entire unit, not just to the Signaling Server(s). WARNING Damage to Equipment OVERCURRENT PROTECTION: The Signaling Server is designed for an AC line voltage source with up to 20 amperes (A) of overcurrent protection.
MG 1000B platform hardware installation a. Align the rack-mount brackets on the Signaling Server with the slide rail system on the rack posts. b. Slide the Signaling Server into place. Refer to Figure 81 "Rack-mounting the Signaling Server" (page 234). Figure 81 Rack-mounting the Signaling Server 3 Tighten the screws through the faceplate of the Signaling Server to the rack-mount bracket. WARNING Do not apply excessive torque while tightening the bolts.
Installing a Signaling Server 235 Connecting and powering up the Signaling Server WARNING Do not modify or use a supplied AC power cord if it is not the exact type required in the region where the Signaling Server is installed and used. Replace the cord with the correct type. Refer to "Check the Power Cord" in the "Unpack and Inspect the Server" section at the front of this guide for power cord requirements.
MG 1000B platform hardware installation Do not modify or use the supplied AC power cord if it is not the correct type. Refer to in Communication Server 1000S: Installation and Configuration (NN43031-310) for a detailed power cord description. b. Attach the female end of the power cord to the mating AC power receptacle on the left side of the Signaling Server’s back panel. See Figure 82 "Back of Signaling Server" (page 235). Plug the male end of the AC power cord into the AC power source (wall outlet).
Installing a Signaling Server 237 2. Gently pull the tabs out and down to swing open the hinged bezel door. Figure 84 Signaling Server with open bezel door The MAC addresses are visible on the lower right-hand side when the bezel door is open. See Figure 85 "MAC address" (page 237). MAC1 is Port 1 (ELAN network interface), and MAC2 is Port 2 (TLAN network interface). Though the MAC1 address is the top address, Port 1 is the bottom network interface port on the back of the Signaling Server.
MG 1000B platform hardware installation Figure 86 Signaling Server indicators and power switch The Signaling Server LED indicators show the following: • Power – green LED on, power on; LED off, power off. • Status – red LED off, CPU running; LED on, CPU halted. • Drive – green LED flashing, Hard Drive or CD ROM Drive active. • Link – green LED, Ethernet port active. • 100Mbps – green LED on, Ethernet port running at 100Mbps; LED off, Ethernet port running at 10Mbps.
MG 1000B software installation Contents This section contains information on the following topics: "Signaling Server software installation" (page 239) "Materials required" (page 240) "Creating the Signaling Server CD" (page 240) "Installing the Signaling Server software" (page 241) "Signaling Server tools" (page 241) "Signaling Server port speed" (page 243) "Verifying a successful configuration" (page 244) "Connecting the MG 1000B Core to the network" (page 244) "Connecting the MG 1000B Core to the net
MG 1000B software installation The Install Tool installs all Signaling Server software, including the operating system, applications, and web files. The Install Tool also copies software files for the Voice Gateway Media Cards and IP Phones, which are used to upgrade these components. For a new Signaling Server, the Install Tool prompts for IP telephony parameters to perform basic system configuration.
Signaling Server software installation 241 3 Label the CD appropriately (for example, Signaling Server, sse-x.xx.xx). —End— The Software CD-ROM must be readable in a standard CD-ROM drive. After you create a CD from the CD image, the CD contains several directories and files. If you cannot create a CD, please refer to the CD writer’s software documentation. Once the CD is created, you can use it to install new software or upgrade software on an existing Signaling Server.
MG 1000B software installation 1 Enter t at the Main Menu to access the Tools menu. The Tools Menu appears as shown in Tools menu. 2 Under the Tools Menu: Figure 87 Tools menu a. Set the date and time (default). b. Repartition and reinitialize the hard disk. c. Delete the Administrator login and password. d. Test the hard disk. e. Change the web server security flag. f. Initialize the unprotected partition (/u).
Signaling Server software installation 243 Signaling Server port speed Use Procedure 19 "Changing the Signaling Server port speed" (page 243) to change the initial port speed of the Signaling Server for a maintenance terminal connection. This procedure is optional. Procedure 19 Changing the Signaling Server port speed Step Action 1 Make sure the DTE–DTE null modem cable (supplied with the Signaling Server) runs from the back port of the Signaling Server to the maintenance terminal.
MG 1000B software installation —End— After installing software and configuring basic information about the Signaling Server, the Signaling Server components can be configured using the web-based Element Manager interface. See Element Manager System Reference - Administration (NN43001-632). Verifying a successful configuration To ensure that ELAN and TLAN network interfaces on the Signaling Server are configured correctly, perform a ping test at each interface.
Connecting the MG 1000B Core to the network 245 Figure 88 Back of MG 1000B Core Connect to the 10BaseT ELAN network interface port 1, or, in the case of the MGC, the AUI port, that is connected to the Ethernet port on the motherboard. Use the AUI port with an Ethernet Media Attachment Unit (MAU) for the MGC. Port 2 and LED lights on both ports are for future use.
MG 1000B software installation Procedure 21 Configuring the ELAN network interface IP address Step Action To configure the active ELNK Ethernet interface for the Branch Office: 1 Go into LD 117. 2 Create host entries with IP address on the ELAN subnet. Enter the following command: NEW HOST 3 Configure the ELAN network interface subnet mask. Enter the following command: CHG MASK where = nnn.nnn.nnn.nnn 4 Configure a new Routing Entry.
Connecting the MG 1000B Core to the network 247 Procedure 22 Connecting the Ethernet ports Step Action To configure the TLAN and ELAN network interfaces at the MG 1000B Core and enable traffic over the LAN/WAN, connect the CAT5 cables and configure the data connectivity. 1 Insert the CAT5 cable into the RJ-45 10BaseT Port 1 or Ethernet MAU. Connect the other end of the CAT5 cable to the switch. For more information about the switch, see Converging the Data Network with VoIP Fundamentals (NN43001-260).
MG 1000B software installation • under SIP GW Settings (see Figure 90 "Confirm IP telephony node values SIP Redirect Server" (page 249)): — Primary Proxy/Redirect IP address — Primary Proxy/Redirect IP port — select Primary Proxy Supports Registration — Primary Proxy or Redirect server flag — Secondary Proxy/Redirect IP address (if equipped) — Secondary Proxy/Redirect IP port — select Secondary Proxy Supports Registration — Secondary CDS Proxy or Redirect server flag To configure a Follower Signaling
Installing MG 1000B Hardware 249 Figure 90 Confirm IP telephony node values SIP Redirect Server Installing MG 1000B Hardware To upgrade the hardware for an Option 11C Chassis, perform the following steps: • Power down the chassis. • Remove the SSC card as described in Procedure 3. • Destroy or return the SSC security device to your local Nortel Repairs/ Returns center. • Install the DSP Daughterboard on the MGC card as described in Installing a DSP Daughterboard.
MG 1000B software installation Installing the cards The following sections describe the process required to install the MGC and CP PM cards. Removing the SSC card Step Action 1 Unlatch the SSC card. 2 Remove the SSC card from its slot. ATTENTION The SSC card should be preserved for a minimum of five days. It is illegal to continue to run the system software on the existing SSC card. Please DESTROY or RETURN the SSC dongle to your local Nortel Repairs/Returns center.
Installing MG 1000B Hardware 251 Figure 91 DSP Daughterboard Installing a DSP Daughterboard Step Action 1 Place the MGC on a safe ESD surface. 2 Place the DSP Daughterboard in either Daughterboard position 1 (for DSP DB-96) or Daughterboard position 2 (for DSP DB-32), depending on how the Daughterboard will be configured from a TN perspective. 3 Ensure the DSP Daughterboard is securely attached to the MGC. (using supplied screws).
MG 1000B software installation Installing the MGC card Step Action 1 Insert the MGC into Slot 0 of the Chassis. ATTENTION You must ensure that all dongles (for both MGC and CP PM cards) are correctly identified. Please DESTROY or RETURN the SSC dongle to your local Nortel Repairs/Returns center. For the MGC card and the CP PM call server, you must use the dongles provided in the software kit. Chassis Expander dongles may be disposed of, as they are no longer needed.
Installing MG 1000B Hardware 253 —End— The preceding steps enable users to upgrade the system one MG 1000B at a time. For each additional IPMG, repeat Procedure 3 (Removing the SSC card) to Procedure 5 (Installing the CP PM card). Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
MG 1000B software installation Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Branch Office configuration Contents This section contains information on the following topics: "Configuring the Branch Office" (page 255) "Summary of steps" (page 255) "Configuring the Media Cards" (page 256) "Configuring the trunks and lines" (page 256) "Zone parameters" (page 256) "Adding the Branch Office endpoints to the NRS database" (page 260) Configuring the Branch Office After connecting the MG 1000B Core to the network and configuring the system user names and passwords (see "MG 1000B softwa
Branch Office configuration —End— Configuring the Media Cards The Media Cards (see Figure 73 "Media Card" (page 228)) arrive at a customer location with pre-installed software. To install and upgrade these cards, you need the latest workfile. The workfile is delivered by the PC card or Element Manager and contains all Media Card operating system and application files. The workfile is a single packed and compressed file.
Zone parameters 257 Procedure 23 Configuring the MG 1000B zone Step Action WARNING Before and after an upgrade, perform a datadump (using LD 43 EDD or NRS Manager) on the CPPM or MGC to back up the existing data. 1 Set the current date and time. See Software Input Output Administration (NN43001-611). LD 2 Define system date.
Branch Office configuration 3 Configure Vacant Number Routing (VNR). VNR must be configured at the Branch Office. When a Branch User is in Normal Mode, a call to that user arriving at the Branch Office will be routed to the main office. VNR at the Branch Office and the NRS configuration identifies the main office as the endpoint for that user. VNR is routed through the Virtual Trunk. This enables the NRS to centralize Numbering Plan definitions.
Zone parameters 259 ATTENTION IMPORTANT! Zone 0, the default zone, must not be configured as a Branch Office zone. Network Bandwidth Management does not support zone 0. If zone 0 is configured as a Branch Office zone, the Network Bandwidth Management feature will not be activated. LD 117 Define zone properties at the Branch Office.
Branch Office configuration 5 Configure the parameters for IP Phone passwords and modifications. This procedure is outlined in "IP Phone passwords and parameters" (page 215). —End— Element Manager Branch Office zone configuration Figure 92 "Branch Office-specific Zone Basic Property and Bandwidth Management" (page 260) shows the only zone configuration screen required at the Branch Office. It is an alternative to zone configuration using LD 117.
Adding the Branch Office endpoints to the NRS database 261 the BUID points to both the Branch Office and the main office. However, there may be situations where a separate BUID may be required, such as in a Multiple Appearance DN (MADN) configuration. In this case, the separate BUID may not be a public DN and explicit configuration is required. The BUID must be added to the numbering plan to point to the main office.
Branch Office configuration Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
MG 1000B telephones Contents This section contains information on the following topics: "Overview" (page 263) "Installing and configuring IP Phones" (page 264) "Password requirements" (page 265) "Installing an IP Phone using the keypad" (page 265) "Branch User Config" (page 270) "Transferring IP Phone data using TM 3.
MG 1000B telephones • Analog (500/2500-type) telephones and devices – "Analog devices" (page 288) • Digital telephones and devices – "Digital devices" (page 288) This chapter provides information on installing and configuring IP Phones, analog devices, and digital devices at the Branch Office. Installing and configuring IP Phones All MG 1000B IP Phones must be configured in the main office on the main office Call Server (see "MG 1000B IP Phone configuration" (page 218)).
Installing and configuring IP Phones 265 At the Branch Office, under a Branch User registration request (plugging an IP Phone into a jack), the main office Call Server checks the configured terminal type against the IP Phone type and configuration. This check occurs at the Branch Office. At the main office, under a Branch User registration request, the main office Call Server checks for a match of the configuration to the IP Phone type. If they do not match, registration is blocked.
MG 1000B telephones Step Action 1 Connect the IP Phone to an Ethernet jack and configure the S1 IP address (or use Dynamic Host Control Protocol (DHCP) to retrieve the IP address). The S1 IP address is the IP address of the MG 1000B TPS. If it is entered as the main office TPS, the IP Phones register to the main office, but do not behave as MG 1000B IP Phones.
Installing and configuring IP Phones 267 2002 have a one-line display. The IP Phone 2004, IP Phone 2007 and IP SoftPhone 2050 have a three-line display. Users can scroll through the display screens using the navigation keys. Procedure 24 Using Set-Based Installation Step Action This procedure installs IP Phones at the Branch Office and main office. If necessary, the administrator can perform a Set-Based Installation when the Branch User is in Local Mode.
MG 1000B telephones Figure 95 Set-Based Installation Step 3 4 Lift the handset and listen for the continuous dial tone. The Model prompt is displayed as shown in Figure 96 "Set-Based Installation Step 4" (page 268). Figure 96 Set-Based Installation Step 4 5 Press the # key to select the default model, or enter the model number and press #. 6 Listen for a special tone. The prompt appears as shown in Figure 97 "Set-Based Installation Step 6" (page 268).
Installing and configuring IP Phones 269 Figure 98 Set-Based Installation Step 7 8 Replace the handset when you hear a relocation tone and see "OK" on the screen display. 9 The IP Phone is now registered with the Call Server. Wait approximately ten seconds for the key map download to complete. The IP Phone is now fully operational in Local Mode. The screen appears as shown in Figure 99 "Set-Based Installation complete" (page 269).
MG 1000B telephones Branch User Config To complete the interface-based configuration of the Branch User, the administrator or a trusted user can configure the IP Phone with the Branch User Config command. Before proceeding, be sure to obtain the required passwords as described in "Password requirements" (page 265). If the Branch User ID (BUID) is not configured, the IP Phone registers at the MG 1000B CP PM and stays in Local Mode.
Installing and configuring IP Phones • 271 Main office password — IP Phone Installer’s Password, Temporary IP Phone Installer’s Password, or SCPW. For information on setting up passwords, see "IP Phone passwords and parameters" (page 215). Branch User Config is used for configuration. Once the IP Phone is configured at the Branch Office, its parameters redirect the IP Phone to the main office.
MG 1000B telephones Figure 101 Branch User ID 4 Enter the branch password, that is the IP Phone Installer’s Password or Temporary IP Phone Installer’s Password for the TPS node at the Branch Office. See Figure 102 "Branch password" (page 272). Figure 102 Branch password 5 To enter the Main Office TN: • Choose Select to accept the default Main Office TN on the display. • Enter the Main Office TN in a Large System format (four fields), and press Select.
Installing and configuring IP Phones 273 Figure 103 Main Office Terminal Number 6 Enter the IP Phone Installer’s Password, Temporary Internet Installer’s Password for the main office, or the SCPW for the Main Office TN. See Figure 104 "Main office password" (page 273). Figure 104 Main office password Following entry of this data, the IP Phone is taken offline and the display shows "Locating Remote Server". The IP Phone registers with the main office and becomes operational.
MG 1000B telephones CAUTION Network Problems During Installation: Setup: The IP Phone in the Branch Office is on a different subnet to the MG 1000B TPS and has a different route to the main office. The MG 1000B TPS can connect to the main office but the IP Phone cannot. Symptom: The terminal registers to the MG 1000B TPS and is redirected to the main office (displaying the "Locating Remote Server" message).
Installing and configuring IP Phones 2 3 4 5 6 Configure the report file in the Customize a Report page: • Under Field Selection, choose fields that have been configured in the IP Phone. • Under Custom Criteria, enter criteria SYNCSTATUS = Transmitted. • Under Report Format, choose CSV. • Under Format Options, enter a file name. • Under Save Report Definition, enter a report name. • Click Save to save the report configuration. Generate the report file.
MG 1000B telephones • Enter search criteria Sync Status = All and click Search. • All the imported telephones are listed, click on a few telephones to verify the attributes. • Select all the telephone(s) imported and clickTransmit to synchronize with the PBX and test appropriately. —End— Survivability test This section pertains to IP Phones installed at a Branch Office. When LAN/WAN connectivity is lost, the IP Phones reboot and are registered at the MG 1000B Call Server.
Installing and configuring IP Phones 277 A Branch User Identification (BUID) and Main Office TN (MOTN) can be provisioned, if the Internet telephone belongs to a MG 1000B Branch Office. The local TN configured for the Branch Office set with CS 1000 Release 5.0 accepts a four-field format. This prompt accepts TN’s in two or four-field format. If nothing is entered for the BUID, then the set does not get automatically redirected to the Main Office.
MG 1000B telephones LD 20 printing of the IP Phone TN Block with CS 1000 Release 5.0 MG 1000B with MGC shows the TN entered as four-field format, with the matching MOTN TN as four-field format, shown in the following example: Refer to "Test Local Mode" (page 286) for details on testing Local Mode functionality. Procedure 26 Testing the telephone for survivability Step Action Test the survivability of the connections and functions using the Test Local Mode command on the MG 1000B IP Phone.
Installing and configuring IP Phones 279 c. Press the Select soft key. This reregisters the telephone at the main office. If Resume Normal Mode is not selected, the IP Phone automatically returns to Normal Mode after ten minutes. —End— Installing IP Phones through LD 11 To use the Virtual Office feature at the Branch Office in Local Mode, a Station Control Password must be configured.
MG 1000B telephones The BUID, or primary DN, of an MG 1000B IP Phone should match its primary DN at the main office, though this is not a requirement. If different DNs are configured, the dial-in numbers change when the Branch Office is in Local Mode. WARNING Do not delete the BUID/MOTN. If they are subsequently deleted, the association between the main office and the Branch Office will be lost, and any IP Phones which are in, or go into, Local Mode, will remain in Local Mode.
Using the IP Phones 3 281 (Optional) Disallow usage of Virtual Office. For more information on the Virtual Office feature, refer to Features and Services Fundamentals (NN43001-106-B1). LD 11 Enable/disable Virtual Office (optional). Prompt Response Description REQ: NEW CHG Add new data, or change existing data. TYPE: a...a Terminal type. Type ? for a list of possible responses. CLS (VOLA) VOLD Allow Virtual Office operation from this TN. Deny Virtual Office operation from this TN.
MG 1000B telephones Changing the SCPW Use Procedure 27 "Installing IP Phones through overlays" (page 279) to change the SCPW of a telephone at any time. Procedure 28 Changing the SCPW Step Action 1 Dial the SCPC code followed by the current Station Control Password. An FFC tone is given at this point. 2 Enter the new password. The new password must be the same length as SCPL. 3 Wait for the FFC tone and enter the new password again. If the new password is accepted, another FFC tone is given.
Using the IP Phones 283 Figure 106 Options menu The Virtual Office Login option only appears if VOLA CLS is configured. 2 Use the navigation keys to highlight Telephone Option. 3 Press the Select soft key to activate the feature. 4 Use the Up or Down keys to select an option. The available options will differ depending on the type of IP Phone in use.
MG 1000B telephones Virtual Office Login on the Branch Office The Virtual Office Login feature is described in IP Phones Fundamentals (NN43001-368). Procedure 30 Using the Virtual Office Login feature Step Action This procedure explains how to log in to and log out of Virtual Office. The IP Phone has been configured using Branch User Config and is operating in Normal Mode or Local Mode. 1 Press the Services key (the key with the Globe icon).
Using the IP Phones 285 b. Use the navigation keys to highlight Virtual Office Logout. See Figure 108 "Virtual Office application menu" (page 285). Figure 108 Virtual Office application menu c. Press the Select soft key. —End— Feature interactions between Branch User and Virtual Office logins When an MG 1000B IP Phone user travels to the main office or another network location, the user can access their own Main Office TN from an IP Phone at the visited location by using the Virtual Office feature.
MG 1000B telephones 2. Press the Virtual soft key to activate Virtual Office Login. In either case, the user is prompted for the User ID and the SCPW. When a Branch User IP Phone re-powers, it registers with the MG 1000B Call Server, and is automatically redirected to the main office.
Set-Based Removal 287 Figure 110 Resume Normal Mode The Virtual Office Login option only appears if VOLA CLS is configured. b. Use the Navigation keys to highlight Resume Normal Mode. c. Press the Select soft key. —End— If you fail to resume Normal Mode, Test Local Mode lasts for ten minutes, and then automatically redirects the telephone to the main office Call Server.
MG 1000B telephones Procedure 32 Using the Set-Based Removal feature Step Action When the Automatic Set Removal (AREM) feature is enabled and you have a Set Relocation Security Code (SRCD), follow these steps: 1 Lift the handset or press the DN key of the IP Phone to be removed. 2 Key in the AREM code after hearing the dial tone. 3 Enter the SRCD. 4 Hang up, or press the Release key.
Analog and digital devices in the Branch Office 289 Digital telephones at a Branch Office can be configured using: • Set-Based Installation (not for M3900-series telephones) • Overlays (locally or remotely through a modem or Ethernet connection). For more information, see Procedure 27 "Installing IP Phones through overlays" (page 279). • TM 3.01 Digital devices supported by the Branch Office feature include digital telephones, consoles, and a CallPilot Mini or CallPilot 201i.
MG 1000B telephones Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Dialing plan configuration Contents This section contains information on the following topics: "Overview" (page 291) "Introduction" (page 292) "Dialing plans" (page 292) "Routing" (page 294) "SIP/H.
Dialing plan configuration This section primarily describes the configuration of a dialing plan for off-net calls from MG 1000B IP Phones in Normal Mode. However, the procedures in this chapter are also applicable when configuring on-net UDP dialing for these telephones, if a single Access Code is used for both UDP and some or all off-net calls. Introduction The Branch Office feature is versatile enough to provide solutions for a wide variety of applications which require different dialing plans.
Introduction 293 select trunks at the main office, Branch Office, or other branch offices as required. Therefore, the user can route calls to gateways that minimize long-distance costs, minimize bandwidth usage, or meet other criteria.
Dialing plan configuration The NRS replies with the address information for E.164 numbers. It also provides a list of alternative SIP or H.323 endpoints, sorted by cost. If a terminating endpoint resource is busy when a call attempt is made, the originating endpoint tries the next alternative. If no alternative is available over the IP network, the originating endpoint steps to the next entry on its route list, which could be a TIE or PSTN alternate route.
Zone-based digit manipulation 295 Bandwidth management zones An IP Peer network is divided into different bandwidth management zones. Each IP Phone, Virtual Trunk, or Voice Gateway DSP channel is assigned to a bandwidth management zone.
Dialing plan configuration By performing this zone-based digit manipulation, calls from main office users and Branch Users undergo different routing.
Configuring the dialing plan for PSTN access to Branch Users in Normal Mode 297 If ISPN is YES, the CLID is formed based on the call-type before digit manipulation. INST digits are inserted, and the CLID is considered an IP Special Number. The call-type before digit manipulation is determined as follows: • If the call-type before digit manipulation is SPN (Special Number), it is converted to a value corresponding to the CLTP parameter in the Special Number Translations data block, as shown in Table 21.
Dialing plan configuration • At the main office, configure the Branch Office zone properties in LD 117, excluding the ZACB and ZDP properties. Refer to IP Peer Networking Installation and Commissioning (NN43001-313) for details. • At the main office, configure the routing for PSTN access. • At the Branch Office, configure the routing to enable calls made from TDM or IP Phones in Local Mode to access the PSTN. • At the Branch Office, configure Vacant Number Routing (VNR).
Configuring the dialing plan for PSTN access to Branch Users in Normal Mode 299 A sample configuration is given in Appendix "Off-net dialing plan configuration example" (page 405). Procedure 33 Configuring the main office Step Action 1 Configure the ZACB property for the Branch Office zone. LD 117 Define the zone Access Code handling for the Branch Office zone.
Dialing plan configuration dials "2 87654321", zone-based digit manipulation does not occur and the digit string remains unchanged. • CHG ZACB AC2 AC2 In this configuration, only calls dialed with AC2 undergo zone-based digit manipulation. All Branch User calls dialed with AC2 can then be routed to the MG 1000B PSTN. For example, assume that AC1 = 1, AC2 = 2, and ZDP = 101. If a Branch User dials "1 87654321", zone-based digit manipulation does not occur and the digit string remains unchanged.
Configuring the dialing plan for PSTN access to Branch Users in Normal Mode 301 digit manipulation occurs before any digit processing in the main office Call Server or NRS. If DialingCode1, DialingCode2, or DialingCode3 are already present in the dialed digits, then they will not be re-inserted. Nortel recommends that the ZDP attribute for each Branch Office zone be set to a unique non-dialable number within the dialing plan (for example "1019" or "999").
Dialing plan configuration a. Configure the DMI in LD 86 with the DGT feature. LD 86 Configure the Digit Manipulation Index at the main office. Prompt Response Description REQ NEW Add new data. CUST xx Customer number as defined in LD 15. FEAT DGT Digit manipulation data block DMI 1-999 Digit Manipulation Index numbers The maximum number of Digit Manipulation tables is defined at the MXDM prompt in LD 86. DEL (0)-19 Number of leading digits to be deleted, usually 0 at the main office.
Configuring the dialing plan for PSTN access to Branch Users in Normal Mode Prompt Response 303 Description ROUT Route number of the Virtual Trunk as provisioned in LD 16. 0-511 Range for Large System and CS 1000E system 0-127 Range for Small System and Media Gateway 1000B 1-999 Digit Manipulation Index number as defined in LD 86, FEAT = DGT (see Step a). ...
Dialing plan configuration Prompt Response Description SPN x…x Special Number translation Enter the SPN digits in groups of 3 or 4 digits, separated by a space (for example, xxxx xxx xxxx). The SPN can be up to 19 digits long. The maximum number of groups allowed is 5. - FLEN (0)-24 Flexible Length The number of digits the system expects to receive before accessing a trunk and outpulsing these digits.
Configuring the dialing plan for PSTN access to Branch Users in Normal Mode 305 (ZDP + two dialed digits), a maximum of 100 SPNs must be configured for each Branch Office. For each additional dialed digit included in the SPN, the maximum number of SPNs that must be provisioned for each Branch Office is increased by a factor of ten.
Dialing plan configuration Procedure 34 Configuring the NRS database Step Action After configuring main office routing to the NRS, the NRS database must be provisioned to identify the desired endpoint for the calls. This procedure configures the NRS database with the inserted digits specified by the zone-based digit manipulation configuration. Instead of configuring the NRS database, you can configure a route in the main office to directly route the call (see Step 4).
Configuring the dialing plan for PSTN access to Branch Users in Normal Mode 307 Figure 112 NRS Lookup path for gateway endpoints Figure 113 NRS Routing Entries window for selected endpoint 7 Click Add in the Routing Entries window to add a routing entry. The Add Routing Entry window opens, as shown in Figure 114 "NRS Add Routing Entry" (page 307). Figure 114 NRS Add Routing Entry 8 Configure the numbering plan entries for the Branch Office.
Dialing plan configuration If some calls are to be routed differently from others, it is possible to provision the multiple Numbering Plan Entries in the NRS to achieve this. For example, if ZDP = 101, it is possible to provision multiple Numbering Plan Entries (101, 1011, and so on) to route calls based on the ZDP value or the ZDP value plus some of the dialed digits.
Configuring the dialing plan for PSTN access to Branch Users in Normal Mode Prompt Response Description DEL (0)-19 Number of leading digits to be deleted. This would normally be configured to remove the unique non-dialable number that identifies the Branch Office, configured in the ZDP property of the Branch Office zone in LD 117 at the main office (Step 2). ISPN NO IP Special Number INST x…x Insert. Up to 31 leading digits can be inserted. CTYP Call type used by the call.
Dialing plan configuration For example, assume that the PSTN trunk is on route 18 and the Customer number = 0. >LD REQ CUST FEAT DMI 86 NEW 0 DGT 18 Set to remove ZDP added in the main office DEL 3 INST CTYP CUST FEAT RLI ENTR LTER ROUT … DMI … 2 LOCREQ 0 RLB 18 0 NO 18 NEW Set according to associated SPN pattern 18 Configure ESN Special Number and Digit Manipulation. LD 90 Configure ESN Special Number and Digit Manipulation. Prompt Response Description REQ NEW Add new data.
Configuring the dialing plan for PSTN access to Branch Users in Normal Mode 311 After configuring the specialized route for calls that have been routed to the Branch Office by the NRS, the route must be associated with the ESN Special Number. The Branch Office will receive the manipulated number as an incoming call, indicating that the ZDP value added at the main office is at the beginning of the number.
Dialing plan configuration Figure 115 Zone Dialing Plan and Access Codes Testing PSTN access using an MG 1000B IP Phone Use Procedure 36 "Testing PSTN access using an MG 1000B IP Phone" (page 312) to test that PSTN access is working correctly. Procedure 36 Testing PSTN access using an MG 1000B IP Phone Step Action 1 From an MG 1000B IP Phone in Local Mode (use Procedure 31 "Using the Test Local Mode feature" (page 286) if necessary): a. Make a local PSTN call. b. Make a long-distance call.
Testing PSTN access using an MG 1000B IP Phone 313 For calls that tandem over the Virtual Trunk to the Branch Office and go out to the PSTN trunk(s) in the Branch Office, the following configuration problems can occur: • The call can receive overflow tones. Use LD 96 to view the digits sent to the Virtual Trunk (ENL MSGO {dch#}). • If the digits look correct at the main office, the NRS might not be properly configured.
Dialing plan configuration Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Emergency Services configuration Contents This section contains information on the following topics: "Overview" (page 315) "Emergency Services Access (ESA)" (page 316) "Routing ESA calls" (page 316) "Emergency call routing" (page 316) "PSTN routing: Enhanced 911 versus Basic 911" (page 316) "Configuring ESA for the Branch Office" (page 317) "Reregistering to minimally configured branch" (page 318) "Element Manager ESA configuration" (page 326) "Emergency Service using Special Numbers (SPN)" (page 327)
Emergency Services configuration Either of these methods have a Branch Office implementation which triggers the main office Call Server to forward emergency services calls to the MG 1000B PSTN. Calls are redirected over a Virtual Trunk using the services of the NRS. Emergency Services Access (ESA) Routing ESA calls ATTENTION IMPORTANT! Do not route ESA calls to a node that has no direct ESA trunks.
Emergency Services Access (ESA) 317 The Selective Router looks up the caller’s ANI in its Selective Routing Data Base (which is synchronized with the ALI database) to determine the correct PSAP and then routes the emergency call appropriately. Hence, the call can be routed to any CO in the correct E911 Tandem area. The Selective Router automatically routes the call to the appropriate PSAP based on the ANI. In areas that support Basic 911, the route to the PSAP is determined by the PSTN access point.
Emergency Services configuration 13 Configure the Branch Office zone on the Branch Office. 14 Configure the ESN SPN on the Branch Office. 15 Configure the NRS for the ESA Special Number used. 16 Test ESDN using an MG 1000B IP Phone. 17 Test ESDN using an analog (500/2500-type) or digital telephone located at the Branch Office. —End— Reregistering to minimally configured branch A Branch User in Local Mode but not physically at the branch may get incorrect emergency service handling.
Emergency Services Access (ESA) 319 The basic ESA feature only provides for a single ESA route per system. Since all IP Phones are associated with the same main office, all ESA calls therefore go to the same Public Safety Answering Point (PSAP) regardless from which Branch Office they originated. This is not satisfactory if the branch offices are widely dispersed. In general, ESA calls should leave the network through a trunk at the Branch Office where the originating telephone is located.
Emergency Services configuration ESA uses a route number rather than ESN route list index. However, ESN is required at the Branch Office. 4 Configure Emergency Services Access (ESA) in LD 24. Configure an ACD number as an Emergency Services Directory Number. LD 24 Configure Emergency Services Access. Prompt Response Description REQ NEW CHG Add new data, or change existing data.
Emergency Services Access (ESA) 321 Description Command • ESA Route # = Virtual Trunk route to MG 1000B Core. • AC = Access Code to add to dialed digits. If no AC is required, AC0 is to be entered in place of AC1 or AC2. • ESA Prefix = Digit string added to start of ESDN. This is a unique prefix in the NRS. Nortel recommends that users use "0" + ESN location code of the Branch Office node. An example for location code 725 would be: 0725.
Emergency Services configuration Prompt Response Description DMI is only prompted when the Directory Number Expansion (DNXP) package 150 is equipped and SDRR = LDID. The maximum number of Digit Manipulation tables is defined by prompt MXDM. DMI is not prompted if route TKTP = ADM. DEL (0)-19 Number of leading digits to be deleted INST x…x Insert. Up to 31 leading digits can be inserted. CTYP Call type to be used by the manipulated digits.
Emergency Services Access (ESA) Prompt Response Description FEAT NET Network translation tables TRAN Translator AC1 AC2 Access Code 1 (NARS/BARS) Access Code 2 (NARS) TYPE SPN Special code translation data block SPN x…x Special Number translation Enter the SPN digits in groups of 3 or 4 digits, separated by a space (for example, xxxx xxx xxxx). The SPN can be up to 19 digits long. The maximum number of groups allowed is 5.
Emergency Services configuration 7 Test ESDN using a main office telephone to confirm that main office calls go out the main office trunks. If OSDN is used, the ESA route number must be blank to make test calls without using any trunk resources. It the route number has been configured, remove it by entering "x" at the prompt. —End— Procedure 38 Configuring the Branch Office Step Action You can use Element Manager or the Command Line Interface for this procedure.
Emergency Services Access (ESA) 325 —End— Procedure 39 Configuring the Branch Office zone Step Action 1 Configure the Branch Office zone on the Branch Office. In the Branch Office, only the zone number and bandwidth/codec selection is configured. Use the same zone number between the Branch Office and main office. The main office configuration (Procedure 37 "Configuring the main office" (page 319), step 5) provides the Branch Office zone characteristics (local time, local dialing, and ESA).
Emergency Services configuration Procedure 40 Testing ESDN using an MG 1000B Telephone Step Action 1 For IP Phones: a. Dial the ESDN on an MG 1000B IP Phone in Local Mode. Use Procedure 31 "Using the Test Local Mode feature" (page 286) to enter Local Mode. The calls must go out on the emergency trunks in the Branch Office. b. Dial the ESDN on an MG 1000B IP Phone in Normal Mode. The calls must tandem over the Virtual Trunk to the Branch Office and go out on the emergency trunks in the Branch Office.
Emergency Service using Special Numbers (SPN) 327 Figure 116 Zone Emergency Service Information Emergency Service using Special Numbers (SPN) Determining the dialing plan for emergency access calls is critical. In many jurisdictions, the emergency number is a fixed number (for example, "112" or "999"). The call processor (main office Call Server or MG 1000B CP PM) cannot have a DN that conflicts with these digits.
Emergency Services configuration CLID verification (CLIDVER) Use the CLIDVER prompt in LD 20 to verify that the ESA or non-ESA (SPN) emergency number is properly composed and configured. Refer to "Verify CLID" (page 355) for more information. Networked M911 The Networked M911 feature introduces a new trunk subtype 911P exclusively for 911 calls redirected over an MCDN Network. A new prompt, 911P, is introduced in the Route Data Block for TIE trunks only.
Basic Emergency Services When VO Logged Out Contents "Overview" (page 329) "Making an ESA Call From a Logged Out Phone" (page 330) "Receiving ESA Callback" (page 330) "ESA Call Processing" (page 330) "CLID Composition" (page 331) "ESA VO Logout Timer" (page 331) "Provisioning, Administration and Maintenance" (page 332) "Keeping Logged Out State" (page 332) "Configure ESA Data Block" (page 333) "Sysload" (page 333) "Warm Start" (page 333) "Emergency Services For Client Mobility" (page 333) "Active Call
Basic Emergency Services When VO Logged Out New functionality is introduced: to provide the ability for the logged out phone to make ESA calls and receive callbacks, temporarily register with the Call Server. The registration begins as the user tries to make a call from the logged out phone by going off hook or pressing the primary key, or using the handsfree or headset.
Contents 331 • CPND block: uses the English string VOLO and is automatically configured against the primary key of all the emergency TNs. • DES: All the emergency TNs have the ESTN designator. • DN: The emergency DN configured by administrator. The primary DN, that is configured by the administrator, is sent to the OSN phone/terminal, so that callback to this phone is possible. CLID Composition In Release 4.5 and earlier, the CLID configuration is static.
Basic Emergency Services When VO Logged Out • If the timer expires but the phone is involved in a call, the time out event is ignored. When this call is finished, the 20 minute timer reloads. Provisioning, Administration and Maintenance The Basic Emergency Services When VO Logged Out feature is provisioned like follows: Step Action 1 First, specify the number of emergency TNs in the pool and specify the range of the emergency pool in LD 24. 2 Then go to LD 11 and configure emergency TNs.
Contents 333 The use case Scenario: Keep Logged Out State provides the requirement to prevent the logged out phone registered with the Call Server for ESA from reregistering. When this scenario occurs, the VOLO phone will sustain it’s Awaiting Callback state until the ESAVOLO timer expires, and returns to it’s original Logged Out state, to give you the chance to go back to normal registration by using the soft key provided.
Basic Emergency Services When VO Logged Out The call to PSAP occurs immediately after the set registers, requiring the correct location information; This is not desired. Special handling may be required, possibly by directly calling background LIS for the VOLO TN. Active Call Fail Over Interactions with Active Call Fail over can be considered under the following possible scenarios: • ELAN failure happens for less than 10 minutes: — The ESA VOLO phone is on a call.
Contents 335 Element Manager CS 1000 Release 5.0 Element Manager supports the following configuration, provisioning and maintenance aspects of the Basic Emergency Services When VO Logged Out Feature. • Configuration: Changes in ESA data block in LD 24. • Diagnostics: A new command PRT ESALO is added in LD 117. Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Basic Emergency Services When VO Logged Out Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Abbreviated Dialing configuration Contents This section contains information on the following topics: "Overview" (page 337) "Recommended configuration" (page 337) "Configuring Abbreviated Dialing" (page 338) Overview With Abbreviated Dialing, IP Phone users in the same geographic location, either the main office or the Branch Office, can call one another using a DN shorter than the configured DN. This feature is implemented with a pretranslation group assigned to every telephone.
Abbreviated Dialing configuration • Each bandwidth management zone has a unique pretranslation group number assigned to it. • CLID of calls going to the public network (E.164/PSTN) are converted to the shorter DN by removing the digits added during pretranslation. • Additional digits can still be added to the outgoing calling party number (the shortened DN) using CLID capabilities.
Configuring Abbreviated Dialing 339 Procedure 41 Configuring Speed Call List (SCL) Step Action 1 In LD 18, configure the SCL for each main office zone. LD 18 Configure Speed Call Lists (SCL) for each zone.
Abbreviated Dialing configuration Procedure 42 Configuring Pretranslation Groups Step Action While not required, it is recommended that the Pretranslation Group number (XLAT) be the same as the number of the zone to which it is assigned. 1 In LD 18, configure the Pretranslation Group for each main office zone. LD 18 Configure Pretranslation Group for each zone. Prompt Response Description REQ NEW Add new data. TYPE PRE Pretranslation Group XLAT 1-8191 Group number.
Configuring Abbreviated Dialing 341 —End— Procedure 43 Assigning Pretranslation Groups to the telephones Step Action The Pretranslation Group must be assigned to all IP Phones and TDM telephones. This procedure describes how to configure a single telephone, and it must be repeated for each telephone in the group. The global change utility in TM 3.01 can be used to configure all TDM telephones in the group at one time. For details, see Telephony Manager 3.0: System Administration (NN43050-601)..
Abbreviated Dialing configuration Procedure 44 Configuring Incoming DID Digit Conversion (IDC) Step Action 1 In LD 15, configure Flexible Code Restriction for IDC. LD 15 Configure Flexible Code Restriction (FCR) for Incoming DID Digit Conversion. Prompt Response Description REQ: CHG Change existing data. TYPE: FCR Flexible Code Restriction YES Enable new Flexible Code Restriction. IDCA YES Incoming DID Digit Conversion allowed. - DCMX 1-255 Maximum number of IDC conversion tables.
Configuring Abbreviated Dialing 3 343 In LD 49, configure Flexible Code Restriction to allow all codes. LD 49 Configure Flexible Code Restriction (FCR). Prompt Response Description REQ NEW Add new data. TYPE FCR Flexible Code Restriction CRNO (0)-254 Code Restriction tree number INIT ALOW Allow all codes ... 4 In LD 16, configure the Route Data Block to enable IDC on this route. LD 16 Configure Route Data Block. Prompt Response Description REQ CHG Change existing data.
Abbreviated Dialing configuration Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Maintenance and diagnostics Contents This section contains information on the following topics: "Firmware downloads" (page 345) "Troubleshooting" (page 349) "Signaling Server CLI commands" (page 354) "isetShow" (page 354) "clearLockout TN or IP" (page 354) "Call Server commands" (page 355) "Verify CLID" (page 355) "Print Branch Office zone information" (page 356) "Enable/disable Branch Office zone features" (page 357) "View status of Branch Office zone at main office Call Server" (page 357) "Change/pri
Maintenance and diagnostics The administrator enters umsUpgradeAll command at the main office. The firmware version on the Normal Mode Branch Office IP Phone is compared to the firmware policy of the main office. If the firmware is the same as the main office, no firmware update is required. If the firmware is different, the IP Phones are redirected to the Branch Office. The firmware files are transferred from the main office to the Branch Office by FTP.
Firmware downloads 347 The umsUpgradeAll command has no immediate impact on IP Phones that are logged in or out by Virtual Office. However, the firmware files may be upgraded, if required, when the Virtual Office session is terminated. For information on Enhanced UNIStim Firmware, refer to IP Line Fundamentals (NN43100-500). Each IP Phone that is redirected back to the Branch Office has its firmware version checked against the MG 1000B TPS firmware policy.
Maintenance and diagnostics 3 The Branch Office IP Phones that are in Normal Mode (for example, IP Phones registered to the main office Call Server) are checked to see if they require a firmware upgrade. If the IP Phones require a firmware upgrade, the IP Phones are redirected back to the Branch Office. 4 The Branch Office checks its own firmware version and compares it with the firmware version which is required by the IP Phone.
Troubleshooting 349 —End— Troubleshooting This section contains error messages and troubleshooting information for IP Phone operation. When a login is attempted and one of the messages provided in Table 26 "Normal Operation troubleshooting" (page 349) through Table 28 "Branch User Config troubleshooting" (page 351) appears on the telephone display, there can be more than one reason.
Maintenance and diagnostics Message Local Mode Invalid ID (1) Local Mode Invalid ID (2) Local Mode Invalid ID (3) Required FW Vers Probable Cause Actions Main office node is not registered as a SIP or H.323 endpoint to the NCS. Register the main office node to the NCS. Branch User ID endpoint is not in NCS database. Check NRS database and update as required. Incorrect Branch User ID configured. Correct Branch User ID configuration in Branch Office TN.
Troubleshooting Number Description 12 Branch User main office unreachable, 351 or Main office is not registered with the NRS as an endpoint. 13 Branch User main office User ID Unknown, or Branch User main office User ID and Main Office TN Combination does not exist, or IP Phone telephone type and Main Office TN telephone type do not match.
Maintenance and diagnostics Message Probable Cause Actions Invalid ID (2) Incorrect Branch User ID entered. Retry with correct Branch User ID. No Main Office TN associated with Branch User ID configured. Configure Main Office TN to associate with Branch User ID. Main Office TN associated with the Branch User ID and the programmed TN on the IP Phone does not match.
Troubleshooting 353 Message Probable Cause Actions Permission Denied (2) Incorrect Branch User ID entered. Retry with correct Branch User ID. IP Phone Installer’s Password at the main office TPS not configured or disabled and the Branch User ID is already assigned to a user in another Branch Office. Identify duplicate Branch User ID allocation, and make correction. Incorrect Branch User ID entered. Retry with correct Branch User ID.
Maintenance and diagnostics Message Probable Cause Actions Server Unreacha ble (1) Incorrect Primary or Alternate NRS IP address configured. Correct Primary or Alternate NRS IP address. Primary or Alternate NRS IP address unreachable from this endpoint. Check network configuration and update as required. NCS port number is not properly configured. Correct main office and MG 1000B NCS port numbers. NRS is down. Bring NRS into service. Link to NRS is down. Restore Link to NRS.
Call Server commands 355 The lockout affects the Virtual Office login or Branch User Config and lasts for one hour. This lockout does not survive re-registration of the IP Phone. However, the installation technician can issue the clearLockout command to clear the lockout for a particular telephone. This command has one parameter the TN or IP address of the telephone. Call Server commands This section contains LD commands on the Call Server applicable to the Branch Office feature.
Maintenance and diagnostics The CLIDVER report contains the CLID composed for the Branch User. If the report is generated on the main office Call Server, the CLID is composed as follows: • If ESA is enabled in the Branch Office, the CLID is the same as the value entered for the ESA Locator parameter in the CHG ZESA command in LD 117 (see Procedure 37 "Configuring the main office" (page 319), step 5).
Call Server commands 357 Description Command Print a table of Branch Office zone time adjustment properties entries. PRT ZTP [] Print a table of Branch Office zone time adjustment properties entries. Enable/disable Branch Office zone features LD 117 contains commands to enable and disable features for the Branch Office zones. LD 117 Enable/Disable Branch Office zone features. Description Command ENL ZBR [] [ALL] [LOC] [ESA] [TIM] Enable features for the Branch Office zone.
Maintenance and diagnostics ATTENTION IMPORTANT! The notification level for a Branch Office zone must be configured the same at both the main office and the Branch Office. LD 117 Change/print PVQ notification levels. Description Command CHG ZQNL ALL Change the notification level for all zones. CHG ZQNL Change the notification level for the specified zone. PRT ZQNL ALL Print a table of the notification level for all zones.
Call Server commands 359 To register all IP Phones at the CP PM, disconnect the LAN/WAN connection to the main office (not recommended) or individually log out the IP Phones from the main office. See "Test Local Mode" (page 286). LD 117 contains inventory commands. These commands include the registered IP Phones. LD 117 Print inventory. Command Description INV PRT Print STATUS, CARDS, SETS or ALL. INV GENERATE Generate inventory CARDS, SETS, ALL or ABORT.
Maintenance and diagnostics Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Appendix A Preprogrammed data Contents This section contains information on the following topics: "Introduction" (page 361) "Passwords and codes" (page 362) "Default numbering plan" (page 362) "First digits" (page 363) "Important extension numbers" (page 363) "Flexible Feature Codes" (page 364) "SDI ports" (page 364) "ESDI settings" (page 365) "Telephone tones" (page 366) "Trunk routes" (page 366) "System parameters" (page 367) "Customer data" (page 367) "Trunk models" (page 367) "Telephone models" (pa
Appendix A Preprogrammed data • "Default numbering plan" (page 362) • "Flexible Feature Codes" (page 364) • "SDI ports" (page 364) • "Trunk routes" (page 366) • "System parameters" (page 367) • "Customer data" (page 367) • "Trunk models" (page 367) • "Telephone models" (page 370) Passwords and codes Table 29 "Passwords and codes" (page 362) lists each function and its default password or code. The user may be prompted to change the password upon first entry.
Default numbering plan 363 outside this range. This arrangement enables the CS 1000E to automatically configure telephones. First digits Table 30 "Default numbering plan First digit" (page 363) shows the default numbering plan for a Branch Office.
Appendix A Preprogrammed data Flexible Feature Codes Many administrative procedures use Flexible Feature Code (FFC) data. Table 32 "Flexible Feature Codes" (page 364) lists the FFCs for the CS 1000E system.
SDI ports TTY Number Card Port 1 0 2 0 Use Configuration 0 MTC/SCH/BUG 1200/8/1/NONE 1 CTY 1200/8/1/NONE 365 Table 34 Pre-configured PTY ports TTY Number Card Port Use 14 0 0 MTC/SCH/BUG 15 0 1 MTC/SCH/BUG Modem port The pre-configured modem port enables the remote maintenance modem to be connected without additional system programming. This port is pre-configured as TTY 0 (port 0 on the MGC) and programmed for Maintenance (MTC), Service Change (SCH), and BUG messages.
Appendix A Preprogrammed data Setting Code USER CMS ENL NO Telephone tones The telephone tones in North America are as follows: • Dial tone: A continuous tone. • Special dial tone: Three beeps followed by continuous dial tone. • Overflow tone: Like a busy tone, except faster and higher. • Relocation tone: A short high-pitched beep that continues for 4 seconds, followed by silence.
Trunk models 367 Route Type Access Code Mode Interface 51 FEX 7151 ICT - 52 FEX 7152 OGT - Trunk routes marked with an asterisk (*) are configured to support Call Detail Recording (CDR) output. CDR is pre-configured in LD 16 as follows: CDR INC OAL AIA YES YES YES YES System parameters Table 37 "System parameters" (page 367) provides the default system parameter values for the system.
Appendix A Preprogrammed data supervision = YES.
Trunk models Mode WAT Card XUT DIP or DTN BIMP and TIMP LDR Wink Start Supv = YES DIP 3COM/900 8* LDR Wink Start Supv = YES DTN 3COM/900 1 GRD DIP 3COM/600 2 LOP DIP 3COM/600 3 GRD DTN 3COM/600 4 LOP DTN 3COM/600 5 GRD DIP 3COM/900 6 LOP DIP 3COM/900 7 GRD DTN 3COM/900 8 LOP DTN 3COM/900 Model Signaling 7* MUS XUT 1 3COM/600 AWR XUT 1 600/1200 RAN XUT 1 600/1200 PAG XUT 1 LDR DIP 3COM/600 2 OAD DIP 3COM/600 3 LDR DTN 3COM/600 4 OAD
Appendix A Preprogrammed data Mode Card Model Signaling DIP or DTN BIMP and TIMP FEX XUT 1 GRD DIP 3COM/600 2 LOP DIP 3COM/600 3 GRD DTN 3COM/600 4 LOP DTN 3COM/600 5 GRD DIP 3COM/900 6 LOP DIP 3COM/900 7 GRD DTN 3COM/900 8 LOP DTN 3COM/900 Telephone models Define four models (model# 20) for IP Phone 2001, IP Phone 2002, IP Phone 2004, IP Phone 1110, IP Phone 1120E, IP Phone 1140E, IP Phone 1150E, and IP Softphone 2050 with KEY 0 SCR, VOLA CLS, and VOUA CLS.
Appendix B Branch Office engineering example Contents This section contains information on the following topics: "Introduction" (page 371) "Assumptions" (page 372) "Calculations" (page 373) "Traffic" (page 373) "MG 1000B Core and MG 1000B Expander requirements" (page 375) "Bandwidth requirements" (page 377) "Branch Office conference engineering" (page 379) Introduction This chapter provides sample engineering calculations for a Branch Office with a CS 1000M or CS 1000E main office.
Appendix B Branch Office engineering example Assumptions Equipment characteristics Assume the Branch Office has the equipment characteristics provided in Table 39 "Equipment characteristics" (page 372). Table 39 Equipment characteristics Number Type 120 IP Phones 36 Analog (500/2500-type) telephones Traffic characteristics Assume the Branch Office has the traffic characteristics provided in Table 40 "Traffic characteristics" (page 372).
Calculations 373 Calculations Figure 119 "Branch Office traffic flow" (page 373) is a conceptual representation of an MG 1000B Core. An actual system could require different types and numbers of cards. Traffic Traffic calculations are based on the traffic flows shown in Figure 119 "Branch Office traffic flow" (page 373).
Appendix B Branch Office engineering example 2 Calculate the IP Phone traffic to analog (500/2500-type) telephones: Number of ATs x CCS for each AT x % of calls to ITs = IT traffic to analog (500/2500-type) telephones 36 x 5 x 0.
Calculations 375 MG 1000B Core and MG 1000B Expander requirements Table 41 "MG 1000B Core and MG 1000B Expander card type, number and devices" (page 375) shows the number of cards required and the devices on those cards.
Appendix B Branch Office engineering example 252 x 100 ÷ 120 = 210 calls 3 Calculate the IP Phone to analog (500/2500-type) telephones: IT to AT CCS x 100 seconds ÷ average hold time = IT to AT calls 108 x 100 ÷ 120 = 90 calls 4 Calculate the analog (500/2500-type) telephone to Virtual Trunks (IPPT) calls: AT to IT CCS x 100 seconds ÷ average hold time = AT to IPPT calls 72 x 100 ÷ 120 = 60 calls 5 Calculate the Call Server loading in EBC: IT to IT calls x (1+f1) + IT to MOR calls x (1+f2) + IT to
Calculations 377 Bandwidth requirements Bandwidth requirements in this section refer to the information in Table 42 "Full Duplex Ethernet bandwidth for one channel (one Erlang)" (page 377), Table 43 "Traffic capacity at P.01, P.005, and P.001 GOS" (page 377), and Table 44 "LAN/WAN bandwidth for one channel (one Erlang)" (page 377). Table 42 Full Duplex Ethernet bandwidth for one channel (one Erlang) CODEC Payload Full Duplex Ethernet G.711 10 ms 126 kbit/s G.711 20 ms 95 kbit/s G.
Appendix B Branch Office engineering example 1 Calculate the data rate: Total traffic in Erlangs (from Page 439) x 95 kbps 22 x 95 kbps = 2090 kbps = 2.09 Mbps One Erlang of TDM 64 kbps channel becomes 95 kbps packets after G.711 codec transcoding, which adds overhead. See Table 44 "LAN/WAN bandwidth for one channel (one Erlang)" (page 377) if another type of codec is used. Requirement: TLAN subnet bandwidth 2.
Calculations 379 = 333 kbps Refer to Table 44 "LAN/WAN bandwidth for one channel (one Erlang)" (page 377) for other codecs or payload sizes. —End— Branch Office conference engineering With no local conference Two parties at a Branch Office using IP Phones call each other. They conference-in a third party from the same Branch Office. The conference calls use a LAN/WAN to reach the Conference Bridge at the main office.
Appendix B Branch Office engineering example LAN/WAN kbps = TCON (erlangs) x 37 kbps —End— Procedure 52 Calculating known conference traffic Step Action When a Branch Office is known or expected to make a significant number of conference calls, traffic statistics should be collected or estimated. Use the statistics to calculate LAN/WAN bandwidth requirements.
Calculations 381 Procedure 53 "Calculating Branch Office traffic, and LAN/WAN bandwidth without local messaging (CallPilot) capabil" (page 381) covers only simple CallPilot voice messaging traffic for a LAN/WAN bandwidth calculation. The engineering requirement for Multimedia Processing Units (MPU), such as CallPilot, depends on traffic type (for example, voice, fax, and speech-recognition) and service type (for example, enterprise networking, network message service).
Appendix B Branch Office engineering example LAN/WAN kbps = VMT (erlangs) x 37 kbps —End— Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Appendix C On-net dialing plan configuration examples Contents This section contains information on the following topics: "Introduction" (page 383) "Coordinated Dialing Plan" (page 383) "Uniform Dialing Plan" (page 387) "Group Dialing Plan" (page 392) "Transferable DN" (page 399) Introduction This section contains configuration examples for the following on-net (or private) dialing plans: • "Coordinated Dialing Plan" (page 383) • "Uniform Dialing Plan" (page 387) • "Group Dialing Plan" (page 392)
Appendix C On-net dialing plan configuration examples Figure 120 Coordinated Dialing Plan (CDP) Call Scenarios This section describes the following call scenarios, all based on Figure 120 "Coordinated Dialing Plan (CDP)" (page 384): • "From main office to Branch Office" (page 384) • "From Branch Office to main office" (page 385) • "When the Branch User telephone is in Local Mode" (page 385) From main office to Branch Office In this scenario, the following occurs: • DN 3001 (in the main office) o
Coordinated Dialing Plan 385 From Branch Office to main office In this scenario, the following occurs: • DN 3101 (in the Branch Office) dials DN 3001 (or 3002 - both are registered with the main office). • The Branch Office recognizes 3001 as a vacant number. Since VNR is enabled, the call is routed using the RLI defined for VNR, using the Virtual Trunk specified for that route. • The NRS is queried for the destination node IP address with which to route the call over the Virtual Trunk.
Appendix C On-net dialing plan configuration examples TYPE DSC DSC 31 FLEN 4 RLI 12 Refer to IP Peer Networking Installation and Commissioning (NN43001-313) for more information. —End— NRS configuration To configure the NRS, do the following: Step Action 1 Create CDP Domain: "MO_BO_CDP". 2 Create H.323 endpoints: "MO", "BO". 3 Create Numbering Plan entries in CDP Domain: a. Add "31" for endpoint "BO". b. Add "30" for endpoint "MO".
Uniform Dialing Plan 387 TYPE: 2004P1, 2004P2 TN 61 0 CUST 0 BUID 3002 —End— Refer to Procedure 27 "Installing IP Phones through overlays" (page 279) and IP Peer Networking Installation and Commissioning (NN43001-313) for more information. Uniform Dialing Plan Figure 121 "Uniform Dialing Plan (UDP)" (page 387) shows a sample Uniform Dialing Plan (UDP) (Access Code + LOC + DN) configuration.
Appendix C On-net dialing plan configuration examples From main office to Branch Office In this scenario, the following occurs: • DN 3001 or 3002 dials DN "65043101" (a digital telephone in the Branch Office). • The main office Call Server recognizes the digit "6" as AC1 and the digits "504" as LOC. It accesses the associated RLI and uses the defined Virtual Route and Virtual Trunk. • The NRS is queried for the destination node IP address with which to route the call over the Virtual Trunk.
Uniform Dialing Plan 389 — DN 3101 can call DN 3002 by dialing "3002", instead of the "65013002" dialed in Normal Mode. — DN 3002 can call DN 3001 by dialing "65013001", instead of the "3001" dialed in Normal Mode. — DN 3002 can call DN 3101 by dialing "3101", instead of the "65043101" dialed in Normal Mode. Configuration example Main office To configure UDP at the main office, do the following: Step Action 1 Configure ESN Control Block for UDP.
Appendix C On-net dialing plan configuration examples 5 Configure HLOC in Customer Data Block. >LD 15 REQ: CHG TYPE: CDB NET_DATA YES ISDN YES CLID YES ENTRY HLOC 501 6 Configure Virtual Trunk route. >LD16 REQ NEW TYPE RDB CUST 00 ROUT 120 DES VTRKNODE51 TKTP TIE VTRK YES ZONE 101 NODE 51 PCID H323 ISDN YES MODE ISLD DCH 12 IFC SL1 INAC YES —End— Refer to IP Peer Networking Installation and Commissioning (NN43001-313) for more information.
Uniform Dialing Plan 391 —End— Refer to IP Peer Networking Installation and Commissioning (NN43001-313) for more information. Branch Office To configure UDP at the Branch Office, do the following: Step Action 1 Configure ESN Control Block for UDP. >LD 86 REQ NEW CUST 0 FEAT ESN AC1 6 2 Configure Digit Manipulation. >LD 86 REQ NEW FEAT DGT DMI 6 DEL 3 3 Configure UDP LOC. >LD 90 REQ NEW FEAT NET TRAN AC1 TYPE LOC LOC 501 FLEN 7 RLI 1 LDN 0 4 Configure UDP HLOC.
Appendix C On-net dialing plan configuration examples >LD 15 REQ: CHG TYPE: CDB NET_DATA YES ISDN YES CLID YES ENTRY HLOC 50 6 Configure Branch User.
Group Dialing Plan 393 Figure 122 Group Dialing Plan (GDP) Call Scenarios This section describes the following call scenarios, all based on Figure 122 "Group Dialing Plan (GDP)" (page 393): • "From main office to Branch Office using CDP" (page 393) • "From main office to Branch Office using UDP-LOC" (page 394) • "From Branch Office to main office using CDP" (page 394) • "From Branch Office to main office using UDP-LOC" (page 394) • "Branch User telephone (DN 3002) is in Local Mode" (page 395) Fro
Appendix C On-net dialing plan configuration examples • The MG 1000B Core terminates the incoming Virtual Trunk call to DN 3101. • The Voice Gateway channel in the Branch Office provides IP-TDM transcoding. From main office to Branch Office using UDP-LOC In this scenario, the following occurs: • DN 3001 or 3002 dials a number "65043101". • The main office Call Server recognizes the digit "6" as AC1.
Group Dialing Plan 395 • The NRS is queried for a destination node IP address with which to route the call over the Virtual Trunk. The main office node IP address is returned because "501" is registered to the main office. • The main office Call Server terminates the incoming Virtual Trunk call to DN 3001 (or 3002) because "501" matches the HLOC of the main office. • The Voice Gateway channel in the Branch Office provides IP-TDM transcoding.
Appendix C On-net dialing plan configuration examples 3 Configure Route List Block (RLB). For more information, refer to Procedure 9 "Configuring ESN and MG 1000B zones" (page 210). >LD 86 REQ NEW FEAT RLB RLI 12 ENTR 0 ROUT 120 DMI 0 4 Configure CDP Distant Steering Code (DSC). >LD 87 REQ NEW CUST 0 FEAT CDP TYPE DSC DSC 31 FLEN 4 RLI 12 5 Configure UDP LOC. >LD 90 REQ NEW FEAT NET TRAN AC1 TYPE LOC LOC 504 FLEN 7 RLI 12 LDN 0 6 Configure UDP HLOC.
Group Dialing Plan 397 ENTRY HLOC 501 8 Configure Virtual Trunk Route. >LD 16 REQ NEW TYPE RDB CUST 00 ROUT 120 DES VTRKNODE51 TKTP TIE VTRK YES ZONE 101 NODE 51 PCID H323 ISDN YES MODE ISLD DCH 12 IFC SL1 INAC YES —End— Refer to Procedure 9 "Configuring ESN and MG 1000B zones" (page 210) in this document and IP Peer Networking Installation and Commissioning (NN43001-313) for more information. NRS configuration Configure the following in the NRS: • CDP domain: "MO_BO_CDP" • H.
Appendix C On-net dialing plan configuration examples Branch Office To configure GDP at the Branch Office, do the following: Step Action 1 Configure ESN Control Block for CDP and AC1. >LD 86 REQ NEW CUST 0 FEAT ESN CDP YES MXSC 50 NCDP 4 AC1 6 DLTN YES 2 Configure Digit Manipulation. >LD 86 REQ NEW FEAT DGT DMI 6 DEL 3 3 Configure UDP LOC. >LD 90 REQ NEW FEAT NET TRAN AC1 TYPE LOC LOC 501 FLEN 7 RLI 1 LDN 0 4 Configure UDP LOC.
Transferable DN 399 NET_DATA YES ISDN YES CLID YES ENTRY HLOC 504 6 Configure Branch User. >LD 11 REQ: NEW TYPE: 2004P1, 2004P2 TN 61 0 CUST 0 BUID 65013002 7 Configure Virtual Trunk Route.
Appendix C On-net dialing plan configuration examples Original configuration (pre-transfer) Figure 123 "Transferable DN (TNDN) (pre-transfer)" (page 400) shows a sample of a TNDN configuration before the move.
Transferable DN 401 — 3001 "MO" — 3002 "MO" — 3101 "BO" — 3201 "CS_B" The Move Alice is transferred from main office A to Office B. Bob is transferred from Office B to the Branch Office. Linda is transferred from the Branch Office to main office A. All three users want to keep their existing telephone numbers. New configuration (post-transfer) The TNDN configuration after the transfer is shown in Figure 124 "Transferable DN (TNDN) (post-transfer)" (page 401).
Appendix C On-net dialing plan configuration examples • Call Server B — DN: 3001 (zone 20) — VNR: YES • MG 1000B Call Server — DN: 3201 (zone 15, BUID 3201), 3101 — VNR: YES • NRS — CDP Domain "TNDN" — 3001 "CS_B" — 3002 "MO" — 3101 "BO" — 3201 "MO" Call Scenario The following is a general example of a call scenario after the move has occurred, based on Figure 124 "Transferable DN (TNDN) (post-transfer)" (page 401): • Alice (at Office B) calls Bob (at the Branch Office) by dialing DN 3201.
Transferable DN 403 NET_DATA YES VNR YES RLI 12 2 Remove the TN at Office A when the user has moved from office A to office B. >LD 11 REQ: OUT TYPE: 2004P1, 2004P2 TN 61 0 3 Add the new TN at Office B using a new telephone with the same DN. >LD 11 REQ: NEW TYPE: 2004P1, 2004P2 TN 62 8 4 Configure the NRS as follows: a. CDP Domain: "TNDN". b. H323 endpoints: "MO", "BO", "Call Server_B" c.
Appendix C On-net dialing plan configuration examples Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Appendix D Off-net dialing plan configuration example Contents This section contains information on the following topics: "Introduction" (page 405) "Call scenario" (page 405) "Provisioning" (page 406) "Main office" (page 406) "NRS" (page 408) "Branch Office" (page 409) "Call example" (page 409) "Main office" (page 410) "NRS" (page 410) "Branch Office" (page 410) Introduction This section contains an example of how to configure a dialing plan for a call from a Branch User in Normal Mode to the local PS
Appendix D Off-net dialing plan configuration example Figure 125 Off-net dialing plan example - call scenario. Provisioning Main office At the main office Call Server, the following is provisioned: • AC1 = 1, and AC2 = 2 >LD86 REQ PRT CUST 0 FEAT ESN MXLC 50 ... NCDP 4 AC1 1 AC2 2 DLTN YES ... TGAR NO • For Zone 1, ZACB = ALL, and ZDP = 101 Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.
Provisioning 407 >LD 117 => PRT ZACB 1 ______________________________________________________ | | | Access Code Behavior | | Zone |State|--------------------------------| | | | | | | Dialed | New | | # DES | | DC1 | DC2 | DC3 | AC | AC | |------------------------------------------------------ | | 1 BRANCH_ZONE | ENL | 101 | | | ALL | AC1 | |------------------------------------------------------ | Number of Zones configured = 2 => • DMI = 10, with DEL = 0 and CTYP = INTL >LD86 REQ PRT CUST 0 FEAT DGT DMI
Appendix D Off-net dialing plan configuration example CLTP RLI SDRR ITEI INTL 1 NONE NONE NRS In the NRS database, a Numbering Plan entry that associates the SPN 101 with the Branch Office endpoint is provisioned. The Numbering Plan entry is provisioned in NRS Manager, as shown in Figure 126 "NRS Routing Entries window" (page 408) and Figure 127 "NRS Add Routing Entry" (page 408).
Call example 409 Branch Office At the MG 1000B Small System Controller, the following is provisioned: • DMI = 12 with DEL = 3 to remove the ZDP digits added in the main office >LD86 REQ PRT CUST 0 FEAT DGT DMI 12 DMI 12 DEL 3 ISPN NO CTYP INTL • RLI = 4, with DMI = 12 and ROUT = 11, where this is the route number for the PSTN Trunk >LD86 REQ PRT CUST 0 FEAT RLB RLI 4 RLI 4 ... ROUT 11 ... DMI 12 ...
Appendix D Off-net dialing plan configuration example Main office At the main office Call Server: 1. The call is recognized as originating from a Branch User in Zone 1. 2. Based on the ZACB property, the Call Server recognizes that the call has been dialed with AC1, and that zone-based digit manipulation must be performed. 3. The ZDP digits are inserted after the Access Code, changing the digit string to "1 101 87654321". 4. The digits are translated by the ESN feature. a.
List of terms CDP Coordinated Dialing Plan. Under the recommended Coordinated Dialing Plan, the Branch User ID can be an extension (for example, 4567). For more information about CDP, consult Dialing Plans Reference (NN43001-283). datadump A datadump, or Equipment Datadump (EDD), is performed on the Call Server to save the active database to backup and to copy the database to static memory on the pertinent Small System Controller.
List of terms same conference even though they are using different videoconferencing applications. Although most videoconferencing vendors have announced that their products conform to H.323, it is too early to say whether such adherence actually results in interoperability. IP Abbreviation of Internet Protocol, pronounced as two separate letters. IP specifies the format of packets, also called datagrams, and the addressing scheme.
List of terms 413 IP addresses to unique IP addresses before sending out packets. NAT is practical when only a few users in a domain need to communicate outside of the domain at the same time. NCS Short for Network Connection Server. It provides a TPS interface to the NRS, allowing the TPS to query the NRS using the UNIStim protocol. It is a remote system node IP based on BUID (Branch Office), virtual office user (network wide virtual office login), and NUID (Geographic Redundancy).
List of terms routing The process of selecting the correct path for packets transmitted between IP networks by using software-based algorithms. Each packet is processed by the algorithm to determine its destination. SIP Short for Session Initiation Protocol. SIP is a protocol standard used for establishing, modifying, and terminating conference and telephony sessions in IP networks. A session can be a simple two-way telephone call or it can be a collaborative multi-media conference session.
List of terms 415 of voice streams. The voice gateway software can run on an 8- or 32-port Media Card or the 24-port ITG-P card. Within the MG 1000B Core, both of these cards register the voice channels to the MG 1000B Small System Controller when they are configured. WAN Wide Area Network. A computer network that spans a relatively large geographical area. Typically, a WAN consists of two or more local-area networks (LANs).
List of terms Nortel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nortel Networks .
Nortel Communication Server 1000 Branch Office Installation and Commissioning Copyright © 2007, Nortel Networks All Rights Reserved. Publication: NN43001-314 Document status: Standard Document version: 01.02 Document date: 20 June 2007 To provide feedback or to report a problem with this document, go to www.nortel.com/documentfeedback Sourced in Canada The information in this document is subject to change without notice.
