Remote Gateway Installation Guide

ManualsBrandsNortel Networks ManualsNetwork RouterRemote Gateway 50

Nortel Communication Server 1000

Nortel Communication Server 1000 Release 4.5

Main Office Configuration for Survivable

Remote Gateway 50

Configuration Guide

Document Number: 553-3001-207

Document Release: Standard 2.00

Date: January 2006

Year Publish FCC TM

Produced in Canada

Information is subject to change without notice. Nortel Networks reserves the right to make changes in design

or components as progress in engineering and manufacturing may warrant.

Nortel, Nortel (Logo), the Globemark, This is the Way, This is Nortel (Design mark), SL-1, Meridian 1, and

Succession are trademarks of Nortel Networks.

Title page

Summary of content (260 pages)

PAGE 1
Title page Nortel Communication Server 1000 Nortel Communication Server 1000 Release 4.5 Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide Document Number: 553-3001-207 Document Release: Standard 2.00 Date: January 2006 Year Publish FCC TM Copyright © Nortel Networks Limited 2006 All Rights Reserved Produced in Canada Information is subject to change without notice.
PAGE 2
PAGE 3
4 Page 3 of 258 Revision history January 2006 Standard 2.00. This document is up-issued for CR Q01202736, with information on reconfiguring Call Server alarm notification levels if necessary when configuring Adaptive Network Bandwidth Management. See pages 76 and 84. August 2005 Standard 1.00. This document is a new document to support Communication Server 1000 Release 4.5.
PAGE 4
Page 4 of 258 553-3001-207 Revision history Standard 2.
PAGE 5
8 Page 5 of 258 Contents List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 9 About this document . . . . . . . . . . . . . . . . . . . . . . . 11 Subject .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Applicable systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Conventions .. . .
PAGE 6
Page 6 of 258 Contents SRG information required by the main office . . . . . . . . . . . . . . . . . . . 36 Main office information required by the SRG . . . . . . . . . . . . . . . . . . . 37 Zone parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Branch office IP Phone configuration at the main office . . . . . . . . . . . 46 Bandwidth Management . . . . . . . . . . . . . . . . . . . . 49 Contents . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 7
Contents Page 7 of 258 On-net dialing plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Off-net dialing plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Routing calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 H.323 zones .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Zone-based digit manipulation . . . . . . . . . . . . .
PAGE 8
Page 8 of 258 553-3001-207 Contents Standard 2.
PAGE 9
10 Page 9 of 258 List of procedures Procedure 1 Configuring ESN and SRG zones . . . . . . . . . . . . . . . . . 40 Procedure 2 Configuring branch office IP Phones at the main office using LD 11 . . . . . . . . . . . . . . . . . . . . . . . . . 47 Procedure 3 Printing intrazone and interzone statistics for a zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Procedure 4 Displaying CAC parameters for one or more zones . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 10
Page 10 of 258 List of procedures Procedure 10 Suppress Alternative Call Routing for NBWM alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Procedure 11 Configuring the main office . . . . . . . . . . . . . . . . . . . . . . 175 Procedure 12 Configuring the NRS database . . . . . . . . . . . . . . . . . . . 184 Procedure 13 Configuring the branch office . . . . . . . . . . . . . . . . . . . . 187 Procedure 14 Testing PSTN access using an SRG IP Phone . . . . . . .
PAGE 11
14 Page 11 of 258 About this document 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. Subject This document describes the Main Office Configuration for the Survivable Remote Gateway 50: Configuration Guide (553-3001-207).
PAGE 12
Page 12 of 258 About this document Applicable systems This document applies to the following systems: • Communication Server 1000S (CS 1000S) • Communication Server 1000M Chassis (CS 1000M Chassis) • Communication Server 1000M Cabinet (CS 1000M Cabinet) • Communication Server 1000M Half Group (CS 1000M HG) • Communication Server 1000M Single Group (CS 1000M SG) • Communication Server 1000M Multi Group (CS 1000M MG) • Communication Server 1000E (CS 1000E) Note: When upgrading software, memory
PAGE 13
About this document • Page 13 of 258 Communication Server 1000M Cabinet (CS 1000M Cabinet) The following systems are referred to generically as “Large System”: • Communication Server 1000M Half Group (CS 1000M HG) • Communication Server 1000M Single Group (CS 1000M SG) • Communication Server 1000M Multi Group (CS 1000M MG) Related information This section lists information sources that relate to this document.
PAGE 14
Page 14 of 258 About this document • SRG50 Configuration Guide • Communication Server 1000M and Meridian 1: Small System Planning and Engineering (553-3011-120) • Communication Server 1000M and Meridian 1: Large System Planning and Engineering (553-3021-120) • Communication Server 1000S: Planning and Engineering (553-3031-120) • Communication Server 1000E: Planning and Engineering (553-3041-120) • Software Input/Output: Maintenance (553-3001-511) Online To access Nortel documentation online, c
PAGE 15
34 Page 15 of 258 Overview Contents This section contains information about the following topics: Survivable Remote Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Main office hardware description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Main office requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Optional features to enhance SRG functionality. . . . . . . . . . . . . . . . . .
PAGE 16
Page 16 of 258 Overview The SRG is implemented on a BCM50 platform and is connected to a CS 1000 at the main office over a LAN or a WAN. This configuration allows the call processing for the IP Phones at the SRG site to be centralized at the main office. The Call Server at the main office provides the call processing for the IP Phones in both the main office and branch offices. The SRG provides call processing functionality to telephones in local mode and local analog devices.
PAGE 17
Overview Page 17 of 258 Figure 1: SRG network Main office hardware description The main office must be one of the following systems: • CS 1000S • CS 1000E • CS 1000M Cabinet • CS 1000M Chassis • CS 1000M HG • CS 1000M SG • CS 1000M MG Note: Throughout this document, references to CS 1000 systems encompass all CS 1000 system types. The diagrams throughout this documentation show a CS 1000S main office.
PAGE 18
Page 18 of 258 Overview Signaling Server The Signaling Server is required at the main office only. It provides the following functions: • Terminal Proxy Server (TPS) — The TPS provides a connection from the IP Phones to the Call Server. It also provides a connection path from a virtual trunk to the Call Server.
PAGE 19
Overview Page 19 of 258 • NRS Database — stores the central dialing plan in XML format for the H.323 Gatekeeper. The H.323 Gatekeeper accesses this common endpoint and gateway database. • Network Connect Server (NCS) — used only for Media Gateway 1000B (MG 1000B), SRG, Geographic Redundancy and Virtual Office solutions. The NCS allows the Line TPS (LTPS) to query the NRS using the UNIStim protocol. • NRS Manager web interface — the NRS provides its own web interface to configure the H.
PAGE 20
Page 20 of 258 Overview • Analog (500/2500-type) telephones • WLAN Handset 2210/2211 Note: Throughout this document, the IP Phones in this list are referred to collectively as IP Phones. Main office requirements The branch office requires the following at the main office: • CS 1000 hardware, running Succession 3.0, CS 1000 Release 4.0, or CS 1000 Release 4.5. • IP Peer H.323 Trunk (H323_VTRK) package 399. This package is required to support H.323 functionality.
PAGE 21
Overview Page 21 of 258 Interface: Features (553-3001-369) for more information about these features. • Network Attendant Service (NAS) package 159. This package is required for analog (500/2500-type) telephones in the branch office to access attendant services when the attendant is configured on the main office. • Network Message Services (NMS) package 175. This package is required for analog (500/2500-type) telephones in the branch office to share the voicemail system in the main office.
PAGE 22
Page 22 of 258 Overview Normal Mode and Local Mode overview Normal Mode IP Phones that are physically located at the SRG but are registered with the main office are in Normal Mode. The main office provides centralized call processing for the SRG IP Phones. These telephones are registered to the main office TPS and are controlled by the Call Server at the main office. Users of the SRG IP Phones receive the features, key layout, and tones of the main office Call Server.
PAGE 23
Overview Page 23 of 258 SRG supports the Geographic Redundancy feature. For further information about Geographic Redundancy, see Communication Server 1000: System Redundancy (553-3001-307). In the event of a WAN failure, the SRG IP Phones lose communication with the main office. This causes the SRG IP Phones to reset and register with the SRG. The IP Phones then operate in Local Mode, providing services based on a limited SRG feature set, which has significant differences from the CS 1000 software.
PAGE 24
Page 24 of 258 Overview However, they cannot call any SRG analog (500/2500-type) telephones or any external numbers through the SRG trunks because the Virtual Trunks are not available. (SRG analog [500/2500-type] telephones are accessible if alternate routing is available through the PSTN.) Recovery to Normal Mode If an IP Phone is in Local Mode due to WAN failure or main office component failure, the SRG tries to communicate with the main office TPS at regular intervals.
PAGE 25
Overview Page 25 of 258 Nortel recommends testing Local Mode operation after changing the provisioning for a telephone on the SRG. To ensure that users do not forget to resume Normal Mode operation, the SRG redirects the telephone to the main office to return the telephone to Normal mode. This occurs if the telephone remains registered to the SRG in Test Local Mode for ten minutes (default setting). Alternatively, the user can press the Quit key from the set to return to Normal Mode.
PAGE 26
Page 26 of 258 Overview Bandwidth Management Overview For a complete overview of Bandwidth Management, refer to the Converging the Data Network with VoIP (553-3001-160), and for details on configuration, refer to “Bandwidth Management” on page 49. Network Bandwidth Management Network Bandwidth Management allows for a limit to be placed on the amount of interzone bandwidth allowed between IP Phones in Normal Mode at the SRG and the rest of the CS 1000 network.
PAGE 27
Overview Page 27 of 258 Miscellaneous items Time of Day Because the SRG IP Phones, in Normal Mode, receive their clock information from the main office, which may be located in a different time zone, the main office must be able to provide a different time of day for these phones. The time zone of the SRG is configured with the SRG zone at the main office. The time zone adjusts the main office time for display at the SRG.
PAGE 28
Page 28 of 258 Overview 2500-type) telephone. Since this is a call between IP and circuit-switched devices, a DSP resource on a Media Card is allocated and connected to the analog (500/2500-type) telephone. The IP address of the DSP resource is returned to the main office Call Server so a direct media path between the IP Phone and the DSP resource can be set up when the call is established. Refer to IP Peer Networking: Installation and Configuration (553-3001-213) for details.
PAGE 29
Overview Page 29 of 258 Networking consideration A fault condition can occur if IP Phones use a different route to the main office than that used by the SRG. CAUTION — Service Interruption If the network is planned so that IP Phones use a different route to the main office than that used by the SRG, a fault condition can occur.
PAGE 30
Page 30 of 258 Overview Virtual Trunks capacity The SRG capacity to support a number of simultaneous calls depends on the specific codec type used. In Normal Mode, the codec selection used is controlled by specific programming of the CS 1000. In this case: SRG 505 supports up to a maximum of 15 Virtual trunks unless both the intrazone and interzone codecs are configured as Best Quality (G.711), in which case the maximum number of Virtual Trunks would be 24.
PAGE 31
Overview Page 31 of 258 can be an extension (for example, 4567). Under the Uniform Dialing Plan (UDP), it is the user’s main office DN, the Location Code (LOC), plus the Access Code (for example, 6 343-5555). Note: The main office DN must be an ESN compliant DN. See “ESN Access Codes” on page 31. For more information about dialing plans and configuration, see “Dialing Plan configuration” on page 167. For more information about the branch office dialing plan, refer to SRG50 Configuration Guide.
PAGE 32
Page 32 of 258 Overview Cross reference for branch office and SRG50 terminology Table 1 lists configuration-related terms and contexts where branch office and SRG50 terminology differ.
PAGE 33
Overview Page 33 of 258 Table 1: Cross reference for branch office and SRG50 terminology (Part 2 of 2) Term or context Branch office SRG50 Network Class of Service (NCOS) telephone numbers (internal, not PSTN) TN DN, MOTN Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide
PAGE 34
Page 34 of 258 553-3001-207 Overview Standard 2.
PAGE 35
48 Page 35 of 258 Setting up the main office Contents This section contains information on the following topics: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 SRG information required by the main office. . . . . . . . . . . . . . . . . . . . 36 Main office information required by the SRG . . . . . . . . . . . . . . . . . . . 37 Zone parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 36
Page 36 of 258 Setting up the main office For more information on main office configuration, refer to IP Peer Networking: Installation and Configuration (553-3001-213). SRG information required by the main office The main office administrator must gather information about the SRG system.
PAGE 37
Setting up the main office Page 37 of 258 Table 2: SRG information required for the main office configuration (Part 2 of 2) SRG parameters Destination codes (steering codes) to route the main office calls to the SRG and out through the SRG PSTN lines IP Ports that affect SRG traffic with the main office and have been assigned firewall filters For further information on port configuration, refer to Converging the Data Network with VoIP (553-3001160) or SRG50 Configuration Guide.
PAGE 38
Page 38 of 258 Setting up the main office Table 3 Main office interoperation information (Part 2 of 3) Main office components Information about this system Trunk/telephony preferred codecs and jitter buffers listed in order of preference NRS (H.323 Gatekeeper) requirements Indicate if the SRG needs to manually assign ports with firewall filters. Telephony programming: DN length, DN (TN) range Numbering plan ID Private (default) Type of number Note 1: SRG50 only supports CDP and UDP dialing plans.
PAGE 39
Setting up the main office Page 39 of 258 Table 3 Main office interoperation information (Part 3 of 3) Main office components Information about this system Zone dialing: • ZDP appended to SRG IP Phone PSTN dialing strings to redirect the call to SRG PSTN • Any steering codes (destination codes) that must be mirrored by SRG programming IP Phone configuration: MOTN/BUID list, including which type of IP Phone is assigned to each number Note: Make note of the leading number, as SRG uses this as the DN rang
PAGE 40
Page 40 of 258 Setting up the main office Procedure 1 Configuring ESN and SRG zones IMPORTANT! Before and after an upgrade, perform a data dump (using LD 43 EDD or through Element Manager) on the Call Server or SSC to back up existing data. 1 Configure the Home Location Code (HLOC) and the Virtual Private Network Identifier (VPNI). LD 15 – Configure Customer Data Home Location Code and Virtual Private Network Identifier (Part 1 of 2) Prompt Response Description REQ: CHG Change existing data.
PAGE 41
Setting up the main office Page 41 of 258 LD 15 – Configure Customer Data Home Location Code and Virtual Private Network Identifier (Part 2 of 2) Prompt Response Description ISDN YES Integrated Services Digital Network -VPNI (0)-16383 Virtual Private Network Identifier for Bandwidth Management feature X = Disables feature 1-16383 = Enables feature = No Change 2 Configure the zone properties for IP Telephony bandwidth management. Use LD 117 or Element Manager.
PAGE 42
Page 42 of 258 Setting up the main office Note: The branch office zone number and zone bandwidth management parameters at the main office must match the corresponding branch office zone number and zone bandwidth management parameters at the branch office. 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 an branch office zone, the Bandwidth Management feature is not activated.
PAGE 43
Setting up the main office 4 Page 43 of 258 Enable the features for the branch office zone in LD 11. LD 117 – Enable features for an SRG zone. Command Description ENL ZBR ALL Enables features for branch office . End of Procedure Configuring zone parameters using CS 1000 Element Manager Use Element Manager to configure the branch office specific zone properties and time difference. 1 Select IP Telephony > Zones in Element Manager navigator. The Zones window opens (Figure 2 on page 44).
PAGE 44
Page 44 of 258 Setting up the main office Figure 2 Zone List web page 2 553-3001-207 Select the zone to be configured and configure the following properties. • Basic Property and Bandwidth Management (see Figure 3 on page 45) • Dialing Plan and Access Codes (see Figure 61 on page 192) • Emergency Service Information (see Figure 78 on page 239) • Time Difference and Daylight Saving Time Property (see Figure 4 on page 46) Standard 2.
PAGE 45
Setting up the main office Page 45 of 258 Figure 3 Zone Basic Property and Bandwidth Management web page Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide
PAGE 46
Page 46 of 258 Setting up the main office Figure 4 Zone Time Difference and Time web page Zone parameters must be configured on the main office and the branch office. For information on configuring zones, refer to “Bandwidth Management” on page 49. Branch office IP Phone configuration at the main office After the branch office zones and passwords are provisioned, provision the branch office IP Phones at the main office.
PAGE 47
Setting up the main office Page 47 of 258 Note: There is no automatic data synchronization between the main office Call Server and SRG. The technician must provision the telephone on both the Call Server and the SRG. Branch office IP Phone configuration using OTM At the main office, OTM can be used to configure branch office IP Phones.
PAGE 48
Page 48 of 258 Setting up the main office • 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. The zone prompt applies only when the TYPE is i2001, i2002, i2004, or i2050.
PAGE 49
126 Page 49 of 258 Bandwidth Management Contents This section contains information on the following topics: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Codec negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Codec selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Codec selection algorithms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 50
Page 50 of 258 Bandwidth Management Introduction CS 1000 supports Bandwidth Management on a network-wide basis so that voice quality can be managed between multiple Call Servers. Bandwidth management allows for codec selection and bandwidth limitations to be placed on calls, depending on whether the calls are intrazone or interzone. Adaptive Network Bandwidth Management is an enhancement of Bandwidth Management in which Quality of Service (QoS) metrics are used to automatically lower available bandwidth.
PAGE 51
Bandwidth Management Page 51 of 258 By default, the G.711 codec must be supported at both ends of a call. Codec configuration is performed for each node and is independent of the signaling gateway that is used on the node. Note: The payload size on the CS 1000 must be set to 30 msec in order to work with the SRG. IP Peer Networking performs codec negotiation by providing a list of codecs that the devices can support. Use CS 1000 Element Manager to configure the list of codec capabilities.
PAGE 52
Page 52 of 258 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.
PAGE 53
Bandwidth Management Page 53 of 258 zones involved (that is, Best Bandwidth or Best Quality). Likewise, the bandwidth calculations use the preferred codec of the Voice Gateway Media Card for connections between a circuit-switched device (for example, a PRI trunk) and a Virtual Trunk. Codec selection For every Virtual Trunk call, a codec must be selected before the media path can be opened.
PAGE 54
Page 54 of 258 Bandwidth Management H.323 Master/Slave algorithm In the case of a Virtual Trunk call between Nortel and third-party equipment, the H.323 Master/Slave algorithm is used. The codec selection algorithm proposed by the H.323 standard involves a Master/Slave negotiation. This is initiated each time two nodes exchange their capabilities (TCS message). The Master/Slave information decides that one node is Master and the other node is Slave.
PAGE 55
Bandwidth Management • Page 55 of 258 For tandem calls, the Master/Slave information is not relevant. The Master/Slave information is designed for use between two nodes only, not between three or more nodes. It makes the codec selection for tandem calls more complex and inefficient. To solve the issues, another codec selection algorithm, not based on the unpredictable Master/Slave information, is needed. Since any change to the Master/Slave algorithm implies a change to the H.
PAGE 56
Page 56 of 258 Bandwidth Management Table 4 “Best Bandwidth” algorithm — codec type G.711 A law G.711 mu-law G.729 A G. 729 AB G. 723.1 G.711 A-law G.711 A-law G.711 mu-law G.729 A G. 729 AB G. 723.1 G.711 mu-law G.711 mu-law G.711 mu-law G.729 A G. 729 AB G. 723.1 G.729 A G.729 A G.729 A G.729 A G. 729 AB G.729 A G. 729 AB G. 729 AB G. 729 AB G. 729 AB G. 729 AB G. 729 AB G. 723.1 G. 723.1 G. 723.1 G.729 A G. 729 AB G. 723.
PAGE 57
Bandwidth Management Page 57 of 258 Zones Bandwidth Management Zones are configured for each endpoint on a Call Server. The Network Bandwidth Zone number determines if a call is an intrazone call or an interzone call. Once that is determined, the proper codec and bandwidth limit is applied to the call. All of the endpoints on one Call Server are configured with Zone number to identify all of the endpoints as being in a unique geographic location in the network.
PAGE 58
Page 58 of 258 Bandwidth Management 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.
PAGE 59
Bandwidth Management Page 59 of 258 Figure 5 Configuring a codec Configuring Bandwidth Management The steps to configure Bandwidth Management on the Call Server are as follows: 1 Define a VPNI number in LD 15.
PAGE 60
Page 60 of 258 Bandwidth Management — 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 Quality (BQ) — Interzone Bandwidth = default (1000000) 3 Configure the IP Phone, DSP and Virtual Trunk data with the corresponding zone numbers.
PAGE 61
Bandwidth Management Page 61 of 258 Figure 6 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.
PAGE 62
Page 62 of 258 Bandwidth Management LD 117 Configure a new or existing Bandwidth Management zone. Command Description NEW | CHG ZONE [ ] Configure a new zone (NEW) or change (CHG) an existing zone, where: • zoneNumber = 0-255 • intraZoneBandwidth = Available intrazone bandwidth (Kbit/s); Nortel recommends this value be set to the maximum value.
PAGE 63
Bandwidth Management Page 63 of 258 Maintenance commands Maintenance commands can be run from Element Manager or LD 117. Maintenance using Element Manager The PRT INTRAZONE and PRT INTERZONE commands are available in Element Manager from the Zones web page, shown in Figure 6 on page 61. To access these commands, follow the steps in Procedure 3 on page 63. Procedure 3 Printing intrazone and interzone statistics for a zone 1 Select IP Telephony > Zones from the navigator.
PAGE 64
Page 64 of 258 Bandwidth Management Figure 7 Maintenance Commands for Zones web page 3 Do one of the following: • • To display intrazone statistics: i. Select Print Interzone Statistics (PRT INTERZONE) from the Action drop-down list. ii. 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: i.
PAGE 65
Bandwidth Management ii. 4 Page 65 of 258 Select a zone from the Near End 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. Click Submit. The Maintenance Commands for Zones web page reopens, displaying the statistics for the specified zone or zones. A blank field indicates that that statistic is either not available or not applicable to that zone.
PAGE 66
Page 66 of 258 Bandwidth Management Figure 9 Element Manager — interzone statistics End of Procedure Maintenance using LD 117 Use the PRT INTRAZONE or PRT INTERZONE commands in LD 117 to view the intrazone or interzone statistics for specified zones. Note: Do not use the PRT ZONE command — it has been replaced by the PRT INTRAZONE and PRT INTERZONE commands. 553-3001-207 Standard 2.
PAGE 67
Bandwidth Management Page 67 of 258 LD 117 Print zone statistics.
PAGE 68
Page 68 of 258 Bandwidth Management feedback. This dynamic bandwidth adjustment maintains a high level of voice quality during network degradation. The Adaptive Network Bandwidth Management feature dynamically adapts to QoS in the network and reduces the bandwidth available for interzone calls if QoS degrades. Typically, each Call Server in the network has a zone assigned to it. The Call Server keeps track of the bandwidth being used between its own zone and zones belonging to other Call Servers.
PAGE 69
Bandwidth Management Page 69 of 258 Adaptive Network Bandwidth Management to these new zones as required. Therefore, as new Call Servers are added to the network, it is not necessary to re-provision all the other Call Servers on the network to take into account this new Call Server. Conversely, when Call Servers are removed from the network, the remaining Call Servers age out the old Call Server information and therefore, provide only up to date bandwidth information.
PAGE 70
Page 70 of 258 Bandwidth Management Figure 10 Call Progress with Adaptive Network Bandwidth Management 553-3001-207 Standard 2.
PAGE 71
Bandwidth Management Page 71 of 258 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. Adaptive Network Bandwidth Management cannot be enabled for Zone 0.
PAGE 72
Page 72 of 258 Bandwidth Management When a Call Server receives a QoS alarm, the two zones that originated the alarm are determined. Using this information, the Call Server reduces the bandwidth limit between the two zones. This zone-to-zone bandwidth limit (in effect at any particular time) is known as the Sliding Maximum Bandwidth Limit and is a percentage of the Configured Interzone bandwidth limit. The Sliding Maximum value is displayed using the prt interzone command.
PAGE 73
Bandwidth Management Page 73 of 258 loss (Cpl), jitter (Cj), delay (Cd), and the R factor (Cr) — can be configured and are used to calculate the rate of bandwidth change. Increasing them from their default values causes the Sliding Maximum to decrease faster in response to the specific QoS alarm. The QoS Coefficient (CQoS) can be varied from its default value. Increasing this value causes the Sliding Maximum to change more rapidly in response to QoS alarms.
PAGE 74
Page 74 of 258 Bandwidth Management Figure 13 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.
PAGE 75
Bandwidth Management Page 75 of 258 by a Call Server that is not responsible for the particular zone. Thus, bandwidth management is not possible for these phones. Feature packaging The Adaptive Network Bandwidth Management feature requires the following packages: • QoS Enhanced Reporting (PVQM) package 401 Note: Package 401, QoS Enhanced Reporting (PVQM), is required if the R value from the Phase II IP Phones is to be reported and used in the calculations.
PAGE 76
Page 76 of 258 Bandwidth Management Configuring Adaptive Network Bandwidth Management The following is a summary of the tasks necessary to configure Adaptive Network Bandwidth Management in the network. 1 Enable the Call Admission Control (CAC) package. 2 Configure CAC in Element Manager or LD 117: a Configure the VPNI on the main office and branch offices. b Configure both the main office and branch office zones at the main office. c Configure the branch office zone on the SRG.
PAGE 77
Bandwidth Management Page 77 of 258 Refer to Converging the Data Network with VoIP (553-3001-160) for information on notification levels for alarms. Configuration using Element Manager Element Manager can be used to enable and configure the feature. The zone must exist before it can be configured for Adaptive Network Bandwidth Management. Refer to IP Peer Networking: Installation and Configuration (553-3001-213) for instruction on how to create and configure basic properties of the zone.
PAGE 78
Page 78 of 258 Bandwidth Management Figure 14 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 5 on page 79 shows the fields in the Adaptive Network Bandwidth Management and CAC web page, the field definitions, and their LD 117 command equivalent. 553-3001-207 Standard 2.
PAGE 79
Bandwidth Management Page 79 of 258 Table 5 Adaptive Network Bandwidth Management and CAC fields Field Title Field Definition LD 117 equivalents Enable Call Admission Control Feature (CAC) Control the CAC feature for the zone ENL ZCAC • Enable (check box selected) • disable (clear the check box) DIS ZCAC 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 lim
PAGE 80
Page 80 of 258 Bandwidth Management Configuration using Command Line Interface You can also configure the Adaptive Network Bandwidth Management feature using LD 117. LD 117 — Configure Adaptive Network Bandwidth Management.
PAGE 81
Bandwidth Management Page 81 of 258 LD 117 — Configure Adaptive Network Bandwidth Management.
PAGE 82
Page 82 of 258 Bandwidth Management LD 117 — Configure Adaptive Network Bandwidth Management.
PAGE 83
Bandwidth Management Page 83 of 258 LD 117 — Configure Adaptive Network Bandwidth Management.
PAGE 84
Page 84 of 258 Bandwidth Management LD 117 — Configure Adaptive Network Bandwidth Management. (Part 5 of 6) Command Description CHG ZQNL Change the Notification Level for the specified zone, where: • Zone = 1-255 • Level = 0-(2)-4, where: — Level 0 = All voice quality alarms are suppressed. — Level 1 = All zone-based Unacceptable alarms. — Level 2 = Allow all level 1 alarms PLUS zone-based Warning alarms. — Level 3 = Allow all level 1 and 2 alarms PLUS per-call Unacceptable alarms.
PAGE 85
Bandwidth Management Page 85 of 258 LD 117 — Configure Adaptive Network Bandwidth Management. (Part 6 of 6) Command Description DIS ZCAC Disables the Call Admission Control (CAC) feature for the specified zone, where: • Zone = 1-255 Note: Disables the feature on a zone-by-zone basis. ENL ZCAC Enables the Call Admission Control (CAC) feature for the specified zone, where: • Zone = 1-255 Note: Enables the feature on a zone-by-zone basis.
PAGE 86
Page 86 of 258 Bandwidth Management 2 Click Maintenance Commands for Zones (LD 117). The Maintenance Commands for Zones web page opens, as shown in Figure 7 on page 64. This page lists all the configured zones and their intrazone statistics by default. 3 Select Print Adaptive Network Bandwidth Management and CAC Parameters (PRT ZCAC) from the Action drop-down list. 4 Select a zone from the Zone Number drop-down list, by doing one of the following: 5 • Select ALL to print statistics for all zones.
PAGE 87
Bandwidth Management Page 87 of 258 Figure 15 Element Manager — CAC parameters End of Procedure Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide
PAGE 88
Page 88 of 258 Bandwidth Management Maintenance using LD 117 The same information can be displayed using commands in LD 117.
PAGE 89
Bandwidth Management Page 89 of 258 LD 117 — Display Adaptive Network Bandwidth Management information (Part 2 of 3) Command Description PRT INTERZONE [] [] [] [] Print interzone statistics for the specific VPNI zone; where: • • • • nearZone = ALL or 0-255 nearVPNI = 1-16383 farZone = 0-255 farVPNI = 1-16383 The output of this command displays the following information: • • • • • • • • • • • • • • • Near end Zone Near end VPNI Far end Zone Far end VPNI State = EN
PAGE 90
Page 90 of 258 Bandwidth Management LD 117 — Display Adaptive Network Bandwidth Management information (Part 3 of 3) Command Description PRT ZCAC [] Print CAC parameters for the specified zone, or for all zones, where: • zone = ALL or 0-255 The output of this command displays the following information: • • • • • • • • • • • • Local ZONE = 0-255 State = ENL/DIS CR = 1-100 CPL = 1-100 CD = 1-100 CJ = 1-100 CQOS = 1-100 ZQRT = 1-100 ZQRTI = 10-120 ZQUAT = 1-99 ZQWAT =1-99 CACVT = 1-255 Sample outpu
PAGE 91
Bandwidth Management Page 91 of 258 Figure 16 Sample output for PRT INTRAZONE command => prt intrazone _______________________________________________________________ |Zone|State| Type |Strategy|MO/ | Bandwidth | Usage | Peak | | | | | |VTRK/| kbps | kbps | % | | | | | |BMG | | | | |----|-----|-------|--------|----|-----------|---------|------| | 2| ENL |SHARED | BQ | MO| 10000| 190| 3 | |-------------------------------------------------------------| | 44| ENL |SHARED | BQ | BMG| 10000| 0| 1 | |----------
PAGE 92
553-3001-207 Standard 2.00 January 2006 Note: The Far end and VPNI fields are displayed only when Adaptive Bandwidth Management is enabled in LD 117.
PAGE 93
Bandwidth Management Page 93 of 258 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.
PAGE 94
Page 94 of 258 Bandwidth Management Patch Number A patch is required on the main office in order to invoke this feature. The patch number is MPLR 20259. Dialing Plan Overview Depending upon the type of dialing plan used in the network (Coordinated Dialing Plan [CDP], or Uniform Dialing Plan [UDP] or a combination of both) the general idea is to have all calls that are terminating at a branch office first dial a number that will get routed to the main office associated with that branch office.
PAGE 95
Bandwidth Management Page 95 of 258 Figure 19 General legend Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide
PAGE 96
Page 96 of 258 Bandwidth Management Network using Uniform Dialing Plan The following section provides general network configuration for a network using UDP only. Figure 20 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.
PAGE 97
Bandwidth Management Page 97 of 258 Table 6 describes the network configuration and the steps that a call takes during its setup. Table 6 Configuration details for the general case Region Call progress steps 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. 1, 2, 3 Prefixes for branch offices for regular calls are required for all branch offices.
PAGE 98
Page 98 of 258 Bandwidth Management Differences when every branch office HLOC is shared with the main office Table 7 shows the configuration when the branch office HLOC is shared with the main office. Table 7 Provisioning details for this case Region Provisioning detail 1 Provisioning on the main office requires parsing to only “normal” LOC identification and HLOC deletion. 1 LOC values that are on branch offices may be provisioned as extended LOCs (> 3 digit codes).
PAGE 99
Bandwidth Management Page 99 of 258 Figure 21 Call flow for Scenario 1 - local call 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 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.
PAGE 100
Page 100 of 258 Bandwidth Management No branch office HLOC is shared with the main office, but can be shared with another branch office In this example, the HLOC of the branch offices are the same but the HLOC of the main office is different. See Figure 22. Figure 22 Call flow for Scenario 1 - local call 553-3001-207 1 The branch office user dials 6-395-3456. The system transmits 395-3456 to the NRS.
PAGE 101
Bandwidth Management Page 101 of 258 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.
PAGE 102
Page 102 of 258 Bandwidth Management 1 The branch office user dials 6-395-3456. The system transmits 399-3456 to the branch office user dials 6-399-3456. 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 399-3456 to the main office. 3 The main office determines that this is to another branch office, with office prefix 552.
PAGE 103
Bandwidth Management Page 103 of 258 Figure 24 Call flow for Scenario 1 – call to a 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.
PAGE 104
Page 104 of 258 Bandwidth Management Figure 25 Call flow for Scenario 1 - call to remote branch office (destination side) 553-3001-207 1 Main office B determines that this is to LOC 44434, which is 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.
PAGE 105
Bandwidth Management Page 105 of 258 No branch office HLOC is shared with the main office, but can be shared with another branch office In Figure 26, the first half of the call is shown (originator side of the call). In Figure 27 on page 106, the second half of the call is shown (destination side of the call). Figure 26 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.
PAGE 106
Page 106 of 258 Bandwidth Management Figure 27 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.
PAGE 107
Bandwidth Management Page 107 of 258 Figure 28 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.
PAGE 108
Page 108 of 258 Bandwidth Management Figure 29 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.
PAGE 109
Bandwidth Management Page 109 of 258 3 Provision the NRS to send all calls to a LOC without a gateway routing prefix to the main office of that LOC, or to the main office which provides service for the branch office using the LOC. See step 3 on page 111. 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.
PAGE 110
Page 110 of 258 Bandwidth Management Figure 30 Provisioning example Procedure 5 Provisioning Tandem Bandwidth Management 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 31 shows the tandem endpoint configuration in Element Manager. 553-3001-207 Standard 2.
PAGE 111
Bandwidth Management Page 111 of 258 Figure 31 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.
PAGE 112
Page 112 of 258 Bandwidth Management 5 Provision the main office with the DGT table DMIs to insert the prefixes and set the Type of Number correctly. Create RLB RLI entries to use these DMIs for the VTRK route(s). One RLI per branch office will be the minimum requirement. Note that calls from remote systems will typically have the HLOC prefix, so this is defined here Table 8 lists main office B DMI and RLI provisioning.
PAGE 113
Bandwidth Management Page 113 of 258 Table 9 lists main office B LOC provisioning. Table 9 Main office B LOC provisioning for LOC 741 841 Create a CDP mapped to the LOC: LD 87 REQ NEW CUST 0 FEAT CDP TYPE DSC DSC 4030 FLEN 4 RLI 50 Create a CDP mapped to the LOC: LD 87 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 10 lists main office and branch office HLOC provisioning.
PAGE 114
Page 114 of 258 Bandwidth Management Table 10 Main office and branch office HLOC provisioning – Main office B and branch office B (Part 2 of 2) Create a DMI Create an HLOC DMI 61 TRAN ac1 DEL 3 TYPE hloc ISPN no HLOC 841 DMI 61 Repeat the above for all the main offices and branch offices. 8 Provision the main office to send all other LOCs to the IP network without prefixes. These are going to a remote main office. Table 11 lists main office B LOC provisioning for LOC to remote main office.
PAGE 115
Bandwidth Management Page 115 of 258 Table 12 lists main office A LOC provisioning for LOC to the remote office. Table 12 Main office A LOC provisioning for LOC to remote main office systems – main office B is LOC 841 Create an RLI Create a LOC LD 86 LD 90 REQ new REQ NEW CUST 0 CUST 0 FEAT rlb FEAT NET RLI 71 TRAN AC1 ENTR 0 TYPE LOC LTER no LOC 841 ROUT 75 FLEN 7 RLI 71 9 Provision the branch office with a terminating RLI with a DMI to delete the LOC prefixes.
PAGE 116
Page 116 of 258 Bandwidth Management Table 13 Branch office terminating RLI provisioning (Part 2 of 2) Create a DMI Create an HLOC ISPN no HLOC 741 DMI 61 Network using mixed Coordinated Dialing Plan and Uniform Dialing Plan The following section provides general details of the network setup. Figure 32 shows an example of a mixed network configuration. Figure 32 Scenario 2 - UDP between main offices, CDP inside the main office region 553-3001-207 Standard 2.
PAGE 117
Bandwidth Management Page 117 of 258 Table 14 lists provisioning details for a mixed network. Table 14 Provisioning details for this case Region Provisioning detail 1, 2, 3 CDP used for all calls within the region. 1, 2, 3 UDP used for region to region calls. 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.
PAGE 118
Page 118 of 258 Bandwidth Management Figure 33 Call flow for Scenario 2 – local call dials CDP 553-3001-207 1 The branch office user dials 3456 (CDP). The system transmits 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 3456 to the main office. 3 The main office determines that this is to another branch office. The system transmits 3456 to the NRS.
PAGE 119
Bandwidth Management Page 119 of 258 Abnormal case - calls originating using UDP, but terminating using CDP Figure 34 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 The branch office sends the call to 395-3456 to the main office.
PAGE 120
Page 120 of 258 Bandwidth Management Call between branch offices associated with different main offices In Figure 35, the first half of the call is shown (the originator side of the call). Figure 35 Call flow for Scenario 2 - local call to remote branch office (originator side) 553-3001-207 1 The branch office user dials 6-444-3456. The system transmits 444-3456 to the NRS.
PAGE 121
Bandwidth Management Page 121 of 258 In Figure 36, the second half of the call is shown (destination side of the call). Figure 36 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.
PAGE 122
Page 122 of 258 Bandwidth Management Network using Coordinated Dialing Plan The following section provides general details of network setup. Figure 37 shows a full CDP network configuration. Figure 37 Scenario 3 – full CDP network Table 15 lists the provisioning details for a full CDP network. Table 15 Provisioning details for this case (Part 1 of 2) Region 553-3001-207 Provisioning detail 1, 2, 3 CDP used for all calls within the region. 1, 2, 3 CDP used for region to region calls. Standard 2.
PAGE 123
Bandwidth Management Page 123 of 258 Table 15 Provisioning details for this case (Part 2 of 2) Region Provisioning detail 1, 2, 3 All CDP numbers must be sufficiently long to allow unique termination of the calls. That is, every main office/branch office region requires its own LSC to ensure that all numbers are unique. 1, 2, 3 Prefixes for branch offices for regular calls are required. May have additional prefixes for E-911 calls, if required, or may share prefixes.
PAGE 124
Page 124 of 258 Bandwidth Management Figure 38 Call flow for Scenario 3 - local call 1 The branch office user dials 43456. The system transmits 43456 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 43456 to the main office. 3 The main office determines that this is to another branch office, with office prefix 552.
PAGE 125
Bandwidth Management Page 125 of 258 Figure 39 Call flow for Scenario 3 - calls to remote branch office (originator side) 1 The branch office user dials 53456. The system transmits 53456 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 53456 to the main office. 3 The main office determines that this is to another main office.
PAGE 126
Page 126 of 258 Bandwidth Management Figure 40 Call flow for Scenario 3- calls to remote branch office (destination side) 553-3001-207 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. Standard 2.
PAGE 127
166 Page 127 of 258 Alternative Call Routing for Network Bandwidth Management Contents This section contains information on the following topics: Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Operating parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Feature interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Feature packaging . . . . . . . . . . . . .
PAGE 128
Page 128 of 258 Alternative Call Routing for Network Bandwidth Management Figure 41 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.
PAGE 129
Alternative Call Routing for Network Bandwidth Management Page 129 of 258 When there is insufficient bandwidth for a station-to-station call, the Alternative Call Routing for NBWM feature uses a trunk for a call which would not normally use a trunk.
PAGE 130
Page 130 of 258 Alternative Call Routing for Network Bandwidth Management Configure one of these two modes of operation (Bandwidth insufficiency or All Calls) on a zone basis. The Alternative Call Routing for NBWM feature deals only with interzone calls. This feature is configurable for main office and branch office zones, not virtual trunk zones. It is possible to configure this feature to re-route all calls to MCDN or PSTN routes and still maintain the main office-branch office architecture.
PAGE 131
Alternative Call Routing for Network Bandwidth Management Page 131 of 258 How Alternative Call Routing for NBWM works When a user dials a station-to-station call between two different zones (that is, the calling and called telephones are not located in the same geographic area) and the bandwidth limit has been reached, then the Alternative Call Routing feature is invoked. The following steps occur in Alternative Call Routing scenarios.
PAGE 132
Page 132 of 258 Alternative Call Routing for Network Bandwidth Management 4 The main office determines the RLI and uses a DMI to change the dialed number into a PSTN/MCDN format number. 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.
PAGE 133
Alternative Call Routing for Network Bandwidth Management Page 133 of 258 Before deciding whether to program the steering codes as Distant Steering Codes (DSC) or Trunk Steering Codes (TSC), take into account that the system counts the digits in calls that start with a DSC. Without Flexible Numbering Plan (FNP), DSC calls must have the same number of digits as specified in LD 86 ESN (the NCDP prompt). With FNP, fewer digits are acceptable, if the FLEN prompt is programmed correctly.
PAGE 134
Page 134 of 258 Alternative Call Routing for Network Bandwidth Management Figure 42 Example of an alternately routed call between a branch office telephone in Normal Mode and a main office telephone Telephone B calls Telephone A (the user dials DN 5262). In this example, the call alternately routes to the PSTN. (The PSTN telephone number of Telephone A is 613-966-5262.
PAGE 135
Alternative Call Routing for Network Bandwidth Management Page 135 of 258 At the branch office: • Provision the ALTPrefix as a steering code. Build a Route List Index and DMI associated with this steering code that alternately routes these calls to the PSTN with the correct digits. 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 42 on page 134 and Figure 43 on page 136.
PAGE 136
Page 136 of 258 Alternative Call Routing for Network Bandwidth Management Figure 43 Illustration showing digits dialed and outpulsed with Alternative Call Routing for NBWM 553-3001-207 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 42 on page 134). 2 The main office Call Server determines there is insufficient bandwidth between the two zones. Standard 2.
PAGE 137
Alternative Call Routing for Network Bandwidth Management 3 Page 137 of 258 The Call Server inserts the ALTPrefix configured for the BO2 zone prior to IP Phone A’s telephone number, dialed by the user. Example: ALTPrefix assigned is 222. The dialed number becomes 222 5262. 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.
PAGE 138
Page 138 of 258 Alternative Call Routing for Network Bandwidth Management A call from a main office telephone to a branch office telephone Figure 44 shows two CS 1000 systems. The system shown on the left is a main office. The system shown on the right is a branch office. Both systems have access to the PSTN. The Wide Area Network (WAN) is shown in the center with a gatekeeper/Network Routing Service (NRS) that can be co-resident with a Signaling Server.
PAGE 139
Alternative Call Routing for Network Bandwidth Management Page 139 of 258 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. • Provision an ALTPrefix for the MO 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.
PAGE 140
Page 140 of 258 Alternative Call Routing for Network Bandwidth Management Figure 45 Illustration showing digits dialed and outpulsed with Alternative Call Routing for NBWM 1 IP Phone User A in the MO zone dials IP Phone B in the BO2 zone (DN 3121) (action labeled 1 in Figure 44 on page 138). 2 The main office Call Server determines there is insufficient bandwidth between the two zones. 3 The Call Server inserts the ALTPrefix configured for the MO zone prior to IP Phone B’s telephone number.
PAGE 141
Alternative Call Routing for Network Bandwidth Management 5 Page 141 of 258 The main office manipulates the digits and the call is routed to the PSTN in the MO zone (action labeled 2 in Figure 44 on page 138). Example: Use DMI to delete and insert digits on the PSTN trunk route. — delete 3 digits (remove the ALTPrefix 777) — insert 966 (in order to compose the DID number of the destination telephone which is 9663121, a local call.
PAGE 142
Page 142 of 258 Alternative Call Routing for Network Bandwidth Management Figure 46 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.
PAGE 143
Alternative Call Routing for Network Bandwidth Management • Page 143 of 258 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. Build a Route List Index and DMI associated with this steering code that alternately routes these calls to the PSTN.
PAGE 144
Page 144 of 258 Alternative Call Routing for Network Bandwidth Management Figure 47 Illustration showing digits dialed and outpulsed with Alternative Call Routing for NBWM 553-3001-207 Standard 2.
PAGE 145
Alternative Call Routing for Network Bandwidth Management Page 145 of 258 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 46 on page 142). 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.
PAGE 146
Page 146 of 258 Alternative Call Routing for Network Bandwidth Management Alternative Call Routing for NBWM feature used in All Calls mode The situations illustrated in Figure 42 on page 134, Figure 44 on page 138, and Figure 46 on page 142 can also apply to the operation of the feature when it is active all the time, regardless of available bandwidth. For an example of this, the information below applies to Figure 42 on page 134 when all calls are alternately routed.
PAGE 147
Alternative Call Routing for Network Bandwidth Management Page 147 of 258 by the same Central Office, PSTN calls can use the trunks at the main office. However, if the two systems are located at a great distance from each other, it may make sense to program the main office to use trunks at the branch office for alternately routed calls. If there is a location with multiple NXX codes for DID users, it is possible to translate and outpulse calls properly as long as each NXX has a unique DN range.
PAGE 148
Page 148 of 258 Alternative Call Routing for Network Bandwidth Management Feature interactions Call Redirections The Alternative Call Routing for NBWM feature works with Call Transfer, Call Forward All Calls, and Conference. Redirection operates as if the user dialed the ALTPrefix manually.
PAGE 149
Alternative Call Routing for Network Bandwidth Management Page 149 of 258 Feature packaging The Alternative Call Routing for NBWM feature requires the following software package: • Coordinated Dialing Plan (CDP) package 59 The following software package is optional: • Flexible Numbering Plan (FNP) package 160 Feature implementation using Command Line Interface Task summary list The following is a summary of the tasks in this section: 1 LD 117 - Enable Alternative Call Routing for NBWM for a particula
PAGE 150
Page 150 of 258 Alternative Call Routing for Network Bandwidth Management LD 117 - Configure Alternate Prefix number for a particular zone and the All Calls option, if desired. Command Description CHG ZALT [] Change ALTPrefix number for zone, where: Input zone number (0-255). Note: Configure the branch office zone using LD 117 at the main office.
PAGE 151
Alternative Call Routing for Network Bandwidth Management Page 151 of 258 Sample printout # ZALT Alternate Prefix All Calls Alarms Suppression Time 10 ENL 100 YES 50 11 ENL 101 YES 0 12 DIS 102 NO 1000 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.
PAGE 152
Page 152 of 258 Alternative Call Routing for Network Bandwidth Management Accessing the Zones web page Procedure 6 Accessing the Zones web page 1 From the navigator, click IP Telephony > Zones. (See Figure 48.) Figure 48 Access the Zone web page The Zones web page opens. (See Figure 49 on page 153.) 553-3001-207 Standard 2.
PAGE 153
Alternative Call Routing for Network Bandwidth Management Page 153 of 258 Figure 49 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. (See Figure 50 on page 154.
PAGE 154
Page 154 of 258 Alternative Call Routing for Network Bandwidth Management Figure 50 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).
PAGE 155
Alternative Call Routing for Network Bandwidth Management Page 155 of 258 Diagnostics Command Line Interface diagnostics LD 117 - Obtain status for a particular zone. Command Description STAT ZALT Display Alternative Call Routing Status, where: zone = bandwidth zone Note: If you do not enter a value in the zone field, you obtain a printout of the status of all configured zones.
PAGE 156
Page 156 of 258 Alternative Call Routing for Network Bandwidth Management The printout for all configured branch office zones appears as follows: # State Flags Des 10 ENL TIM BVW 11 DIS LOC ALT TOR 12 DIS ESA ALT Note: Des entries are codes you assign to each branch office for your own records.
PAGE 157
Alternative Call Routing for Network Bandwidth Management Page 157 of 258 Procedure 7 Printing zone ALTPrefix 1 From the navigator, click System > Maintenance. The Maintenance web page appears. (See Figure 51.) Figure 51 System > Maintenance web page 2 Click Select by Functionality. The Select by Functionality web page appears. (See Figure 52 on page 158.
PAGE 158
Page 158 of 258 Alternative Call Routing for Network Bandwidth Management Figure 52 Maintenance web page showing Select by Functionality 3 553-3001-207 Click Zone diagnostics. The Maintenance Commands for Zones web page appears. (See Figure 53 on page 159.) You can also access this page if you click on Zones, as you see in Figure 49 on page 153. Standard 2.
PAGE 159
Alternative Call Routing for Network Bandwidth Management Page 159 of 258 Figure 53 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 53 shows a typical example of the results.
PAGE 160
Page 160 of 258 Alternative Call Routing for Network Bandwidth Management Show the status of the Alternative Call Routing for NBWM feature Procedure 8 Show Status The Show Status functionality displays the enable/disable status of the Alternative Call Routing for NBWM feature. The configured zones and the status of the feature for each zone can be listed. 553-3001-207 1 From the navigator, click System > Maintenance. The Maintenance web page appears. (See Figure 51 on page 157.
PAGE 161
Alternative Call Routing for Network Bandwidth Management Page 161 of 258 Figure 54 Show the status of the Alternative Call Routing feature for the branch office zone 5 Select ALL or a zone number from the Zone Number drop-down list. 6 Click Submit to enter the data The display updates with the data associated with that zone. Figure 54 shows a typical example of the results.
PAGE 162
Page 162 of 258 Alternative Call Routing for Network Bandwidth Management 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.
PAGE 163
Alternative Call Routing for Network Bandwidth Management Page 163 of 258 Sample printout: # Alarms Suppression Time 10 50 11 0 12 1000 Where # is the column header for zone number. Element Manager maintenance Enable a zone’s branch office behavior You can configure the Alternative Call Routing for NBWM feature while you configure the zone’s branch office behavior. Procedure 9 Enabling a zone’s branch office behavior 1 From the navigator, click System > Maintenance.
PAGE 164
Page 164 of 258 Alternative Call Routing for Network Bandwidth Management Figure 55 Enable a zone’s branch office behavior 5 Select the zone number you want to configure from the Zone Number drop-down list. 6 Select the check box beside the Alternate Routing for Branch option to enable the feature. 7 Click Submit. The display updates with new configuration data for the zone you specified. End of Procedure 553-3001-207 Standard 2.
PAGE 165
Alternative Call Routing for Network Bandwidth Management Page 165 of 258 Suppress alarms Procedure 10 Suppress Alternative Call Routing for NBWM alarms You can suppress alarms QoS0038 and QoS0039 for a configurable amount of time (0 - 3600 seconds). 1 Click IP Telephony > Zones > Configuration 2 Click beside the Zone, or click the Zone you are programming, to expand the choices under it. 3 Enter digits in Alarm Suppression Time Period (ZAST). See Figure 56 on page 165.
PAGE 166
Page 166 of 258 Alternative Call Routing for Network Bandwidth Management Feature operation No specific operating procedures are required to use this feature 553-3001-207 Standard 2.
PAGE 167
224 Page 167 of 258 Dialing Plan configuration Contents This section contains information on the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 On-net dialing plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Off-net dialing plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Routing calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 168
Page 168 of 258 Dialing Plan configuration On-net dialing plan Note: The SRG only supports only one dialing plan option at a time. CDP and UDP dialing plan options cannot be configured at the same time in the same system. The SRG supports the following dialing plans: • Coordinated Dialing Plan (CDP) – BUID is the same as the Directory Number (DN) • Uniform Dialing Plan (UDP) – Location code is added to the DN for the BUID Note 1: Nortel recommends that the SRG use CDP.
PAGE 169
Dialing Plan configuration Page 169 of 258 However, this configuration represents only one way that the dialing plan could be configured. PSTN calls can be routed according to the point of origin (main office or branch office) and/or the desired destination, and can 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.
PAGE 170
Page 170 of 258 Dialing Plan configuration Routing calls SRG user call to an SRG PSTN The SRG user telephone is registered at the main office. The SRG user telephones are physically located at the branch office, so routing of local PSTN calls back to the branch office is essential, even if they are registered with the main office. Branch office behavior of the SRG user telephones at the main office is configured by setting branch office zone characteristics through LD 117 at the main office.
PAGE 171
Dialing Plan configuration Page 171 of 258 Zone-based digit manipulation For SRG users in Normal Mode, it may be desirable to provide routing that is different from that provided to main office users. For example, it may be desirable to route certain calls directly to the SRG PSTN trunk, rather than receive the same routing as non-SRG users in the main office.
PAGE 172
Page 172 of 258 Dialing Plan configuration For a given branch office, there may be more than one zone defined at the main office. Therefore, different SRG users may receive different routing treatments. The combination of zone-based digit manipulation and CS 1000 routing capabilities can be used to achieve many other routing outcomes for SRG user calls. Calling Line ID composition Digital manipulation is commonly used for digit insertion and deletion.
PAGE 173
Dialing Plan configuration Page 173 of 258 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 16.
PAGE 174
Page 174 of 258 Dialing Plan configuration • At the branch office, configure the Virtual Trunk to enable calls originating on SRG IP Phones in Normal Mode to reach the branch office. Refer to IP Peer Networking: Installation and Configuration (553-3001-213) for details. • At the branch office, configure trunks for access to the PSTN. • At the main office, configure the branch office zone properties in LD 117, excluding the ZACB and ZDP properties.
PAGE 175
Dialing Plan configuration • Page 175 of 258 At the branch office (see Procedure 13 on page 187): 1 Configure the Route List Index. 2 Configure ESN. These steps can be done using overlays, as described in this section, or in Element Manager and NRS Manager. Refer to IP Peer Networking: Installation and Configuration (553-3001-213) for more details. For information on configuring the dialing plan at the branch office, refer to SRG50 Configuration Guide.
PAGE 176
Page 176 of 258 Dialing Plan configuration For example, assume that AC1 = 1, AC2 = 2, and ZDP = 101. If an SRG user dials “1 87654321”, ZDP is inserted in the dialed digits to form a digit string of “1 101 87654321”. If an SRG user dials “2 87654321”, ZDP is inserted in the dialed digits to form a digit string of “2 101 87654321”. • CHG ZACB AC1 AC2 In this configuration, only calls dialed with AC1 undergo zonebased digit manipulation.
PAGE 177
Dialing Plan configuration 2 Page 177 of 258 Configure the ZDB property for the branch office zone in the main office. Refer to IP Peer Networking: Installation and Configuration (553-3001213). LD 117 – Define the zone digit manipulation for the branch office zone at the main office.
PAGE 178
Page 178 of 258 Dialing Plan configuration routes the call to the NRS because it recognizes “101 87654321” after the Access Code rather than “87654321”. The Access Code (“1”) is not included in the digit string that is sent to the NRS. The NRS recognizes “101” at the front of the digit string and routes the call to the destination SRG. At the branch office, the ESN Special Number is configured (step 2 on page 190) to remove “101” from the digit string and route the call based on the digits “87654321”.
PAGE 179
Dialing Plan configuration Page 179 of 258 LD 86 – Configure the Digit Manipulation Index at the main office. (Part 2 of 2) Prompt Response Description INST x...x Insert. Up to 31 leading digits can be inserted, usually none at the main office. Default is none. ISPN IP Special Number For off-net calls For on-net calls (YES) NO CTYP Call type to be used by the call. This call type must be recognized by the NRS and far-end switch. This is critical for correct CLID behavior.
PAGE 180
Page 180 of 258 Dialing Plan configuration LD 86 – Configure Route List Index. (Part 2 of 2) Prompt Response 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, CS 1000S system, Media Gateway 1000B, and Media Gateway 1000T 1-999 Digit Manipulation Index number as defined in LD 86, FEAT = DGT (see step a on page 178). ...
PAGE 181
Dialing Plan configuration 4 Page 181 of 258 Configure ESN Special Number and Digit Manipulation. LD 90 – Configure ESN Special Number and Digit Manipulation. Prompt Response Description REQ NEW Add new data. CUST xx Customer number as defined in LD 15 FEAT NET Network translation tables AC1 AC2 Translator Access Code 1 (NARS/BARS) Access Code 2 (NARS) TYPE SPN Special code translation data block SPN x...
PAGE 182
Page 182 of 258 Dialing Plan configuration After configuring the zone-based digit manipulation (step 1 on page 175 and step 2 on page 177) and specialized route (step 3 on page 178), the route must be associated with the ESN Special Number. The main office ESN Special Number configuration is based on new digits inserted by zone-based digit manipulation. The digits are processed based on the Access Code, AC1 or AC2, that was dialed.
PAGE 183
Dialing Plan configuration Page 183 of 258 ESN Special Numbers are configured in LD 90. Respond to the prompts as follows: • TRAN — Enter the Access Code. • TYPE — Enter SPN for this configuration, as the ZDP value configured in step 3 on page 178 is usually a unique non-dialable number. • SPN — Enter the ZDP value plus enough digits to distinguish the type of number, such as national, international, or local.
PAGE 184
Page 184 of 258 Dialing Plan configuration CLTP NATL ... SPN FLEN ... RLI CLTP ... 1015 10 7 digits for long-distance + 3 digits for ZDP 30 LOCL SPN 1016 FLEN 10 ... 7 digits for long-distance + 3 digits for ZDP RLI 30 CLTP LOCL ... Procedure 12 Configuring the NRS database After configuring main office routing to the NRS, the NRS database must be provisioned to identify the desired endpoint for the calls.
PAGE 185
Dialing Plan configuration Page 185 of 258 Figure 57 NRS – Routing Entries window with no endpoint selected 4 Choose the appropriate Service Domain, L1 Domain, and L0 Domain from the corresponding drop-down menus. 5 Click on Look up to open a window with a lookup path for gateway endpoints. 6 Click Search to display a list of gateway endpoints (see Figure 58), and click on the endpoint at the branch office.
PAGE 186
Page 186 of 258 Dialing Plan configuration Figure 59 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 60 on page 186. Figure 60 NRS — Add Routing Entry 8 553-3001-207 Configure the numbering plan entries for the branch office.
PAGE 187
Dialing Plan configuration Page 187 of 258 The type of number configured in the NRS should be set to match the type of number as configured in the main office. Note: 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.
PAGE 188
Page 188 of 258 Dialing Plan configuration a. Configure the DMI in LD 86 with the DGT feature. LD 86 – Configure Digit Manipulation Index at the branch 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 by prompt MXDM in LD 86. DEL (0)-19 Number of leading digits to be deleted.
PAGE 189
Dialing Plan configuration b. Page 189 of 258 Configure the RLI in LD 86 with the RLB feature. LD 86 – Configure Route List Index. Prompt Response Description REQ NEW Add new data. CUST xx Customer number as defined in LD 15 FEAT RLB Route List data block 0-127 0-255 0-999 Route List Index to be accessed CDP and BARS NARS FNP ENTR 0-63 X Entry number for NARS/BARS Route List Precede with x to remove.
PAGE 190
Page 190 of 258 Dialing Plan configuration INST CTYP LOC REQ CUST FEAT RLI ENTR LTER ROUT ... DMI ... 2 Set according to associated SPN pattern NEW 0 RLB 18 0 NO 18 18 Configure ESN Special Number and Digit Manipulation. LD 90 – Configure ESN Special Number and Digit Manipulation. (Part 1 of 2) Prompt Response Description REQ NEW Add new data.
PAGE 191
Dialing Plan configuration Page 191 of 258 LD 90 – Configure ESN Special Number and Digit Manipulation. (Part 2 of 2) Prompt Response Description - FLEN (0)-24 Flexible Length The number of digits the system expects to receive before accessing a trunk and outpulsing these digits. 0-999 Route List Index configured in LD 86 (see step 1 on page 187) ...
PAGE 192
Page 192 of 258 Dialing Plan configuration Configuring the dialing plan using CS 1000 Element Manager From Element Manager, configure the branch office–specific zone dialing plan and Access Codes. From the navigator, select IP Telephony > Zones. From the Zones window in Element Manager, select the Branch Office Dialing Plan and Access Codes option, and enter the necessary information. Refer to Figure 61.
PAGE 193
Dialing Plan configuration Page 193 of 258 The calls must be routed according to the branch office ESN configuration. 2 From an SRG IP Phone in Normal Mode: a. Make a call to the local PSTN. b. Make a long-distance call. The calls must be routed according to the ESN configuration that was configured in Procedure 11 on page 175.
PAGE 194
Page 194 of 258 Dialing Plan configuration For specific examples on the dialing plans, refer to “Dialing plan examples” on page 193. • Option 1: DN ranges in the main office and SRG are unique, and DNs for SRG IP Phones are the same in both Normal and Local mode. This is the recommended configuration to support seamless dialing on both systems. See “Option 1: DN ranges in the main office and SRG are unique; DNs for SRG IP Phone are the same in Normal and Local Mode” on page 200.
PAGE 195
Dialing Plan configuration Page 195 of 258 Figure 62 Normal Mode: Main office telephone calls an analog phone at the SRG Normal Mode: Main office telephone calls a branch IP Phone The call is recognized as a main office number, and the call is directed to the SRG IP telephone using internal routing at the main office.
PAGE 196
Page 196 of 258 Dialing Plan configuration Figure 63 Normal Mode: Main office telephone makes a call over the PSTN through the SRG 553-3001-207 Standard 2.
PAGE 197
Dialing Plan configuration Page 197 of 258 Normal Mode: SRG IP Phone makes a call over the PSTN Zone management at the main office recognizes that an SRG IP Phone in Normal Mode is dialing the PSTN. Figure 64 shows how the call proceeds.
PAGE 198
Page 198 of 258 Dialing Plan configuration A telephone registered to the SRG calls another telephone registered to the SRG The SRG routes the call internally. Local Mode: SRG telephone calls an SRG IP Phone The call is handled by the SRG and is sent directly to the SRG IP Phone. Local Mode: SRG telephone calls a main office telephone In this case, the WAN or NRS is not accessible. Figure 65 on page 199 shows how the call proceeds. Note: The user must have configured the fallback route appropriately.
PAGE 199
Dialing Plan configuration Page 199 of 258 Figure 65 Local Mode: SRG telephone calls a main office telephone Local Mode: Main office telephone calls an SRG IP Phone The call is treated according to main office redirection configuration, such as forwarding to voicemail or continuous ringback.
PAGE 200
Page 200 of 258 Dialing Plan configuration Option 1: DN ranges in the main office and SRG are unique; DNs for SRG IP Phone are the same in Normal and Local Mode This is the recommended CDP configuration to offer seamless dialing. In this configuration, the user dials the same DN for SRG IP Phones in either Normal or Local Mode. The DNs for SRG IP Phones are configured to be the same on both the SRG and main office. This allows seamless dialing from both the SRG and main office.
PAGE 201
Dialing Plan configuration Page 201 of 258 Figure 66 CDP Option 1: Main office and SRG DN ranges are unique; SRG IP Phone DNs are the same in Normal and Local Mode Call scenarios Common call scenarios for this CDP option are listed in “Call scenarios” on page 194. The following additional call scenarios are unique to this CDP option: • An SRG analog telephone registered to the SRG calls a telephone registered at the main office that can also be an SRG IP Phone in Normal Mode.
PAGE 202
Page 202 of 258 Dialing Plan configuration Figure 67 WAN is up. SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the main office (Normal Mode) 553-3001-207 Standard 2.
PAGE 203
Dialing Plan configuration Page 203 of 258 Figure 68 WAN is down.
PAGE 204
Page 204 of 258 Dialing Plan configuration Configuration To configure the main office: • Configure the ESN Control Block for CDP in LD 86. > LD 86 REQ NEW CUST 0 FEAT ESN CDP YES MXSC 50 NCDP 4 DLTN YES • Configure the CDP Distant Steering Code (DSC) in LD 87. > LD 87 REQ NEW CUST 0 FEAT CDP TYPE DSC DSC 50 FLEN 4 RLI 12 To configure the NRS (H.323 Gatekeeper): • Create CDP Domain: “MO_BO_CDP”. • Create H.323 endpoints: “MO”, “BO”.
PAGE 205
Dialing Plan configuration • Page 205 of 258 Set the destination code for the VoIP trunk to 30 (retain all digits) or 34 (remove first digit). For example, BUID dialout = 342XX. The VoIP route destination codes 30 (no digits dropped) and 34 (1 digit dropped) route any call that starts with 30 or 34 out of the system over the VoIP trunk to the main office. The main office access code length is still 0.
PAGE 206
Page 206 of 258 Dialing Plan configuration Since the SRG DN range is limited to about 200 DNs, this configuration only works if SRG dialing to the main office is limited to the redirected IP Phones and to a small number of main office telephones, such as to a central attendant and voicemail lines. Figure 69 shows this CDP option.
PAGE 207
Dialing Plan configuration Page 207 of 258 Figure 70 WAN is up.
PAGE 208
Page 208 of 258 Dialing Plan configuration • Local Mode: SRG IP Phones are registered to the SRG. In this scenario, the WAN and the NCS are working. However, the SRG IP Phones are redirected to the SRG and are in Local Mode (Call Forward All Calls is inactive). The following occur: — Telephones registered at the SRG dial local DNs (see the common call scenarios given in “Call scenarios” on page 194). — SRG calls to the main office use VoIP routing (see Figure 71).
PAGE 209
Dialing Plan configuration Page 209 of 258 Figure 71 WAN is down.
PAGE 210
Page 210 of 258 Dialing Plan configuration Configuration To configure the main office: • Configure the ESN Control Block for CDP in LD 86. > LD 86 REQ NEW CUST 0 FEAT ESN CDP YES MXSC 50 NCDP 4 DLTN YES • Configure the CDP Distant Steering Code (DSC) in LD 87. > LD 87 REQ NEW CUST 0 FEAT CDP TYPE DSC DSC 50 FLEN 4 RLI 12 To configure the NRS (H.323 Gatekeeper): • Create CDP Domain: “MO_BO_CDP”. • Create H.323 endpoints: “MO”, “BO”.
PAGE 211
Dialing Plan configuration • Page 211 of 258 Set the destination code for the VoIP trunk to 6, the same value as the access code. For example, BUID dialout = 632XX. The main office access code length is still 0. • Assign the telephones registered to the SRG (IP Phones or analog [500/2500-type] telephones) to a different range, such as 30XX, than the telephones registered to the main office.
PAGE 212
Page 212 of 258 Dialing Plan configuration (3XXX) so that the call can route correctly through the main office VoIP trunk. Users registered at the main office dial the main office DN (3XXX) for the SRG IP Phone. In Local mode, the users registered to the SRG still dial the SRG IP Phone DN (4XXX). The main office users can not call the SRG IP Phone by dialing the main office DN for the telephone (3XXX) because the NRS cannot route the call to the SRG.
PAGE 213
Dialing Plan configuration Page 213 of 258 Call scenarios Common call scenarios for this CDP option are listed in “Call scenarios” on page 194. The following additional call scenarios are unique to this CDP option: • Normal Mode: An SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the main office. In this scenario, the telephone registered to the SRG can either dial the SRG DN or the main office DN for the SRG IP Phone.
PAGE 214
Page 214 of 258 Dialing Plan configuration Figure 73 WAN is up: SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the main office (Normal Mode) • Local Mode: SRG IP Phones are registered at the SRG. In this scenario, the WAN and the NCS are working. If the main office user dials the SRG DN (42xx) to call the IP Phone, the call goes through. 553-3001-207 Standard 2.
PAGE 215
Dialing Plan configuration Page 215 of 258 Configuration To configure the main office: • Configure the ESN Control Block for CDP in LD 86. > LD 86 REQ NEW CUST 0 FEAT ESN CDP YES MXSC 50 NCDP 4 DLTN YES • Configure the CDP Distant Steering Code (DSC) in LD 87. > LD 87 REQ NEW CUST 0 FEAT CDP TYPE DSC DSC 4 FLEN 4 RLI 12 To configure the NRS (H.323 Gatekeeper): • Create CDP Domain: “MO_BO_CDP”. • Create H.323 endpoints: “MO”, “BO”.
PAGE 216
Page 216 of 258 Dialing Plan configuration For more information on configuring the main office and NRS, refer to Branch Office: Installation and Configuration (553-3001-214) and IP Peer Networking: Installation and Configuration (553-3001-213). For more information on configuring the SRG, refer to SRG50 Configuration Guide. Universal Dialing Plan Overview Figure 74 on page 217 shows an example of a Uniform Dialing Plan (UDP) using location codes (Access Code + LOC + DN) configuration.
PAGE 217
Dialing Plan configuration Page 217 of 258 Figure 74 UDP using location codes Call scenarios This section describes how calls interact between the SRG and main office with UDP. Calling from main office to the SRG and SRG PSTN, in Normal mode In this scenario, a telephone registered at the main office calls a telephone registered to the SRG, or makes a call over the PSTN through the SRG. Figure 75 on page 218 shows this scenario.
PAGE 218
Page 218 of 258 Dialing Plan configuration Figure 75 Calling from the main office to the SRG and SRG PSTN, in Normal Mode 553-3001-207 Standard 2.
PAGE 219
Dialing Plan configuration Page 219 of 258 Calling from the SRG to the main office, in Normal Mode In this scenario, a telephone registered at the SRG calls an SRG IP Phone and a main office IP Phone registered to the main office. Figure 76 shows this scenario. Figure 76 WAN is up.
PAGE 220
Page 220 of 258 Dialing Plan configuration Calling in Local Mode In this scenario, the IP Phones at the SRG are in Local Mode because the WAN is down. The SRG IP telephones are reregistered to the SRG and call forward BUID is inactive on these telephones. These IP Phones are registered at the SRG, and call forward BUID is inactive on these telephones. The inset shows a main office call to SRG telephones. The user must dial the SRG DN for the IP telephone (6002 instead of 3002).
PAGE 221
Dialing Plan configuration Page 221 of 258 Figure 77 WAN is down.
PAGE 222
Page 222 of 258 Dialing Plan configuration Configuration examples The following configurations are based on the examples provided in this section. For further information, refer to Branch Office: Installation and Configuration (553-3001-214). To configure the main office: • Configure the ESN Control Block for UDP in LD 86. > LD 86 REQ NEW CUST 0 FEAT ESN AC1 16 • Configure Digit Manipulation (DGT) in LD 86. > LD 86 REQ NEW FEAT DGT DMI 6 DEL 3 • Configure the UDP Location Code (LOC) in LD 90.
PAGE 223
Dialing Plan configuration • Page 223 of 258 Configure the UDP HLOC in LD 90. > LD 90 REQ NEW FEAT NET TRAN AC1 TYPE HLOC HLOC 501 DMI 6 • Configure the HLOC in the Customer Data Block in LD 15. > LD 15 REQ CHG TYPE CDB NET_DATA YES ISDN YES CLID YES ENTRY HLOC 501 • Configure the Virtual Trunk route in LD 16.
PAGE 224
Page 224 of 258 Dialing Plan configuration To configure the NRS (H.323 Gatekeeper): • Create H.323 endpoints: “MO”, “BO”. • Create Numbering Plan entries: — Choose type “UDP-LOC”. — Add “504” for endpoint “BO”. — Add “501” for endpoint “MO”. To configure the SRG: • Create route and destination code to main office. • In the main office screen: — Set the type of number to ESN LOC. — The VoIP trunk access code field is empty. — Set the main office Access Code Length to 1.
PAGE 225
240 Page 225 of 258 Emergency Services configuration Contents This section contains information on the following topics: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Emergency Services Access (ESA). . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Configuring the NRS for ESA SPN . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Testing the ESDN number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 226
Page 226 of 258 Emergency Services configuration IMPORTANT! In Normal Mode, an IP Phone must have a Virtual Trunk available and configured between the main office and branch office in order to complete an emergency services call. IMPORTANT! Do not route ESA calls to a node that has no direct ESA trunks. For SRG applications, Nortel recommends two alternative general methods to specify which digit string results in a call to emergency services: • Use the Emergency Services Access (ESA) feature.
PAGE 227
Emergency Services configuration Page 227 of 258 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 that the main office adds as it routes the call. The suggested prefix is the ESN home location code of the SRG, or alternately, the Numbering Plan Area (NPA) code of the SRG if there is not more than one Call Server in the NPA.
PAGE 228
Page 228 of 258 Emergency Services configuration The implications of routing calls to nodes without direct ESA trunks are as follows: • At the node without the direct ESA trunks, the node cannot route the ESA call directly to the PSAP. Instead, that node must re-route the call to another node. This re-routing is an unnecessary use of resources. • If the node is a CS 1000E node, the only tandem trunks are IP Peer trunks.
PAGE 229
Emergency Services configuration Page 229 of 258 ESA must be configured and tested on the main office Call Server and the SRG to differentiate between emergency calls originating from IP Phones at each location and calls originating on trunks. Use the following steps to configure ESA for emergency access at each location: 1 Determine the dialing plan (for example, numbering plan) for ESA calls. 2 Configure the main office emergency trunk (CAMA or PRI).
PAGE 230
Page 230 of 258 Emergency Services configuration 15 Configure the NRS for the ESA Special Number used. 16 Test ESDN using an analog (500/2500-type) telephone located at the branch office. 17 Test ESDN using an SRG IP Phone in Normal Mode and in Local Mode. Determining the dialing plan for ESA calls In many jurisdictions of the United States and Canada, the emergency number must be “911”.
PAGE 231
Emergency Services configuration Page 231 of 258 Procedure 15 Configuring the main office Use Element Manager or the Command Line Interface for this procedure. Refer to IP Peer Networking: Installation and Configuration (553-3001-213) for details. 1 Configure the main office emergency trunk (CAMA or PRI). Configure either analog CAMA or digital PRI to correctly signal the call identification. ESA overrides all restrictions.
PAGE 232
Page 232 of 258 Emergency Services configuration LD 24 – Configure Emergency Services Access. (Part 2 of 2) Prompt Response Description DDGT x...x Directing Digits (for CAMA Trunks)(for example, 1, 11, or 911). Up to four digits are accepted. DFCL x...x Default ESA Calling Number. The input must be the following lengths: • On a system that is not FNP equipped, 8 or 11 digits are accepted if the first digit of the input is ‘1’; otherwise the input must be 7 or 10 digits.
PAGE 233
Emergency Services configuration a. Page 233 of 258 Configure the branch office zone’s ESA dialing information in LD 117. LD 117 – Configure branch office zone ESA route. Command Description CHG ZESA Defines the ESA parameters for the branch office zone, where: • Zone = Zone number for the branch office. • ESA Route # = Virtual Trunk route to SRG. • AC = Access Code to add to dialed digits. If no AC is required, enter AC0 in place of AC1 or AC2.
PAGE 234
Page 234 of 258 Emergency Services configuration b. Configure the ESN Special Number at the main office. For information on configuring ESN, refer to Basic Network Features (553-3001-379). i. Configure the Digit Manipulation Index in LD 86 with the DGT feature. LD 86 – Configure Digit Manipulation Index. Prompt Response Description REQ NEW Add new data.
PAGE 235
Emergency Services configuration ii. Page 235 of 258 Configure the Route List Index in LD 86 with the RLB feature. LD 86 – Configure Route List Index. Prompt Response Description REQ NEW Add new data. CUST xx Customer number as defined in LD 15 FEAT RLB Route List data block 0-127 0-255 0-999 Route List Index to be accessed CDP and BARS NARS FNP ENTR 0-63 0-6 X Entry number for NARS/BARS Route List Route List entry number for CDP Precede with X to remove.
PAGE 236
Page 236 of 258 Emergency Services configuration iii. Configure the ESN Special Number and Digit Manipulation in LD 90. LD 90 – Configure ESN Special Number and Digit Manipulation. (Part 1 of 2) Prompt Response Description REQ NEW Add new data. CUST xx Customer number as defined in LD 15 FEAT NET Network translation tables AC1 AC2 Translator Access Code 1 (NARS/BARS) Access Code 2 (NARS) TYPE SPN Special code translation data block SPN x...
PAGE 237
Emergency Services configuration Page 237 of 258 LD 90 – Configure ESN Special Number and Digit Manipulation.
PAGE 238
Page 238 of 258 Emergency Services configuration Configuring the NRS for ESA SPN The NRS must be configured for the ESA Special Number (SPN). The NRS uses the ESA SPN to route the emergency call from the main office to the branch office. Nortel recommends that a consistent pattern be followed for all ESA calls. For example, use “0” + ESN Location code of the branch office node + the ESDN. An example for location code 725 would be: 0725911.
PAGE 239
Emergency Services configuration 2 Page 239 of 258 For analog (500/2500-type) telephones, dial the ESDN on an SRG analog (500/2500-type) telephone. The calls must go out on the emergency trunk(s) in the branch office. End of Procedure Configuring ESA using Element Manager From Element Manager, you can configure ESA. From the Zone List window in Element Manager (see Figure 61 on page 192), select the Branch Office Emergency Service option, and enter the necessary information.
PAGE 240
Page 240 of 258 Emergency Services configuration Access to Emergency Service using SPN should be configured in the following circumstances: • When there is more than one number used for accessing Emergency Service; for example, when there are different numbers for Police, Fire, and Ambulance services. • In markets where the ESA feature is not available (outside of North America and CALA). To configure Emergency Service using SPN, follow the process outlined in “Dialing Plan configuration” on page 167.
PAGE 241
244 Page 241 of 258 Enhanced UNIStim Firmware Download Contents Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Firmware upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Description This section applies only to the main office CS 1000 Release 4.
PAGE 242
Page 242 of 258 Enhanced UNIStim Firmware Download For CS 1000 Release 4.5, if the required firmware file does not exist on the SRG50, or the version of the file is incorrect, the SRG50 initiates an FTP session to the TPS for the IP Phone to retrieve the required file. The SRG50 upgrades the IP Phone and redirects the IP Phone back to the CS 1000. For Release 3.0 and Release 4.0, if the required file does not exist on the SRG50, the SRG50 must be patched to the proper firmware level.
PAGE 243
Enhanced UNIStim Firmware Download Page 243 of 258 Procedure 18 Upgrading firmware Upgrade procedures are generally found in Communication Server 1000S: Upgrade Procedures (553-3031-258). Relevant information can be found in IP Line: Description, Installation, and Operation (553-3001-365). 1 At the Main office, upgrade IP Phone firmware on the Signaling Server. For instructions, see the chapter “Uploading software upgrade files” in Communication Server 1000S: Upgrade Procedures (553-3031-258).
PAGE 244
Page 244 of 258 553-3001-207 Enhanced UNIStim Firmware Download Standard 2.
PAGE 245
250 Page 245 of 258 Appendix A: Media Redirection Scenarios In addition to basic call scenarios, Network Bandwidth Management also supports the following media redirection scenarios: • Scenario 1: Codec switches correctly during media redirection. See Table 17 on page 246. • Scenario 2: Call transfer works correctly with IP Phones: — Scenario 2.1: Call Transfer from an SRG IP Phone in Normal Mode to main office IP Phone. See Table 18 on page 246. — Scenario 2.
PAGE 246
Page 246 of 258 Appendix A: Media Redirection Scenarios Note 1: The zone table is examined using the commands in LD 117. See Software Input/Output: Maintenance (553-3001-511) for more information on these commands. Note 2: In these scenarios, consult the zone table at the main office for accurate bandwidth usage information.
PAGE 247
Appendix A: Media Redirection Scenarios Page 247 of 258 Table 18 Scenario 2.1: Call transfer from SRG IP Phone in Normal Mode to main office IP Phone (Part 2 of 2) Event Result 2 The SRG IP Phone registered to the main office initiates a call transfer to a main office IP Phone. The SRG TDM telephone is put on hold. A speech path is established between the SRG IP Phone registered to the main office and the main office IP Phone. The zone table indicates interzone bandwidth usage.
PAGE 248
Page 248 of 258 Appendix A: Media Redirection Scenarios Table 19 Scenario 2.2: Call transfer from main office IP Phone to SRG IP Phone in Normal Mode (Part 2 of 2) Event Result 4 The call is released. The zone table indicates bandwidth usage for the call is unreserved correctly. Table 20 Scenario 3.1: Conference call between branch office and main office, initiated by SRG IP Phone in Normal Mode Event Result 1 An SRG TDM telephone calls an SRG IP Phone registered to the main office.
PAGE 249
Appendix A: Media Redirection Scenarios Page 249 of 258 Table 21 Scenario 3.2: Conference call between main office and branch office, initiated by main office IP Phone Event Result 1 An SRG TDM telephone calls a main office IP Phone. A speech path is established between the SRG TDM telephone and the main office IP Phone. The zone table indicates interzone bandwidth usage. 2 The main office IP Phone initiates a conference call to an SRG IP Phone registered to the main office.
PAGE 250
Page 250 of 258 553-3001-207 Appendix A: Media Redirection Scenarios Standard 2.
PAGE 251
256 Page 251 of 258 List of terms Branch office An SRG that is remote from the main office. The SRG provides telephony services using the main office servers (for Normal Mode) or local system services when the SRG loses IP communication with the main office (Local Mode). 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, refer to Dialing Plans: Description (553-3001-183).
PAGE 252
Page 252 of 258 List of terms provided by ESA. Please note, however, that the ESA feature is also generally useful for users who are not subject to legislation, and is broad enough to be used in different countries. For example, it will be appreciated by any customer who wants to route emergency calls in a special manner, or who wants to be notified when a telephone user makes an emergency call.
PAGE 253
List of terms Page 253 of 258 Transport Control Protocol (TCP), which establishes a virtual connection between a destination and a source. IP by itself is something like the postal system. It enables you to address a package and drop it in the system, but there's no direct link between you and the recipient. TCP/IP, on the other hand, establishes a connection between two hosts so that they can send messages back and forth for a period of time. LAN Local Area Network.
PAGE 254
Page 254 of 258 List of terms PSTN Public Switched Telephone Network. The international telephone system based on copper wires carrying analog voice data. This is in contrast to newer telephone networks based on digital technologies. Telephone service carried by the PSTN is often called plain old telephone service (POTS). QoS Quality of Service, a networking term that specifies a guaranteed throughput level.
PAGE 255
List of terms Page 255 of 258 TPS IP Phone Terminal Proxy Server. This server controls the connection of IP Phones. It resides on the Signaling Server with an emergency backup on the Voice Gateway Media Card. UDP Uniform Dialing Plan. Each location within the network is assigned a Location Code, and each telephone has a Directory Number that is unique within the network. Under the UDP, the SRG must include the location code in the Branch User ID (BUID).
PAGE 256
Page 256 of 258 553-3001-207 List of terms Standard 2.
PAGE 257
Page 257 of 258 Index B E Branch office, 251 Emergency Services Access (ESA), 226 Branch office dialing plan, 30 Emergency Services configuration, 225 Emergency Service using Special Numbers, 239 C ESN Access Codes, 31 Capacity, 29 CDP, 251 G CLID composition, 172 Gatekeeper, 252 CLID verification, 173 Gateway, 252 Conference calls, 28 Configuring ESA for branch office, 228 Configuring ESA using Element Manager, 239 Configuring the dialing plan, 192 H H.
PAGE 258
Page 258 of 258 Index Main office hardware description, 17 T Main office information required by the SRG, 37 Telephones, 19 Main office requirements, 20 Testing PSTN access, 192 Media Redirection Scenarios, 245 Testing the ESDN number, 238 Music on hold, 31 Testing the telephone in Local Mode, 24 Time of Day, 27 N Time of day, 27 NCS, 253 TPS, 255 Normal Mode, 253 Normal Mode operation, 22 U NRS, 253 UDP, 255 Universal Dialing Plan, 216 O Off-net dialing plan, 169 V On-net dialing plan
PAGE 259
PAGE 260
Family Product Manual Contacts Copyright FCC notice Trademarks Document number Product release Document release Date Publish Nortel Communication Server 1000 Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide Copyright © Nortel Networks Limited 2006 All Rights Reserved Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant.