Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 .
Document status: Standard Document version: 02.02 Document date: 3 December 2007 Copyright © 2005-2007, Nortel Networks All Rights Reserved. Sourced in Canada. The information in this document is subject to change without notice. The statements, configuration, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty.
Revision history December 2007 Standard 02.02. This document is up-issued to support CS 1000 Release 5.0 for SRG 50 Release 3.0. This document includes SIP Trunks configuration at the main office. August 2007 Standard 02.01. This document is up-issued to support CS 1000 Release 5.0 for SRG 50 Release 3.0. June 2007 Standard 01.02. This document is up-issued to remove the Nortel Networks Confidential statement. May 2007 Standard 01.01.
Revision history Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Contents New in this release 9 Other 9 Subject 9 Intended audiences 9 Related information 9 NTPs 10 Online 10 CD-ROM 10 Description 11 Contents 11 Survivable Remote Gateway 11 Main office hardware description 14 Main office requirements 17 Optional features to enhance SRG functionality 18 Normal Mode and Local Mode overview 19 Normal Mode 19 Bandwidth Management Overview 24 Time of Day 24 SRG IP Phone to local PSTN calls 25 IP Phone to analog (500/2500-type) telephone calls 25 Capacity 26 Branch off
Contents Dialing Plan configuration 43 Contents 43 Overview 43 On-net dialing plan 43 Off-net dialing plan 45 Routing calls 45 SIP/H.
Contents 7 Enhanced UNIStim Firmware Download Contents 205 Description 205 Firmware upgrade 205 206 Appendix A Media Redirection Scenarios 209 List of terms 213 Index 218 Procedures Procedure 1 Procedure 2 Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure Procedure 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 Configuring ESN and SRG zones 34 Configuring branch office IP Phones at the main of
Contents Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
New in this release The CS 1000 Main Office Configuration for SRG50 (NN43001-307) for CS 1000 Release 5.0 includes support for SRG 50 Release 3.0. The following sections detail what is new in CS 1000 Main Office Configuration for SRG50 (NN43001-307) for CS 1000 Release 5.0 . Other CS 1000 Main Office Configuration for SRG50 (NN43001-307) includes the following changes: • Replaced instances of OTM 2.2 with TM 3.1. • Updated Element Manager with enhancements. • Added support for new IP Phones.
New in this release NTPs The following NTPs are referenced in this document: • Converging the Data Network with VoIP (NN43001-260) • Electronic Switched Network Reference—Signaling and Transmission (NN43001-280) • Dialing Plans Reference (NN43001-283) • Signaling Server Installation and Commissioning (NN43001-312) • IP Peer Networking Installation and Commissioning (NN43001-313) • Branch Office Installation and Commissioning (NN43001-314) • Telephony Manager 3.
Description Contents This section contains information about the following topics: • "Survivable Remote Gateway" (page 11) • "Main office hardware description" (page 14) • "Main office requirements" (page 17) • "Optional features to enhance SRG functionality" (page 18) • "Normal Mode and Local Mode overview" (page 19) • "Capacity" (page 26) • "Branch office dialing plan" (page 27) • "Branch office and SRG 50 terminology" (page 28) Survivable Remote Gateway The Survivable Remote Gateway (
Description SRG 50 Release 3.0 provides the following: • extends support for the IP Phone 1110 See "Supported IP Phones" (page 16) for a complete list of supported IP Phones. • evolves the SIP trunk to support a standard SIP Trunk interface • supports On-site Notification Table 1 Supported software at the branch office IP branch office solution Survivable users Server support Feature description SRG 1.0 up to 90 Succession 3.0 CS 1000 Release 4.0 CS 1000 Release 4.
Survivable Remote Gateway 13 IP branch office solution Survivable users Server support Feature description SRG 50 Release 3.0 up to 80 CS 1000 Release 5.0 VoIP and Application Gateway Local Mode = Basic telephony features Extends IP Phone support to include the IP Phone 1110. Supports On Site Notification for E-911 calls. Provides H.323 and SIP trunking. MG 1000B up to 400 Succession 3.0 CS 1000 Release 4.0 CS 1000 Release 4.5 CS 1000 Release 5.
Description Figure 1 "SRG network" (page 14) shows the networking among the main office, SRG, and IP Phones. 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 • CS 1000M MG Throughout this document, references to CS 1000 systems encompass all CS 1000 system types. The diagrams throughout this documentation show a CS 1000E main office.
Main office hardware description 15 Signaling Server The following Signaling Servers are available for CS 1000 Release 5.0 : • ISP1100 • HP-DL320-G4 • IBM-X306m • Common Processor Pentium Mobile (CP PM) The Signaling Server is required at the main office only. It provides the following functions: • Terminal Proxy Server (TPS) The TPS provides a connection from the IP Phones to the Call Server and a connection from a Virtual Trunk to the Call Server. • H.
Description • H.323 Gatekeeper— provides central dialing plan management and routing for H.323-based endpoints and gateways. • SIP Redirect Server NRS — provides central dialing plan management and routing for SIP-based endpoints and gateways. SIP Trunks are used for Voice packet traffic alone. • NRS Database— stores the central dialing plan in XML format for the H.323 Gatekeeper, and the SIP Redirect Server. The H.
Main office requirements IP Phone 2002 Supported Supported Supported IP Phone 2004 Supported Supported Supported IP Phone 2007 Supported Supported Supported IP Audio Conference Phone 2033 Supported Supported Supported IP Softphone 2050 Supported Supported Supported IP Phone 1110 Not supported Not supported Supported IP Phone 1120E Not supported Supported Supported IP Phone 1140E Not supported Supported Supported IP Phone 1150E Not supported Not supported Not supported Mo
Description — IP User License for the IP Phone 2002, IP Phone 2004, IP Phone 2007, IP Phone 1120E, IP Phone 1140E, IP Softphone 2050, Mobile Voice Client (MVC) 2050, WLAN Handset 2210, WLAN Handset 2211, and WLAN Handset 2212 The main office requires the following software packages to support the specified Basic Network features. See Basic Network Feature Fundamentals (NN43001-579) for more information about these features. • Network Call Back Queuing (MCBQ) package 38.
Normal Mode and Local Mode overview 19 • Network Signaling (NSIG) package 37. This package is optional for 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, see SRG50 Configuration Guide (NN40140-500).
Description ATTENTION When a telephone or trunk in the main office calls an SRG IP Phone that has switched to Local Mode due to WAN failure, the call is treated according to the main office call redirection configuration (such as forwarding to voice mail or continuous ringback).
Normal Mode and Local Mode overview 21 While in Local Mode, the SRG 50 system continues to monitor for a main office CS 1000 heartbeat signal, and once detected, automatically redirects phones on an individual basis back to Normal Mode of operation. If a call is active, the SRG waits until the call is completed before redirecting the phones; calls in progress are not interrupted. This switch-over occurs almost immediately once the SRG determines that an individual phone can be redirected.
Description If the main office Signaling Server fails and an Alternate Signaling Server is available, the SRG IP Phones reset and reregister with the SRG. The SRG will then query the NCS for the Alternate Signaling Server IP address. The SRG will redirect the IP Phone to the Alternate Signaling Server and continue to receive call processing services from the main office Call Server. If no Alternate Signaling Server is available, the SRG IP Phones reset and register with the SRG in Local Mode.
Normal Mode and Local Mode overview 23 Testing the phone in Local Mode From Normal Mode, the branch user has the option of going to Local Mode manually using the Test Local Mode feature, or when the telephone is power-cycled. 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.
Description Bandwidth Management Overview For a complete overview of Bandwidth Management, see the Converging the Data Network with VoIP (NN43001-260) and for details on configuration, see "Bandwidth Management" (page 95). 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.
Bandwidth Management Overview 25 The time zone of the SRG is configured with the SRG zone at the main office. The time zone adjusts the main office time for display at the SRG. SRG phones then display the correct time of the SRG, rather than that of the main office. For any configurations using centralized Call Pilot on the main office with one or more branch offices in separate time zones, the NMS package is required at the main office for the branch IP Phones.
Description 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. When the SRG can reach the main office but the IP Phone cannot ping the main office due to a network outage, an IP Phone registration can force the telephone into a cycle of registering locally, being redirected to the main office, rebooting, and then registering locally again.
Branch office dialing plan 27 Branch office dialing plan Since IP Phone users can be located at a branch office equipped with an SRG, the routing of calls to the local gateway is important (especially when toll charges apply to calls made from the central Call Server that controls the telephone). The administrator can configure digit manipulation through zone attributes for IP Phones to select a main office or branch office that provides PSTN access local to the destination of the call.
Description Music on Hold For SRG users in Normal Mode, the main office provides music to the user if Music on Hold is provisioned. The use of the G.729A/AB codec between the main office and the branch office can impact the music quality. ATTENTION G.723 codec is not supported on SRG 50. Branch office and SRG 50 terminology Table 3 "Branch office and SRG 50 terminology" (page 28) lists configuration-related terms and contexts where branch office and SRG 50 terminology differ.
Limitations Term or context Branch office 29 SRG 50 Network Class of Service (NCOS) telephone numbers (internal, not PSTN) DN DN Limitations The following is a list of limitations for SRG 50 Release 3.0: • When an IP Phone is in Local Mode, the SRG 50 does not provide all the features as those provided by the CS 1000 main office. In Local Mode, the SRG provides basic features, basic call handling, and basic routing capabilities only.
Description Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Setting up the main office Contents This section contains the following topics: • "Introduction" (page 31) • "SRG information required by the main office" (page 31) • "Main office information required by the SRG" (page 32) • "Zone parameters" (page 34) • "Branch office IP Phone configuration at the main office" (page 38) • "SIP IP Trunks configuration at the main office" (page 40) Introduction This section describes the following information required to configure the main office: • SRG info
Setting up the main office • information which allows the administrator to create an NCS (H.
Main office information required by the SRG Use Table 5 "Main office interoperation information" (page 33) to record main office information required by the SRG.
Setting up the main office Main office components Information about this system Zone dialing: • ZDP appended to SRG IP Phone PSTN dialing strings to redirect the call to SRG PSTN • Any steering codes (destination codes) that must be mirrored by SRG programming IP Phone configuration: MOTN/BUID list, including which type of IP Phone is assigned to each number. Make note of the leading number, as SRG uses this as the DN range for CDP dialing.
Zone parameters 35 Table 6 Configure Customer Data Home Location Code and Virtual Private Network Identifier Prompt Response Description REQ: CHG Changing existing data TYPE: NET ISDN and ESN Networking options Customer number CUST 0-99 Range for Large Systems … … … CLID YES Allow Calling Line Identification option -ENTRY xx CLID entry to be configured --HLOC 100-9999999 Home Location code (ESN) (3-7 digits) ISDN YES Integrated Services Digital Network -VPNI (0)-16383 Virtual P
Setting up the main office Description Command Define a zone as a branch office zone. CHG ZDST If the branch office observes Daylight Savings Time (DST), these parameters specify the start and end of DST. During DST, the clock automatically advances one hour forward.
Zone parameters 37 2. Select the zone to be configured and configure the following properties. • Basic Property and Bandwidth Management (see Figure 3 "Zone Basic Property and Bandwidth Management web page" (page 37)) • Time Difference and Daylight Saving Time Property (see Figure 4 "Zone Time Difference and Time web page" (page 38)) Figure 3 Zone Basic Property and Bandwidth Management web page Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.
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" (page 95). 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. These can be provisioned using Telephony Manager 3.1.
Branch office IP Phone configuration at the main office • Customer Number • Branch Office Zone • Prime DN corresponding to the BUID 39 See Telephony Manager 3.1 System Administration (NN43050-601) for details. Branch office IP Phone configuration using LD 11 Use Procedure 2 "Configuring branch office IP Phones at the main office using LD 11" (page 39) at the main office to configure branch office IP Phones.
Setting up the main office Prompt Response Description … … … SCPW xxxx Station Control Password Must equal Station Control Password Length (SCPL) as defined in LD 15. Not prompted if SCPL = 0. Precede with X to delete. —End— SIP IP Trunks configuration at the main office In order for the SRG 50 to act as a SIP endpoint and to use the SIP Trunks for call signaling with the CS 1000, you must configure SIP Trunks between the SRG 50 branch office and the CS 1000 Release 5.5 main office.
SIP IP Trunks configuration at the main office 41 Figure 5 SIP Trunk configuration in Element Manager 8 Click Save and Transfer. The Save and Transfer window appears. 9 Click OK. 10 Log on to Network Routing Service (NRS) Manager. 11 Select the Configuration tab. 12 From the H.323 Support list, select H.323 not supported. 13 Select the Network Connection Server enabled check box. See Figure 6 "SIP Trunk configuration in NRS" (page 41). Figure 6 SIP Trunk configuration in NRS 14 Select Save.
Setting up the main office The Gateways Endpoints window appears. The SRG registers as a static SIP endpoint. See Figure 7 "Gateways Endpoints window in NRS" (page 42). Figure 7 Gateways Endpoints window in NRS —End— Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Dialing Plan configuration Contents This section contains the following topics: • "Overview" (page 43) • "On-net dialing plan" (page 43) • "Off-net dialing plan" (page 45) • "Routing calls" (page 45) • "SIP/H.
Dialing Plan configuration • Uniform Dialing Plan (UDP) – Location code is added to the DN for the BUID ATTENTION Nortel recommends that the SRG use CDP. CDP Terminal Numbers (TN) 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 DN available on the SRG.
SIP/H.323 zones 45 Off-net dialing plan When dialing to the PSTN, the Call Server determines that the call destination is off-net by analyzing the digits that must be preconfigured at major Call Servers in the network. If routed over a Virtual Trunk, a request is sent to the NRS to determine the location of public E.164 numbers. The NRS is configured with a list of potential alternate routes that can be used to reach a certain dialed number.
Dialing Plan configuration It is possible to divide a system into several zones. It is also possible to divide a customer within a system into different zones. It is more common to assign one zone to one system and one customer. Zone-based digit manipulation For SRG users in Normal Mode, it may be desirable to provide routing that is different from that provided to main office users.
Zone-based digit manipulation 47 The combination of zone-based digit manipulation and CS 1000 routing capabilities can be used to achieve many other routing outcomes for SRG user calls. Calling Line ID composition Digital manipulation is commonly used for digit insertion and deletion. It is also used for call type conversion before out-pulsing the digits to the Virtual Trunk.
Dialing Plan configuration Configuring the dialing plan for PSTN access to SRG users in Normal Mode Preparing to configure the dialing plan Before configuring the dialing plan for PSTN access to SRG users in Normal Mode, you must complete the following steps: • At the main office, configure the Virtual Trunk to enable calls originating on SRG IP Phones in Normal Mode to reach the branch office. See IP Peer Networking Installation and Commissioning (NN43001-313) for details.
Configuring the dialing plan for PSTN access to SRG users in Normal Mode • 49 Configure the NRS—see Procedure 4 "Configuring the NRS database" (page 57). 1. Access NRS Manager. 2. Select an endpoint. 3. Configure the Numbering Plan Entry for the branch office. • At the branch office—see Procedure 5 "Configuring the branch office" (page 60). 1. Configure the Route List Index. 2. Configure ESN. These steps can be done using overlays, as described in this section, or in Element Manager and NRS Manager.
Dialing Plan configuration For example, assume that AC1 = 1, AC2 = 2, and ZDP = 101. If an SRG user dials 1 87654321, ZDP is inserted in the dialed digits to form a digit string of 1 101 87654321. If an SRG user dials 2 87654321, ZDP is inserted in the dialed digits to form a digit string of 2 101 87654321. • CHG ZACB AC1 AC2 In this configuration, only calls dialed with AC1 undergo zone-based digit manipulation. All SRG user calls dialed with AC1 can then be routed to the SRG PSTN.
Configuring the dialing plan for PSTN access to SRG users in Normal Mode 51 LD 117 Define the zone digit manipulation for the branch office zone at the main office Description Command CHG ZDP Define the dialing plan for the branch office zone, where DialingCode1, DialingCode2, and DialingCode3 are inserted into the dialed digits between the Access Code and the remainder of the dialed number.
Dialing Plan configuration 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). This unique non-dialable number can then be used, when configuring the main office ESN Special Number (step 4 of Procedure 3 "Configuring the main office" (page 49)) and the NRS (H.
Configuring the dialing plan for PSTN access to SRG users in Normal Mode Prompt Response Description CUST xx Customer number as defined in LD 15. FEAT DGT Digit manipulation data block DMI 1-999 Digit Manipulation Index numbers 53 The maximum number of Digit Manipulation tables is defined at the MXDM prompt in LD 86. DEL (0)-19 Number of leading digits to be deleted, usually 0 at the main office. INST x…x Insert. Up to 31 leading digits can be inserted, usually none at the main office.
Dialing Plan configuration Prompt Response Description 0-511 0-127 Range for Large Systems 1-999 Digit Manipulation Index number as defined in LD 86, FEAT = DGT (see step a). Range for MG 1000B … DMI For example, assume that the Virtual Trunk is on route 10, and the Customer number is 0: >LD REQ CUST FEAT DMI DEL INST ISPN CTYP REQ CUST FEAT RLI ENTR LTER ROUT ... DMI ... 4 86 NEW 0 DGT 10 YES NATL NEW 0 RLB 10 0 NO 10 Configure ESN Special Number and Digit Manipulation.
Configuring the dialing plan for PSTN access to SRG users in Normal Mode Prompt Response Description SPN x…x Special Number translation 55 Enter the SPN digits in groups of 3 or 4 digits, separated by a space (for example, xxxx xxx xxxx). The SPN can be up to 19 digits long. The maximum number of groups allowed is 5. FLEN Flexible Length (0)-24 The number of digits the system expects to receive before accessing a trunk and outpulsing these digits.
Dialing Plan configuration • Be careful when choosing how many dialed digits to include in the SPN. If one of the dialed digits is included in the SPN (that is, ZDP + one dialed digit), a maximum of ten SPN must be configured for each branch office. Similarly if two dialed digits are included in the SPN (ZDP + two dialed digits), a maximum of 100 SPN must be configured for each branch office.
Configuring the dialing plan for PSTN access to SRG users in Normal Mode >LD 90 REQ NEW CUST 0 FEAT NET TRAN AC1 TYPE SPN SPN 1011 FLEN 14 11 digits for long-distance + 3 digits for ZDP … RLI CLTP … SPN FLEN 1015 10 7 digits for long-distance + 3 digits for ZDP … RLI 30 CLTP LOCL … SPN 1016 FLEN 10 7 digits for long-distance + 3 digits for ZDP 57 10 NATL RLI 30 CLTP LOCL … After configuring main office routing to the NRS, the NRS database must be provisioned to identify the desired endpoint for t
Dialing Plan configuration The Routing Entries window opens, as shown in Figure 8 "NRS Routing Entries window with no endpoint selected" (page 58). Figure 8 NRS Routing Entries window with no endpoint selected 4 Choose the appropriate Service Domain, L1 Domain, and L0 Domain from the corresponding drop-down menus. 5 Click on Look up to open a window with a lookup path for gateway endpoints.
Configuring the dialing plan for PSTN access to SRG users in Normal Mode 59 Figure 10 NRS Routing Entries window for selected endpoint 7 Click Add in the Routing Entries window to add a routing entry. The Add Routing Entry window opens, as shown in Figure 11 "Add Routing Entry" (page 59). Figure 11 Add Routing Entry 8 Configure the numbering plan entries for the branch office.
Dialing Plan configuration For example, if ZDP = 101, it is possible to provision multiple Numbering Plan Entries (101, 1011, and so on) to route calls based on the ZDP value or the ZDP value plus some of the dialed digits. Unlike on the Call Server, if the ZDP plus additional digits are used to identify routing it is not necessary to provision all of the combinations.
Configuring the dialing plan for PSTN access to SRG users in Normal Mode Prompt Response Description ISPN NO IP Special Number INST x…x Insert. Up to 31 leading digits can be inserted. 61 Call type used by the call. The far-end switch must recognize this call type. CTYP INTL International NPA National NXX UDP LOC Local PSTN SPN Special Number b. Configure the RLI in LD 86 with the RLB feature. LD 86 Configure Route List Index Prompt Response Description REQ NEW Add new data.
Dialing Plan configuration >LD REQ CUST FEAT DMI DEL 86 NEW 0 DGT 18 3 Set to remove ZDP added in the main office INST CTYP LOC REQ CUST FEAT RLI ENTR LTER ROUT ... DMI ... 2 Set according to associated SPN pattern NEW 0 RLB 18 0 NO 18 18 Configure ESN Special Number and Digit Manipulation. LD 90 Configure ESN Special Number and Digit Manipulation Prompt Response Description REQ NEW Add new data. CUST xx Customer number as defined in LD 15.
Configuring the dialing plan for PSTN access to SRG users in Normal Mode Prompt Response Description 0-999 Route List Index configured in LD 86 (see step 1) 63 … - RLI After configuring the specialized route for calls that have been routed to the branch office by the NRS, the route must be associated with the ESN Special Number. The branch office receives the manipulated number as an incoming call, indicating that the ZDP value added at the main office is at the beginning of the number.
Dialing Plan configuration Figure 12 Zone Dialing Plan and Access Codes Testing PSTN access using an SRG IP Phone Use Procedure 6 "Testing PSTN access using an SRG IP Phone" (page 64) to test that PSTN access is working correctly. Procedure 6 Testing PSTN access using an SRG IP Phone Step Action 1 From an SRG IP Phone in Local Mode: a. Make a local PSTN call. b. Make a long-distance call. The calls must be routed according to the branch office ESN configuration.
Dialing plan examples 65 For calls that tandem over the Virtual Trunk to the branch office and go out to the PSTN trunk(s) in the branch office, the following configuration problems can occur: • The call can receive overflow tones. Use L D 96 to view the digits sent to the Virtual Trunk (ENL MSGO {dch#}). • If the digits look correct at the main office, the NRS might not be properly configured. If the NRS rejects the call, a diagnostic message is displayed on the Signaling Server console.
Dialing Plan configuration This section describes the common call scenarios. The unique call scenarios are described with the configuration of the corresponding option, starting with"Option 1" (page 70). Normal Mode: Main office telephone calls an analog phone at the SRG The call is routed through the NRS and handled by the SRG. Figure 13 "Normal Mode: Main office telephone calls an analog phone at the SRG" (page 66) shows how the call proceeds.
Dialing plan examples 67 Normal Mode: Main office telephone makes a call over the PSTN through the SRG Routing is configured so the destination code of the PSTN through the SRG is at the start of the dialing string. Figure 14 "Normal Mode: Main office telephone makes a call over the PSTN through the SRG" (page 67) shows how the call proceeds.
Dialing Plan configuration Figure 15 Normal Mode: SRG IP Phone makes a call over the PSTN 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 by the SRG and is sent directly to the SRG IP Phone. The call is handled Local Mode: SRG telephone calls a main office telephone In this case, the WAN or NRS is not accessible.
Dialing plan examples 69 The user must have configured the fallback route appropriately. See the SRG50 Configuration Guide (NN40140-500) for further information. Figure 16 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. Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.
Dialing Plan configuration Option 1 DN ranges in the main office and SRG are unique; DNs for SRG IP Phone are the same in Normal and Local Mode This is the recommended CDP configuration to offer seamless dialing. In this configuration, the user dials the same DN for SRG IP Phones in either Normal or Local Mode. The DN for SRG IP Phones are configured to be the same on both the SRG and main office. This allows seamless dialing from both the SRG and main office.
Dialing plan examples 71 Figure 18 "Calls to an SRG IP Phone and a main office IP Phone registered to the main office " (page 72) shows the WAN is up. An SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the main office (Normal Mode). Figure 19 "Calls to an SRG analog phone, SRG IP Phone, and a main office IP Phone " (page 73) shows the WAN is down. An SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the SRG (Local Mode).
Dialing Plan configuration Figure 18 Calls to an SRG IP Phone and a main office IP Phone registered to the main office Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Dialing plan examples 73 Figure 19 Calls to an SRG analog phone, SRG IP Phone, and a main office IP Phone Configuration • To configure the main office: Configure the ESN Control Block for CDP in LD 86. >LD 86 REQ NEW CUST 0 Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Dialing Plan configuration FEAT ESN CDP YES MXSC 50 NCDP 4 DLTN YES • Configure the CDP Distant Steering Code (DSC) in LD 87. > LD 87 REQ NEW CUST 0 FEAT CDP TYPE DSC DSC 50 FLEN 4 RLI 12 To configure the NRS (H.323 Gatekeeper/SIP Redirect Server): • Create CDP Domain: MO_BO_CDP. • Create H.323/SIP endpoints: MO, BO. • Create Numbering Plan entries in CDP Domain: — Add 40 for endpoint BO. — Add 30 for endpoint MO. — Add 42 for endpoint MO. For information about configuring H.
Dialing plan examples 75 The users in both the main office and the SRG dial only the DN for all telephones in the main office and the SRG in both Normal Mode and Local Mode. For more information on configuring the main office and NRS, see Branch Office Installation and Commissioning (NN43001-314) and IP Peer Networking Installation and Commissioning (NN43001-313). For more information on configuring the SRG, see SRG50 Configuration Guide (NN40140-500).
Dialing Plan configuration Figure 20 CDP Option 2 Call scenarios Common call scenarios for this CDP option are listed in "Call scenarios" (page 65). The following additional call scenarios are unique to this CDP option: • Normal Mode: An SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the main office. The WAN is up. SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the main Office (Normal Mode).
Dialing plan examples 77 Figure 21 SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the main office • Local Mode: SRG IP Phones are registered to the SRG. Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Dialing Plan configuration In this scenario, the WAN and the NCS are working. However, the SRG IP Phones are redirected to the SRG and are in Local Mode (Call Forward All Calls is inactive). The following occur: — Telephones registered at the SRG dial local DNs (see the common call scenarios given in "Call scenarios" (page 65)). — SRG calls to the main office use VoIP routing. The WAN is down.
Dialing plan examples 79 Figure 22 SRG analog phone calls an SRG IP Phone and a main office IP Phone Configuration • To configure the main office: Configure the ESN Control Block for CDP in LD 86. > LD 86 REQ NEW Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Dialing Plan configuration CUST 0 FEAT ESN CDP YES MXSC 50 NCDP 4 DLTN YES • Configure the CDP Distant Steering Code (DSC) in LD 87. > LD 87 REQ NEW CUST 0 FEAT CDP TYPE DSC DSC 50 FLEN 4 RLI 12 To configure the NRS (H.323 Gatekeeper/SIP Redirect Server): • Create CDP Domain: MO_BO_CDP. • Create H.323 and SIP endpoints: MO, BO. • Create Numbering Plan entries in CDP Domain: — Add 30 for endpoint BO. — Add 32 for endpoint MO. For information about configuring H.
Dialing plan examples 81 For more information on configuring the main office and NRS, see Branch Office Installation and Commissioning (NN43001-314) and IP Peer Networking Installation and Commissioning (NN43001-313). For more information on configuring the SRG, see SRG50 Configuration Guide (NN40140-500).
Dialing Plan configuration Figure 23 CDP Option 3 Call scenarios Common call scenarios for this CDP option are listed in "Call scenarios" (page 65). The following additional call scenarios are unique to this CDP option: • Normal Mode: An SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the main office. In this scenario, the telephone registered to the SRG can either dial the SRG DN or the main office DN for the SRG IP Phone.
Dialing plan examples 83 Figure 24 SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the main office • Local Mode: SRG IP Phones are registered at the SRG. Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Dialing Plan configuration In this scenario, the WAN and the NCS are working. If the main office user dials the SRG DN (42xx) to call the IP Phone, the call goes through. Configuration • To configure the main office: Configure the ESN Control Block for CDP in LD 86. > LD 86 REQ NEW CUST 0 FEAT ESN CDP YES MXSC 50 NCDP 4 DLTN YES • Configure the CDP Distant Steering Code (DSC) in LD 87. > LD 87 REQ NEW CUST 0 FEAT CDP TYPE DSC DSC 4 FLEN 4 RLI 12 To configure the NRS (H.
Dialing plan examples 85 For more information on configuring the main office and NRS, see Branch Office Installation and Commissioning (NN43001-314) and IP Peer Networking Installation and Commissioning (NN43001-313). For more information on configuring the SRG, see SRG50 Configuration Guide (NN40140-500). Uniform Dialing Plan Overview Figure 25 "UDP using location codes" (page 85) shows an example of a Uniform Dialing Plan (UDP) using location codes (Access Code + LOC + DN) configuration.
Dialing Plan configuration Call scenarios This section describes how calls interact between the SRG and main office with UDP. Calling from main office to the SRG and SRG PSTN, in Normal mode In this scenario, a telephone registered at the main office calls a telephone registered to the SRG, or makes a call over the PSTN through the SRG. Figure 26 "Calling from the main office to the SRG and SRG PSTN, in Normal Mode" (page 86) shows this scenario.
Dialing plan examples 87 Calling from the SRG to the main office, in Normal Mode In this scenario, a telephone registered at the SRG calls an SRG IP Phone and a main office IP Phone registered to the main office. The WAN is up. SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the main office (Normal Mode). Figure 27 "SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the main office" (page 88)shows this scenario.
Dialing Plan configuration Figure 27 SRG analog phone calls an SRG IP Phone and a main office IP Phone registered to the main office Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Dialing plan examples 89 Calling in Local Mode In this scenario, the IP Phones at the SRG are in Local Mode because the WAN is down. The SRG IP telephones are reregistered to the SRG and call forward BUID is inactive on these telephones. These IP Phones are registered at the SRG, and call forward BUID is inactive on these telephones. The inset shows a main office call to SRG telephones. The user must dial the SRG DN for the IP telephone (6002 instead of 3002).
Dialing Plan configuration Figure 28 SRG analog phone calls an IP Phone and a main office IP Phone registered to the SRG 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). Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Dialing plan examples 91 To configure the main office: • Configure the ESN Control Block for UDP in LD 86. > LD 86 REQ NEW CUST 0 FEAT ESN AC1 16 • Configure Digit Manipulation (DGT) in LD 86. > LD 86 REQ NEW FEAT DGT DMI 6 DEL 3 • Configure the UDP Location Code (LOC) in LD 90. > LD 90 REQ NEW FEAT NET TRAN AC1 TYPE LOC LOC 504 FLEN 7 RLI 12 LDN 0 • Configure the UDP HLOC in LD 90. FEAT NET TRAN AC1 TYPE HLOC HLOC 501 DMI 6 • Configure the HLOC in the Customer Data Block in LD 15.
Dialing Plan configuration 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 To configure the NRS (H.323 Gatekeeper/SIP Redirect Server): • Create H.323/SIP endpoints: MO, BO. • Create Numbering Plan entries: — Choose type UDP-LOC. — Add 504 for endpoint BO. — Add 501 for endpoint MO. For information about configuring H.
Dialing plan examples 93 — Set LOC to 504. • Set the BUID on the IP Phones to + + . For more information on configuring the main office and NRS, see Branch Office Installation and Commissioning (NN43001-314) and IP Peer Networking Installation and Commissioning (NN43001-313). For more information on configuring the SRG, see SRG50 Configuration Guide (NN40140-500). Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.
Dialing Plan configuration Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Bandwidth Management Contents This section contains information on the following topics: • "Introduction" (page 95) • "Codec negotiation" (page 95) • "Interoperability between CS 1000 and SRG" (page 101) • "Adaptive Network Bandwidth Management" (page 110) • "Tandem Bandwidth Management overview" (page 129) • "Dialing Plan Overview" (page 130) • "Network using Uniform Dialing Plan" (page 132) • "Network using Coordinated Dialing Plan" (page 154) Introduction CS 1000 supports Bandwidth Ma
Bandwidth Management IP Peer Networking supports the per-call selection of codec standards, based on the type of call (interzone or intrazone). IP Peer Networking supports the following codecs (with supported payload sizes in parentheses, with the default value in bold): • G.711 A/mu-law (10 ms, 20 ms, and 30 ms) • G.729 A (10 ms, 20 ms, 30 ms, 40 ms, and 50 ms) • G.729 AB (10 ms, 20 ms, 30 ms, 40 ms, and 50 ms) • G.723.
Codec negotiation 97 SRG 50 does not support G.723 codec. ATTENTION 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. 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.
Bandwidth Management call is not known until both call endpoints have negotiated which codec to use. The bandwidth used for calculating the usage of a Virtual Trunk call is determined by the preferred codec of the device that connects to the Virtual Trunk. If the device is an IP Phone, the bandwidth calculations use the preferred codec of the IP Phone, based on the codec policy defined for the zones involved (that is, Best Bandwidth or Best Quality).
Codec negotiation 99 that one node is Master and the other node is Slave. The outcome of the Master/Slave negotiation is not known in advance; it is a random result. One node could be Master then Slave (or vice versa) during the same call. Algorithm details following manner: The H.323 Master/Slave algorithm operates in the • The Master node uses its own codec list as the preferred one and finds a common codec in the far end’s list.
Bandwidth Management The following three cases of codec negotiation are supported: • The calling user agent sends an SDP offer with its codec list in the INVITE message with a sendrecv attribute. In this case, the called user agent selects one codec and sends the selected codec in an SDP answer. The SDP answer is included in the 200 OK message (which is the response to the INVITE) with the sendrecv attribute. This is the preferred method of operation.
Configuring Bandwidth Management parameters G. 729 AB G. 729 AB G. 729 AB G. 729 AB G. 729 AB G. 729 AB G. 723.1 G. 723.1 G. 723.1 G.729 A G. 729 AB G. 723.1 101 SRG 50 does not support G.723 codec. 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.
Bandwidth Management 2. Branch office (MG 1000B and SRG) Call Servers must be configured with the same VPNI as that of the main office Call Server with which they register. 3. Nortel recommends that all the endpoints on a Call Server (IP Phones and Voice Gateway Media Cards) be configured with the same Zone number. 4. Virtual Trunks must be configured with a different Zone number than the endpoints.
Configuring Bandwidth Management parameters 103 Select the zone on the Zones web page (see Figure 30 "Zones web" (page 105)) and click VGW and IP phone codec profile. Select an existing codec or configure a new one in the VGW and IP phone codec profile section, shown in Figure 29 "Configuring a codec" (page 103). See IP Peer Networking Installation and Commissioning (NN43001-313) for full instructions on configuring a codec.
Bandwidth Management — Intrazone Preferred Strategy = Best Quality (BQ) — Intrazone Bandwidth = default (1000000) — Interzone Preferred Strategy = Best Bandwidth (BB) — Interzone Bandwidth = maximum bandwidth usage allowed between peer Call Servers • Call Server zones that will be used for Virtual Trunks with the following properties: — Intrazone Preferred Strategy = Best Quality (BQ) — Intrazone Bandwidth = default (1000000) — Interzone Preferred Strategy = Best Quality (BQ) — Interzone Bandwidth = d
Configuring Bandwidth Management parameters 105 Figure 30 Zones web Configuration using LD 117 A new Bandwidth Management zone is configured in LD 117 using the NEW ZONE command. An existing zone can be modified using the CHG ZONE command. LD 117 Configure a new or existing Bandwidth Management zone.
Bandwidth Management Description Command — shared = shared DSP channels (default) — private = private DSP channels In CS 1000 Release 5.0, the zones that were described with BMG designator stay with BMG one, all the other zones are provided with MO designator. It is possible to update ZoneIntent using CHG ZONE command. Maintenance commands Maintenance commands can be run from Element Manager or LD 117.
Configuring Bandwidth Management parameters 107 Figure 31 Maintenance Commands for Zones web page 3 Do one of the following: • To display intrazone statistics: 1. Select Print Interzone Statistics (PRT INTERZONE) from the Action drop-down list. 2. Select a zone from the Zone Number drop-down list, by doing of the following: • • Select ALL to print statistics for all zones. • Select a specific zone number to display statistics for a specific zone. To display interzone statistics: 1.
Bandwidth Management The Maintenance Commands for Zones web page reopens, displaying the statistics for the specified zone or zones. A blank field indicates that statistic is either not available or not applicable to that zone. Figure 32 "Element Manager intrazone statistics" (page 108) shows an example of intrazone statistics.Figure 33 "Element Manager interzone statistics" (page 108) shows an example of interzone statistics.
Configuring Bandwidth Management parameters 109 —End— 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. ATTENTION Do not use the PRT ZONE command — it has been replaced by the PRT INTRAZONE and PRT INTERZONE commands. LD 117 Print zone statistics.
Bandwidth Management Description Command • Type= PRIVATE/SHARED • Strategy = BB/BQ • ZoneIntent = MO/VTRK Adaptive Network Bandwidth Management CS 1000 Release 4.5 supports the Adaptive Network Bandwidth Management feature. Description The Adaptive Network Bandwidth Management feature enhances the performance of Voice over Internet Protocol (VoIP) networks based on real-time interaction.
Adaptive Network Bandwidth Management 111 period. When the degradation is removed or the performance of the network improves, the allowable bandwidth returns to provisioned levels and the Call Server gradually starts allowing new calls. Essentially, Adaptive Network Bandwidth Management provides a fallback to PSTN on QoS degradation for new calls. As a result, bandwidth is managed and quality measured between all the zones across the entire network, and when necessary corrective action is taken.
Bandwidth Management Figure 34 Call Progress with Adaptive Network Bandwidth Management Zone bandwidth management and Adaptive Network Bandwidth Management Using Element Manager or the Command Line Interface (CLI), previously configured zones (except Zone 0) can have the Adaptive Network Bandwidth Management feature turned on or off. Once turned on, alarm threshold levels and the QoS coefficients can be adjusted from the default values.
Adaptive Network Bandwidth Management 113 When a call is made from a zone with Adaptive Network Bandwidth Management enabled, to a third party gateway, which has no zone, then the zone of the Virtual Trunk (VTRK) is used and appears in the zone table. Figure 35 "Adaptive Network Bandwidth Management graph" (page 113) shows an example of the bandwidth changes.
Bandwidth Management Multiple Appearance Directory Numbers (MADN) can exist on different zones. Calls to an MADN are handled the same as other IP Phone calls, and are subject to the same bandwidth limitations. New SNMP alarms are provided to monitor the system. When the bandwidth limit between zones is reduced below configured levels, an alarm is raised. A Warning alarm and an Unacceptable alarm, each corresponding to a drop below a configured threshold, are used.
Adaptive Network Bandwidth Management Figure 36 Effect of the default CQos Coefficient Figure 37 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.
Bandwidth Management The Call Admission Control (CAC) Validity Time Interval (CACVT) is used to control the length of time that records from a Call Server are saved in the Bandwidth Management table. If there have not been any calls between two Call Servers within the configured time, the Call Server is removed from the table.
Adaptive Network Bandwidth Management • 117 Adaptive Network Bandwidth Management parameters are configured on the main office only and must not be configured at the branch offices. Configuring Adaptive Network Bandwidth Management The following is a summary of the tasks necessary to configure Adaptive Network Bandwidth Management in the network. 1. Enable the Call Admission Control (CAC) package. 2. Configure CAC in Element Manager or LD 117: a. Configure the VPNI on the main office and branch offices.
Bandwidth Management The zone must exist before it can be configured for Adaptive Network Bandwidth Management. See IP Peer Networking Installation and Commissioning (NN43001-313) for instruction on how to create and configure basic properties of the zone. To configure the Adaptive Network Bandwidth Management feature, select a zone on the Zones web page. See Figure 30 "Zones web" (page 105) and click Adaptive Network Bandwidth Management and CAC.
Adaptive Network Bandwidth Management Table 9 Adaptive Network Bandwidth Management and CAC fields Field Title Field Definition LD 117 equivalents Enable Call Admission Control Feature (CAC) Control the CAC feature for the zone ENL ZCAC • Enable (check box selected) • disable (clear the check box) DIS ZCAC QoS Response Time Increase (ZQRT) Bandwidth limit increment, as a percentage of the QoS factor for the zone CHG ZQRT QoS Response Time Interval (ZQRTI) Time (in minutes) between bandwidth l
Bandwidth Management Command Description Configure the zone-to-zone record validity time interval, where: • Zone = 1-255 • Interval = 1-(48)-255 CHG CD Change the Cd coefficient in the formula that determines how quickly an alarm reduces the Sliding Maximum bandwidth for the identified zone, where: • Zone = 1-255 • Cd = Cd coefficient = 1-(50)-100 CHG CPL Change the Cpl coefficient in the formula that determines how quickly an alarm reduces the Sliding Maximum bandwi
Adaptive Network Bandwidth Management Command 121 Description CHG ZONE [ ] Change the parameters of an existing zone, where: • zoneNumber = 1-255 • intraZoneBandwidth = 1000000 (Mbit/s) • intraZoneStrategy = intrazone preferred strategy — Best Quality = BQ — Best Bandwidth = BB • interZoneBandwidth = 1000000 (Mbit/s) • interZoneStrategy = intrazone preferred strategy — B
Bandwidth Management Command Description Change the QoS Response Time Interval while alarms are not coming, in order to increase the Sliding Maximum for the identified zone, where: • Zone = 1-255 • Interval = interval in minutes = 1-(5)-120 CHG ZQUAT Change the QoS Unacceptable Alarm Threshold value for the identified zone, where: • Zone = 1-255 • Thres = threshold value = 1-(75)-99 When the zone-to-zone QoS value drops below the threshold value, the alarm is presented.
Adaptive Network Bandwidth Management 123 Description Command • zoneNumber = 1-255 • intraZoneBandwidth = 1000000 (Mbit/s) • intraZoneStrategy = BQ (Best Quality) • interZoneBandwidth = 1000000 (Mbit/s) • interZoneStrategy = intrazone preferred strategy — Best Quality = BQ — Best Bandwidth = BB • zoneIntent = type of zone, where: — MO = Main Office zone — BMG = Branch Media Gateway (branch office) zone — VTRK = Virtual Trunk zone • zoneResourceType = resource intrazone preferred strategy —
Bandwidth Management 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 30 "Zones web" (page 105). To view the intrazone or interzone statistics, use Procedure 7 "Printing intrazone and interzone statistics for a zone" (page 106). To display the CAC parameters, follow the steps in Procedure 8 "Displaying CAC parameters for one or more zones" (page 124).
Adaptive Network Bandwidth Management Figure 39 Element Manager CAC parameters —End— Maintenance using LD 117 The same information can be displayed using commands in LD 117.
Bandwidth Management Command Description Print intrazone statistics for the identified zones, where: • zone = ALL or 1-255 The output of this command displays the following information: • Zone • State = ENL/DIS • Type = PRIVATE/SHARED • Strategy = BB/BQ • MO/VTRK/BMG = zoneIntent • Bandwidth = Kbps • Usage = Kbps • Peak = % Figure 40 "Sample output for PRT INTRAZONE command" (page 128) shows an example of the output for this command.
Adaptive Network Bandwidth Management Command Description • Strategy = BB/BQ • MO/VTRK/BMG = zoneIntent • QoS factor = % • Bandwidth configured = Kbps • Sliding max = Kbps • Usage = Kbps • Peak = % • Call = Cph • Alarm = Aph The report rows are grouped as: • First row = summary bandwidth usage per near zone • Next rows = bandwidth usage per near (VPNI- Zone) and far (VPNI - Zone) Figure 41 "Sample output for PRT INTERZONE command" (page 129) shows an example of the output for this c
Bandwidth Management Command Description • ZQRTI = 10-120 • ZQUAT = 1-99 • ZQWAT =1-99 • CACVT = 1-255 Sample outputs for PRT commands Figure 40 "Sample output for PRT INTRAZONE command" (page 128) shows an example of the output of the PRT INTRAZONE command. Figure 41 "Sample output for PRT INTERZONE command" (page 129) shows an example of the output of the PRT INTERZONE command.
Tandem Bandwidth Management overview 129 Figure 41 Sample output for PRT INTERZONE command Tandem Bandwidth Management overview In order for the main office to correctly keep track of all the bandwidth being used to and from a branch office the call must be tandemed through the main office. When calls are tandemed through the main office only the signaling is tandemed, the actual voice bandwidth travels directly between the source and destination.
Bandwidth Management Bandwidth utilization for the branch office is tracked at the main office and can be displayed in LD 117 using the PRT INTERZONE command. In order to provide the correct bandwidth utilization to the main office Call Server, when a branch office is calling another node in the network, the calls must be tandemed through the main office Call Server in both the inbound and outbound direction.
Dialing Plan Overview Figure 42 A call between two branch offices tandems through the main office Figure 43 "General legend" (page 132) shows a general legend for the figures in the following section. Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Bandwidth Management Figure 43 General legend Network using Uniform Dialing Plan The following section provides general network configuration for a network using UDP only. Figure 44 "Scenario 1: UDP throughout the network" (page 133) 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.
Network using Uniform Dialing Plan 133 In a typical network, a full region uses a single Home Location Code (HLOC). However, it is also possible, where the number of users requires it, to have two or more codes, although using one for the main office and one for each branch office is unlikely at best.
Bandwidth Management Region Call progress steps Configuration detail and call progress during call setup 1 1 All branch offices are provisioned at the NRS to route all outbound calls (from the branch office) through the main office. (NRS tandem configuration). 1 2 Main office sends all UDP calls to destinations that are not its own branch office to the NRS with unchanged dialled digits.
Network using Uniform Dialing Plan 135 Figure 45 Call flow for Scenario 1 - local call 1. The branch office user dials 6-395-3456. The system transmits 395-3456 to the NRS. The NRS checks its provisioning, and determines that all calls are to be sent to the main office; it directs the call to the main office. 2. The branch office sends the call to 395-3456 to the main office. 3. The main office determines that this is LOC 39534, to another branch office, with gateway routing prefix 552.
Bandwidth Management Figure 46 Call flow for Scenario 1 - local call 1. The branch office user dials 6-395-3456. The system transmits 395-3456 to the NRS. The NRS checks its provisioning, and determines that all calls are to be sent to the main office; it directs the call to the main office. 2. The branch office sends the call to 395-3456 to the main office. 3. The main office determines that this is LOC 39534 to another branch office, with gateway routing prefix 552.
Network using Uniform Dialing Plan 137 Figure 47 Call flow for Scenario 1- local call 1. The branch office user dials 6-395-3456. The system transmits 399-3456 to the branch office user dials 6-399-3456. NRS. The NRS checks its provisioning, and determines that all calls are to be sent to the main office; it directs the call to the main office. 2. The branch office sends the call to 399-3456 to the main office. 3. The main office determines that this is to another branch office, with office prefix 552.
Bandwidth Management Every branch office HLOC is shared with the main office Figure 48 "Call to a remote branch office on the originator side " (page 138)shows the first half of the call setup (the originator side is side A). In this example, the branch office and the main office share the same HLOC. Figure 49 "Call to remote branch office on the destination side" (page 139)shows the second half of the call (the terminating side is side B).
Network using Uniform Dialing Plan 139 Figure 49 Call to remote branch office on the destination side 1. Main office B determines that this is to LOC 44434, which is a local branch office with prefix 225. The system transmits 225-444-3456 to the NRS. The NRS checks its provisioning, and determines that this call goes to branch office B1. 2. The main office sends the call to 225-444-3456 to the branch office.
Bandwidth Management Figure 50 Call to remote branch office on the originator side 1. The branch office user dials 6-444-3456. The system transmits 444-3456 to the NRS. The NRS checks its provisioning, and determines that all calls are to be sent to the main office; it directs the call to the main office. 2. The branch office sends the call to 444-3456 to the main office. 3. The main office determines that this is to another main office. The system transmits 444-3456 to the NRS.
Network using Uniform Dialing Plan 141 Figure 51 Call to remote branch office on destination side 1. Main office B determines that this LOC plus digits is to a local branch office with prefix 225. (If sharing this LOC with another branch office, the extended LOC is 44434.) The system transmits 225-444-3456 to the NRS. The NRS checks its provisioning, and determines that this call goes to branch office B1. 2. The main office sends the call to 225-444-3456 to the branch office.
Bandwidth Management Figure 52 Call to remote branch office on the originator side 1. The branch office user dials 6-444-3456. The system transmits 444-3456 to the NRS. The NRS checks its provisioning, and determines that all calls are to be sent to the main office; it directs the call to the main office. 2. The branch office sends the call to 444-3456 to the main office. 3. The main office determines that this is to another main office. The system transmits 444-3456 to the NRS.
Network using Uniform Dialing Plan 143 Figure 53 Call to remote branch office on destination side 1. Main office B determines that LOC 444 is to a local branch office with prefix 225. The system transmits 225-444-3456 to the NRS. The NRS checks its provisioning, and determines that this call goes to branch office B1. 2. The main office sends the call to 225-444-3456 to the branch office. The branch office deletes the prefix, discovers the call is to its HLOC, deletes the HLOC, and rings set 3456.
Bandwidth Management which provides service for the branch office using the LOC. See Step 3. 4 Provision the NRS to send all calls to a LOC with a gateway routing prefix to the branch office directly. Using the gateway routing prefix and the Type of Number of SPN, the entries can be differentiated from the normal LOC easily. See Step 4. 5 Provision the main office with the DGT table DMI to insert the prefixes and set the Type of Number correctly.
Network using Uniform Dialing Plan 145 Figure 54 Provisioning example Procedure 9 Provisioning Tandem Bandwidth Management Step Action 1 Enter the main office Gateway endpoint identifier in the Tandem Endpoint field for each branch office GW configured on the NRS. This provides tandeming for outbound calls from a branch office through its main office. Figure 55 "Tandem endpoint configuration in Element Manager" (page 146) shows the tandem endpoint configuration in Element Manager.
Bandwidth Management Figure 55 Tandem endpoint configuration in Element Manager 2 Plan the gateway routing prefixes. At least one prefix is needed per branch office, although any branch offices that have a prefix for ESA 911 calls does not necessarily require another. (These prefixes will be SPN - Special Number - entries if you are using ESA 911. In the example these are LOC codes because network 911 is not being used.
Network using Uniform Dialing Plan 147 Table 12 "Main office B DMI and RLI provisioning for calls in branch office B" (page 147) lists main office B DMI and RLI provisioning.
Bandwidth Management 7 Provision the main office and branch office with a home location code (HLOC) or multiple codes to terminate all calls that should terminate on this system. Table 14 " Main office B and branch office B" (page 148) lists main office and branch office HLOC provisioning.
Network using Uniform Dialing Plan 149 Table 16 "Main office A LOC provisioning for LOC to remote main office systems " (page 149) lists main office A LOC provisioning for LOC to the remote office.
Bandwidth Management Figure 56 UDP between main offices and CDP inside the main office region Table 18 "Provisioning details for this case" (page 150) lists provisioning details for a mixed network. Table 18 Provisioning details for this case Region Provisioning detail 1, 2, 3 CDP used for all calls within the region. 1, 2, 3 UDP used for region to region calls. 1, 2, 3 Prefixes for branch offices for regular calls not required. May still have prefixes for E-911 calls, if required.
Network using Uniform Dialing Plan 151 Region Provisioning detail 1 Main office sends all UDP calls to destinations that are its own branch office to the NRS after deleting the HLOC and converting to CDP. 2,3 Similar configuration, as above, applies to regions 2 and 3. Call between two local branch offices Figure 57 "Local call dials CDP" (page 151) shows the NRS Configuration web page in Element Manager. Figure 57 Local call dials CDP 1. The branch office user dials 3456 (CDP).
Bandwidth Management Abnormal case - calls originating using UDP, but terminating using CDP Figure 58 Call flow for Scenario 2 - local call dial UDP 1. The branch office user dials 6-395-3456. The system transmits 395-3456 to the NRS. The NRS checks its provisioning, and determines that all calls are to be sent to the main office; it directs the call to the main office. 2. The branch office sends the call to 395-3456 to the main office. 3.
Network using Uniform Dialing Plan 153 Figure 59 Call flow for Scenario 2 - local call to remote branch office (originator side) 1. The branch office user dials 6-444-3456. The system transmits 444-3456 to the NRS. The NRS checks its provisioning, and determines that all calls are to be sent to the main office; it directs the call to the main office. 2. The branch office sends the call to 444-3456 to the main office. The main office determines that this is to another main office.
Bandwidth Management Figure 60 Call to remote branch office on the destination side 1. The main office B deletes the HLOC, and determines that this is to a local branch office. The system transmits 3456 to the NRS. The NRS checks its provisioning, and determines that for this CDP region this call goes to branch office B1. 2. The main office sends the call to 3456 to the branch office. The branch office rings set 3456.
Network using Coordinated Dialing Plan 155 Figure 61 Full CDP network Table 19 "Provisioning details for this case" (page 155) lists the provisioning details for a full CDP network. Table 19 Provisioning details for this case Region Provisioning detail 1, 2, 3 CDP used for all calls within the region. 1, 2, 3 CDP used for region to region calls. 1, 2, 3 All CDP numbers must be sufficiently long to allow unique termination of the calls.
Bandwidth Management Region Provisioning detail 1 All branch offices are provisioned at the NRS to route all calls through the main office. 1 Main office sends all CDP calls to destinations that are not its own branch office to the NRS with unchanged dialled digits. 1 Main office sends all CDP calls to destinations that are its own branch office to the NRS with a specific gateway prefix in front of the dialled digits. 1 All branch offices delete the prefix and terminate the calls.
Network using Coordinated Dialing Plan 157 to the NRS. The NRS checks its provisioning, and determines that all calls to prefix 552 are to be sent to branch office A2; it directs the call to the branch office. 4. The main office sends the call to 552-43456 to the branch office. The branch office deletes the prefix and LSC 4, and rings set 3456.
Bandwidth Management Figure 64 Call flow for Scenario 3- calls to remote branch office (destination side) 1. Main office B determines that this is to a local branch office with prefix 225. The system transmits 225-53456 to the NRS. The NRS checks its provisioning, and determines that this call goes to branch office B1. 2. The main office sends the call to 225-53456 to the branch office. The branch office deletes the prefix and LSC, and rings set 3456.
Alternative Call Routing for Network Bandwidth Management Contents This section contains information on the following topics: • "Description" (page 159) • "Operating parameters" (page 174) • "Feature interactions" (page 175) • "Feature packaging" (page 176) • "Feature implementation using Command Line Interface" (page 176) • "Feature implementation using Element Manager" (page 178) • "Diagnostics" (page 180) • "Maintenance" (page 184) • "Feature operation" (page 187) Description Alter
Alternative Call Routing for Network Bandwidth Management Event number 1 pertains to the originally dialed call that experiences low bandwidth or unacceptable QoS conditions. Event number 2 pertains to the alternately routed call. Figure 65 Example of Alternative Call Routing for NBWM in operation There are multiple choices of alternate routes provided for the overflowed calls.
Description 161 This feature enables alternate routing to occur for branch office users registered to the main office, when they place interzone, station-to-station calls to main office stations or branch office stations.
Alternative Call Routing for Network Bandwidth Management How Alternative Call Routing for NBWM works When a user dials a station-to-station call between two different zones (that is, the calling and called telephones are not located in the same geographic area) and the bandwidth limit has been reached, then the Alternative Call Routing feature is invoked. The following steps occur in Alternative Call Routing scenarios. Call from branch office telephone in Normal Mode 1.
Description 163 For SRG, the main office manipulates the digits in the call into a format appropriate for routing from the SRG on PSTN/MCDN trunks. The steering code allows the call to be translated and referenced to a Route List Index from which the system chooses the alternate route. The digit manipulation capability of CDP allows digits (such as the ALTPrefix) to be deleted and it can insert digits so the resulting number is appropriate for the alternate route choice selected (PSTN or MCDN).
Alternative Call Routing for Network Bandwidth Management Examples of Alternative Call Routing for NBWM in operation A call from a branch office telephone to a main office telephone Figure 66 "Call between a branch office telephone in Normal Mode and a main office telephone" (page 164) shows an example of an alternately routed call between 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.
Description • 165 Provision the ALTPrefix as a Steering Code at the main office. Build a Route List Index (RLI) so these calls go to the virtual trunk or configure the Vacant Number Routing feature to do the same. At the branch office: • Provision the ALTPrefix as a steering code. Build a Route List Index and DMI associated with this steering code that alternately routes these calls to the PSTN with the correct digits. At the NRS: • Create a CDP entry for the ALTPrefix in the branch office gateway.
Alternative Call Routing for Network Bandwidth Management Figure 67 Digits dialed and outpulsed with Alternative Call Routing for NBWM 1. IP Phone User B in the BO2 zone dials IP Phone A in the main office zone (DN 5262) (action labeled 1 in Figure 66 "Call between a branch office telephone in Normal Mode and a main office telephone" (page 164)). 2. The main office Call Server determines there is insufficient bandwidth between the two zones. 3.
Description 167 6. The branch office receives the call and recognizes the first part of the number as a Steering Code. The call is steered to an RLI. The DMI manipulates the number into a PSTN number and the branch office outpulses the digits to the Central Office (CO) serving the branch office. (This may be the same CO as the one serving the main office.
Alternative Call Routing for Network Bandwidth Management Figure 68 Call between a main office telephone and a branch office telephone Telephone A calls Telephone B (the user dials DN 3121). In this example, the call alternately routes to the PSTN. (The PSTN telephone number of Telephone B is 613-966-3121.) Configuration required Configure the following: At the main office: • Use one of the dialing plan software packages to process the call, such as CDP or NARS.
Description 169 Sequence of events in the call The information that follows refers to Figure 68 "Call between a main office telephone and a branch office telephone" (page 168) and Figure 69 "Digits dialed and outpulsed with Alternative Call Routing for NBWM" (page 169). Figure 69 Digits dialed and outpulsed with Alternative Call Routing for NBWM 1.
Alternative Call Routing for Network Bandwidth Management • insert 966 (in order to compose the DID number of the destination telephone which is 9663121, a local call.) 6. The call terminates on IP Phone B from the PSTN in the BO2 zone (action labeled 3 in Figure 68 "Call between a main office telephone and a branch office telephone" (page 168)).
Description 171 Figure 70 Call between a branch office telephone and another branch office telephone Telephone B in the BO2 zone calls Telephone F in the BO1 zone (the user dials 6020). In this example, the call alternately routes to the PSTN. (The PSTN telephone number of Telephone F is 506-348-6020.) Configuration required Configure the following: At the main office: • Use one of the dialing plan software packages to process the call, such as CDP or NARS. • Provision an ALTPrefix for the BO2 zone.
Alternative Call Routing for Network Bandwidth Management Sequence of events in the call The information that follows refers to Figure 70 "Call between a branch office telephone and another branch office telephone" (page 171) and Figure 71 "Digits dialed and outpulsed with Alternative Call Routing for NBWM" (page 172). Figure 71 Digits dialed and outpulsed with Alternative Call Routing for NBWM 1.
Description 173 3. The Call Server inserts the ALTPrefix configured for the BO2 zone prior to IP Phone F’s telephone number, dialed by the user. Example: ALTPrefix assigned is 222. The dialed number becomes 222 6020. 4. The call is routed to the virtual trunk by CDP or VNR. The virtual trunk sends a request to the NRS for address resolution. The digit string sent to the NRS contains the ALTPrefix. The NRS returns the IP address of the branch office endpoint to the virtual trunk. 5.
Alternative Call Routing for Network Bandwidth Management The configuration and provisioning for the All Calls mode is exactly the same as the regular Alternative Call Routing for NBWM feature except that the Alternate Routing for All Calls option is selected in overlay 117 or Element Manager. Operating parameters This feature applies to all CS 1000 systems. This feature applies to station-to-station, interzone calls.
Feature interactions 175 This feature does not apply to virtual trunk calls. It only applies to station-to-station calls, and routes them over the PSTN or MCDN network. Virtual Trunk calls already have this feature and can be alternately routed using traditional methods (such as NARS), which is outside the scope of this feature. Alternative Call Routing for NBWM does not apply to users who are registered in local mode to the Branch Office.
Alternative Call Routing for Network Bandwidth Management Network Routing Service (NRS) Both the main office and branch office must be registered on the Nortel NRS for tandem routing to work for main office to branch office tandeming. Trunk Route Optimization (TRO) Disable Trunk Route Optimization between the branch office (or SRG) and the main office in order to allow the tandeming required for the feature to work.
Feature implementation using Command Line Interface 177 LD 117 Description Command CHG ZALT [] Change ALTPrefix number for zone, where: Input zone number (0 to 255). Configure the branch office zone using LD 117 at the main office. A digit string, of up to 7 digits, added to the start of the dialed number, if the call will not be routed through the WAN (due to lack of bandwidth, poor QoS, or feature is configured for all calls).
Alternative Call Routing for Network Bandwidth Management Feature implementation using Element Manager Zone configuration Use Element Manager to configure the specific zone properties. 1. Access the Zones web page to select Alternate Routing for Calls between IP Stations. 2. Access the Alternate Routing for Calls between IP Stations web page to configure the feature. Accessing the Zones web page Procedure 10 Accessing the Zones web page Step Action 1 From the navigator, click IP Network > Zones.
Feature implementation using Element Manager 179 A web page appears that displays the configuration parameters related to the Alternative Call Routing for NBWM feature. See Figure 73 "Access the Alternate Routing for Calls between IP Stations " (page 179). Figure 73 Access the Alternate Routing for Calls between IP Stations The Zone Number for the zone you selected in step 3 is displayed.
Alternative Call Routing for Network Bandwidth Management Diagnostics Command Line Interface diagnostics LD 117 Obtain status for a particular zone Command Description STAT ZALT Display Alternative Call Routing Status, where: zone = bandwidth zone If you do not enter a value in the zone field, you obtain a printout of the status of all configured zones.
Diagnostics 181 • enable/disable status of the All Calls option Procedure 11 Printing zone ALTPrefix Step Action 1 From the navigator, click System > Maintenance. The Maintenance web page appears. See Figure 74 "Maintenance web page" (page 181). Figure 74 Maintenance web page 2 Click Select by Functionality. The Select by Functionality web page appears. See Figure 75 " Select by Functionality" (page 182). Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.
Alternative Call Routing for Network Bandwidth Management Figure 75 Select by Functionality 3 Click Zone diagnostics. The Maintenance Commands for Zones web page appears. See Figure 76 "Maintenance Commands for Zones " (page 182). You can also access this page if you click on Zones, as you see in Figure 72 "Zones" (page 178). Figure 76 Maintenance Commands for Zones Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.
Diagnostics 183 4 Select Print Zone Alternate Prefix Information (PRT ZALT) from the drop-down list beside Action. See Figure 77 Maintenance Commands for Zones Action list 5 Select ALL or a zone number from the Zone Number drop-down list. 6 Click Submit. —End— Show the status of the Alternative Call Routing for NBWM feature The Show Status functionality displays the enable/disable status of the Alternative Call Routing for NBWM feature.
Alternative Call Routing for Network Bandwidth Management 4 Select Show Alternate Routing Status (STAT ZALT) from the drop-down list beside Action. See Figure 78 "Show Alternative Routing Status" (page 184). Figure 78 Show Alternative Routing Status 5 Select ALL or a zone number from the Zone Number drop-down list. 6 Click Submit to enter the data The display updates with the data associated with that zone.
Maintenance 185 Description Command ENL ZBR [ALL] [LOC][ESA][TIM][ALT] Enable features for the branch office zone. If you do not input features, then all are enabled. DIS ZBR [ALL] [LOC][ESA][TIM][ALT] Disable features for the branch office zone. If you do not input features, then all are disabled. The system responds with ok, if operation is successful.
Alternative Call Routing for Network Bandwidth Management 2 Click Select by Functionality. The Select by Functionality web page appears. See Figure 75 " Select by Functionality" (page 182). 3 Click Zone diagnostics. The Maintenance Commands for Zones web page appears . 4 Select Enable a Zone’s Branch Office Behavior from the drop-down list beside Action. See Figure 79 "Enable branch office behavior for a zone" (page 186).
Feature operation 187 Procedure 14 Suppress Alternative Call Routing for NBWM alarms Step Action 1 Click IP Network > Zones. The Zones web page appears. 2 Click beside the Zone, or click the Zone you are programming, to expand the choices under it. 3 Enter digits in Alarm Suppression Time Period (ZAST). See Figure 80 "Alarm Suppression Time Period (ZAST)" (page 187). 4 Click Submit to enter the data.
Alternative Call Routing for Network Bandwidth Management Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Emergency Services configuration Contents This section contains the following topics: • "Overview" (page 189) • "Emergency Services Access" (page 190) • "Emergency Services for Virtual Office" (page 200) • "On-Site Notification" (page 201) • "Configuring the NRS for ESA SPN" (page 201) • "Testing the ESDN number" (page 202) • "Configuring ESA using Element Manager" (page 202) • "Emergency Service using Special Numbers (SPN)" (page 202) Overview Support for access to emergency services b
Emergency Services configuration Nortel recommends using the Emergency Services Access (ESA) feature. This is the preferred method in North America, the Caribbean and Latin America (CALA), and in those countries that are members of the European Union (EU). ESA provides specific features and capabilities required by legislation in these jurisdictions.
Emergency Services Access 191 The Automatic Number Identification (ANI) data sent to the Public Safety Answering Point (PSAP) identifies the location of the caller. In some constituencies, legislation requires one ANI (DID) per fixed area, so the physical location of the emergency can be approximated based on the telephone number delivered to the PSAP. The ESA feature has a comprehensive scheme that can be used to convert an extension into an appropriate DID.
Emergency Services configuration Configuring ESA for the branch office For ESA, the main office Call Server forwards the call to the branch office for termination. Calls are redirected over a Virtual Trunk using the NRS. The NRS routes the calls using a special number, referred to in this section as the ESA Special Number.
Emergency Services Access 11 Configure ESA at the branch office. 12 Configure the branch office zone on the branch office. 193 The branch office zone is required for bandwidth management but does not require ESA parameters. 13 Configure the ESN SPN on the branch office. 14 Configure the NRS for the ESA Special Number used. 15 Test ESDN using an analog (500/2500-type) telephone located at the branch office. 16 Test ESDN using an SRG IP Phone in Normal Mode and in Local Mode.
Emergency Services configuration Reregistering to minimally configured branch office A branch user in Local Mode but who is not physically at the branch can get incorrect emergency service handling.
Emergency Services Access 195 Determining the dialing plan for ESA calls In many jurisdictions of the United States and Canada, the emergency number must be “911”. The call processor cannot have a DN that conflicts with these digits, but since “9” is often used for NARS AC2 (the local call Access Code), this is not usually a problem. ESA for international deployment must support the standard emergency number 112 and any emergency numbers in use prior to the EU directive.
Emergency Services configuration The Virtual Trunk must be configured to enable emergency calls originating from SRG IP Phones registered at the main office to reach the branch office. 3 Configure ESN. ESA uses a route number rather than ESN route list index. However, ESN is required at the branch office. 4 Configure Emergency Services Access (ESA) in LD 24. LD 24 Configure Emergency Services Access Prompt Response Description REQ: NEW CHG Add new data, or change existing data.
Emergency Services Access 197 provides CLID Verification (CLIDVER) reports that determine how an emergency call is routed, without actually routing the call. Use LD 20 to generate a CLIDVER report. Table 20 LD 20 Generate a CLIDVER report Prompt Response Description REQ: PRT Print TYPE CLIDVER CLID Verification SORTBY (DN) TN The output/report is sorted based on this flag. If the response is DN, the overlay prompts the user to enter the DN, and the output is sorted by the DN.
Emergency Services configuration For more information about CLIDVER reports, see Emergency Services Access Fundamentals (NN43001-613). 6 Configure the branch office zone on the main office. a. Configure the branch office zone ESA dialing information in LD 117. LD 117 Configure branch office zone ESA route Description Command CHG ZESA Defines the ESA parameters for the branch office zone, where: • Zone = Zone number for the branch office.
Emergency Services Access 199 LD 86 Prompt Response Description REQ NEW CHG Add, Change CUST xx Customer number as defined in LD 15 FEAT DGT Digit Manipulation … … … DMI 1- 999 Digit Manipulation Table numbers. ATTENTION Do not use Digit Manipulation Table 0, as it results in the incorrect call termination treatment. b. Configure the system to trap the ESDN within the AC1 and AC2 translation tables to reprocess the ESDN locally.
Emergency Services configuration LD 90 Prompt Response Description REQ NEW CHG Add, Change CUST xx Customer number as defined in LD 15 FEAT NET Network translation tables TRAN aaa TYPE SPN - SPN 911 AC + ESDN is recognized as an Emergency Service Access call. 112 Use the number configured for ESDN. xxx Route List Index. - RLI Use Route List Index configured in LD 86.
Configuring the NRS for ESA SPN 201 The use of the terms Normal Mode and Local Mode apply to SRG branch user only. Emergency Services while logged in to Virtual Office The E911 Virtual Office feature recognizes when a user dials an ESDN and it forces the Virtual Office IP Phone to log out of Normal Mode (into Local Mode) in order to place the emergency call directly from the branch office location to the PSAP.
Emergency Services configuration Testing the ESDN number Use Procedure 17 "Testing ESDN using an SRG telephone" (page 202) to test the ESDN number from any telephone in the branch office. Procedure 17 Testing ESDN using an SRG telephone Step Action 1 For IP Phones: a. Dial the ESDN on an SRG IP Phone in Local Mode. The calls must go out on the emergency trunk(s) in the branch office. b. Dial the ESDN on an SRG IP Phone in Normal Mode.
Emergency Service using Special Numbers (SPN) 203 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. Access to Emergency Service using SPN should be configured in the following circumstances: • When the Emergency Service number at the branch office is different from that at the main office.
Emergency Services configuration Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Enhanced UNIStim Firmware Download Contents This section contains the following topics: • "Description" (page 205) • "Firmware upgrade" (page 206) Description This section applies to the main office and the following IP Phones: • IP Phone 2001 • IP Phone 2002 • IP Phone 2004 • IP Phone 2007 • IP Audio Conference Phone 2033 • IP Phone 1110 • IP Phone 1120E • IP Phone 1140E • IP Phone 1150E It does not apply to the IP Softphone 2050 and WLAN 2210/2211/2212/6120/6140.
Enhanced UNIStim Firmware Download For CS 1000 Release 4.5 and later, if the required firmware file does not exist on the SRG 50, or the version of the file is incorrect, the SRG 50 initiates an FTP session to the TPS for the IP Phone to retrieve the required file. The SRG 50 upgrades the IP Phone and redirects the IP Phone back to the CS 1000. For SRG 50 Release 2.
Firmware upgrade Procedure 18 Upgrading firmware Step Action 1 At the Main office, upgrade IP Phone firmware on the Signaling Server. For instructions, see Signaling Server Installation and Commissioning (NN43001-312). 2 Issue the CLI command umsUpgradeAll at the main office. IP Phones at the Main office and branch office are upgraded as necessary. —End— Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.
Enhanced UNIStim Firmware Download Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Appendix A Media Redirection Scenarios In addition to basic call scenarios, Network Bandwidth Management also supports the following media redirection scenarios: • Scenario 1: Codec switches correctly during media redirection. See Table 21 "Codec switches correctly during media redirection" (page 210). • Scenario 2: Call transfer works correctly with IP Phones: — Scenario 2.1: Call Transfer from an SRG IP Phone in Normal Mode to main office IP Phone.
Appendix A Media Redirection Scenarios Table 21 Codec switches correctly during media redirection Event Result 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. The external caller hears music and announcements with a G.729 codec. Bandwidth usage in the main office indicates the call is an interzone call. The external caller is connected to an Automatic Call Distribution (ACD) agent with a G.
Appendix A Media Redirection Scenarios 211 Event Result 2 The main office IP Phone initiates a call transfer to an SRG IP Phone registered to the main office. The SRG TDM telephone is put on hold. A speech path is established between the main office IP Phone and the SRG IP Phone registered to the main office. The zone table indicates interzone bandwidth usage. 3 The Call Transfer key on the main office IP Phone is pressed to complete the call transfer.
Appendix A Media Redirection Scenarios Table 25 Conference call between main office and branch office, initiated by main office IP Phone Event Result 1 An SRG TDM telephone calls a main office IP Phone. A speech path is established between the SRG TDM telephone and the main office IP Phone. The zone table indicates interzone bandwidth usage. 2 The main office IP Phone initiates a conference call to an SRG IP Phone registered to the main office. The SRG TDM telephone is put on hold.
List of terms Branch office An SRG that is remote from the main office. The SRG provides telephony services using the main office servers (for Normal Mode) or local system services when the SRG loses IP communication with the main office (Local Mode). CDP Coordinated Dialing Plan. Under the recommended Coordinated Dialing Plan, the Branch User ID can be an extension (for example, 4567). For more information about CDP, see Dialing Plans Reference (NN43001-283).
List of terms special manner, or who wants to be notified when a telephone user makes an emergency call. It would also appeal to a customer who wishes to have ESA calls answered on-site, on the business premises, rather than being forwarded to the Public Services Answering Point (PSAP). See Emergency Services Access Fundamentals (NN43001-613) for complete information. Gatekeeper The Gatekeeper is a separate application on an IP network that directs IP traffic to all the systems on the network.
List of terms 215 Local Mode The SRG is in Local Mode when: • The IP Phones are first installed and not yet reregistered with the main office • The SRG cannot communicate with the main office and the IP Phones are reregistered with the SRG • A user deliberately puts the IP Phone in the Test Local Mode condition. Main office The CS 1000 system that has been programmed to accept redirection of the SRG IP Phones and provide call service for the SRG in Normal Mode. NCS Network Connection Service.
List of terms • packet classification • DiffServ • IP fragmentation • traffic shaping • use of the platform’s queuing mechanisms routing The process of selecting the correct path for packets transmitted between IP networks by using software-based algorithms. Each packet is processed by the algorithm to determine its destination. SRG 50 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.
List of terms 217 ZDP Zone Digit Prefix. This is the number that the main office appends to a local 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. Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Index B Emergency Services for Virtual Office 200 ESN Access Codes 27 Branch office 213 Branch office dialing plan 27 G C Capacity 26 CDP 213 CLID composition 47 CLID verification 47 Configuring ESA for branch office 192 Configuring ESA using Element Manager 202 Configuring the dialing plan using Element Manager 63 Configuring the NRS for ESA SPN 201 Configuring zone parameters using Element Manager 36 Coordinated Dialing Plan 65 Gatekeeper 214 Gateway 214 H H.
Index 219 NRS 215 O Off-net dialing plan 45 On-net dialing plans 43 Optional features to enhance SRG functionality 18 SRG PSTN to an SRG telephone (DID call) 45 SRG user call to an SRG PSTN 45 Supported IP Phones 16 Survivable Remote Gateway 11, 11 T Testing PSTN access 64 Testing the ESDN number 202 Testing the phone in Local Mode 23 Time of Day 24 TPS 216 P PSTN 215 Q QoS 215 U R UDP 216 Uniform Dialing Plan 85 Routing 216 Routing calls 45 Routing ESA calls 191 V S Signaling Server 15, 15 SIP
Index Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 NN43001-307 02.02 Standard Release 5.0 3 December 2007 Copyright © 2005-2007, Nortel Networks .
Nortel Communication Server 1000 Main Office Configuration Guide for SRG 50 Copyright © 2005-2007, Nortel Networks All Rights Reserved. Publication: NN43001-307 Document status: Standard Document version: 02.02 Document date: 3 December 2007 To provide feedback or report a problem in this document, go to www.nortel.com/documentfeedback. Sourced in Canada. The information in this document is subject to change without notice.
