Nortel Remote Gateway 50 Configuration Manual
  1. Manuals
  2. Brands
  3. Nortel Manuals
  4. Gateway
  5. 50 Series
  6. Configuration manual

Nortel Remote Gateway 50 Configuration Manual

Main office configuration for survivable remote gateway
Hide thumbs Also See for Remote Gateway 50:
Table of Contents

Advertisement

Quick Links

Download this manual
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. 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.

Advertisement

Table of Contents
loading

Related Manuals for Nortel Remote Gateway 50

Summary of Contents for Nortel Remote Gateway 50

  • Page 1: Procedure

    All Rights Reserved 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...

  • Page 3: Revision History

    Adaptive Network Bandwidth Management. See pages August 2005 Standard 1.00. This document is a new document to support Communication Server 1000 Release 4.5. Main Office Configuration for Survivable Remote Gateway 50 and 84. Page 3 of 258 Configuration Guide...
  • Page 4 Page 4 of 258 Revision history 553-3001-207 Standard 2.00 January 2006...

  • Page 5: Table Of Contents

    Introduction ..........Main Office Configuration for Survivable Remote Gateway 50...
  • Page 6 SRG information required by the main office ....Main office information required by the SRG ....Zone parameters .
  • Page 7 List of terms ....... 251 Main Office Configuration for Survivable Remote Gateway 50...
  • Page 8 Page 8 of 258 Contents 553-3001-207 Standard 2.00 January 2006...

  • Page 9: List Of Procedures

    Show Status ........160 Procedure 9 Enabling a zone’s branch office behavior ..163 Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • 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 .

  • Page 11: About This Document

    Subject This document describes the Main Office Configuration for the Survivable Remote Gateway 50: Configuration Guide (553-3001-207). Information in this document complements information found in documents in the Communication Server 1000 documentation suite, as listed in “Related information”...

  • Page 12: Applicable Systems

    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) •...

  • Page 13: Related Information

    Optivity Telephony Manager: System Administration (553-3001-330) • Element Manager: System Administration (553-3001-332) • IP Line: Description, Installation, and Operation (553-3001-365) • ISDN Primary Rate Interface: Features (553-3001-369) • Basic Network Features (553-3001-379) Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 14 • 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) •...

  • Page 15: Overview

    Media Gateway 1000B product, there is a new “mini” model for the smaller branch office, known as the SRG50. The SRG50 is optimized for the 5-32 user branch office. Main Office Configuration for Survivable Remote Gateway 50 Page 15 of 258 Configuration Guide...
  • Page 16 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.

  • Page 17: Main Office Hardware Description

    All of the systems appearing in the list perform identical main office functions as far as the SRG is concerned. For information about the SRG, refer to SRG50 Configuration Guide. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...

  • Page 18: Signaling Server

    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 • Web server for Element Manager and Network Routing Service (NRS) Manager A second Signaling Server can be used to provide redundancy in the case of failure in the primary Signaling Server at the main office.
  • Page 19 The SRG supports the following telephones: • IP Phone 2001 • IP Phone 2002 • IP Phone 2004 • IP Phone 2007 • IP Softphone 2050 • Mobile Voice Client (MVC) 2050 Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...

  • Page 20: Main Office Requirements

    • 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.

  • Page 21: Optional Features To Enhance Srg Functionality

    SRG IP Phones to access set-based Network Class of Service (NCOS) features. • Adaptive Network Bandwidth Management package 407. • Alternative Call Routing for Network Bandwidth Management. For software and hardware requirements for SRG, refer to SRG50 Configuration Guide. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...

  • Page 22: Normal Mode And Local Mode 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.
  • Page 23 SRG IP Phones in Normal Mode remain registered with the main office if the Primary NRS fails and no Alternate NRS is available. They can call any main office telephone or IP Phones in Normal Mode in other branch offices. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...

  • Page 24: Testing The Telephone In Local Mode

    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: Ip Phone Calls

    For more information on Direct IP media path functionality, see IP Peer Networking: Installation and Configuration (553-3001-213). Main Office Configuration for Survivable Remote Gateway 50 from the set to return to Normal Mode. Configuration Guide...

  • Page 26: Bandwidth Management 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 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: Miscellaneous Items

    Server. A Virtual Trunk route is selected according to the digits dialed. The call is routed over a Virtual Trunk to the branch office. The SRG processes the incoming Virtual Trunk call and terminates it to the local analog (500/ Main Office Configuration for Survivable Remote Gateway 50 IMPORTANT! Configuration Guide...

  • Page 28: Conference Calls

    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.

  • Page 29: Capacity

    • Communication Server 1000M and Meridian 1: Small System Planning and Engineering (553-3011-120). Main Office Configuration for Survivable Remote Gateway 50 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: Branch Office Dialing Plan

    Virtual Trunks capacity The SRG capacity to support a number of simultaneous calls depends on the specific codec type 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: Music On Hold

    Music on Hold is provisioned. The use of the G.729A/AB codec between the main office and the branch office may impact the music quality. Note: G.723 codec is not supported on SRG50. Main Office Configuration for Survivable Remote Gateway 50 page page 167.

  • Page 32: Cross Reference For Branch Office And Srg50 Terminology

    Cross reference for branch office and SRG50 terminology Table 1 lists configuration-related terms and contexts where branch office and SRG50 terminology differ. Table 1: Cross reference for branch office and SRG50 terminology (Part 1 of 2) Term or context dialing plan routing alternate routing selection Type of number...
  • Page 33 Table 1: Cross reference for branch office and SRG50 terminology (Part 2 of 2) Term or context telephone numbers (internal, not PSTN) Main Office Configuration for Survivable Remote Gateway 50 Branch office Network Class of Service (NCOS) SRG50 DN, MOTN...
  • Page 34 Page 34 of 258 Overview 553-3001-207 Standard 2.00 January 2006...

  • Page 35: Setting Up The Main Office

    SRG information required by the main office • Main office information required by the SRG • Zone parameters • IP Phone passwords and parameters • Branch office IP Phone configuration Main Office Configuration for Survivable Remote Gateway 50 Page 35 of 258 Configuration Guide...

  • Page 36: Srg Information Required By 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. The following information is required: • an inventory of IP Phones that will be installed on the SRG so the administrator knows what type of telephone to assign to each main office terminal record...

  • Page 37: Main Office Information Required By The Srg

    Main office components Main office IP network information: Main office call server type Primary network connect server address Alternate network connect server Network Connect server port Main Office Configuration for Survivable Remote Gateway 50 Information about this system S1000 (default) Configuration Guide...
  • Page 38 Table 3 Main office interoperation information (Part 2 of 3) Main office components 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...

  • Page 39: Zone Parameters

    Zone parameters are defined at the main office in LD 117 (see Procedure 1 on page 40) and applied to IP Phones in LD 11. Use Procedure 1 on Main Office Configuration for Survivable Remote Gateway 50 Information about this system page 40 to configure ESN and SRG zones.

  • Page 40: Configuring Esn And Srg Zones

    Procedure 1 Configuring ESN and SRG zones 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. Configure the Home Location Code (HLOC) and the Virtual Private Network Identifier (VPNI).
  • Page 41 Configure the zone properties for IP Telephony bandwidth management. Use LD 117 or Element Manager. Refer to IP Peer Networking: Installation and Configuration (553-3001-213). Main Office Configuration for Survivable Remote Gateway 50 Description Integrated Services Digital Network Virtual Private Network Identifier for Bandwidth...
  • Page 42 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. Zone 0, the default zone, must not be configured as a branch office zone.
  • Page 43 Select IP Telephony > Zones in Element Manager navigator. The Zones window opens (Figure 2 on page 44). The zone list is the main window used for zone configuration. Main Office Configuration for Survivable Remote Gateway 50 Description Enables features for branch office <zone>.
  • Page 44 Figure 2 Zone List web page Select the zone to be configured and configure the following properties. • • • • 553-3001-207 Standard 2.00 Basic Property and Bandwidth Management (see Figure 3 on page Dialing Plan and Access Codes (see Figure 61 on Emergency Service Information (see Figure 78 on Time Difference and Daylight Saving Time Property (see Figure 4 on page...
  • 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: Branch Office Ip Phone Configuration At 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 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: Configuring Branch Office Ip Phones At The Main Office Using Ld 11

    Configuring branch office IP Phones at the main office using LD 11 Configure the branch office zones and dialing plan. See Procedure 1 on page Configure the following telephone data in LD 11: • Terminal type • Customer Number • Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...

  • Page 48: A Zone

    • • LD 11 – Provision Branch User and SCPW at the main office Prompt Response REQ: NEW CHG TYPE: a...a CUST ZONE 0-255 SCPW xxxx 553-3001-207 Standard 2.00 Zone Prime DN to correspond to BUID Description Add new data, or change existing data. Terminal type.

  • Page 49: Bandwidth Management

    Network using Coordinated Dialing Plan ..... . . Main Office Configuration for Survivable Remote Gateway 50 Page 49 of 258...

  • Page 50: Introduction

    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.
  • Page 51 IP calls are affected by higher latency. This is because the codec configuration applies to both IP Peer calls and local IP (IP Line) calls. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • 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.

  • Page 53: Codec Selection

    When the codec lists meet the above conditions, one of the following codec selection algorithms selects the codec to be used: • H.323 Master/Slave algorithm • “Best Bandwidth” codec selection algorithm Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 54 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).
  • Page 55 The selected codec is the type considered as the best bandwidth codec type. To know whether one codec type has better bandwidth than another, see the rule as summarized in Table 4 on Main Office Configuration for Survivable Remote Gateway 50 page Configuration Guide...

  • Page 56: Configuring Bandwidth Management Parameters

    Table 4 “Best Bandwidth” algorithm — codec type G.711 A law G.711 A-law G.711 A-law G.711 mu-law G.711 mu-law G.729 A G.729 A G. 729 AB G. 729 AB G. 723.1 G. 723.1 Interoperability between CS 1000 and SRG The SRG is designed to interoperate with CS 1000 in a manner similar to MG 1000B but with a limitation with respect to codec selection policy.

  • Page 57: Zones

    Choose unique VPNIs for all Call Servers in the network. Choose unique Bandwidth Zone numbers for all Call Servers in the network. These are used when configuring the endpoints (telephones and gateways) on the Call Server. Main Office Configuration for Survivable Remote Gateway 50 page Configuration Guide...

  • Page 58: Enabling Codecs

    Choose unique Bandwidth Zone numbers for the Virtual Trunks in the network. Choose the codecs that will be enabled on each Call Server. Identify what the interzone codec strategy will be (BB-Best Bandwidth or BQ-Best Quality) for each zone in the network. Identify what the intrazone codec strategy will be (BB-Best Bandwidth or BQ-Best Quality) for each zone in the network.

  • Page 59: Configuring Bandwidth Management

    — Intrazone Preferred Strategy = Best Quality (BQ) — Intrazone Bandwidth = default (1000000) — Interzone Preferred Strategy = Best Bandwidth (BB) Main Office Configuration for Survivable Remote Gateway 50 page 60) or LD 117 (see “Configuration page...
  • Page 60 • Configure the IP Phone, DSP and Virtual Trunk data with the corresponding zone numbers. For example, for an IP Phone 2004 telephone in zone 8: Configuration using CS 1000 Element Manager Zones are configured from the Zones web page, shown in Figure 6. Refer to “Configuring zone parameters using CS 1000 Element Manager”...
  • Page 61 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. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 62 LD 117 Configure a new or existing Bandwidth Management zone. Command NEW | CHG ZONE <zoneNumber> [<intraZoneBandwidth> <intraZoneStrategy> <interZoneBandwidth> <interZoneStrategy> <zoneIntent> <zoneResourceType>] 553-3001-207 Standard 2.00 Description Configure a new zone (NEW) or change (CHG) an existing zone, where: • zoneNumber = 0-255 •...

  • Page 63: Maintenance Commands

    Click Maintenance Commands for Zones (LD 117). The Maintenance Commands for Zones web page opens, as shown in Figure 7 on page Main Office Configuration for Survivable Remote Gateway 50 64. This page lists all the configured zones. page page...
  • Page 64 Figure 7 Maintenance Commands for Zones web page Do one of the following: • • 553-3001-207 Standard 2.00 To display intrazone statistics: Select Print Interzone Statistics (PRT INTERZONE) from the Action drop-down list. Select a zone from the Zone Number drop-down list, by doing of the following: —...
  • Page 65 Zone 3. Figure 8 Element Manager — intrazone statistics Main Office Configuration for Survivable Remote Gateway 50 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.
  • Page 66 Figure 9 Element Manager — interzone statistics 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.

  • Page 67: Adaptive Network Bandwidth Management

    Voice over Internet Protocol (VoIP) networks based on real-time interaction. It provides the means to automatically adjust bandwidth limits and take corrective action in response to Quality of Service (QoS) Main Office Configuration for Survivable Remote Gateway 50 Description Print intrazone statistics for the identified zones, where: •...
  • 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.
  • Page 69 This feature operates between all IP Peer CS 1000 systems, including the Media Gateway 1000B and Survivable Remote Gateway 50. Call scenario A call is requested from a telephone in VPNI 1/Zone 2 on Call Server A to a telephone in VPNI 3/Zone 3 on Call Server B.
  • Page 70 Page 70 of 258 Bandwidth Management Figure 10 Call Progress with Adaptive Network Bandwidth Management 553-3001-207 Standard 2.00 January 2006...
  • Page 71 Virtual Trunk (VTRK) is used and appears in the zone table. Figure 11 shows an example of the bandwidth changes. Figure 11 Adaptive Network Bandwidth Management graph Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • 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.
  • Page 73 QoS alarms. However, making this value too large will result in loss of overall bandwidth, as shown in Figure 12 below and Figure 13 on Figure 12 Effect of the default CQos Coefficient Main Office Configuration for Survivable Remote Gateway 50 page Configuration Guide...
  • Page 74 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: Feature Packaging

    • Adaptive Network Bandwidth Management parameters are configured on the main office only and must not be configured at the branch offices. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...

  • Page 76: Configuring Adaptive Network 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. Enable the Call Admission Control (CAC) package. Configure CAC in Element Manager or LD 117: Tandem the outbound branch office calls by configuring the NRS. Tandem the inbound branch office calls by creating a dialing plan which routes all calls destined for the branch office through the main office.
  • Page 77 Bandwidth Management and CAC web page opens, as shown in Figure 14 page Note: Do not configure Adaptive Networks Bandwidth Management for Zone 0 or Virtual Trunk zones. Main Office Configuration for Survivable Remote Gateway 50 page 61) and click Adaptive Configuration Guide...
  • 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...
  • Page 79 Delay Alarm Coefficient (CD) Jitter Alarm Coefficient (CJ) Coefficient of QoS (CQoS) Recent Validity Time Interval (CACVT) Main Office Configuration for Survivable Remote Gateway 50 Bandwidth Management Field Definition Control the CAC feature for the zone • Enable (check box selected) •...
  • Page 80 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. (Part 1 of 6) Command Description CHG CACVT <Zone> <Interval> Configure the zone-to-zone record validity time interval, where: •...
  • Page 81 Change the Cr coefficient in the formula that determines how quickly an alarm reduces the Sliding Maximum bandwidth for the identified zone, where: • Zone = 1-255 • Cr = Cr coefficient = 1-(50)-100 Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 82 LD 117 — Configure Adaptive Network Bandwidth Management. (Part 3 of 6) Command Description CHG ZONE <zoneNumber> <intraZoneBandwidth> <intraZoneStrategy> <interZoneBandwidth> <interZoneStrategy> [<zoneIntent> <zoneResourceType>] Change the parameters of an existing zone, where: • zoneNumber = 1-255 • intraZoneBandwidth = 1000000 (Mbit/s) •...
  • Page 83 When the zone-to-zone QoS value is greater than this threshold value, this alarm is presented as being deactivated. The value for ZQWAT must be higher than the value of ZQUAT. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 84 LD 117 — Configure Adaptive Network Bandwidth Management. (Part 5 of 6) Command Description CHG ZQNL <ZoneNumber> <level> 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. —...

  • Page 85: Zones

    Displaying CAC parameters for one or more zones Select IP Telephony > Zones from the navigator. The Zones web page opens (see Figure 6 on Main Office Configuration for Survivable Remote Gateway 50 page 61. To view the intrazone or interzone statistics, page 63.
  • Page 86 Click Maintenance Commands for Zones (LD 117). The Maintenance Commands for Zones web page opens, as shown in Figure 7 on intrazone statistics by default. Select Print Adaptive Network Bandwidth Management and CAC Parameters (PRT ZCAC) from the Action drop-down list. Select a zone from the Zone Number drop-down list, by doing one of the following: •...
  • 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 Maintenance using LD 117 The same information can be displayed using commands in LD 117. LD 117 — Display Adaptive Network Bandwidth Management information (Part 1 of 3) Command Description CLR CACR <nearZone> [<nearVPNI>] [<farZone>] [<farVPNI>] Clear zone-to-zone record for near (VPNI-Zone) for far (VPNI-Zone), where: •...
  • Page 89 • First row = summary bandwidth usage per near zone • Next rows = bandwidth usage per near (VPNI- Zone) and far (VPNI - Zone) Figure 17 on Main Office Configuration for Survivable Remote Gateway 50 page 92 shows an example of the output for this command. Configuration Guide...
  • Page 90 LD 117 — Display Adaptive Network Bandwidth Management information (Part 3 of 3) Command Description PRT ZCAC [<zone>] 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: •...
  • Page 91 |Strategy|MO/ | Bandwidth | |----|-----|-------|--------|----|-----------|---------|------| 2| ENL |SHARED | |-------------------------------------------------------------| 44| ENL |SHARED | |-------------------------------------------------------------| Number of Zones configured = 2 Main Office Configuration for Survivable Remote Gateway 50 |VTRK/| kbps |BMG | 10000| | BMG| 10000| Usage | Peak |...
  • Page 92 Page 92 of 258 Bandwidth Management Figure 17 Sample output for PRT INTERZONE command 553-3001-207 Standard 2.00 January 2006...

  • Page 93: Tandem Bandwidth Management Overview

    (digital, analog [500/2500-type], and IP Phones) or trunks at the branch office to another node in the network. It does not apply when using branch office IP Phones that are registered with the main office (for example, Normal Mode). Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...

  • Page 94: Dialing Plan Overview

    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: Network Using Uniform Dialing Plan

    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.
  • Page 97 1, 2, 3 1, 2, 3 1, 2, 3 Main Office Configuration for Survivable Remote Gateway 50 Configuration detail and call progress during call setup UDP used for all calls within the region. UDP used for region to region calls.
  • Page 98 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 Call between two branch offices associated with the same main office The following scenarios describe calls between two branch offices that belong to the same main office.
  • Page 99 A2; it directs the call to the branch office. The main office sends the call to 552-395-3456 to the branch office. The branch office deletes the prefix and the HLOC, and rings set 3456. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 100 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 The branch office user dials 6-395-3456.
  • Page 101 In this example, the HLOC is unique between all the branch offices and the main office. See Figure 23. Figure 23 Call flow for Scenario 1- local call Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 102 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. The branch office sends the call to 399-3456 to the main office.
  • Page 103 The main office determines that this is to another main office. The system transmits 444-3456 to the NRS. The NRS checks its provisioning, and determines that this call goes to main office B. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 104 Figure 25 Call flow for Scenario 1 - call to remote branch office (destination side) 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.
  • Page 105 The main office determines that this is to another main office. The system transmits 444-3456 to the NRS. The NRS checks its provisioning, and determines that this call goes to main office B. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 106 Figure 27 Call flow for Scenario 1 - call to remote branch office (destination side) 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.
  • Page 107 The main office determines that this is to another main office. The system transmits 444-3456 to the NRS. NRS checks its provisioning, and determines that this call goes to main office B. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 108 Figure 29 Call flow for Scenario 1 - call to remote branch office (destination side) 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.
  • Page 109 Provision the branch office with a terminating RLI with a DMI to delete the LOC prefixes. See step 9 on Provisioning Example of Tandem Bandwidth Management Figure 30 shows an example of the network configuration. Main Office Configuration for Survivable Remote Gateway 50 page 111. page 112.

  • Page 110: Provisioning Tandem Bandwidth Management

    Figure 30 Provisioning example Procedure 5 Provisioning Tandem Bandwidth Management 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.
  • Page 111 Type of Number as used (LOC or SPN), the entries can be differentiated from the normal LOCs easily. In our example the NRS is provisioned with 741-841 at branch office B and 742-842 for branch office A. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 112 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.
  • Page 113 Main office B and branch office B (Part 1 of 2) Create a DMI LD 86 REQ new CUST 0 FEAT dgt Main Office Configuration for Survivable Remote Gateway 50 Create an HLOC LD 90 REQ new CUST 0 FEAT net...
  • Page 114 Table 10 Main office and branch office HLOC provisioning – Main office B and branch office B (Part 2 of 2) Create a DMI DMI 61 DEL 3 ISPN no Repeat the above for all the main offices and branch offices. Provision the main office to send all other LOCs to the IP network without prefixes.
  • Page 115 Branch office terminating RLI provisioning (Part 1 of 2) Create a DMI LD 86 REQ new CUST 0 FEAT dgt DMI 61 DEL 6 Main Office Configuration for Survivable Remote Gateway 50 Create a LOC LD 90 REQ NEW CUST 0 FEAT NET TRAN AC1 TYPE LOC...
  • Page 116 Table 13 Branch office terminating RLI provisioning (Part 2 of 2) Create a DMI ISPN no 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...
  • Page 117 Call between two local branch offices Figure 33 on page 118 Manager. Main Office Configuration for Survivable Remote Gateway 50 Provisioning detail CDP used for all calls within the region. UDP used for region to region calls. Prefixes for branch offices for regular calls not required.
  • Page 118 Figure 33 Call flow for Scenario 2 – local call dials CDP 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. The branch office sends the call to 3456 to the main office.
  • Page 119 CDP region are to be sent to branch office A2; it directs the call to the branch office. The main office sends the call to 3456 to the branch office. The branch office rings set 3456. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 120 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) The branch office user dials 6-444-3456.
  • Page 121 CDP region this call goes to branch office B1. The main office sends the call to 3456 to the branch office. The branch office rings set 3456. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...

  • Page 122: Network Using Coordinated Dialing Plan

    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...
  • Page 123 Similar configuration, as above, applies to regions 2 and 3. Call between two local branch offices Figure 38 on page 124 offices. Main Office Configuration for Survivable Remote Gateway 50 Bandwidth Management Provisioning detail shows the call flow of a call between two local branch Page 123 of 258...
  • Page 124 Figure 38 Call flow for Scenario 3 - local call 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. The branch office sends the call to 43456 to the main office.
  • Page 125 53456 to the NRS. The NRS checks its provisioning, and determines that this call goes to main office B. In Figure 40 on page side of the call). Main Office Configuration for Survivable Remote Gateway 50 126, the second half of the call is shown (destination Configuration Guide...
  • Page 126 Figure 40 Call flow for Scenario 3- calls to remote branch office (destination side) 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.

  • Page 127: Alternative Call Routing For Network Bandwidth

    The feature also applies to station-to-station calls from one branch office to another branch office, provided both stations are registered to the same main office. Main Office Configuration for Survivable Remote Gateway 50 Page 127 of 258 Configuration Guide...
  • Page 128 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.
  • Page 129 QoS in the originating or terminating zone as the calls are being established • All Calls: Alternately routes station-to-station IP network calls, regardless of available bandwidth Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • 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.
  • Page 131 The main office inserts the ALTPrefix associated with the originator’s zone (the main office in this case) before the dialed digits. The main office uses CDP and recognizes the ALTPrefix as a steering code. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...

  • Page 132: Dialing Plans

    The main office determines the RLI and uses a DMI to change the dialed number into a PSTN/MCDN format number. 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 (main office zone - MO zone and branch office zone - BO2 zone). Telephone A and the Media Gateway belong to the MO zone. The branch office and Telephone B belong to the BO2 zone. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 134 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.) Configuration required Configure the following:...
  • Page 135 136 station-to-station call. The diagram assumes that alternately routed calls originate on Voice Gateway Media Cards at the branch office. Main Office Configuration for Survivable Remote Gateway 50 illustrates the steps that occur in an alternately routed page 134...
  • Page 136 Figure 43 Illustration showing digits dialed and outpulsed with Alternative Call Routing for NBWM 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 The main office Call Server determines there is insufficient bandwidth between the two zones.
  • Page 137 Call comes into IP Phone A from the PSTN or MCDN trunks in the main office zone (action labeled 3 in Figure 42 on Main Office Configuration for Survivable Remote Gateway 50 page 134).
  • Page 138 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.
  • Page 139 No provisioning required. At the NRS: • No provisioning required. Sequence of events in the call The information that follows refers to Figure 44 on page 140. Main Office Configuration for Survivable Remote Gateway 50 page 138 and Figure 45 Configuration Guide...
  • Page 140 Figure 45 Illustration showing digits dialed and outpulsed with Alternative Call Routing for NBWM 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 The main office Call Server determines there is insufficient bandwidth between the two zones.
  • Page 141 [MO zone], branch office zone [BO2 zone], and branch office 1 zone [BO1 zone]). Telephone F and branch office 1 belong to the BO1 zone. Telephone B and the other branch office belong to the BO2 zone. Main Office Configuration for Survivable Remote Gateway 50 page 138).
  • Page 142 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.) Configuration required Configure the following:...
  • Page 143 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 46 on page 144. Main Office Configuration for Survivable Remote Gateway 50 page 142 and Figure 47 Configuration Guide...
  • 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.00 January 2006...
  • Page 145 — insert 1506348 (in order to compose the DID number of the destination telephone, which is 15063486020) The call comes into IP Phone F from the PSTN in the BO1 zone (action labeled 3 in Figure 46 on Main Office Configuration for Survivable Remote Gateway 50 page 142). page 142).

  • Page 146: Operating Parameters

    Alternative Call Routing for NBWM feature used in All Calls mode The situations illustrated in Figure 42 on and Figure 46 on 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 The configuration and provisioning for the All Calls mode is exactly the same as the regular Alternative Call Routing for NBWM feature except that the...
  • Page 147 A QoS0039 message prints out when the Alternative Call Routing for NBWM feature is invoked. If a user at a branch office attempts to make a conference call, Alternative Call Routing for NBWM is not invoked. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...

  • Page 148: Feature Interactions

    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. Multiple Appearance Directory Number If telephone endpoints sharing Multiple Appearance DNs (MADNs) are configured in different zones, then this feature handles the call in the same way that Network Bandwidth Management does.

  • Page 149: Feature Packaging

    LD 117 - Enable Alternative Call Routing for NBWM for a particular zone. Command ENL ZALT <zone> Enable Alternative Call Routing for NBWM, where: <zone> Main Office Configuration for Survivable Remote Gateway 50 Description Input zone number (0-255). Note: Configure the branch office zone using LD 117 at the main office.
  • Page 150 LD 117 - Configure Alternate Prefix number for a particular zone and the All Calls option, if desired. Command CHG ZALT <zone> <ALTPrefix> [<re-route all calls>] Change ALTPrefix number for zone, where: <zone> <ALTPrefix> [<re-route all calls>] LD 117 - Print Alternate Prefix number for a particular zone. Command PRT ZALT <zone>...

  • Page 151: Feature Implementation Using Element Manager

    Access the Zones web page to select Alternate Routing for Calls between IP Stations. Access the Alternate Routing for Calls between IP Stations web page to configure the feature. Main Office Configuration for Survivable Remote Gateway 50 Alternate Prefix All Calls Alarms...

  • Page 152: Accessing The Zones Web Page

    Accessing the Zones web page Procedure 6 Accessing the Zones web page 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 553-3001-207 Standard 2.00 January 2006 page...
  • Page 153 A web page appears that displays the configuration parameters related to the Alternative Call Routing for NBWM feature. (See Figure 50 on page Main Office Configuration for Survivable Remote Gateway 50 beside the Zone, or click the Zone you 154.)
  • Page 154 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. Select the Enable Alternate Routing feature (ENL_ZALT) check box to enable the Alternative Call Routing for NBWM feature.

  • Page 155: Diagnostics

    Note: If you do not enter a value in the zone field, you obtain a printout of the status of all configured branch office zones. Main Office Configuration for Survivable Remote Gateway 50 Description Display Alternative Call Routing Status, where:...
  • Page 156 The printout for all configured branch office zones appears as follows: Note: Des entries are codes you assign to each branch office for your own records. Element Manager diagnostics Print zone Alternative Call Routing information The print capability allows the following parameters to be viewed for each zone: •...

  • Page 157: Printing Zone Altprefix

    From the navigator, click System > Maintenance. The Maintenance web page appears. (See Figure 51.) Figure 51 System > Maintenance web page Click Select by Functionality. The Select by Functionality web page appears. (See Figure 52 on Main Office Configuration for Survivable Remote Gateway 50 page 158.) Configuration Guide...
  • Page 158 Figure 52 Maintenance web page showing Select by Functionality Click Zone diagnostics. The Maintenance Commands for Zones web page appears. (See Figure 53 on page if you click on Zones, as you see in Figure 49 on 553-3001-207 Standard 2.00 page January 2006 159.) You can also access this...
  • Page 159 Action. Select ALL or a zone number from the Zone Number drop-down list. Click Submit. Figure 53 shows a typical example of the results. Main Office Configuration for Survivable Remote Gateway 50 End of Procedure Configuration Guide...

  • Page 160: Show Status

    Show the status 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. From the navigator, click System > Maintenance. The Maintenance web page appears.
  • Page 161 Select ALL or a zone number from the Zone Number drop-down list. 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. Main Office Configuration for Survivable Remote Gateway 50 End of Procedure Configuration Guide...

  • Page 162: Maintenance

    Maintenance Command Line Interface maintenance LD 117 - Enable and disable Alternative Call Routing for NBWM for a zone. Command ENL ZALT <zone> DIS ZALT <zone> ENL ZBR <zone> [ALL] [LOC][ESA][TIM][ALT] Enable features for the branch office zone. If you do not input features, then all are enabled.

  • Page 163: Enabling A Zone's Branch Office Behavior

    Click Zone diagnostics. The Maintenance Commands for Zones web page appears. (See Figure 53 on Select Enable a Zone’s Branch Office Behavior from the drop-down list beside Action. (See Figure 55 on Main Office Configuration for Survivable Remote Gateway 50 Alarms Suppression Time 1000 page 157.)
  • Page 164 Figure 55 Enable a zone’s branch office behavior Select the zone number you want to configure from the Zone Number drop-down list. Select the check box beside the Alternate Routing for Branch option to enable the feature. Click Submit. The display updates with new configuration data for the zone you specified.

  • Page 165: Nbwm Alarms

    Enter digits in Alarm Suppression Time Period (ZAST). See Figure 56 Click Submit to enter the data. Figure 56 Alarm Suppression Time Period (ZAST) Main Office Configuration for Survivable Remote Gateway 50 beside the Zone, or click the Zone you are programming, to page 165.

  • Page 166: Feature Operation

    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.00 January 2006...

  • Page 167: Dialing Plan Configuration

    If internal or off-net, the system terminates the call on the appropriate terminal. If external or on-net, the system routes the call using one of the supported dialing plans. Main Office Configuration for Survivable Remote Gateway 50 Page 167 of 258 Configuration Guide...

  • Page 168: On-Net Dialing Plan

    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: •...

  • Page 169: Off-Net Dialing Plan

    If no alternative is available over the IP network, the originating endpoint steps to the next entry on its route list, which could be a TIE or PSTN alternate route. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...

  • Page 170: Routing Calls

    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.

  • Page 171: Zone-Based Digit Manipulation

    In the case where a single Access Code is not shared, that is, where one Access Code is exclusively used for UDP on-net dialing, standard procedures should be used. Refer to Dialing Plans: Description (553-3001-183). Main Office Configuration for Survivable Remote Gateway 50 page 182 and Note 2 on...

  • Page 172: Standard 2.00 January

    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.

  • Page 173: Configuring Pstn Access For Srg Users In Normal Mode

    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 main office, configure trunks for access to the PSTN. Main Office Configuration for Survivable Remote Gateway 50 Call-type before digit manipulation Local PSTN National PSTN International PSTN...

  • Page 174: Configuring The Dialing Plan

    • 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. •...

  • Page 175: Configuring The Main Office

    Configure the ZACB property for the branch office zone. LD 117 – Define the zone Access Code handling for the branch office zone. Command CHG ZACB <zone> [ALL]|[<AC1|AC2> <AC1|AC2>] Main Office Configuration for Survivable Remote Gateway 50 Configure the Route List Index. Configure ESN. Description...
  • Page 176 Note 1: As part of the ZACB configuration, you can also change the dialed Access Code, so if you dial AC2 it can be changed to AC1, or vice versa. This provides more flexibility in the main office NARS configurations. Normally, you do not need to change the Access Code. Note 2: The Access Code dialed by the user is used internally by the Call Server.
  • Page 177 CHG ZDP <zone> <DialingCode1> <DialingCode2> <DialingCode3> Note: If DialingCode1, DialingCode2, or DialingCode3 are already present in the dialed digits, then they will not be re-inserted. Main Office Configuration for Survivable Remote Gateway 50 Description Define the dialing plan for the branch office zone, where...
  • Page 178 Configure the Route List Index at the main office. After configuring zone-based digit manipulation, a specialized route for the call must be configured. To select a trunk to route calls, a Route List Index (RLI) must be configured in the Route List Block (RLB). The RLI uses the route number for the Virtual Trunk to route calls to the NRS.
  • Page 179 0-127 0-255 0-999 ENTR 0-63 LTER Main Office Configuration for Survivable Remote Gateway 50 Description Insert. Up to 31 leading digits can be inserted, usually none at the main office. Default is none. IP Special Number For off-net calls For on-net calls Call type to be used by the call.
  • Page 180 LD 86 – Configure Route List Index. (Part 2 of 2) Prompt Response ROUT 0-511 0-127 1-999 553-3001-207 Standard 2.00 Description Route number of the Virtual Trunk as provisioned in LD 16. Range for Large System and CS 1000E system Range for Small System, CS 1000S system, Media Gateway 1000B, and Media Gateway 1000T Digit Manipulation Index number as defined in LD 86,...
  • Page 181 (0)-24 - RLI 0-999 - CLTP LOCL NATL INTL Main Office Configuration for Survivable Remote Gateway 50 Description Add new data. Customer number as defined in LD 15 Network translation tables Translator Access Code 1 (NARS/BARS) Access Code 2 (NARS)
  • Page 182 After configuring the zone-based digit manipulation (step 1 on step 2 on 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 >LD CUST 0 FEAT NET TRAN AC1 TYPE SPN 1011 FLEN 14 Main Office Configuration for Survivable Remote Gateway 50 page 178 is usually a unique non-dialable 11 digits for long-distance + 3 digits for ZDP page 189. Configuration Guide...

  • Page 184: Configuring The Nrs Database

    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. This procedure configures the NRS database with the inserted digits specified by the zone- based digit manipulation configuration.
  • Page 185 The Routing Entries window then displays a list of routing entries corresponding to that endpoint, if any. See Figure 59 on Figure 58 NRS — Lookup path for gateway endpoints Main Office Configuration for Survivable Remote Gateway 50 page 186. Configuration Guide...
  • Page 186 Figure 59 NRS — Routing Entries window for selected endpoint 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 Figure 60 NRS — Add Routing Entry Configure the numbering plan entries for the branch office.

  • Page 187: Configuring The Branch Office

    ZDP digits that were inserted in the dialed digits at the main office. The DMI is also used to convert the call type back correctly according to the incoming SPN pattern. Main Office Configuration for Survivable Remote Gateway 50 End of Procedure Configuration Guide...
  • Page 188 LD 86 – Configure Digit Manipulation Index at the branch office. Prompt Response CUST FEAT 1-999 (0)-19 ISPN INST x...x CTYP INTL 553-3001-207 Standard 2.00 Configure the DMI in LD 86 with the DGT feature. Description Add new data. Customer number as defined in LD 15 Digit manipulation data block Digit Manipulation Index numbers The maximum number of Digit Manipulation tables is...
  • Page 189 0-63 LTER ROUT 0-511 0-127 1-999 Main Office Configuration for Survivable Remote Gateway 50 Configure the RLI in LD 86 with the RLB feature. Description Add new data. Customer number as defined in LD 15 Route List data block Route List Index to be accessed...
  • Page 190 Configure ESN Special Number and Digit Manipulation. LD 90 – Configure ESN Special Number and Digit Manipulation. (Part 1 of 2) Prompt Response CUST FEAT TRAN TYPE x...x 553-3001-207 Standard 2.00 INST Set according to associated SPN pattern CTYP LOC CUST 0 FEAT RLB ENTR 0...
  • Page 191 For example, assume ZDP at the main office = 101, Customer number = 0, and the RLI for the PSTN trunk = 18. c. >LD Main Office Configuration for Survivable Remote Gateway 50 Description Flexible Length The number of digits the system expects to receive before accessing a trunk and outpulsing these digits.

  • Page 192: Testing Pstn Access Using An Srg Ip Phone

    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.

  • Page 193: Dialing Plan Examples

    CDP dialing configuration. The option you choose will determine how the user dials the other system or the SRG IP telephones. Main Office Configuration for Survivable Remote Gateway 50 Make a call to the local PSTN.
  • Page 194 For specific examples on the dialing plans, refer to “Dialing plan examples” page • 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.
  • Page 195 SRG Routing is configured so the destination code of the PSTN through the SRG is at the start of the dialing string. Figure 63 shows how the call proceeds. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • 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.00 January 2006...
  • Page 197 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. Figure 64 Normal Mode: SRG IP Phone makes a call over the PSTN Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 198 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.
  • Page 199 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. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • 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.
  • Page 201 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. Figure 67 on Main Office Configuration for Survivable Remote Gateway 50 page 202 shows this scenario. Configuration Guide...
  • 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.00 January 2006...
  • Page 203 Dialing Plan configuration Page 203 of 258 Figure 68 WAN is down. SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the SRG (Local Mode) Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 204 Configuration To configure the main office: • Configure the ESN Control Block for CDP in LD 86. • Configure the CDP Distant Steering Code (DSC) in LD 87. To configure the NRS (H.323 Gatekeeper): • Create CDP Domain: “MO_BO_CDP”. • Create H.323 endpoints: “MO”, “BO”.
  • Page 205 DN. This plan allows all systems on the network to appear to be available within a range of numbers. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 206 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.
  • Page 207 Page 207 of 258 Figure 70 WAN is up. SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the main Office (Normal Mode) Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 208 • 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: —...
  • Page 209 Dialing Plan configuration Page 209 of 258 Figure 71 WAN is down. SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the SRG (Local Mode) Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 210 Configuration To configure the main office: • Configure the ESN Control Block for CDP in LD 86. • Configure the CDP Distant Steering Code (DSC) in LD 87. To configure the NRS (H.323 Gatekeeper): • Create CDP Domain: “MO_BO_CDP”. • Create H.323 endpoints: “MO”, “BO”.
  • Page 211 SRG, to the SRG IP Phone in Normal mode, the SRG system translates the SRG IP telephone DN (4XXX) to the main office BUID Main Office Configuration for Survivable Remote Gateway 50 212, the SRG IP Phones have a DN starting with 4 on...
  • Page 212 (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).
  • Page 213 In Normal Mode, the display on the IP Phone displays the main office DN (3xxx) for the IP Phone. In Local Mode, the SRG DN (4xxx) is displayed. Figure 73 on page 214 Main Office Configuration for Survivable Remote Gateway 50 shows this scenario. Configuration Guide...
  • 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.
  • Page 215 Set the BUID to the same number that was assigned for the TN by the main office. • Set the main office VoIP Trunk Access code to 0. • Do not assign a value to the main office trunk access code field. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...

  • Page 216: Universal Dialing Plan

    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 using location codes (Access Code + LOC + DN) configuration.
  • Page 217 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 Main Office Configuration for Survivable Remote Gateway 50 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.00 January 2006...
  • Page 219 IP Phone registered to the main office. Figure 76 shows this scenario. Figure 76 WAN is up. SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the main office (Normal Mode) Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 220 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.
  • Page 221 Dialing Plan configuration Page 221 of 258 Figure 77 WAN is down. SRG analog phone calls an IP Phone and a main office IP Phone registered to the SRG (Local Mode) Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 222 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. •...
  • Page 223 REQ NEW TYPE RDB CUST 00 ROUT 120 DES VTRKNODE51 TKTP TIE VTRK YES ZONE 101 NODE 51 PCID H323 ISDN YES MODE ISLD DCH 12 IFC SL1 INAC YES Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 224 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. •...

  • Page 225: Emergency Services Configuration

    SRG IP Phone must route from the main office Call Server to the SRG so that the call can be sent on the SRG PSTN Trunks. Main Office Configuration for Survivable Remote Gateway 50 Page 225 of 258...

  • Page 226: Emergency Services Access (Esa)

    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. 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: •...
  • Page 227 Ideally, route ESA calls directly over Central Office (CO) trunks to the Public Safety Answering Point (PSAP). In those cases where this routing is not possible, do not route ESA calls to nodes that have no direct ESA trunks. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 228 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.
  • Page 229 13 Configure the branch office zone on the branch office. Note: The branch office zone is required for bandwidth management but does not require ESA parameters. 14 Configure the ESN SPN on the branch office. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 230 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: Configuring The Main Office

    NEW CHG TYPE CUST ESDN xxxx ESRT 0-511 0-127 Main Office Configuration for Survivable Remote Gateway 50 office. branch office. Description Add new data, or change existing data. Emergency Services Access data block Customer number as defined in LD 15 Emergency Services DN (for example, 911).
  • Page 232 LD 24 – Configure Emergency Services Access. (Part 2 of 2) Prompt Response DDGT x...x DFCL x...x OSDN x...x Test ESDN using a main office telephone to confirm that main office calls exit the main office trunks. If OSDN is used, the ESA route number must be blank to make test calls without using any trunk resources.
  • Page 233 PSAP to locate the source of the call. Configure the ESA Special Number at the main office. Main Office Configuration for Survivable Remote Gateway 50 Configure the branch office zone’s ESA dialing information in LD 117.
  • Page 234 LD 86 – Configure Digit Manipulation Index. Prompt Response CUST FEAT (0)-31 (0)-255 (0)-999 (0)-19 INST x...x CTYP <cr> 553-3001-207 Standard 2.00 Configure the ESN Special Number at the main office. For information on configuring ESN, refer to Basic Network Features (553-3001-379).
  • Page 235 LTER ROUT 0-511 0-127 (0)-999 Main Office Configuration for Survivable Remote Gateway 50 Configure the Route List Index in LD 86 with the RLB feature. Description Add new data. Customer number as defined in LD 15 Route List data block...
  • Page 236 LD 90 – Configure ESN Special Number and Digit Manipulation. (Part 1 of 2) Prompt Response CUST FEAT TRAN TYPE x...x - FLEN (0)-24 - RLI 0-127 0-255 0-999 553-3001-207 Standard 2.00 iii. Configure the ESN Special Number and Digit Manipulation in LD 90.

  • Page 237: Configuring The Branch Office Zone

    Configure the routing tables on the SRG. The SRG must recognize the incoming digits on the Virtual Trunk and remove all but the ESDN. The call is routed to a local termination. Main Office Configuration for Survivable Remote Gateway 50 Description Supplemental Digit Restriction or Recognition...

  • Page 238: Configuring The Nrs For Esa Spn

    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”...

  • Page 239: Configuring Esa Using Element Manager

    In many jurisdictions, the emergency number is a fixed number (for example, “112” or “999”). The main office Call Server or SRG cannot have a DN that conflicts with these digits. Main Office Configuration for Survivable Remote Gateway 50 End of Procedure page...
  • Page 240 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).

  • Page 241: Enhanced Unistim Firmware Download

    CS 1000. When an IP Phone requires firmware upgrade, the CS 1000 uses the umsUpgradeAll command, or variant, to redirect the IP Phone back to the SRG50 for upgrading. Main Office Configuration for Survivable Remote Gateway 50 Page 241 of 258 Configuration Guide...

  • Page 242: Firmware Upgrade

    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.

  • Page 243: Upgrading Firmware

    Communication Server 1000S: Upgrade Procedures (553-3031-258). Issue the CLI command IP Phones at the Main office and branch office are upgraded as necessary. Main Office Configuration for Survivable Remote Gateway 50 umsUpgradeAll at the main office. End of Procedure Configuration Guide...

  • Page 244: Standard 2.00 January

    Page 244 of 258 Enhanced UNIStim Firmware Download 553-3001-207 Standard 2.00 January 2006...

  • Page 245: Appendix A: Media Redirection Scenarios

    Scenario 3: Conference Call works correctly with a branch office: — Scenario 3.1: Conference call between branch office and main — Scenario 3.2: Conference call between main office and branch Main Office Configuration for Survivable Remote Gateway 50 page 246.
  • Page 246 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. Table 17 Scenario 1: Codec switches correctly during media redirection Event...
  • Page 247 3 The Call Transfer key on the main office IP Phone is pressed to complete the call transfer. Main Office Configuration for Survivable Remote Gateway 50 Result 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.
  • Page 248 Table 19 Scenario 2.2: Call transfer from main office IP Phone to SRG IP Phone in Normal Mode (Part 2 of 2) Event 4 The call is released. Table 20 Scenario 3.1: Conference call between branch office and main office, initiated by SRG IP Phone in Normal Mode Event 1 An SRG TDM telephone calls an SRG...
  • Page 249 IP Phone is pressed to complete the conference call. 4 The SRG TDM telephone releases the call. 5 The call is released. Main Office Configuration for Survivable Remote Gateway 50 Result A speech path is established between the SRG TDM telephone and the main office IP Phone.
  • Page 250 Page 250 of 258 Appendix A: Media Redirection Scenarios 553-3001-207 Standard 2.00 January 2006...

  • Page 251: List Of Terms

    Emergency Services Access is a feature that places a customer in compliance with federal legislation that requires the Private 911 type of functionality Main Office Configuration for Survivable Remote Gateway 50 Page 251 of 258 Configuration Guide...
  • Page 252 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 Call Server. Network Routing Service. The software application where all systems in the network are registered. The NRS consists of the H.323 Gatekeeper and the Network Connection Service (NCS). Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 254 SRG50 Survivable Remote Gateway 50. This describes the equipment used to create an IP branch office with a CS 1000 system acting as the main office. The base system for SRG is a Business Communication Manager running BCM 3.6 software.
  • Page 255 SRG PSTN call dialed from an SRG IP Phone in Normal Mode. This number differentiates the call from a main office PSTN call dialed by the main office telephones. The ZDP routes the call through VoIP trunk to the SRG. Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide...
  • Page 256 Page 256 of 258 List of terms 553-3001-207 Standard 2.00 January 2006...
  • Page 257 Dialing plan configuration, 167 Dialing plan configuration for SRG PSTN access, Dialing plan configuration in Normal Mode, 173 DSP, 251 Main Office Configuration for Survivable Remote Gateway 50 Emergency Services Access (ESA), 226 Emergency Services configuration, 225 Emergency Service using Special Numbers, 239...
  • Page 258 Main office hardware description, 17 Main office information required by the SRG, 37 Main office requirements, 20 Media Redirection Scenarios, 245 Music on hold, 31 NCS, 253 Normal Mode, 253 Normal Mode operation, 22 NRS, 253 Off-net dialing plan, 169 On-net dialing plans, 168 Overview, 15 PSTN, 254...
  • Page 260 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. 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.

Table of Contents