1. Manuals
  2. Brands
  3. Nortel Manuals
  4. Gateway
  5. SRG200
  6. Configuration manual

Nortel SRG200 Configuration Manual

Communication server, main office configuration for survivable remote gateway release 1.5
Hide thumbs Also See for SRG200:
Table of Contents

Advertisement

Quick Links

Download this manual
Title page
Nortel Communication Server 1000
Nortel Communication Server 1000 Release 5.0
Main Office Configuration for SRG200/
400 Release 1.5

Configuration Guide

Document Number: NN43001-308
Document Release: Standard 01.02
Date: May 2007
Copyright © 2005–2007 Nortel Networks
All Rights Reserved.
Produced in Canada.
The information in this document is subject to change without notice. The statements, configurations, technical
data, and recommendations in this document are believed to be accurate and reliable, but are presented
without express or implied warranty. Users must take full responsibility for their applications of any products
specified in this document. The information in this document is proprietary to Nortel Networks.
Nortel, Nortel (Logo), the Globemark, SL-1, Meridian 1, and Succession are trademarks of Nortel Networks.

Advertisement

Table of Contents
loading

Related Manuals for Nortel SRG200

Summary of Contents for Nortel SRG200

  • Page 1: Configuration Guide

    Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks. Nortel, Nortel (Logo), the Globemark, SL-1, Meridian 1, and Succession are trademarks of Nortel Networks.

  • Page 3: Revision History

    Communication Server 1000 Release 5.0. This document is also up-issued to include updated information due to CR Q01587820. See “Codec negotiation” page June 2006 Standard 01.01. This document is issued to support SRG200/400 Release 1.5 with Communication Server 1000 Release 4.5. This document reflects the new document number. June 2006 Standard 2.00.
  • Page 4 Page 4 of 254 Revision history NN43001-308 Standard 01.02 May 2007...

  • Page 5: Table Of Contents

    Contents ..........Survivable Remote Gateway ....... . .
  • Page 6 Page 6 of 254 Contents Main office information required by the SRG ....Zone parameters ......... . Branch office IP Phone configuration at the main office .
  • Page 7 Index ........253 Main Office Configuration for SRG200/400 Release 1.5...
  • Page 8 Page 8 of 254 Contents NN43001-308 Standard 01.02 May 2007...

  • Page 9: List Of Procedures

    ........120 Procedure 8 Displaying CAC parameters for one or more zones . . 142 Procedure 9 Provisioning Tandem Bandwidth Management ..166 Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide...
  • Page 10 Page 10 of 254 List of procedures Procedure 10 Accessing the Zones web page ....207 Procedure 11 Printing zone ALTPrefix ......212 Procedure 12 Show Status .

  • Page 11: New In This Release

    Communication Server 1000 documentation suite, as listed in “Related information” on For information about how to configure the SRG200/400 Release 1.5, see the SRG200/400 Release 1.5 Configuration Guide at www.nortel.com. Select Support and Training > Technical Documentation > Communication Servers >...

  • Page 12: Intended Audience

    This NTP contains information about systems, components, and features that are compatible with Nortel Communication Server 1000 Release 5.0 software. For more information about legacy products and releases, click the Technical Documentation link under Support & Training on the Nortel home page: www.nortel.com...
  • Page 13 (NN43041-220) • Software InputOutput Reference—Maintenance (NN43001-711) Online To access Nortel documentation online, click the Technical Documentation link under Support & Training on the Nortel home page: www.nortel.com CD-ROM To obtain Nortel documentation on CD-ROM, contact your Nortel customer representative. Main Office Configuration for SRG200/400 Release 1.5...
  • Page 14 Page 14 of 254 New in this release NN43001-308 Standard 01.02 May 2007...

  • Page 15: Overview

    This section contains information about the following topics: Survivable Remote Gateway....... . .
  • Page 16 90 survivable IP users and the MG 1000B solution is positioned for larger branch offices for up to 400 users. The SRG200/400 solution is supported on CS 1000 Release 4.0, CS 1000 Release 4.5, and CS 1000 Release 5.0 systems.
  • Page 17 SRG, can be accommodated by the SRG call processing. Figure 1 on page 18 shows the networking among the main office, SRG, and IP Phones. Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide...

  • Page 18: Main Office Hardware Description

    Page 18 of 254 Overview Figure 1: SRG network Main office hardware description The main office must be one of the following systems: • CS 1000E • CS 1000M Cabinet • CS 1000M Chassis • CS 1000M HG • CS 1000M SG •...

  • Page 19: Signaling Server

    H.323 Gatekeeper — provides central dialing plan management and routing for H.323-based endpoints and gateways. NRS also contains SIP Redirect Server but SIP Trunks are not supported on an SRG. Main Office Configuration for SRG200/400 Release 1.5 Overview Page 19 of 254 Configuration Guide...
  • Page 20 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.

  • Page 21: Main Office Requirements

    MPLR21148 patch is required for CS 1000 Release 4.0 systems to support Enhanced UNIStim Firmware Download feature for branch user IP Phones. Main Office Configuration for SRG200/400 Release 1.5 2033, and IP Phone 1110 2007, IP Phone 1120E, IP Phone 1140E, IP Phone 1150E, IP...

  • Page 22: Optional Features To Enhance Srg Functionality

    Page 22 of 254 Overview The main office requires the following software packages to support the specified Basic Network features. For more information, see Basic Network Features Fundamentals (NN43001-579). • Network Call Back Queuing (MCBQ) package 38. This package is required for SRG IP Phones to invoke any queuing feature or ringback when free.

  • Page 23: Normal Mode And Local Mode Overview

    Adaptive Network Bandwidth Management package 407. • Alternative Call Routing for Network Bandwidth Management. For software and hardware requirements for SRG, see the SRG200/400 Release 1.5 Configuration Guide. Normal Mode and Local Mode overview Normal Mode and Local Mode overview provides a description of the following sections: •...

  • Page 24: Local Mode

    Page 24 of 254 Overview 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, applications, key layout, and tones of the main office Call Server. This provides feature and application transparency between the branch office and the main office.
  • Page 25 WAN or system failure. The SRG supports a main office heartbeat or reliable UDP signaling Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide...
  • Page 26 Overview which automatically reregisters users once WAN or system failure has recovered. For information about the features supported in Local Mode, see the SRG200/ 400 Release 1.5 Configuration Guide. Survivability SRG is specifically designed to provide automatic survivability against WAN failure, main office Call Server failure, main office Signaling Server failure, and Gatekeeper failure.

  • Page 27: Recovery To Normal Mode

    IP Phones and other analog (500/2500-type) telephones at the branch office. They can also be used to make outgoing PSTN calls and receive incoming calls as usual. SRG IP Phones can access Main Office Configuration for SRG200/400 Release 1.5 Overview Page 27 of 254...

  • Page 28: Virtual Trunks

    The test can be performed by the user at any time and does not require a password. This test is invoked from any IP Phone at the branch office. Nortel recommends testing Local Mode operation after changing the provisioning for a telephone on the SRG.

  • Page 29: Bandwidth Management Overview

    For more information about Virtual Trunks, see IP Peer Networking Installation and Commissioning (NN43001-313). Virtual Trunks are sometimes referred to as H.323 IP Peer Trunks. In the SRG200/400 Release 1.5 Configuration Guide, Virtual Trunks are referred to as IP Trunks. IP Phone calls When an IP Phone calls another IP Phone, each telephone receives the address of the other to exchange media directly between the telephones.

  • Page 30: Srg Ip Phone To Local Pstn Calls

    Page 30 of 254 Overview Network Bandwidth Management Zones A zone is a collection of IP Phones that: • share similar IP bandwidth restrictions • are geographically close to one another • are all in the same time zone • are all in the same PSTN dialing plan The Network Bandwidth Management Zone is made up of the VPNI and the zone.

  • Page 31: Conference Calls

    LAN/WAN bandwidth of three media paths is used. The calls are controlled by the main office, except in Local Mode. In Local Mode, SRG users do not have access to conferencing. Main Office Configuration for SRG200/400 Release 1.5 Overview IMPORTANT!

  • Page 32: Capacity

    Each CS 1000 main office can support up to 255 branch offices, which can be made up of any combination of SRGs and MG 1000Bs. SRG200/400 Release 1.5 supports up to 90 survivable IP Phone users. However, since all IP Phones register with the main office, the governing factor is the maximum number of IP Phones that can be supported at the main office.

  • Page 33: Branch Office Dialing Plan

    SRG user to be routed to the desired local PSTN facilities. Outgoing calls can include local and, optionally, long distance calls. Nortel recommends that the Branch User ID (BUID) be the same at the branch office as the DN at the main office. A BUID has a maximum of 15 digits.

  • Page 34: Branch Office And Srg200/400 Release 1.5 Terminology

    Branch office and SRG200/400 Release 1.5 terminology Table 2 lists configuration-related terms and contexts where branch office and SRG200/400 Release 1.5 terminology differ. Table 2: Branch office and SRG200/400 Release 1.5 terminology (Part 1 of 2) Term or context dialing plan routing...
  • Page 35 Table 2: Branch office and SRG200/400 Release 1.5 terminology (Part 2 of 2) Term or context Numbering Plan ID Trunks access codes (SRG200/ 400 Release 1.5: destination codes) telephone numbers (internal, not PSTN) Main Office Configuration for SRG200/400 Release 1.5...
  • Page 36 Page 36 of 254 Overview NN43001-308 Standard 01.02 May 2007...

  • Page 37: 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 SRG200/400 Release 1.5 Page 37 of 254 Configuration Guide...

  • Page 38: Srg Information Required By The Main Office

    Page 38 of 254 Setting up the main office For more information on main office configuration, see IP Peer Networking Installation and Commissioning (NN43001-313). SRG information required by the main office The main office administrator must gather information about the SRG system.

  • Page 39: 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 Main Office Configuration for SRG200/400 Release 1.5 Setting up the main office SRG200/400 Information about this system S1000 (default)
  • Page 40 Telephony programming: DN length, DN (TN) range Numbering plan ID Type of number SRG200/400 Release 1.5 only supports CDP and UDP dialing plans. Nortel recommends that the SRG use CDP. The SRG 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.

  • Page 41: Zone Parameters

    Zone parameters are defined at the main office in LD 117 (see Procedure 1 on page 42) and applied to IP Phones in LD 11. Use Procedure 1 on Main Office Configuration for SRG200/400 Release 1.5 Setting up the main office Information about this system page 42 to configure ESN and SRG zones.

  • Page 42: Configuring Esn And Srg Zones

    Page 42 of 254 Setting up the main office 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.
  • Page 43 CHG ZTDF <Zone> <TimeDifferencefromMainOffice> Specified in minutes, the time difference between main office and branch office when both are not in DST. Main Office Configuration for SRG200/400 Release 1.5 Setting up the main office IMPORTANT! Configuration Guide...
  • Page 44 Page 44 of 254 Setting up the main office LD 117 – Define zone parameters for the branch office. Command Description CHG ZDES <Zone> <ZoneDescription A name to render data display more meaningful. Enable the features for the branch office zone in LD 11. LD 117 –...
  • Page 45 Time Difference and Daylight Saving Time Property (see Figure 4 on page Figure 3 Zone Basic Property and Bandwidth Management web page Main Office Configuration for SRG200/400 Release 1.5 Setting up the main office Configuration Guide Page 45 of 254...

  • Page 46: Branch Office Ip Phone Configuration At The Main Office

    Page 46 of 254 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, see “Bandwidth Management” on page 107.

  • Page 47: 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 SRG200/400 Release 1.5 Setting up the main office Configuration Guide Page 47 of 254...
  • Page 48 Page 48 of 254 Setting up the main office • • 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 NN43001-308 Standard 01.02 Zone Prime DN to correspond to BUID Description Add new data, or change existing data.

  • Page 49: 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 SRG200/400 Release 1.5 Page 49 of 254 Configuration Guide...

  • Page 50: On-Net Dialing Plan

    Uniform Dialing Plan (UDP) – Location code is added to the DN for the BUID Nortel recommends that the SRG use CDP. CDP Terminal Numbers (TNs) can be activated on the other systems if the user moves and wants to retain their phone number. SRG does not support Transferable Directory Numbers (TNDN) due to differences in dialing plans and the small range of DNs available on the SRG.

  • Page 51: Off-Net Dialing Plan

    Therefore, the user can route calls to gateways that minimize long-distance costs, minimize bandwidth usage, or meet other criteria. Nortel recommends that customers use Coordinated Dialing Plan (CDP) between the main office and its branch offices since it enables all users, at the main office or the branch office, to call each other using just an extension number.

  • Page 52: Routing Calls

    Page 52 of 254 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.

  • Page 53: 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. See Dialing Plans Reference (NN43001-283). Main Office Configuration for SRG200/400 Release 1.5 Dialing Plan configuration page 64...
  • Page 54 Page 54 of 254 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 55: Access To Srg Users In Normal Mode

    SRG IP Phones in Normal Mode to reach the branch office. For more information, see IP Peer Networking Installation and Commissioning (NN43001-313). • At the main office, configure trunks for access to the PSTN. Main Office Configuration for SRG200/400 Release 1.5 Dialing Plan configuration Call-type before digit manipulation Local PSTN National PSTN...
  • Page 56 • Configure IP Phones with the same zone number at both the main office and the branch office. Nortel also recommends that the Prime DNs be the same at both the main and the branch offices. If different DNs are configured, the dial-in numbers change when the branch office is in Local Mode.

  • Page 57: 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 SRG200/400 Release 1.5 Dialing Plan configuration Configure the Route List Index. Configure ESN.
  • Page 58 Page 58 of 254 Dialing Plan configuration 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.
  • Page 59 The digit manipulation occurs before any digit processing in the main office Call Server or NRS. Nortel recommends that the ZDP attribute for each branch office zone be set to a unique non-dialable number within the dialing plan (for example 1019 or 999).
  • Page 60 Page 60 of 254 Dialing Plan configuration 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).
  • Page 61 0-127 0-255 0-999 ENTR 0-63 LTER Main Office Configuration for SRG200/400 Release 1.5 Dialing Plan configuration 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 62 Page 62 of 254 Dialing Plan configuration LD 86 – Configure Route List Index. (Part 2 of 2) Prompt Response ROUT 0-511 1-999 NN43001-308 Standard 01.02 Description Route number of the Virtual Trunk as provisioned in LD 16. Range for Large Systems Digit Manipulation Index number as defined in LD 86, FEAT = DGT (see step a on For example, assume that the Virtual Trunk is on route 10, and the...
  • Page 63 - FLEN (0)-24 - RLI 0-999 - CLTP LOCL NATL INTL Main Office Configuration for SRG200/400 Release 1.5 Dialing Plan configuration Description Add new data. Customer number as defined in LD 15 Network translation tables Translator Access Code 1 (NARS/BARS)
  • Page 64 Page 64 of 254 Dialing Plan configuration After configuring the zone-based digit manipulation (step 1 on step 2 on 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.
  • Page 65 FEAT NET TRAN AC1 TYPE SPN 1011 11 digits for long-distance + 3 digits for ZDP FLEN 14 Main Office Configuration for SRG200/400 Release 1.5 Dialing Plan configuration page 60 is usually a unique non-dialable Configuration Guide Page 65 of 254 page 71.

  • Page 66: Configuring The Nrs Database

    Page 66 of 254 Dialing Plan configuration Procedure 4 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 67 Choose the appropriate Service Domain, L1 Domain, and L0 Domain from the corresponding drop-down menus. Click on Look up to open a window with a lookup path for gateway endpoints. Click Search to display a list of gateway endpoints (see Figure 6), and click on the endpoint at the branch office.
  • Page 68 Page 68 of 254 Dialing Plan configuration Figure 7 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 8 on Figure 8 Add Routing Entry Configure the numbering plan entries for the branch office.

  • Page 69: 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 SRG200/400 Release 1.5 Dialing Plan configuration End of Procedure...
  • Page 70 Page 70 of 254 Dialing Plan configuration LD 86 – Configure Digit Manipulation Index at the branch office. Prompt Response CUST FEAT 1-999 (0)-19 ISPN INST x...x CTYP INTL NN43001-308 Standard 01.02 Configure the DMI in LD 86 with the DGT feature. Description Add new data.
  • Page 71 ENTR 0-63 LTER ROUT 0-511 1-999 Main Office Configuration for SRG200/400 Release 1.5 Dialing Plan configuration 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...
  • Page 72 Page 72 of 254 Dialing Plan configuration 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 - FLEN (0)-24 NN43001-308 Standard 01.02 CUST 0 FEAT RLB ENTR 0 LTER NO...
  • Page 73 From the Zones window in Element Manager, select the Branch Office Dialing Plan and Access Codes option, and enter the necessary information. See Figure 9. Main Office Configuration for SRG200/400 Release 1.5 Dialing Plan configuration Description Route List Index configured in LD 86 (see step 1 on...

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

    Page 74 of 254 Dialing Plan configuration Figure 9 Zone Dialing Plan and Access Codes Testing PSTN access using an SRG IP Phone Use Procedure 6 to test that PSTN access is working correctly. Procedure 6 Testing PSTN access using an SRG IP Phone From an SRG IP Phone in Local Mode: The calls must be routed according to the branch office ESN configuration.

  • Page 75: Dialing Plan Examples

    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” Main Office Configuration for SRG200/400 Release 1.5 Dialing Plan configuration page...
  • Page 76 Page 76 of 254 Dialing Plan configuration • Option 2: DN ranges in the main office and SRG overlap, and DNs for SRG IP Phones are the same in both Normal and Local mode. See “Option 2: DN ranges in the main office and SRG overlap; DNs for SRG IP Phones are the same in Normal and Local Mode”...
  • Page 77 SRG Routing is configured so the destination code of the PSTN through the SRG is at the start of the dialing string. Figure 11 shows how the call proceeds. Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide...
  • Page 78 Page 78 of 254 Dialing Plan configuration Figure 11 Normal Mode: Main office telephone makes a call over the PSTN through the SRG NN43001-308 Standard 01.02 May 2007...
  • Page 79 Zone management at the main office recognizes that an SRG IP Phone in Normal Mode is dialing the PSTN. Figure 12 shows how the call proceeds. Figure 12 Normal Mode: SRG IP Phone makes a call over the PSTN Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide...
  • Page 80 In this case, the WAN or NRS is not accessible. Figure 13 on how the call proceeds. The user must have configured the fallback route appropriately. For more information, see the SRG200/400 Release 1.5 Configuration Guide. NN43001-308 Standard 01.02 May 2007...
  • Page 81 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 voice mail or continuous ringback. Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide...
  • Page 82 Page 82 of 254 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 83 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 15 on Main Office Configuration for SRG200/400 Release 1.5 Dialing Plan configuration page 84 shows this scenario.
  • Page 84 Page 84 of 254 Dialing Plan configuration Figure 15 WAN is up. SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the main office (Normal Mode) NN43001-308 Standard 01.02 May 2007...
  • Page 85 Dialing Plan configuration Page 85 of 254 Figure 16 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 SRG200/400 Release 1.5 Configuration Guide...
  • Page 86 Page 86 of 254 Dialing Plan configuration 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): •...
  • Page 87 Branch Office Installation and Commissioning (NN43001-314) and IP Peer Networking Installation and Commissioning (NN43001-313). For more information on configuring the SRG, see the SRG200/400 Release 1.5 Configuration Guide. Option 2: DN ranges in the main office and SRG overlap; DNs for SRG IP Phones are the same in Normal and Local Mode In this configuration, the SRG DNs overlap with the main office DNs.
  • Page 88 Page 88 of 254 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 voice mail lines.
  • Page 89 Dialing Plan configuration Page 89 of 254 Figure 18 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 SRG200/400 Release 1.5 Configuration Guide...
  • Page 90 Page 90 of 254 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).
  • Page 91 Dialing Plan configuration Page 91 of 254 Figure 19 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 SRG200/400 Release 1.5 Configuration Guide...
  • Page 92 Page 92 of 254 Dialing Plan configuration 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): •...
  • Page 93 Branch Office Installation and Commissioning (NN43001-314) and IP Peer Networking: Installation and Configuration (553-3001-213). For more information on configuring the SRG, see the SRG200/400 Release 1.5 Configuration Guide. Option 3: DNs of SRG IP Phones and DNs in the main office...
  • Page 94 Page 94 of 254 Dialing Plan configuration translates the SRG IP telephone DN (4XXX) to the main office BUID (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.
  • Page 95 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 21 on page 96 Main Office Configuration for SRG200/400 Release 1.5 Dialing Plan configuration shows this scenario. Page 95 of 254 Configuration Guide...
  • Page 96 Page 96 of 254 Dialing Plan configuration Figure 21 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 97 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 SRG200/400 Release 1.5 Dialing Plan configuration Configuration Guide Page 97 of 254...

  • Page 98: Universal Dialing Plan

    For more information on configuring the main office and NRS, see Branch Office Installation and Commissioning (NN43001-314) and IP Peer Networking: Installation and Configuration (553-3001-213). For more information on configuring the SRG, see the SRG200/400 Release 1.5 Configuration Guide. Universal Dialing Plan...
  • Page 99 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 23 on Main Office Configuration for SRG200/400 Release 1.5 Dialing Plan configuration page 100 shows this scenario.
  • Page 100 Page 100 of 254 Dialing Plan configuration Figure 23 Calling from the main office to the SRG and SRG PSTN, in Normal Mode NN43001-308 Standard 01.02 May 2007...
  • Page 101 IP Phone registered to the main office. Figure 24 shows this scenario. Figure 24 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 SRG200/400 Release 1.5 Configuration Guide...
  • Page 102 Page 102 of 254 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.
  • Page 103 Dialing Plan configuration Page 103 of 254 Figure 25 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 SRG200/400 Release 1.5 Configuration Guide...
  • Page 104 Page 104 of 254 Dialing Plan configuration Configuration examples The following configurations are based on the examples provided in this section. For further information, see Branch Office Installation and Commissioning (NN43001-314). To configure the main office: • Configure the ESN Control Block for UDP in LD 86. •...
  • Page 105 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 SRG200/400 Release 1.5 Dialing Plan configuration Configuration Guide Page 105 of 254...
  • Page 106 For more information on configuring the main office and NRS, see Branch Office Installation and Commissioning (NN43001-314) and IP Peer Networking: Installation and Configuration (553-3001-213). For more information on configuring the SRG, see the SRG200/400 Release 1.5 Configuration Guide. NN43001-308 Standard 01.02...

  • Page 107: Bandwidth Management

    Network using Uniform Dialing Plan ......Network using Coordinated Dialing Plan ..... . . Main Office Configuration for SRG200/400 Release 1.5 Page 107 of 254...

  • Page 108: Introduction

    Page 108 of 254 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.
  • Page 109 8 kbit/s. The G.723.1 codec provides the greatest compression. IMPORTANT! SRG200/400 Release 1.5 does not support G.723 codec. Payload default values need to be changed if the customer wants to communicate with a third-party gateway that does not support the above default payload sizes.
  • Page 110 If the payload sizes are set higher than the default values (for example, to support a third-party gateway), then the local 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.

  • Page 111: Codec Selection

    Each codec list is sorted by order of preference (the first codec in the near end’s list is the near end’s most preferred codec, the first codec in the far end’s list is the far end’s preferred codec). Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management Configuration Guide...

  • Page 112: Codec Selection Algorithms

    • Best Bandwidth codec selection algorithm 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 113 Master/Slave information, is needed. Since any change to the Master/Slave algorithm implies a change to the H.323 standard, the new codec algorithm is used for Virtual Trunk calls between Nortel equipment. ‘Best Bandwidth’ codec selection algorithm The Best Bandwidth codec selection algorithm solves the issues caused by the H.323 Master/Slave algorithm.

  • Page 114: Configuring Bandwidth Management Parameters

    Configuring Bandwidth Management parameters The following sections describe how to configure Bandwidth Management in a CS 1000 network. Nortel recommends that you read the Bandwidth Management section in Converging the Data Network with VoIP Fundamentals (NN43001-260) before using the following configuration information.

  • Page 115: Zones

    VPNI as that of the main office Call Server with which they register. Nortel recommends that all the endpoints on a Call Server (IP Phones and Voice Gateway Media Cards) be configured with the same Zone number.

  • Page 116: Enabling Codecs

    Page 116 of 254 Bandwidth Management 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 117: Configuring Bandwidth Management

    Call Server zones that will be used for endpoints (telephones and gateways) with the following properties: — Intrazone Preferred Strategy = Best Quality (BQ) — Intrazone Bandwidth = default (1000000) Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management page 118) or LD 117 (see “Configuration...
  • Page 118 Page 118 of 254 Bandwidth Management • 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 27. See “Configuring zone parameters using CS 1000 Element Manager”...
  • Page 119 • zoneNumber = 0-255 • intraZoneBandwidth = Available intrazone bandwidth (Kbit/s); Nortel recommends this value be set to the maximum value. • intraZoneStrategy = BB (Best Bandwidth) or BQ (Best Quality); Nortel recommends this value be set to BQ.

  • Page 120: Maintenance Commands

    Standard 01.02 Description • interZoneStrategy = BB (Best Bandwidth) or BQ (Best Quality); Nortel recommends this value be set to BB to conserve interzone bandwidth. • zoneIntent = type of zone, where: — MO = Main Office (Call Server) zone —...
  • Page 121 — Select ALL to print statistics for all zones. — Select a specific zone number to display statistics for a specific zone. Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management Configuration Guide Page 121 of 254...
  • Page 122 Page 122 of 254 Bandwidth Management 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. Figure 29 shows an example of intrazone statistics.
  • Page 123 Do not use the PRT ZONE command — it has been replaced by the PRT INTRAZONE and PRT INTERZONE commands. Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management End of Procedure...

  • Page 124: Adaptive Network Bandwidth Management

    Page 124 of 254 Bandwidth Management LD 117 Print zone statistics. Command PRT INTRAZONE [<zone>] PRT INTERZONE [nearZone>] [<nearVPNI>] [<farZone>] [<farVPNI>] Adaptive Network Bandwidth Management Description The Adaptive Network Bandwidth Management feature enhances the performance of Voice over Internet Protocol (VoIP) networks based on real-time interaction.
  • Page 125 With Adaptive Network Bandwidth Management, it is not necessary to provision bandwidth parameters between every zone in the network. Rather, the Call Server automatically learns of new zones in the network and applies Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide...
  • Page 126 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 127 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. Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide...
  • Page 128 When a call is made from a zone with Adaptive Network Bandwidth Management enabled, to a third party gateway, which has no zone, then the zone of the Virtual Trunk (VTRK) is used and appears in the zone table.
  • Page 129 Sliding Maximum to change more rapidly in response to QoS alarms. However, making this value too large will result in loss of overall bandwidth, as shown in Figure 33 below and Figure 34 on page 130. Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide...
  • Page 130 Page 130 of 254 Bandwidth Management Figure 33 Effect of the default CQos Coefficient Figure 34 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).

  • Page 131: Feature Packaging

    VPNI as the main office Call Server. • All IP Phones (other than specific i2050 software phones) and DSP endpoints on a Call Server must be configured for the same zone. Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management Configuration Guide Page 131 of 254...

  • Page 132: Configuring Adaptive Network Bandwidth Management

    Page 132 of 254 Bandwidth Management • i2050 software phones being used remotely must be configured for Zone 0. • Branch office systems must tandem all calls through the main office Call Server to allow bandwidth monitoring and control. In this case, the media path is direct between the branch office and any point in the network.
  • Page 133 Bandwidth Management and CAC web page appears, as shown in Figure 35. Do not configure Adaptive Networks Bandwidth Management for Zone 0 or Virtual Trunk zones. Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management page 119) and click Adaptive...
  • Page 134 Page 134 of 254 Bandwidth Management Figure 35 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. NN43001-308 Standard 01.02 May 2007...
  • Page 135 QoS Response Time Interval (ZQRTI) Warning Alarm Threshold (ZQWAT) Critical Alarm Threshold (ZQUAT) Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management page 135 shows the fields in the Adaptive Network Bandwidth Field Definition Control the CAC feature for the zone •...
  • Page 136 Page 136 of 254 Bandwidth Management Table 7 Adaptive Network Bandwidth Management and CAC fields (Part 2 of 2) Field Title R Alarm Coefficient (CR) Packet Loss Alarm Coefficient (CPL) Delay Alarm Coefficient (CD) Jitter Alarm Coefficient (CJ) Coefficient of QoS (CQoS) Recent Validity Time Interval (CACVT) NN43001-308...
  • Page 137 Sliding Maximum bandwidth for the identified zone, where: • Zone = 1-255 • Jitter = Jitter coefficient = 1-(50)-100 CHG CQOS <Zone> <QoS> Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management Configuration Guide Page 137 of 254...
  • Page 138 Page 138 of 254 Bandwidth Management LD 117 — Configure Adaptive Network Bandwidth Management. (Part 2 of 5) Command Description Change the QoS coefficient in the formula that determines how quickly an alarm reduces the Sliding Maximum bandwidth for the identified zone, where: •...
  • Page 139 Sliding Maximum for the identified zone, where: • Zone = 1-255 • Interval = interval in minutes = 1-(5)-120 CHG ZQUAT <Zone> <Thres> Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management Configuration Guide Page 139 of 254...
  • Page 140 Page 140 of 254 Bandwidth Management LD 117 — Configure Adaptive Network Bandwidth Management. (Part 4 of 5) Command Description Change the QoS Unacceptable Alarm Threshold value for the identified zone, where: • Zone = 1-255 • Thres = threshold value = 1-(75)-99 When the zone-to-zone QoS value drops below the threshold value, the alarm is presented.
  • Page 141 ENL ZCAC <Zone> Enables the Call Admission Control (CAC) feature for the specified zone, where: • Zone = 1-255 Enables the feature on a zone-by-zone basis. Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management Configuration Guide Page 141 of 254...

  • Page 142: Maintenance Commands

    Page 142 of 254 Bandwidth Management Maintenance commands The Adaptive Network Bandwidth Management feature can be maintained using Element Manager or LD 117. Maintenance using Element Manager The CAC parameters, intrazone statistics, and interzone statistics for one of more zones are available in Element Manager from the Zones web page, shown in Figure 27 on use Procedure 7 on steps in Procedure 8.
  • Page 143 Clear zone-to-zone record for near (VPNI-Zone) for far (VPNI-Zone), where: • nearZone = 0-255 • nearVPNI = 1-16383 • farZone = 0-255 • farVPNI = 1-16383 Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management End of Procedure Page 143 of 254 Configuration Guide...
  • Page 144 Page 144 of 254 Bandwidth Management LD 117 — Display Adaptive Network Bandwidth Management information (Part 2 of 4) Command Description PRT INTRAZONE [<zone>] Print intrazone statistics for the identified zones, where: • zone = ALL or 1-255 The output of this command displays the following information: •...
  • Page 145 • First row = summary bandwidth usage per near zone • Next rows = bandwidth usage per near (VPNI- Zone) and far (VPNI - Zone) Figure 38 on Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management page 148 shows an example of the output for this command.
  • Page 146 Page 146 of 254 Bandwidth Management LD 117 — Display Adaptive Network Bandwidth Management information (Part 4 of 4) 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 147 Bandwidth Management Page 147 of 254 Figure 37 Sample output for PRT INTRAZONE command Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide...

  • Page 148: Tandem Bandwidth Management Overview

    Page 148 of 254 Bandwidth Management Figure 38 Sample output for PRT INTERZONE command Tandem Bandwidth Management overview In order for the main office to correctly keep track of all the bandwidth being used to and from a branch office the call must be tandemed through the main office.
  • Page 149 IP Phones that are registered with the main office (for example, Normal Mode). Patch Number A patch is required on the main office in order to invoke this feature. The patch number is MPLR 20259. Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management Configuration Guide Page 149 of 254...

  • Page 150: Dialing Plan Overview

    Page 150 of 254 Bandwidth Management 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 151 Bandwidth Management Page 151 of 254 Figure 40 General legend Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide...

  • Page 152: Network Using Uniform Dialing Plan

    Page 152 of 254 Bandwidth Management Network using Uniform Dialing Plan The following section provides general network configuration for a network using UDP only. Figure 41 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 153 Region steps 1, 2, 3 1, 2, 3 1, 2, 3 Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management Configuration detail and call progress during call setup UDP used for all calls within the region. UDP used for region to region calls.
  • Page 154 LOC values that are on branch offices may be provisioned as extended LOCs (> 3 digit codes). The DMI for the branch office “LOC” inserts a gateway routing prefix in front of the number. Similar configuration, as above, applies to regions 2 and 3.
  • Page 155 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 SRG200/400 Release 1.5 Bandwidth Management Configuration Guide...
  • Page 156 Page 156 of 254 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 43. Figure 43 Call flow for Scenario 1 - local call The branch office user dials 6-395-3456.
  • Page 157 In this example, the HLOC is unique between all the branch offices and the main office. See Figure 44. Figure 44 Call flow for Scenario 1- local call Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management Configuration Guide Page 157 of 254...
  • Page 158 Page 158 of 254 Bandwidth Management 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;...
  • Page 159 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 SRG200/400 Release 1.5 Bandwidth Management Configuration Guide...
  • Page 160 Page 160 of 254 Bandwidth Management Figure 46 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 161 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 SRG200/400 Release 1.5 Bandwidth Management Configuration Guide...
  • Page 162 Page 162 of 254 Bandwidth Management Figure 48 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 163 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 SRG200/400 Release 1.5 Bandwidth Management Configuration Guide...

  • Page 164: Summary Of Provisioning Procedures For Tandem Bandwidth Management

    This provides tandeming for outbound calls from a branch office through its main office. See step 1 on Plan the gateway routing prefixes, if not already done. At least one prefix is needed per branch office, although any branch offices that have a prefix for ESA “911”...
  • Page 165 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 167.

  • Page 166: Provisioning Example Of Tandem Bandwidth Management

    Procedure 9 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.
  • Page 167 841 (for main office B) and 842 (for main office A). 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 as used (LOC or SPN), the entries can be differentiated from the normal LOCs easily.
  • Page 168 Page 168 of 254 Bandwidth Management 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 169 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 SRG200/400 Release 1.5 Bandwidth Management Create an HLOC LD 90 REQ new CUST 0...
  • Page 170 Page 170 of 254 Bandwidth Management Table 12 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 171 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 SRG200/400 Release 1.5 Bandwidth Management Create a LOC LD 90 REQ NEW CUST 0 FEAT NET TRAN AC1...

  • Page 172: Network Using Mixed Coordinated Dialing Plan And Uniform Dialing Plan

    Page 172 of 254 Bandwidth Management Table 15 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 53 shows an example of a mixed network configuration.
  • Page 173 NRS after deleting the HLOC and converting to CDP. Similar configuration, as above, applies to regions 2 and 3. Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management Provisioning detail Configuration Guide Page 173 of 254...
  • Page 174 Page 174 of 254 Bandwidth Management Call between two local branch offices Figure 54 on Manager. Figure 54 Call flow for Scenario 2 – local call dials CDP The branch office user dials 3456 (CDP). The system transmits 3456 to the NRS.
  • Page 175 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 SRG200/400 Release 1.5 Bandwidth Management Configuration Guide Page 175 of 254...
  • Page 176 Page 176 of 254 Bandwidth Management Call between branch offices associated with different main offices In Figure 56, the first half of the call is shown (the originator side of the call). Figure 56 Call flow for Scenario 2 - local call to remote branch office (originator side) The branch office user dials 6-444-3456.
  • Page 177 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 SRG200/400 Release 1.5 Bandwidth Management Configuration Guide Page 177 of 254...

  • Page 178: Network Using Coordinated Dialing Plan

    Page 178 of 254 Bandwidth Management Network using Coordinated Dialing Plan The following section provides general details of network setup. Figure 58 shows a full CDP network configuration. Figure 58 Scenario 3 – full CDP network Table 17 lists the provisioning details for a full CDP network. Table 17 Provisioning details for this case (Part 1 of 2) Region...
  • Page 179 All branch offices delete the prefix and terminate the calls. May be to a local set or to a trunk. Similar configuration, as above, applies to regions 2 and 3. Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management Page 179 of 254...
  • Page 180 Page 180 of 254 Bandwidth Management Call between two local branch offices Figure 59 on offices. Figure 59 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;...
  • Page 181 In Figure 61 on page side of the call). Main Office Configuration for SRG200/400 Release 1.5 Bandwidth Management 181, the first half of the call is shown (originator side of 182, the second half of the call is shown (destination...
  • Page 182 Page 182 of 254 Bandwidth Management Figure 61 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 183: Management

    Quality of Service (QoS) has degraded to unacceptable levels. 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 SRG200/400 Release 1.5 Page 183 of 254 Configuration Guide...
  • Page 184 WAN bandwidth against the incremental cost of overflowed calls. Nortel recommends that this feature be used with DID (Direct Inward Dial) numbers. This allows calls that are rerouted over the PSTN to ring the intended telephone directly.
  • Page 185 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 SRG200/400 Release 1.5 IMPORTANT! Configuration Guide Page 185 of 254...
  • Page 186 Page 186 of 254 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 187: How Alternative Call Routing For Nbwm Works

    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 SRG200/400 Release 1.5 Page 187 of 254 Configuration Guide...

  • Page 188: Dialing Plans

    Page 188 of 254 Alternative Call Routing for Network Bandwidth Management 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.

  • Page 189: Examples Of Alternative Call Routing For Nbwm In Operation

    (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.
  • Page 190 Page 190 of 254 Alternative Call Routing for Network Bandwidth Management Figure 63 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.
  • Page 191 192 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 SRG200/400 Release 1.5 illustrates the steps that occur in an alternately routed Page 191 of 254...
  • Page 192 Page 192 of 254 Alternative Call Routing for Network Bandwidth Management Figure 64 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 63 on The main office Call Server determines there is insufficient bandwidth between the two zones.
  • Page 193 197. Call comes into IP Phone A from the PSTN or MCDN trunks in the main office zone (action labeled 3 in Figure 63 on Main Office Configuration for SRG200/400 Release 1.5 Page 193 of 254 page 190). page 192.
  • Page 194 There are two bandwidth zones indicated by the dashed line (main office zone [MO zone] and branch office zone [BO2 zone]). Telephone A and the Media Gateway belong to the MO zone. Telephones B and C and the branch office belong to the BO2 zone.
  • Page 195 At the NRS: • No provisioning required. Sequence of events in the call The information that follows refers to Figure 65 on page 196. Main Office Configuration for SRG200/400 Release 1.5 Page 195 of 254 page 194 and Figure 66 Configuration Guide...
  • Page 196 Page 196 of 254 Alternative Call Routing for Network Bandwidth Management Figure 66 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 65 on The main office Call Server determines there is insufficient bandwidth between the two zones.
  • Page 197 [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 SRG200/400 Release 1.5 page 194).
  • Page 198 Page 198 of 254 Alternative Call Routing for Network Bandwidth Management Figure 67 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).
  • Page 199 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 67 on page 200. Main Office Configuration for SRG200/400 Release 1.5 Page 199 of 254 page 198 and Figure 68 Configuration Guide...
  • Page 200 Page 200 of 254 Alternative Call Routing for Network Bandwidth Management Figure 68 Illustration showing digits dialed and outpulsed with Alternative Call Routing for NBWM NN43001-308 Standard 01.02 May 2007...
  • Page 201 — 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 67 on Main Office Configuration for SRG200/400 Release 1.5 page 198). page 198).

  • Page 202: Operating Parameters

    PSTN or TIE/MCDN route, if Alternative Call Routing is configured for the originating zone. Configure the Voice Gateway bandwidth zone and the IP Phone bandwidth zone with the same number on each Call Server. For alternately routed calls that originate at the branch office, the network...
  • Page 203 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 SRG200/400 Release 1.5 Configuration Guide...

  • Page 204: Feature Interactions

    The telephone calling must have an NCOS assigned that allows the call to use the alternate route. Network Routing Service (NRS) Both the main office and branch office must be registered on the Nortel NRS for tandem routing to work for main office to branch office tandeming. Trunk Route Optimization (TRO)

  • Page 205: Feature Packaging

    Command ENL ZALT <zone> Enable Alternative Call Routing for NBWM, where: <zone> Main Office Configuration for SRG200/400 Release 1.5 Description Input zone number (0-255). Configure the branch office zone using LD 117 at the main office. Page 205 of 254...
  • Page 206 Page 206 of 254 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 CHG ZALT <zone> <ALTPrefix> [<re-route all calls>] Change ALTPrefix number for zone, where: <zone>...

  • Page 207: Feature Implementation Using Element Manager

    Procedure 10 Accessing the Zones web page From the navigator, click IP Network > Zones. The Zones web page appears. (See Figure 69 on Main Office Configuration for SRG200/400 Release 1.5 Alternate Prefix All Calls Page 207 of 254 Alarms...
  • Page 208 Page 208 of 254 Alternative Call Routing for Network Bandwidth Management Figure 69 Access the Zones web page to select Alternate Routing for Calls between IP Stations Under Configuration click are programming, to expand the choices under it. 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.
  • Page 209 Enter a maximum of 7 digits in Alternate Routing Prefix Digits (ALTPrefix). Select the Re-route for All Calls (ALL_CALLS) check box to enable the feature for all calls. Click Submit to enter the data. Main Office Configuration for SRG200/400 Release 1.5 End of Procedure Page 209 of 254 Configuration Guide...

  • Page 210: Diagnostics

    Page 210 of 254 Alternative Call Routing for Network Bandwidth Management Diagnostics Command Line Interface diagnostics LD 117 - Obtain status for a particular zone. Command STAT ZALT <zone> If you do not enter a value in the zone field, you obtain a printout of the status of all configured zones.
  • Page 211 • enable/disable status of the Alternative Call Routing for NBWM feature • ALTPrefix digits • enable/disable status of the All Calls option Main Office Configuration for SRG200/400 Release 1.5 Page 211 of 254 Flags LOC ALT ESA ALT Configuration Guide...
  • Page 212 Page 212 of 254 Alternative Call Routing for Network Bandwidth Management Procedure 11 Printing zone ALTPrefix From the navigator, click System > Maintenance. The Maintenance web page appears. (See Figure 71.) Figure 71 System > Maintenance web page Click Select by Functionality. The Select by Functionality web page appears.
  • Page 213 Click Zone diagnostics. The Maintenance Commands for Zones web page appears. (See Figure 73 on page if you click on Zones, as you see in Figure 69 on Main Office Configuration for SRG200/400 Release 1.5 Page 213 of 254 page 214.) You can also access this...
  • Page 214 Page 214 of 254 Alternative Call Routing for Network Bandwidth Management Figure 73 The Maintenance Commands for Zones web page with PRT ZALT results Select Print Zone Alternate Prefix Information (PRT ZALT) from the the drop-down list beside Action. Select ALL or a zone number from the Zone Number drop-down list. Click Submit.
  • Page 215 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 74 shows a typical example of the results. Main Office Configuration for SRG200/400 Release 1.5 page 215.) page...

  • Page 216: Maintenance

    Page 216 of 254 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 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 217: Element Manager Maintenance

    Click Zone diagnostics. The Maintenance Commands for Zones web page appears. (See Figure 73 on Select Enable a Zone’s Branch Office Behavior from the drop-down list beside Action. (See Figure 75 on Main Office Configuration for SRG200/400 Release 1.5 Page 217 of 254 Alarms Suppression Time 1000 page 212.)
  • Page 218 Page 218 of 254 Alternative Call Routing for Network Bandwidth Management Figure 75 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.
  • Page 219 Enter digits in Alarm Suppression Time Period (ZAST). See Figure 76 page 219. Click Submit to enter the data. Figure 76 Alarm Suppression Time Period (ZAST) Main Office Configuration for SRG200/400 Release 1.5 End of Procedure Page 219 of 254 Configuration Guide...

  • Page 220: Nn43001-308 Standard 01.02 May

    Page 220 of 254 Alternative Call Routing for Network Bandwidth Management NN43001-308 Standard 01.02 May 2007...

  • Page 221: 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 SRG200/400 Release 1.5 Page 221 of 254 Configuration Guide...

  • Page 222: Emergency Services Access (Esa)

    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 223 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 SRG200/400 Release 1.5 Configuration Guide...
  • Page 224 ESA calls to nodes with direct ESA trunks. Routing configuration for ESA calls on SRG200/400 Release 1.5 Use the following steps to configure routing for ESA calls for the SRG200/ 400 Release 1.5: Build a destination code corresponding to the ESA SPN for the branch office.
  • Page 225 13 Configure the branch office zone on the branch office. 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 SRG200/400 Release 1.5 Page 225 of 254 Configuration Guide...
  • Page 226 SRG telephones. The provisioning of this prefix is an enhancement for branch office. While a variety of numbering schemes are available, Nortel recommends that customers use 0 + the ESN location code of the SRG + ESDN, where ESDN •...
  • Page 227 NEW CHG TYPE CUST ESDN xxxx ESRT 0-511 0-127 Main Office Configuration for SRG200/400 Release 1.5 Emergency Services configuration 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 228 If OSDN is used, the ESA route number must be blank to make test calls without using any trunk resources. It the route number has been configured, remove it by entering “x” at the prompt. Nortel recommends that the system administrator arrange a test call with the Public Services Access Point (PSAP).
  • Page 229 • AC = Access Code to add to dialed digits. If no AC is required, enter AC0 in place of AC1 or AC2. • ESA Prefix = Digit string added to start of ESDN. This is a unique prefix in the NRS. Nortel recommends that users use “0” + ESN location code of the 0725.
  • Page 230 Page 230 of 254 Emergency Services configuration LD 86 – Configure Digit Manipulation Index. Prompt Response CUST FEAT (0)-31 (0)-255 (0)-999 (0)-19 INST x...x CTYP <cr> NN43001-308 Standard 01.02 Configure the ESN Special Number at the main office. For information on configuring ESN, see Basic Network Features Fundamentals (NN43001-579).
  • Page 231 0-63 LTER ROUT 0-511 0-127 (0)-999 Main Office Configuration for SRG200/400 Release 1.5 Emergency Services configuration 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 232 Page 232 of 254 Emergency Services configuration 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 NN43001-308 Standard 01.02 iii. Configure the ESN Special Number and Digit Manipulation in LD 90.
  • Page 233 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 SRG200/400 Release 1.5 Emergency Services configuration Description...

  • Page 234: Configuring The Nrs For Esa Spn

    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.

  • Page 235: Configuring Esa Using Element Manager

    Call Server and the SRG to differentiate between emergency calls originating from IP Phones at each location and emergency calls originating on trunks. Main Office Configuration for SRG200/400 Release 1.5 Emergency Services configuration End of Procedure page 49.
  • Page 236 Page 236 of 254 Emergency Services configuration For information on emergency services for Virtual Office, see Emergency Services Access Fundamentals (NN43001-613). NN43001-308 Standard 01.02 May 2007...

  • Page 237: Enhanced Unistim Firmware Download

    IP Phone 1120E • IP Phone 1140E • IP Phone 1150E The Enhanced UNIStim Firmware download feature is not supported on IP Softphone 2050 and WLAN 2210/2211/2212/6120/6140. Main Office Configuration for SRG200/400 Release 1.5 Page 237 of 254 Configuration Guide...
  • Page 238 Page 238 of 254 Enhanced UNIStim Firmware Download The redirected IP Phones at the SRG 50 are under the control of the main office Call Server for the majority of the deployment (Normal Mode). Users of the SRG IP Phones receive the features, key layout, and tones of the main office Call Server.

  • Page 239: Firmware Upgrade

    For instructions, see Signaling Server Installation and Commissioning (NN43001-312). Issue the CLI command IP Phones at the Main office and branch office are upgraded as necessary. Main Office Configuration for SRG200/400 Release 1.5 Enhanced UNIStim Firmware Download umsUpgradeAll End of Procedure Page 239 of 254...
  • Page 240 Page 240 of 254 Enhanced UNIStim Firmware Download NN43001-308 Standard 01.02 May 2007...

  • Page 241: 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 SRG200/400 Release 1.5 page 242. to main office IP Phone. See Table 19 on IP Phone in Normal Mode.
  • Page 242 Page 242 of 254 Appendix A: Media Redirection Scenarios In these scenarios, consult the zone table at the main office for accurate bandwidth usage information. Table 18 Scenario 1: Codec switches correctly during media redirection Event 1 An incoming Direct Inward Dial (DID) call to branch office uses IP Peer to reach the symposium controller Control Directory Number (CDN) in the main office.
  • Page 243 3 The Call Transfer key on the main office IP Phone is pressed to complete the call transfer. 4 The call is released. Main Office Configuration for SRG200/400 Release 1.5 Appendix A: Media Redirection Scenarios Result A speech path is established between the SRG TDM telephone and the main office IP Phone.
  • Page 244 Page 244 of 254 Appendix A: Media Redirection Scenarios Table 21 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 IP Phone registered to the main office. 2 The SRG IP Phone registered to the main office initiates a conference call to a main office IP Phone.
  • Page 245 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 SRG200/400 Release 1.5 Appendix A: Media Redirection Scenarios Result The SRG TDM telephone is put on hold. A...
  • Page 246 Page 246 of 254 Appendix A: Media Redirection Scenarios NN43001-308 Standard 01.02 May 2007...

  • Page 247: 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 SRG200/400 Release 1.5 Page 247 of 254 Configuration Guide...
  • Page 248 Alternate Gatekeeper, the SRG IP Phones remain registered with the main office but calls cannot be sent to the SRG. gateway In networking, a combination of hardware and software that links two different types of networks. Gateways between e-mail systems, for example, enable users on different e-mail systems to exchange messages.
  • Page 249 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 SRG200/400 Release 1.5 List of terms Page 249 of 254...
  • Page 250 Each packet is processed by the algorithm to determine its destination. SRG200/400 Release 1.5 Survivable Remote Gateway 200/400 Release 1.5. This describes the equipment used to create an IP branch office with a CS 1000 system acting as the main office.
  • Page 251 PSTN call dialed by the main office telephones. The ZDP routes the call through VoIP trunk to the SRG. Main Office Configuration for SRG200/400 Release 1.5 List of terms Page 251 of 254...
  • Page 252 Page 252 of 254 List of terms NN43001-308 Standard 01.02 May 2007...

  • Page 253: Index

    Dialing plan configuration, 49 Dialing plan configuration for SRG PSTN access, Dialing plan configuration in Normal Mode, 55 DSP, 247 Main Office Configuration for SRG200/400 Release 1.5 Emergency Services Access (ESA), 222 Emergency Services configuration, 221 Emergency Service using Special Numbers, 235...
  • Page 254 SRG information required by the main office, 38 SRG IP Phones to local PSTN calls, 30 SRG PSTN to an SRG telephone (DID call), 52 SRG user call to an SRG PSTN, 52 Survivable Remote Gateway, 15 NN43001-308 Standard 01.02 Testing PSTN access, 74...
  • Page 256 Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks. Nortel, Nortel (Logo), the Globemark, SL-1, Meridian 1, and Succession are trademarks of Nortel Networks.

This manual is also suitable for:

Srg4001000 con?guration guide

Table of Contents