NN43001-307 06.01 Commissioning Main Office Config SRG50

8/8/2019 NN43001-307 06.01 Commissioning Main Office Config SRG50

http://slidepdf.com/reader/full/nn43001-307-0601-commissioning-main-office-config-srg50 1/158

Nortel Communication Server 1000

Main Office Configuration Guidefor SRG 50Release: 7.0Document Revision: 06.01

www.nortel.com

NN43001-307.



Nortel Communication Server 1000

Release: 7.0

Publication: NN43001-307

Document release date: 4 June 2010

Copyright © 2005-2010 Nortel Networks. All Rights Reserved.

While the information in this document is believed to be accurate and reliable, except as otherwise expressly

agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF

ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document aresubject to change without notice.

Nortel, Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks.

All other trademarks are the property of their respective owners.



3.

Contents

New in this release 7Features 7

Bandwidth Management 7

RLI and DMI enhancement 7

Other 7

Revision history 7Subject 8

Intended audiences 8

Conventions 9

Terminology 9

Related information 9

NTPs 9

Online 10

CD-ROM 10

Description 11

Contents 11Survivable Remote Gateway 11

Main office hardware description 15

Main office requirements 19

Optional features to enhance SRG functionality 20

Normal Mode and Local Mode overview 20

Normal Mode 21

Bandwidth Management 27

Capacity 27

Branch office dialing plan 27

Branch office and SRG 50 terminology 28

Limitations 29

Setting up the main office 31Contents 31

Introduction 31

SRG information required by the main office 32

Main office information required by the SRG 33

Zone parameters 36

Nortel Communication Server 1000Main Office Configuration Guide for SRG 50

NN43001-307 06.01 4 June 2010


http://slidepdf.com/reader/full/page36





































4

Branch office IP Phone configuration at the main office 40

SIP IP Trunks configuration at the main office 41

IP Phone registration and redirection 45Contents 45

IP Phone registration 45IP Phone initial SRG registration 46

IP Phone redirection to the main office 48

CS 1000 redirection configuration 48

IP Phone redirection failures 49

Normal Mode 50

Call Forward 51

External Attendant Support 51

Normal Mode call scenarios 52

Reverting from Normal Mode to Local Mode 53

Local Mode 53

Local Mode indication 54

Local Mode features 55

Dialing Plan configuration 59Contents 59

Overview 59

On-net dialing plan 59

Off-net dialing plan 61

Dialing Plan Overview 61

Dialing plan examples 63

Routing calls 91

SRG PSTN to an SRG telephone (DID call) 91Network using Uniform Dialing Plan 91

Network using Coordinated Dialing Plan 113

Emergency Services configuration 119Contents 119

Overview 119

Emergency Services Access 120

Emergency Services for Virtual Office 131

On-Site Notification 131

Configuring the NRS for ESA SPN 131

Testing the ESDN number 132Configuring ESA using Element Manager 133

Emergency Service using Special Numbers (SPN) 133

Enhanced UNIStim Firmware Download 135Contents 135

Description 135

Firmware upgrade 139


NN43001-307 06.01 4 June 2010




















































6


NN43001-307 06.01 4 June 2010




7.

New in this release

The following sections detail what’s new in CS 1000 Main Office Configuration for SRG 50 (NN43001-307) for Communication Server 1000Release 7.0.

FeaturesThis document contains the following new features for CommunicationServer 1000 Release 7.0.

Bandwidth ManagementCommunication Server 1000 Release 7.0 provides an increase in thenumber of bandwidth management zones. The range of allowablebandwidth management zone values is increased from 0–255 to 0–8000.

RLI and DMI enhancementFor Communication Server Release 7.0, the range of allowable Route ListIndex (RLI) and Digit Manipulation Index (DMI) values is increased from0–999 to 0–1999.

OtherThere are no other changes.

Revision history

June 2010 Standard 06.01. This document is up-issued to supportCS 1000 Release 7.0.

August 2009 Standard 05.01. This document is up-issued to supportCS 1000 Release 6.0 for SRG 50 Release 5.0.

May 2009 Standard 04.01. This document is up-issued to support

CS 1000 Release 6.0.

July 2008 Standard 03.02. This document is up-issued toreflect changes in technical content. Sections relatingto Bandwidth Management have been moved toConverging the Data Network with VoIP Fundamentals (NN43001-260).


NN43001-307 06.01 4 June 2010




8 New in this release

December 2007 Standard 03.01. This document is up-issued to support

CS 1000 Release 5.5 for SRG 50 Release 3.0.

November 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 themain 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. This document is up-issued to supportCommunication Server 1000 Release 5.0. Thisdocument contains information previously containedin the following legacy document, now retired:(553-3001-207). This document is up-issued to include

updated information due to CR Q01587820.

October 2006 Standard 3.00. This document is up-issued to support

SRG 50 Release 2.0 for CS 1000 Release 4.5.

January 2006 Standard 2.00. This document is up-issued for CR

Q01202736, with information on reconfiguring Call

Server alarm notification levels if necessary when

configuring Adaptive Network Bandwidth Management.

August 2005 Standard 1.00. This document is a new document to

support Communication Server 1000 Release 4.5.

SubjectThis document CS 1000 Main Office Configuration for SRG 50 (NN43001-307) describes the software for CS 1000 Release 6.0.Information in this document complements information found in documentsin the Communication Server 1000 documentation suite. For informationabout how to configure the SRG 50, see SRG 50 Configuration Guide (NN40140-500) at www.nortel.com. Select Support & Training > TechnicalDocumentation > Communication Servers > BCM.

Intended audiencesThis document is intended for individuals responsible for configuring

the main office for Survivable Remote Gateway for organizations usingCS 1000 systems.


NN43001-307 06.01 4 June 2010


http://www.nortel.com/



Related information 9

ConventionsTerminology

In this document, the following systems are referred to generically assystem:

• Communication Server 1000E (CS 1000E)• Communication Server 1000M (CS 1000M)

• Meridian 1

Related informationThis section lists information sources that relate to this document.

NTPsThe following NTPs are referenced in this document:

• Converging the Data Network with VoIP Fundamentals (NN43001-260)• Electronic Switched Network Reference—Signaling and Transmission

(NN43001-280)

• Dialing Plans Reference (NN43001-283)

• Signaling Server IP Line Applications Fundamentals (NN43001-125)

• IP Peer Networking Installation and Commissioning (NN43001-313)

• Branch Office Installation and Commissioning (NN43001-314)

• Software Input Output Reference-Administration (NN43001-611)

• Emergency Service Access Fundamentals (NN43001-613)• Element Manager System Reference - Administration (NN43001-632)

• ISDN Primary Rate Interface Fundamentals (NN43001-569)

• Basic Network Feature Fundamentals (NN43001-579)

• Communication Server 1000M and Meridian 1 Large System Planning and Engineering (NN43021-220)

• Communication Server 1000E Planning and Engineering (NN43041-220)

• Software Input Output Reference - Maintenance (NN43001-711)

• SRG 50 Configuration Guide (NN40140-500)

• Nortel Business Communications Manager 5.0 Configuration — Devices (NN40170-500)


NN43001-307 06.01 4 June 2010




10 New in this release

OnlineTo access Nortel documentation online, click the Technical Documentationlink under Support & Training on the Nortel home page:

www.nortel.com

CD-ROMTo obtain Nortel documentation on CD-ROM, contact your Nortel customerrepresentative.


NN43001-307 06.01 4 June 2010


http://www.nortel.com/



11.

Description

ContentsThis section contains information about the following topics:

• “Survivable Remote Gateway” (page 11)

• “Main office hardware description” (page 15)

• “Main office requirements” (page 19)

• “Optional features to enhance SRG functionality” (page 20)

• “Normal Mode and Local Mode overview” (page 20)

• “Capacity” (page 27)

• “Branch office dialing plan” (page 27)

• “Branch office and SRG 50 terminology” (page 28)

Survivable Remote GatewayThe Survivable Remote Gateway (SRG) extends the desktop featureand user interface of the CS 1000 to remote IP branch office usersand gives them full access to the same applications as the main site.CallPilot, Contact Center Management Server (CCMS), and other centralapplications are shared by remote users to deliver state-of-the-art featuresand functionality to small remote offices.

SRG 50 Release 5.0 provides the following:

• supports Secure File Transfer Protocol (SFTP) for firmware downloadsfrom the main office

• supports treatment of IP client error codes for firmware download (andpossible firmware version incompatibilities)


NN43001-307 06.01 4 June 2010












12 Description

SRG 50 Release 5.0 is released as an integrated, but key-coded featurecomponent on the Nortel Business Communications Manager 5.0hardware platforms. SRG 50 Release 5.0 is supported on the main BCM50 unit and BCM 50b (BRI) unit. (It is not supported on BCM 50a or BCM50e systems.)

SRG 50 Release 5.0 supports CS 1000 Release 5.0, 5.5, and 6.0.


• extends support for the IP Phone 1110, IP Phone 1210, IP Phone1220, IP Phone 1230, WLAN Handset 6120, and WLAN Handset 6140

See “Supported IP Phones” (page 17) for a complete list of supportedIP Phones.

• evolves the SIP trunk to support a standard SIP Trunk interface

• supports On-site Notification


• extends the supported number of survivable IP users from 32 to 80

• extends support for the IP Phone 1120E, IP Phone 1140E, IP AudioConference Phone 2033, and WLAN 2212

See “Supported IP Phones” (page 17) for a complete list of supportedIP Phones.

• supports H.323 and SIP Trunking to the CS 1000 main office

• supports analog devices, such as fax machines and terminals but are

limited in number and limited to basic access

The software supported at the branch office is shown in the following table.

Table 1Supported software at the branch office

IP branch officesolution

SurvivableIP users

CS 1000 Call Serversupport

Feature description

SRG 200/400Release 1.5

up to 90 Succession 3.0CS 1000 Release 4.0CS 1000 Release 4.5

CS 1000 Release 5.0CS 1000 Release 5.5CS 1000 Release 6.0

VoIP and Application Gateway

Local Mode = Basic telephony

features

Provides H.323 trunking.

For more information, see Main

Office Configuration Guide for SRG

200/400 Release 1.5 (NN43001-308).


NN43001-307 06.01 4 June 2010






Survivable Remote Gateway 13


SurvivableIP users


Feature description

SRG 50Release 2.0

up to 80 CS 1000 Release 4.0CS 1000 Release 4.5CS 1000 Release 5.0CS 1000 Release 5.5CS 1000 Release 6.0


Local Mode = Basic telephonyfeatures

Extends IP Phone support and

survivable IP users from 32 to 80.

Provides H.323 and SIP trunking.

(Note: CS 1000 Release 4.0 only

supports H.323.)

For more information, see CS 1000

Main Office Configuration Guide for

SRG 50 (553-3001-207).

SRG 50Release 3.0

up to 80 CS 1000 Release 4.0CS 1000 Release 4.5CS 1000 Release 5.0CS 1000 Release 5.5CS 1000 Release 6.0


Local Mode = Basic telephony

features

Extends IP Phone support to include

the IP Phone 1110.

Supports On Site Notification for

E-911 calls.


(Note: CS 1000 Release 4.0 only

supports H.323.)

CS 1000 Release 5.5 (and later)

extends support to include IP Phone

1210, IP Phone 1220, IP Phone

1230, WLAN Handset 6120, and

WLAN Handset 6140.

SRG 50

Release 5.0

up to 80 CS 1000 Release 5.0

CS 1000 Release 5.5CS 1000 Release 6.0

Feature parity with SRG 50 Release

3.0


CS 1000 Release 6.0 supports

enhanced firmware download using

Secure FTP (SFTP)


NN43001-307 06.01 4 June 2010




14 Description


SurvivableIP users


Feature description

MG 1000B up to 400 Succession 3.0CS 1000 Release 4.0CS 1000 Release 4.5CS 1000 Release 5.0CS 1000 Release 5.5CS 1000 Release 6.0

100% CS 1000 feature and

application redundancy in survivable

mode. Designed and positioned forlarger IP branch offices.


Survivable MG1000E

up to 22500 CS 1000 Release 5.0CS 1000 Release 5.5CS 1000 Release 6.0

100% CS 1000 feature and

application redundancy in survivable

mode. Designed and positioned for

larger IP branch offices.

The SRG is implemented on a BCM 50/50b platform and is connectedto a CS 1000 at the main office through Virtual Trunks over a reliable IPWAN access facility. This configuration allows the call processing for theIP Phones at the SRG site to be centralized at the main office. The CallServer at the main office provides the call processing for the IP Phonesregistered to both the main office and branch offices. The SRG providescall processing functionality to phones in local mode and local analogdevices. The SRG supports business continuity and call failover throughdigital and analog trunk access to the local Public Switched TelephoneNetwork (PSTN).

In order for devices in the CS 1000 network to access analog devices at

the SRG or to access the PSTN at the SRG, virtual trunks are used overthe LAN/WAN.

If the main office fails to function, or if there is a network/WAN outage, theSRG automatically switches to Local mode and provides basic telephonyservice to the phones located at the branch office. This enables the IPPhones to survive the outage between the branch office and the mainoffice.

To ensure proper operation of the SRG solution it must be configured tosupport a common dialing plan with the CS 1000 main office. Any otherconfiguration is not guaranteed to work reliably. Since the Call Serverand the SRG handle dialing slightly differently, ensure that any settingsyou use for the main office that need to interact with the SRG, can beaccommodated by the SRG call processing.

Figure 1 "SRG network" (page 15) shows the networking among the mainoffice, SRG, and IP Phones.


NN43001-307 06.01 4 June 2010






Figure 1SRG network

Main office hardware descriptionThe 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 encompassall CS 1000 system types.

The diagrams throughout this documentation show a CS 1000E mainoffice. All of the systems appearing in the list perform identical main officefunctions as far as the SRG is concerned. For information about the SRG,see SRG 50 Configuration Guide (NN40140-500).


NN43001-307 06.01 4 June 2010




16 Description

Signaling ServerThe following Signaling Servers are available for CS 1000 Release 6.0:

• Common Processor Pentium Mobile (CP PM)

• Common Processor Pentium Mobile (CP PM) Co-resident

• HP-DL320-G4

• IBM-X306m

• IBM-X3350

• Dell R300

The Signaling Server is required at the main office only. It provides thefollowing functions:

• Terminal Proxy Server (TPS)

The TPS provides a connection from the IP Phones to the Call Serverand a connection from a Virtual Trunk to the Call Server.

• H.323 Gateway (Virtual Trunk)

• SIP Gateway (Virtual Trunk)

• CS 1000 Element Manager Web Server and Network Routing Service(NRS)

• NRS, consisting of:

— SIP Proxy and SIP Registrar

— H.323 Gatekeeper

— Network Connection Service (NCS)

• Personal Directory

A second Signaling Server can be used to provide redundancy in the caseof a failure in the primary Signaling Server at the main office.

A similar function to the TPS is used at the SRG when the IP Phones arein Local mode.

The Signaling Server supports en bloc signaling which is standard on theSignaling Server.

For more information about the Signaling Server, see Signaling Server IP Line Applications Fundamentals (NN43001-125). For moreinformation about H.323 and SIP, see IP Peer Networking Installation and Commissioning (NN43001-313).


NN43001-307 06.01 4 June 2010





Network Routing ServiceThe Network Routing Service (NRS) application provides network-basedrouting, combining the following into a single application:

• 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 areused for Voice packet traffic alone.

• NRS Database—stores the central dialing plan in XML format forthe H.323 Gatekeeper, and the SIP Redirect Server. The H.323Gatekeeper and the SIP Redirect Server accesses this commonendpoint and gateway database.

• Network Connect Server (NCS)—used only for Media GatewayController (MGC) based MG 1000B, SRG, Geographic Redundancy,

and Network-wide Virtual Office solutions. The NCS allows the LineTPS (LTPS) to query the NRS.

• NRS Manager web interface—the NRS provides its own web interfaceto configure the H.323 Gatekeeper, SIP Redirect Server, and the NCS.

The NRS application provides routing services to H.323 devices andSIP-compliant devices. The H.323 Gatekeeper can be configured tosupport H.323 routing services, while the SIP Redirect Server NRS can beconfigured to support SIP routing services. The H.323 Gatekeeper and theSIP Redirect Server NRS can reside on the same Signaling Server.

Each system in an IP Peer network must register to the NRS. The NRSsoftware identifies the IP addresses of systems based on the network-widenumbering plan. NRS registration eliminates the need for manualconfiguration of IP addresses and numbering plan information at everysite.

When configuring the NRS it is necessary to enable the NCS. Ensure thatthe check box “Network Connection Server enabled” is checked in theNRS configuration window of CS 1000 Element Manager.

For information about configuring the NRS, see IP Peer Networking Installation and Commissioning (NN43001-313).

Supported IP PhonesThe following table shows the supported IP Phones for each softwarerelease of SRG 5.0.


NN43001-307 06.01 4 June 2010




18 Description

Table 2IP Phone support for SRG 50

IP Phone Release 2.0 Release 3.0 Release 5.0

IP Phone 2001 Supported Supported SupportedIP Phone 2002 Supported Supported Supported

IP Phone 2004 Supported Supported Supported

IP Phone 2007 Supported Supported Supported

IP Audio ConferencePhone 2033

Supported Supported Supported

IP Phone 1210 Notsupported

Supported Supported


Supported Supported


Supported Supported

IP Softphone 2050 Supported Supported Supported


Supported Supported

IP Phone 1120E Supported Supported Supported

IP Phone 1140E Supported Supported Supported

IP Phone 1150E Notsupported

Notsupported

Notsupported

Mobile Voice Client (MVC)2050


Analog (500/2500-type)telephones


WLAN Handset 2210 Supported Supported Supported



WLAN Handset 6120 Notsupported

Supported Supported

WLAN Handset 6140 Not

supported

Supported Supported

Throughout this document, the IP Phones are referred to collectively asIP Phones.


NN43001-307 06.01 4 June 2010




Main office requirements 19

Main office requirementsThe branch office running SRG Release 5.0 requires the following at themain office:

• CS 1000 hardware, running CS 1000 Release 5.0, CS 1000 Release

5.5, or CS 1000 Release 6.0.• Configure at least one of the following packages for IP Peer

Networking:

— H.323 Virtual Trunk (H323_VTRK) package 399

— SIP Gateway and Converged Desktop Package (SIP) package 406

• The main office must have a software Service Level of 2 or higher towork with the branch office.

• Ensure that you have ordered enough IP user and Virtual Trunklicenses at the main office to support the SRG 50 or the capacity ofyour branch office.

The two different IP user licenses at the main office are:

— Basic IP License for the IP Phone 2001, IP Audio ConferencePhone 2033, IP Phone 1110, and IP Phone 1210

— IP User License for the IP Phone 2002, IP Phone 2004, IP Phone2007, IP Phone 1220, IP Phone 1230, IP Phone 1120E, IP Phone1140E, IP Softphone 2050, Mobile Voice Client (MVC) 2050,WLAN Handset 2210, WLAN Handset 2211, WLAN Handset 2212,WLAN Handset 6120, and WLAN Handset 6140

The main office requires the following software packages to supportthe specified Basic Network features. See Basic Network Feature Fundamentals (NN43001-579) for more information about these features.

• Network Call Back Queuing (MCBQ) package 38. This package isrequired for SRG IP Phones to invoke any queuing feature or ringbackwhen free.

• Network Speed Call (NSC) package 39. This package is required forSRG IP Phones to invoke the Network Speed Call feature.

The main office requires the following software packages to support thespecified ISDN Primary Rate Interface features. See ISDN Primary Rate

Interface Fundamentals (NN43001-569) for more information about thesefeatures.

• Network Attendant Service (NAS) package 159. This package isrequired for analog (500/2500-type) telephones in the branch office to


NN43001-307 06.01 4 June 2010




20 Description

access attendant services when the attendant is configured on themain office.

• Network Message Services (NMS) package 175. This package isrequired for analog (500/2500-type) telephones in the branch office to

share the voice mail system in the main office. For any configurationsusing centralized CallPilot on the main office with one or more branchoffices in separate time zones, the NMS package is required at themain office for the branch IP Phones.

Optional features to enhance SRG functionality

• Network Alternate Route Selection (NARS) package 58. See Basic Network Feature Fundamentals (NN43001-579).

• Emergency Services Access (ESA) package 329. This package isoptional; it is required only to receive 911/ESA features in NorthAmerican and some Caribbean and Latin American (CALA) markets.See Emergency Service Access Fundamentals (NN43001-613).

• Virtual Office (VIRTUAL_OFFICE) package 382. This package isoptional; it is required only for Virtual Office functionality.

• Network Signaling (NSIG) package 37. This package is optional forSRG 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.

• Geographic Redundancy support. (For example, enhanced survivabilityusing the Alternate NRS for SIP trunking.)

• Calling Number/Calling Name information on incoming calls an digitaland analog PSTN trunks.

• Music on Hold (MOH) for calls received over a PSTN trunk.

• Modem support.

For software and hardware requirements for SRG, see SRG 50 Configuration Guide (NN40140-500).

Normal Mode and Local Mode overviewNormal Mode and Local Mode overview provides a description of thefollowing sections:

• “Normal Mode” (page 21)

• “Local Mode” (page 22)


NN43001-307 06.01 4 June 2010







• “Survivability” (page 24)

• “Recovery to Normal Mode” (page 25)

• “Local Mode operation” (page 25)

• “Virtual Trunks” (page 26)

Normal ModeIP Phones that are physically located at the SRG but are registered withthe main office and are operating in Normal Mode. In Normal Mode,the main office provides centralized call processing to all applicationstransparently to all IP Phones at the branch office. All IP Phones at thebranch office, in Normal Mode, are registered to the main office TPS andare controlled by the Call Server at the main office.

Users of the SRG IP Phones receive the features, applications, key

layout, and tones of the main office Call Server. This provides feature andapplication transparency between the branch office and the main office.

During Normal Mode, the IP Phones are controlled by the main office CallServer as shown in Figure 2 "Normal Mode operation" (page 21). Themain office uses the zone data associated with the IP Phone to define thenumbering plan for geographically local calls and for emergency servicescalls. For example, a local IP Phone call to the PSTN (local to the SRG)is actually handled at the main office and the call is routed back to thelocal SRG using VoIP trunks. The case is similar while handling calls foremergency services. Therefore, the SRG acts as VoIP–PSTN gateway

during Normal Mode.

Figure 2Normal Mode operation


NN43001-307 06.01 4 June 2010









22 Description

For more information, see “Normal Mode” (page 50).

Local ModeUsers at the branch office may be in Local Mode for different reasons:

1. IP Phone has just booted up.

2. IP Phone cannot communicate to the main office because of a WANfailure or a failure of the main office components.

3. IP Phone can be in Test Local Mode.

ATTENTIONWhen a telephone or trunk in the main office calls an SRG IP Phone that hasswitched to Local Mode due to WAN failure, the call is treated according to themain office call redirection configuration (such as forwarding to voice mail orcontinuous ringback).

During Local Mode, the IP Phones are controlled by the SRG as shown inFigure 3 "Local Mode operation" (page 22). The IP Phones are in LocalMode when the WAN connectivity is lost or when the IP Phones fail toregister correctly with the main office Call Server. The SRG offers a limitedset of basic features to the IP Phones, which include access to the localPSTN, dialling emergency service numbers, and calling local extensions.

Figure 3Local Mode operation

In the event that the IP Phones at the branch office lose the connectionto the main office CS 1000 call server for any reason (WAN failure, mainoffice call server failure, main office Signaling Server failure), the SRG 50reverts to Local Mode automatically. Essentially, when VoIP connectivity


NN43001-307 06.01 4 June 2010







is lost, each IP Phone loses its Reliable UDP (RUDP) connection with themain office Terminal Proxy Server (TPS). The IP Phones at the branchoffice reboot and reregister to the SRG 50, placing them in Local Mode.

After this occurs, the IP Phones displays an indication on the display area

that the set is in Local Mode of operation. This display is configurable byinstallers to meet local language and usage norms.

In Local Mode, the IP users connected at the branch office are underthe control of the SRG 50 call services. As such, the normal mainoffice call server features are not available. The SRG 50 offers a basicfeature set when in Local Mode which allows IP Phones to continue tomake and receive calls internally within the branch office and over theprovisioned local PSTN interfaces. Basic services, such as transfer, lastnumber redial, and single key access through the PSTN to a centralizedvoice messaging system are supported. Local PSTN access and local

Emergency Services access is also supported. No local applications orBusiness Communication Manager (BCM) features are supported in LocalMode operation.

Analog devices continue to be under the control of the SRG 50 system. Itis the intent of Local Mode to provide continued access to the PSTN forcritical calls and emergency services.

In Local Mode, since the SRG 50 handles all call processing, callsbetween two IP phones at the SRG 50 are handled locally as a simplestation-to-station call. When an IP Phone initiates a local PSTN call, theSRG 50 routes the call to a trunk that is connected to the local PSTN.

Incoming DID calls are also handled by the SRG 50 and terminated onthe appropriate IP Phone.

In the event of a WAN failure, in Local Mode, the IP Phones do nothave access to the main office network over the VoIP trunks. If theappropriate alternate routes are configured, calls will be routed to the mainoffice or other branch offices using the available PSTN trunks. Similaralternate routes can be configured for incoming PSTN calls which must betandemed across the SRG. As another option, the incoming calls can bedirected to a Prime DN (which typically is an IP Phone maintained in LocalMode).

While in survival mode, the SRG 50 system continues to monitor for amain office CS 1000 heartbeat signal, and once detected, automaticallyredirects phones on an individual basis back to Normal Mode ofoperation. If a call is active, the SRG waits until the call is completedbefore redirecting the phones; calls in progress are not interrupted. Thisswitch-over occurs almost immediately once the SRG determines thatan individual phone can be redirected. This reinstates the CS 1000


NN43001-307 06.01 4 June 2010




24 Description

normal user interface and feature set for the IP Phone user, on a user byuser basis. In addition to waiting for call completion, if firmware is beingdownloaded to an IP Phone when the WAN comes up, the SRG waits untilthe firmware download is complete and then redirects the IP Phone.

The SRG 50 system implements the same interface used by the MG1000B system to interact with the main office CS 1000 system. This allowsthe main office to identify attached clients and the local PSTN as branchoffice entities, enabling proper operation of dial plans and E911 access.

In Local Mode, devices that are physically located at the branch office, thatare controlled by the local system and receive a basic telephony featureset, provide business continuity for the branch office during the WAN orsystem failure.

For more information, also see “Local Mode” (page 53).

For information about the features supported in Local Mode, see SRG 50 Configuration Guide (NN40140-500).

SurvivabilitySRG is specifically designed to provide automatic survivability againstWAN failure, main office Call Server failure, main office Signaling Serverfailure, and Gatekeeper failure.

SRG supports the Geographic Redundancy feature. For further informationabout Geographic Redundancy, see System Redundancy Fundamentals (NN43001-507).

In the event of a WAN failure, the SRG IP Phones lose communicationwith the main office. This causes the SRG IP Phones to reset and registerwith the SRG. The IP Phones then operate in Local Mode, providingbasic telephony services delivered by the local SRG system. For furtherinformation about services and features supported on the SRG, see SRG 50 Configuration Guide (NN40140-500).

If the main office Call Server fails and call processing services areprovided by an Alternate Call Server, the SRG IP Phones reset andreregister with the Alternate Call Server and receive call processing

services from it. If no Alternate Call Server is available, the SRG IPPhones go to Local Mode while the SRG attempts to find an Alternate CallServer by way of the NCS.

If the main office Signaling Server fails and an Alternate Signaling Serveris available, the SRG IP Phones reset and reregister with the SRG.The SRG will then query the NCS for the Alternate Signaling Server IPaddress. The SRG will redirect the IP Phone to the Alternate Signaling


NN43001-307 06.01 4 June 2010






Server and continue to receive call processing services from the mainoffice Call Server. If no Alternate Signaling Server is available, the SRG IPPhones reset and register with the SRG in Local Mode.

When an IP Phone at the SRG first boots up, the IP Phone attempts

to communicate with the SRG. After communication with the SRG isestablished, the SRG redirects the IP Phone to the main office. Whenthe SRG IP Phone attempts to register with the main office, the SRG firstqueries the Primary NCS for the main office Virtual Trunk node IP addressto redirect the IP Phone. If the Primary NCS is down or unreachable, theSRG queries the Alternate NRS (H.323 Gatekeeper/SIP Redirect Server),if one is specified. If it receives a positive response, the SRG IP Phone isredirected to the specified main office. Otherwise, if neither a Primary oran Alternate NRS (H.323 Gatekeeper/SIP Redirect Server) is available,the SRG IP Phone remains in Local Mode, and receives call processingservices from the SRG until communication can be reestablished.

SRG IP Phones in Normal Mode remain registered with the main office ifthe Primary NCS fails and no Alternate NCS is available. They can callany main office telephone or IP Phones in Normal Mode in other branchoffices. However, they cannot call any SRG analog (500/2500-type)telephones or any external numbers through the SRG trunks because anH.323 Gatekeeper/SIP proxy server, which could route call properly incase of an NRS failure, is not available.

Recovery to Normal ModeAfter communication is reestablished with the main office call server, all IPPhones at the branch office that are in Local Mode automatically redirect

and reregister to the main office and return to Normal Mode operation.IP Phones that were busy at the time communication was reestablishedcomplete the call in Local Mode, and then reregister with the main officeafter the call is complete.

Local Mode operationWhen an SRG IP Phone is in Local Mode, the user has full access tothe services configured at the SRG (analog devices or analog or digitaltrunks) and to other IP Phones registered to the SRG. In Local Mode,the IP Phones can make local calls to other IP Phones and other analog(500/2500-type) telephones at the branch office. They can also be used to

make outgoing PSTN calls and receive incoming calls as usual. SRG IPPhones can access the main office IP Phones or other branches by routingthrough the local PSTN.


NN43001-307 06.01 4 June 2010




26 Description

Testing the phone in Local ModeFrom Normal Mode, the branch user has the option of going to Local Modemanually using the Test Local Mode feature, or when the telephone ispower-cycled. The test can be performed by the user at any time anddoes not require a password. This test is invoked from any IP Phone at

the branch office.

Nortel recommends testing Local Mode operation after changing theprovisioning for a telephone on the SRG.

To ensure that users do not forget to resume Normal Mode operation, theSRG redirects the telephone to the main office to return the telephone toNormal mode. This occurs if the telephone remains registered to the SRGin Test Local Mode for ten minutes (default setting). Alternatively, the usercan press the Quit key on the phone to return to Normal Mode.

For further information about Local Mode functionality for SRG, see SRG 50 Configuration Guide (NN40140-500).

Virtual TrunksIn order for endpoints in the CS 1000 network to access endpoints in localmode at the SRG or to access the PSTN at the SRG, Virtual Trunks areused over the LAN/WAN.

Virtual Trunks are software components that provide the trunking featuresof the Meridian Customer-Defined Network (MCDN) feature set. Accessto PSTN digital or analog trunks at the branch office occurs through theMCDN Virtual Trunk.

Virtual Trunks are sometimes referred to as SIP or H.323 Virtual Trunks.In the SRG 50 Configuration Guide (NN40140-500) Virtual Trunks arereferred to as IP Trunks.

For more information about Virtual Trunks, see IP Peer Networking Installation and Commissioning (NN43001-313).

IP Phone callsWhen an IP Phone calls another IP Phone, each telephone receives theaddress of the other to exchange media directly between the telephones.

When in Normal Mode, an SRG IP Phone calling a main office IP Phonedoes not require any trunking to set up the call. However, LAN/WANbandwidth is used to provide a media path for the call. For moreinformation on Direct IP media path functionality, see IP Peer Networking Installation and Commissioning (NN43001-313).


NN43001-307 06.01 4 June 2010




Branch office dialing plan 27

Bandwidth ManagementFor information about Bandwidth Management, see Converging the Data Network with VoIP Fundamentals (NN43001-260).

CapacityEach CS 1000 main office can support up to 255 branch offices, which canbe made up of any combination SRG and MGC based MG 1000B. SRG 50Release 2.0 and later supports up to 80 survivable IP users. However,since all IP Phones register with the main office, the governing factor is themaximum number of IP Phones that can be supported at the main office.This means the total number of IP Phones in all offices can be no greaterthan the capacity of the main office. See one of the following documents todetermine the total number of phones your system can support:

• Communication Server 1000E Planning and Engineering (NN43041-220)

• Communication Server 1000M and Meridian 1 Large System Planning and Engineering (NN43021-220)

Virtual Trunks capacityThe SRG capacity to support a number of simultaneous calls depends onthe specific codec type used and the available bandwidth.

If both the intrazone and interzone codes are configured as Best Quality(G.711), the SRG supports up to 24 Virtual Trunks (H.323 or SIP),otherwise, only 15 G.729 Virtual Trunks (H.323 or SIP) are supported.

In Normal Mode, the codec selection used is controlled by specificprogramming of the CS 1000.

In Local Mode, if the WAN has failed, Virtual Trunks between the SRGand CS 1000 cannot be established. However, the SRG will continueto convert calls from IP terminals for communication through the PSTN.Nortel recommends you use G.711 codec.

Branch office dialing planSince IP Phone users can be located at a branch office equipped with anSRG, the routing of calls to the local gateway is important (especially when

toll charges apply to calls made from the central Call Server that controlsthe telephone). The administrator can configure digit manipulation throughzone attributes for IP Phones to select a main office or branch office thatprovides PSTN access local to the destination of the call.

Calls from the PSTN to users within the network can be routed with thevarious ESN numbering plan configurations.


NN43001-307 06.01 4 June 2010




28 Description

To access local PSTN resources, outgoing calls can be routed usingESN as well as zone parameters that enable digit insertion. The zoneparameters force calls made by an SRG user to be routed to the desiredlocal PSTN facilities.

ATTENTIONOutgoing calls can include local and, optionally, long distance calls.

Nortel recommends that the Branch User ID (BUID) be the same at thebranch office as the DN at the main office. A BUID has a maximum of 15digits. Under the recommended Coordinated Dialing Plan (CDP), the BUIDcan be an extension (for example, 4567). Under the Uniform Dialing Plan(UDP), the BUID is the user main office DN, the Location Code (LOC),plus the Access Code (for example, 6 343-5555). The main office DN mustbe an ESN compliant DN. See “ESN Access Codes” (page 28).

The SRG only supports only one dialing plan option at a time. CDP andUDP dialing plan options cannot be configured at the same time in thesame system.

For more information about dialing plans and configuration, see “DialingPlan configuration” (page 59).

ESN Access CodesESN data is configured with two Access Codes, called AC1 and AC2.AC1 normally applies to long distance calls, whether placed on or offthe customer’s private network (for example, dialing 6). AC2 normallyapplies to local calls (for example, 9). For more information, see

Electronic Switched Network Reference—Signaling and Transmission (NN43001-280).

Music on HoldFor SRG users in Normal Mode, the main office provides music to the userif Music on Hold is provisioned. The use of the G.729A/AB codec betweenthe main office and the branch office can impact the music quality.

ATTENTIONG.723 codec is not supported on SRG 50.

Branch office and SRG 50 terminologyTable 3 "Branch office and SRG 50 terminology" (page 29) listsconfiguration-related terms and contexts where branch office and SRG 50terminology differ.


NN43001-307 06.01 4 June 2010








Limitations 29

Table 3Branch office and SRG 50 terminology

Term or context Branch office SRG 50

dialing plan on-net/off-net dialing Private/Public network dialing

routing distant steering codes (DSC),Trunk steering codes (TSC), Localsteering codes (LSC)

call routing, destination codes, linepool access codes

Digit manipulation table dial-out digits (routing)

alternate routing

selection

Facility Restriction Level (FRL) scheduled call routing

Type of number CDP/UDP/TNDN CDP/UDP/no equivalent

Numbering Plan ID ISDN/Telephony(E.164), Private, Telephony(E.163), Telex, (F.69), Data(X.121), National Standard

Private

User ID BUID BUID

bandwidth management zone Zone ID

Trunks public exchange PSTN

virtual trunk IP trunk

access codes (SRG 50:destination codes)

7 = system trunk access

8 = Basic Alternate Route

Selection (BARS)/Network

Alternate Route Selection (NARS)

9 = public exchange access

7 = not assigned

8 = not assigned

9 = line pool A access code

Network Class of Service (NCOS)

telephone numbers(internal, not PSTN)

DN DN

LimitationsFor the SRG 50 Release 5.0 limitations, see Survivable Remote Gateway Release 5.0 Release Notes .


NN43001-307 06.01 4 June 2010




30 Description


NN43001-307 06.01 4 June 2010




31.

Setting up the main office

ContentsThis section contains the following topics:

• “Introduction” (page 31)

• “SRG information required by the main office” (page 32)

• “Main office information required by the SRG” (page 33)

• “Branch office IP Phone configuration at the main office” (page 40)

• “SIP IP Trunks configuration at the main office” (page 41)

IntroductionThis section describes the following information required to configure themain office:

• SRG information required by the main office

• Main office information required by the SRG

• Zone parameters

• IP Phone passwords and parameters

• Branch office IP Phone configuration

For more information on main office configuration, see IP Peer Networking Installation and Commissioning (NN43001-313).


NN43001-307 06.01 4 June 2010









32 Setting up the main office

SRG information required by the main officeThe main office administrator must gather information about the SRGsystem. The following information is required:

• an inventory of IP Phones that will be installed on the SRG so the

administrator knows what type of telephone to assign to each mainoffice terminal record

• information which allows the administrator to create an NCS (H.323Gatekeeper or SIP Redirect Server) entry for the SRG

• if using advanced routing, such as tandem dialing between systems,local PSTN number for the SRG and the internal SRG routing codesthat will allow the main office to connect to the SRG and to tandemover the SRG PSTN lines, is required

Use Table 4 "SRG information required for the main office configuration"(page 32) to record the information before setting up the SRG on the main

office server.

Table 4SRG information required for the main office configuration

SRG parameters Information about this system

SRG public IP address

H.323 ID (required for requests to NCS)

Each H.323 ID in the node should match SIP endpoint name

for this system in pure SIP environment.

List of types and number of IP Phones

Telephone types are hard-coded to the Terminal Numbers

(TN) and the main office. Therefore, install the same type of IP

Phones to the coordinating record on the SRG.

PSTN number to dial into the SRG (in local mode)

Destination codes (steering codes) to route the main office

calls to the SRG and out through the SRG PSTN lines

IP Ports that affect SRG traffic with the main office and have

been assigned firewall filters

For further information on port configuration, see Converging

the Data Network with VoIP Fundamentals (NN43001-260) or

SRG 50 Configuration Guide (NN40140-500).


NN43001-307 06.01 4 June 2010







Main office information required by the SRGThe main office administrator must supply numerous main office settingsto the SRG installer so that the SRG can be efficiently configured. Inaddition, the main office administrator needs to supply the followinginformation:

• a list of the terminal record numbers (TN)

• a list of BUID (Prime DN)

• if using advanced routing, such as tandem dialing between systems,main office routing (steering) codes, are required

Use Table 5 "Main office interoperation information" (page 33) to recordmain office information required by the SRG.

Table 5

Main office interoperation information

Main office components Information about this system

Main office IP network information:

Main office call server type S1000 (default)

Primary Network Connect Server IP address

Alternate Network Connect Server IP address

Network Connect Server port (The range is

0-65535.)

16500 (default)

Trunk/telephony preferred codecs and jitterbuffers listed in order of preference

NRS (H.323 Gatekeeper/SIP Redirect Server)requirements

Indicate if the SRG needs to manually assignports with firewall filters.

Heartbeat Protocol Port (The range is 1-65535.)

Used to determine whether the TPS identified

by the Network Connect Server is online. Also

used to poll the primary NCS and alternate

NCS.

16501 (default)

VoIP trunk access code

Specifies the access coded used by the SRG

when it invokes the CFAC feature on redirect

Test Local Mode timer (The range is 2-10minutes.)

10 minutes (default)


NN43001-307 06.01 4 June 2010






Table 5Main office interoperation information (cont’d.)


H.323 ID

Used as part of the ARQ exchange with theNetwork Connect Server.

Telephony programming:

DN length, DN (TN) range

Numbering Plan ID

This parameter is written to the DRAM of the IP

Phone on redirect.

Private (default)

Type of number

SRG 50 only supports CDP and UDP dialing

plans. Nortel recommends that the SRG useCDP.

The SRG supports only one dialing plan option

at a time. CDP and UDP dialing plan options

cannot be configured at the same time in the

same system.

This parameter is written to the DRAM of the IP

Phone on redirect.

Node IDWhen the SRG is down, the phones use S2

settings to register with the main office.

This parameter is written to the EEPROM of the

IP Phone along with the Branch User ID (BUID)

on redirect

Virtual Private Network ID (VPNI)

Zone ID and dialing string informationrequirements

Main office dial-up number (for PSTN calls to

the main office in Local Mode)

Main office access code length

Access code to reach the main office PSTN

through VoIP trunks


NN43001-307 06.01 4 June 2010







Zone dialing:

• ZDP appended to SRG IP Phone PSTNdialing strings to redirect the call to SRG

PSTN

• Any steering codes (destination codes) thatmust 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. If

the DCP access code is more than one digit,

the second digit number must also be used to

further define the DN range.

Main Office Terminal Number (MOTN)

This parameter is provisionable and mandatory

for an IP Phone to be redirected. It represents

the TN to be associated with the IP Phone in

the main office on redirect. SRG writes this data

to the DRAM of the set on redirect.

Branch User ID (BUID)

This parameter is provisionable and mandatory

for an IP Phone to be redirected. It represents

the dialable DN to be associated with the IP

Phone in the main office on redirect. SRG

writes this data to the DRAM of the set on

redirect.

Main Office TPS (MOTPS) IP address

This parameter is informational and is updated

by SRG on redirect. This is the TPS address

returned by the Network Connect Server on

successful ARQ.


NN43001-307 06.01 4 June 2010







Firmware Version

Current IP Phone firmware version

This parameter is informational and is updated

by the main office (in the DRAM of the terminal)

when a terminal is sent back to SRG for

firmware upgrade purposes. This specifies the

desired firmware version of the main office.

Is a VLAN configured on the network?

Zone parametersZone parameters must be configured at both the main office Call Serverand the SRG. The main office procedure is similar to an IP Peer Networkconfiguration with the branch office-specific configuration outlined in thischapter.

Zone parameters are defined at the main office in LD 117 and are appliedto IP Phones in LD 11.

Use Procedure 1 “Configuring ESN and SRG zones” (page 36) toconfigure ESN and SRG zones.

Procedure 1

Configuring ESN and SRG zonesATTENTIONBefore and after an upgrade, perform a data dump (using LD 43 EDD or throughElement Manager) on the Call Serve or on the MGC to back up existing data.

Step Action

1 Configure the Home Location Code (HLOC) and the VirtualPrivate Network Identifier (VPNI).

Table 6Configure 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

CUST Customer number


NN43001-307 06.01 4 June 2010





Zone parameters 37

0-99Range for Large Systems

… … …

CLIDYES

Allow Calling Line Identification option

-ENTRY xx CLID entry to be configured

--HLOC100-9999999

Home Location code (ESN) (3-7 digits)

ISDNYES

Integrated Services Digital Network

-VPNI(0)-16383

Virtual Private Network Identifier for Bandwidth

Management feature

X = Disables feature

1-16383 = Enables feature

<cr> = No Change

2 Configure the zone properties for IP Telephony bandwidthmanagement. Use LD 117 or Element Manager. See IP Peer Networking Installation and Commissioning (NN43001-313).

The branch office zone number and zone bandwidthmanagement parameters at the main office must match thecorresponding branch office zone number and zone bandwidthmanagement parameters at the branch office.

ATTENTIONZone 0, the default zone, must not be configured as a branch officezone. Network Bandwidth Management does not support zone 0.If zone 0 is configured as an branch office zone, the BandwidthManagement feature is not activated.

3 Define the zone parameters for the branch office. Use LD 117or Element Manager. See IP Peer Networking Installation and Commissioning (NN43001-313).

Table 7LD 117 Define zone parameters for the branch office

Command Description

CHG ZBRN <Zone> <yes|no>

Define a zone as a branch office zone.

CHG ZDST <Zone> <yes|no> <StartMonth> <StartWeek> <StartDay> <StartHour><EndMonth> <EndWeek> <EndDay> <EndHour>


NN43001-307 06.01 4 June 2010





Table 7LD 117 Define zone parameters for the branch office (cont’d.)

Command Description

If the branch office observes Daylight Savings Time (DST), these parameters

specify the start and end of DST. During DST, the clock automatically advancesone hour forward.

CHG ZTDF <Zone> <TimeDifferencefromMainOffice>

Specified in minutes, the time difference between main office and branch officewhen both are not in DST.

CHG ZDES <Zone> <ZoneDescription

A name to render data display more meaningful.

4 Enable the features for the branch office zone in LD 11.

Table 8

LD 117 Enable features for an SRG zoneCommand Description

ENL ZBR <zone> ALL Enables features for branch office <zone>.

--End--

Configuring zone parameters using CS 1000 Element ManagerUse Element Manager to configure the branch office specific zoneproperties and time difference.

1. Select IP Network > Zones in Element Manager navigator.

The Zones window opens. See Figure 4 "Zone List web page" (page38). The zone list is the main window used for zone configuration.

Figure 4Zone List web page

2. Select the zone to be configured and configure the following properties.


NN43001-307 06.01 4 June 2010






Zone parameters 39

— Basic Property and Bandwidth Management (see Figure 5 "ZoneBasic Property and Bandwidth Management web page" (page 39))

— Time Difference and Daylight Saving Time Property (see Figure 6"Zone Time Difference and Daylight Saving Time web page" (page

39))Figure 5Zone Basic Property and Bandwidth Management web page

Figure 6

Zone Time Difference and Daylight Saving Time web page


NN43001-307 06.01 4 June 2010












Table 9LD 11 Provision Branch User and SCPW at the main office (cont’d.)


ZONE0-255

0-8000

Zone number to which the IP Phone belongs.

The zone prompt applies only when the TYPE is 2001P2,

2002P2, 2004P2, 2050PC, 2007, 1110, 1120, 1140, 2210,

2211, 2212, 1210, 1220, 1230

Zone number is not checked against LD 117.

… … …

SCPWxxxx

Station Control Password

Must equal Station Control Password Length (SCPL) asdefined in LD 15. Not prompted if SCPL = 0. Precede with

X to delete.

--End--

SIP IP Trunks configuration at the main officeIn order for the SRG 50 to act as a SIP endpoint and to use the SIPTrunks for call signaling with the CS 1000, you must configure SIP Trunksbetween the SRG 50 branch office and the main office.

Configuring SIP IP Trunks

Step Action

1 From the Element Manager navigator, click IP Network >Nodes: Servers, Media Cards.

The Node Configuration window appears.

2 Click the Edit button associated with the node to be updated.

3 Click the plus (+) sign beside Signaling Server Properties.

4 From the Enable IP Peer Gateway (Virtual Trunks TPS) list,select SIP only.

5 Enter the CS 1000 domain name in the SIP Domain Name field.6 Enter the SIP Port number in the Local SIP TCP UDP Port to

Listen to field.

7 Enter the Signaling Server name in the SIP Gateway EndpointName field. See Figure 7 "SIP Trunk configuration in ElementManager" (page 42).


NN43001-307 06.01 4 June 2010







Figure 7SIP 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 8 "SIP Trunk configuration in NRS" (page 42).Figure 8SIP Trunk configuration in NRS

14 Select Save.15 Select Configuration > Gateway Endpoints.

The Gateways Endpoints window appears.

The SRG registers as a static SIP endpoint. See Figure 9"Gateways Endpoints window in NRS" (page 43).


NN43001-307 06.01 4 June 2010








Figure 9Gateways Endpoints window in NRS

--End--


NN43001-307 06.01 4 June 2010






NN43001-307 06.01 4 June 2010




45.

IP Phone registration and redirection

ContentsThis section contains information about the following topics:

• “IP Phone registration” (page 45)

• “IP Phone initial SRG registration” (page 46)

• “IP Phone redirection to the main office” (page 48)

• “IP Phone redirection failures” (page 49)

• “Normal Mode” (page 50)

• “Local Mode” (page 53)

IP Phone registrationThe IP Phones must be registered on both the main office Call Server andon the SRG to be properly configured in both Normal Mode and Local

Mode. The registration also facilitates the creation of an instance of the IPPhone on the SRG, which is kept alive in a standby mode such that thebooting time for the IP Phone in a WAN failure scenario is greatly reduced.

The complete registration process consists of two steps:

• The registration of the IP Phone on the SRG.

• The registration of the IP Phone on the main office.

Due to usage differences between Call Servers for the S1 and S2parameters of the IP Phone, the order of the registration can differdepending on the Call Server. However, this document covers only the

CS 1000 Call Server. For CS 1000, the SRG is configured as S1 in the IPPhones. Branch-based IP Phones initially register with the local SRG. TheIP Phone can then be redirected to the main office, where they will registerand receive Normal Mode features.


NN43001-307 06.01 4 June 2010










46 IP Phone registration and redirection

Regardless of the order of registration, once an IP Phone is registered onthe SRG it must then be provisioned as being redirected to enable thelogic, which detects the presence of the main office Call Server for thattype of IP Phone. This logic is the means for subsequent redirection of theIP Phone to the specified main office.

IP Phone initial SRG registrationWhen an IP Phone first registers with the SRG, as the installer, youare prompted to enter the SRG password followed by the DirectoryNumber (DN) as outlined in the normal BCM IP Phone manual installationprocedures. See Figure 10 "Password prompt screen" (page 46) andFigure 11 "DN prompt screen" (page 47).

Figure 10Password prompt screen


NN43001-307 06.01 4 June 2010






IP Phone initial SRG registration 47

Figure 11DN prompt screen

After the correct password and DN are entered, the IP Phone registerswith the SRG and is in Local Mode. In the example shown in Figure 12 "IPPhone registered with SRG" (page 47), a DN of 345 is entered for the IPPhone.

Figure 12IP Phone registered with SRG


NN43001-307 06.01 4 June 2010







The list of registered IP Phones can be viewed in the Element Manager(under the SRG > IP Terminal Details tab). This list displays differentlybased on the type of main office Call Server because the mainoffice-specific fields are different depending on the Call Server type.

IP Phone redirection to the main officeAfter an IP Phone is registered on the SRG, you must provide theinformation for the redirection of a given IP Phone to the main office. Theinformation provided depends on the Call Server type and is informationapplied using the designated SRG Element Manager interfaces. The SRGElement Manager can be accessed locally or remotely using the remoteaccess capabilities of the BCM 50 Release 5.0 platform. As a result,redirection of IP Phones (after installation) can be done remotely withoutthe need for physical contact with the IP Phones.

After the redirection information is entered, the SRG automaticallyredirects the IP Phones to register with the main office, provided the mainoffice Call Server is online and reachable from the SRG. The redirectionmethod depends on the Call Server type.

If this redirection provisioning process is not performed, the correspondingIP Phones will register to SRG in Local Mode and no redirection processwill be started.

CS 1000 redirection configurationThe IP address and port information for the Primary and Alternate NetworkConnect Servers (NCS) must be configured.

The SRG uses the NCS to resolve the address of the main office TPSprior to redirecting the IP Phones. The SRG sends the Type of Number(TON), Numbering Plan Identification (NPI), and DN of the IP Phone to theNCS. The NCS resolves the main office TPS using the dialing plan and DNsupplied, and returns either the associated IP address of the main officeTPS or an IP_UNKNOWN message. If the Primary NCS is unavailableafter a retry period, the SRG automatically queries the Alternate NCS. TheSRG stays with the Alternate NCS until it receives the Not Active Reasonresponse and then it switches back to the Primary NCS.

The SRG > IP Terminal Details tab shows the fields as indicated in Figure13 "IP Phone entries in Element Manager" (page 49). The following figureshows that the IP Phone (associated with DN 345 on the SRG) has beenredirected to a CS 1000 main office TN 61 31 with a BUID of 5678. The IPaddress of the TPS associated with this IP Phone in the main office (MOTPS) is also shown.


NN43001-307 06.01 4 June 2010






IP Phone redirection failures 49

Figure 13IP Phone entries in Element Manager

Before redirecting the IP Phone, the SRG copies the main office installerpassword and other parameters such as the MOTN and BUID to theDRAM of the IP Phone. The main office authenticates the IP Phoneregistration by validating the installer password present in the DRAM. Youmust ensure that the registration password configured in the SRG matchesthe installer password configured at the main office.

The response received from the Network Connect Server contains theaddress information of the main office TPS that is designated to handle the

registration of the IP Phone. The SRG then monitors the heartbeat of themain office TPS to make sure that it is available before redirecting the IPPhone.

The redirected IP Phone registers with the main office, provided that theinformation you entered is valid. The IP Phones registered with the mainoffice have different user interface (compared to the IP Phones registeredto the SRG).

IP Phone redirection failuresThe IP Phone registration to the main office Call Server may fail due to

improper configuration or lack of WAN connectivity. When a login failureoccurs, the error code and description is shown in the status field for the IPPhone in the IP Terminal Details tab within SRG Element Manager. TheIP Phone remains registered with the SRG in Local Mode after a loginregistration failure with the main office. The reasons for login failure varybased on Call Server type.

After the failure cause has been rectified, you can click the Redirect Setbutton to trigger the SRG to again redirect the IP Phones to register withthe main office.

Any of the following cause CS 1000 redirection failures:

• The remote Call Server is unreachable.

• There is no endpoint configured for the user ID or branch user ID(BUID) – TN combination.

• An IP Phone 2002 is not allowed to register with IP Phone 2004 or IPSoftphone 2050 TN or the IP Phone type does not match MOTN settype.


NN43001-307 06.01 4 June 2010






Normal Mode 51

Call ForwardThe forwarding of incoming PSTN calls to the main office is key to utilizingthe H.323/SIP-to-PSTN Gateway capability of the SRG for inbound calls.The Call Forward feature for CS 1000 branch can be configured in theSRG using either of the following two methods:

1. Target DN is determined based on the BUID/Main Office DN andVoIP Trunk Access Codes—The access code for the VoIP trunks isconfigured under SRG > Main Office Settings in Element Manager.Before redirecting the IP Phone to the main office, the SRG processsends an ActivateCallForward (DN, TargetDN) message to thecore. The SRG process creates the target DN number by prefixingthe VoIP trunk access code to the BUID/main office DN. Whenthe IP Phones comes back to the SRG, the SRG process sends aDeactivateCallForward (DN) message to the core.

2. Target DN is configured explicitly for each IP Phone—The Fwd All

Call field is added for each IP Phone, in the capabilities componentin the generic BCM Element Manager. You can configure the targetDN in this location. The target DN typically is the BUID/main office DNprefixed with VoIP trunk access code. Before redirecting the IP Phoneto the main office, the SRG process sends an ActivateCallForward(DN) message to the core to activate the Fwd All Call feature forthe IP Phone DN. The target DN is not sent to the core because itis already configured under the Telephony section. Similarly, whenthe IP Phone comes back to the SRG, the SRG process sends aDeactivateCallForward (DN) message to the core to deactivate theFwd All Call feature for the IP Phone DN. The disadvantage of thisoption is that you must configure the Target DN for each IP Phone inaddition to the BUID/main office DN.

External Attendant SupportThe SRG supports an external attendant by using the BCM SelectiveLine Redirection capability. With this capability a line can be redirectedthrough a specified interface (such as a VoIP trunk) to a specified DN.There is no local auto attendant capability included with the SRG. If anattendant is located in the main office and the main office unreachable inthe VoIP domain due to a WAN failure, the attendant is not reachable.Two methods are available for dealing with this situation:

• Specify a fallback (or Prime) DN in the SRG. Since this DN is likely toreceive calls in a WAN failure scenario, it must be an IP Phone whichcan transfer the calls to the desired party. If the IP Phone is also aredirected IP Phone, there is a period of time where inbound calls are


NN43001-307 06.01 4 June 2010





not routable, until the IP Phone fails back to the SRG due to the WANfailure.

• Specify a fallback route over the PSTN to the main office Call Server,where vacant number handling can be applied (such as routing to

Voice Mail).

Normal Mode call scenariosTable 10 "Call scenarios" (page 52) summarizes the call scenarios for IPPhones operating in Normal Mode.

Table 10Call scenarios

Scenario Type Description

IP Phone to

IP Phone

Originating or

Terminating

• The main office handles the call.

• The SRG is not involved in the call.

IP Phone tolocal non-IPterminal onSRG

Originating orTerminating

• The main office sets up the call usingan IP trunk at the main office and an IPtrunk at the SRG.

• No media flow over the WAN.

Originating • The main office sets up the call usingan IP trunk at the main office and an IP

trunk at the SRG.

• SRG routes the call to the local PSTNinterface.


IP Phone tolocal PSTN

Terminating • The inbound call is presented to theFTE representations of the IP Phone onthe SRG. The SRG forwards the call tothe designated DN using the IP trunk.

• The main office sees the call origination

and routes the call to the designatedIP Phone using an IP trunk at the mainoffice.


IP Phone toother branchoffice or mainoffice DN orremote PSTN

Originating orTerminating • The main office handles the call.• The SRG is not involved in the call.


NN43001-307 06.01 4 June 2010





Local Mode 53

Reverting from Normal Mode to Local ModeIn certain cases the IP Phones (which are in Normal Mode) switch backto Local Mode operation. In Local Mode, the IP Phones are under thecontrol of the SRG and have a limited set of features. The followingsections describe the different cases where an IP Phone reverts back to

local mode.

• “WAN failure” (page 53)

• “Test Local Mode” (page 53)

WAN failureWhen WAN connectivity is lost, each IP Phone loses its Reliable UDP(RUDP) connection with the main office TPS. Each IP Phone rebootsand re-registers at the SRG. The IP Phones remain under the control ofthe SRG until WAN connectivity is confirmed. During this period, the IP

Phones are in Local Mode and have a limited set of features necessary forthe phones to be survivable.

Test Local ModeTest Local Mode is a method for placing an IP Phone temporarily in LocalMode. This is the convenient way to confirm the provisioning of the IPPhone on the SRG for WAN failure, without resorting to WAN failuremanually. Test Local Mode must be supported on all CS 1000 IP Phones.

For CS 1000, the Test Local Mode option is available for testing survivalfunctionality. The CS 1000 main office Call Server provides the Test LocalMode option and the user interface (UI) for selecting the mode. Once

the Test Local Mode option is selected, the IP Phone is redirected to theSRG with the status field in the DRAM indicating Test Local Mode. TheIP Phone registers with the SRG and remains in Local Mode under SRGcontrol until the user completes the survivability testing and presses theStop key (the key with the octagon on it) to return back to Normal Mode oron expiry of the Test Local Mode timer.

An IP Phone in Normal Mode can also be brought to Test Local Mode byselecting the Test Local Mode option when the Services key is pressed.You can configure the Test Local Mode timer through Element Managerand the timer can have values from 2 to 10 minutes.

Local ModeThe Local Mode provides survivability to the branch IP Phones in casethe WAN connection to the main office fails or the when IP Phones fail toregister correctly with the main office. In this mode, the IP Phones areregistered to the SRG and receive call processing from the SRG. The SRG


NN43001-307 06.01 4 June 2010







provides a limited set of features that allow the IP Phones to be usableduring the period when they are not registered with the main office CallServer.

When a branch IP Phone is registered to the SRG due to power-up or

loss of WAN connectivity, it is automatically redirected to the main officewhen connectivity is confirmed between the SRG and main office andwhen the IP Phone is not on a call. Automatic redirection requires no userintervention (login).

When the network connection between the main office and the SRG isdown, the main office Call Server has no access to the IP Phones at theSRG. Calls to these IP Phones are treated according to the main officeredirection configuration, such as being redirected to the message centreor receiving ring no answer.

In Local Mode, the call processing for the IP Phones is handled by theSRG. Whenever an IP Phone re-registers with the SRG in Local Mode,the Call Forward All Calls associated with the redirection, if enabled, isautomatically cancelled. Calls between two IP Phones in the local SRGare handled locally as simple station-to-station call. When a Local ModeIP Phone initiates a local trunk call, the call is processed by the SRG androuted on to an appropriate trunk connected to local PSTN. Incoming DIDcalls are also handled by the SRG and terminated on the appropriate IPPhone.

In Local Mode, the IP Phones do not have access to the main officenetwork, and therefore, can only call other IP Phones directly registered

with the SRG. If alternate routes are available to the main office or otherbranch offices, then Local Mode IP Phones can make calls to them.

Local Mode indicationThe branch IP Phone is identified as being in Local Mode by displaying theSRG advertisement/logo banner . This indication is critical because theuser must be aware that the IP Phone has switched from Normal Mode toLocal Mode and that the feature capabilities and operation are different.The display in Local Mode is different from the display presented by themain office Call Server. The default advertisement/logo text is Local Mode.The text can be customized at install time through the SRG Element

Manager.


NN43001-307 06.01 4 June 2010




Local Mode 55

Figure 14IP Phone (registered with SRG) in Local Mode

Local Mode featuresThe SRG supports the following features in Local Mode:

• “Hold” (page 55)

• “Transfer” (page 55)

• “Call Forward No Answer/Busy” (page 56)

• “Last Number Redial” (page 56)

• “Inbox key” (page 56)

HoldThe Hold feature is provided using the Hold button key on the IP Phone.The Hold functionality is same as what is provided on the BCM platforms.

TransferThe Transfer feature (BCM Feature *70) is provided using a dedicatedkey on the IP Phone 2002 and 2004. The Transfer feature is critical giventhat inbound call handling in Local Mode may be different than NormalMode, increasing the likelihood of having to transfer an inbound call to theappropriate DN.


NN43001-307 06.01 4 June 2010










Call Forward No Answer/BusyThe Call Forward No Answer/Busy feature is configured using the SRGElement Manager. The configure must be done for each DN. This featureis same as on the BCM platforms.

Last Number RedialThis feature is provided by a dedicated key on the IP Phone 2002 and2004. This feature is same as on the BCM platforms.

Inbox keyThe Inbox key is enabled on the IP Phone 2002 and 2004. You mustprogram this key to autodial the PSTN number for accessing the user’svoice mail at the main office Call Server.

The SRG provides only a limited set of features in Local Mode. To limitaccess to undesirable features, the following keys are inoperative on the

IP Phones:• Navigation cluster (including the Copy key). The Exit key would be

active during Test Local Mode. The key is used to Resume NormalMode.

• Directory

• Outbox

• Services

• Expand

• Top two soft labelled keys (IP Phone 2004 only)

• Four context sensitive soft keys

Since the Feature key is disabled, features such as Hot Desking, Do NotDisturb, Page, Call Forward, Background Music, Call Park, Call Pickup,Speed Dial, and Conference are not available to the user. The Conferencefeature is not available for any analog interfaces like those connectedacross ATA modules, analog phones, and analog Polycom conferencephones as well.

The display on the IP Phones registered with the SRG will also be differentfrom the display provided by the BCM. The changes are as follows:

• The DN string is moved to the Line key in place of the soft labelled keyIntercom display string, except on the IP Phone 2001.

• BCM/Norstar Display line 1 containing time/date, feature input prompts,dial pad digit echo and CLID information is redirected to the top line ofthe IP Phone 2004 main three line display. There is no change donefor the IP Phone 2002 because the line is already on the top.


NN43001-307 06.01 4 June 2010




Local Mode 57

• The four soft key labels are blanked out.

• The advertisement/logo banner (set in Element Manager) is redirectedto the bottom line of the IP Phone 2001 and 2002, in place of the softkey label string.

• The advertisement/logo banner (set in Element Manager) is redirectedto the bottom line of the IP Phone 2004 main three line display.

The SRG 5.0 Release 5.0 does not provide local applications or thefollowing services (however, they are available on the BCM 50 Release3 platform):

• LAN CTE (A LAN CTE key code must be enabled to have the RSI toolconnect to the BCM server. However, you cannot configure any LANCTE-related services through Element Manager as in all previous SRG50 releases.)

• Multimedia Call Center• IVR

• Console Services

• Voice Mail


NN43001-307 06.01 4 June 2010






NN43001-307 06.01 4 June 2010




59.

Dialing Plan configuration


• “Overview” (page 59)

• “On-net dialing plan” (page 59)

• “Off-net dialing plan” (page 61)

• “Dialing Plan Overview” (page 61)

• “Dialing plan examples” (page 63)

• “Routing calls” (page 91)

• “Network using Uniform Dialing Plan” (page 91)

• “Network using Coordinated Dialing Plan” (page 113)

Overview This section provides an overview of dialing plan programming on the SRGand the main office.

When a number is dialed, the Call Server determines whether the callednumber is internal or external to the branch office. If internal or off-net,the system terminates the call on the appropriate terminal. If external oron-net, the system routes the call using one of the supported dialing plans.

On-net dialing planThe SRG only supports only one dialing plan option at a time. CDP and

UDP dialing plan options cannot be configured at the same time in thesame system.


NN43001-307 06.01 4 June 2010












60 Dialing Plan configuration

The SRG supports the following dialing plans:

• Coordinated Dialing Plan (CDP) – BUID is the same as the DirectoryNumber (DN)

• Uniform Dialing Plan (UDP) – Location code is added to the DN for the

BUID

ATTENTIONNortel recommends that the SRG use CDP.

CDP Terminal Numbers (TN) can be activated on the other systems ifthe user moves and wants to retain their phone number. SRG does notsupport Transferable Directory Numbers (TNDN) due to differences indialing plans and the small range of DN available on the SRG.

For specific examples for CDP and UDP dialing plans, see “Dialing planexamples” (page 63).

Once the call is sent over the IP network, the call is routed to the SRG,which uses the NRS (H.323 Gatekeeper/SIP Redirect Server) to routethe call. The NRS (H.323 Gatekeeper/SIP Redirect Server) translates theaddress form a telephone number to an IP address, and authorizes thecall.

Specific dialing plan configuration is required for IP Phones to properlyselect a main office or a branch office that provides access to the PSTNfor the originating IP Phone. A common configuration might be:

• SRG users select the SRG PSTN for local calls.

• Main office users select the main office PSTN for local calls.

• All users select either the main office or SRG PSTN for long-distancecalls to minimize toll charges.

• calls configured to minimize toll charges.

However, this configuration represents only one way that the dialing plancould be configured. PSTN calls can be routed according to the point oforigin (main office or branch office) and/or the desired destination, and canselect trunks at the main office, branch office, or other branch offices asrequired. Therefore, the user can route calls to gateways that minimizelong-distance costs, minimize bandwidth usage, or meet other criteria.

Nortel recommends that customers use Coordinated Dialing Plan (CDP)between the main office and its branch offices since it enables all users,at the main office or the branch office, to call each other using just anextension number. CDP enables consistent dialing between the mainoffice and SRG IP Phones and devices.


NN43001-307 06.01 4 June 2010






Dialing Plan Overview 61

For more information, see Dialing Plans Reference (NN43001-283).

Off-net dialing planWhen dialing to the PSTN, the Call Server determines that the calldestination is off-net by analyzing the digits that must be preconfigured atmajor Call Servers in the network.

If routed over a Virtual Trunk, a request is sent to the NRS to determinethe location of public E.164 numbers. The NRS is configured with a listof potential alternate routes that can be used to reach a certain dialednumber. Each route is configured with a unique route cost to determinethe least-cost route.

The NRS replies with the address information for E.164 numbers. It alsoprovides a list of alternative SIP or H.323 endpoints, sorted by cost. If aterminating endpoint resource is busy when a call attempt is made, the

originating endpoint tries the next alternative. If no alternative is availableover the IP network, the originating endpoint steps to the next entry on itsroute list, which could be a TIE or PSTN alternate route.

Dialing Plan OverviewDepending upon the type of dialing plan used in the network (CoordinatedDialing Plan [CDP], or Uniform Dialing Plan [UDP] or a combination ofboth) the general idea is to have all calls that are terminating at a branchoffice first dial a number that will get routed to the main office associatedwith that branch office. The main office recognizes this number asbelonging to the branch office and appends a tandem prefix to this number

using Digit Manipulation Index (DMI). The main office then routes the callto the branch office while accounting for the additional bandwidth used.

See Figure 15 "A call between two branch offices tandems through themain office" (page 62) for an example of a tandem call.


NN43001-307 06.01 4 June 2010







Figure 15A call between two branch offices tandems through the main office

Figure 16 "General legend" (page 63) shows a general legend for thefigures in the following section.


NN43001-307 06.01 4 June 2010






Figure 16General legend

Dialing plan examplesThis section describes the following dialing plans:

• Coordinated Dialing Plan (CDP)• Uniform Dialing Plan (UDP)

Coordinated Dialing PlanThe following section provides three options for creating a CDP dialingconfiguration.


NN43001-307 06.01 4 June 2010





OverviewDialing plans between the SRG and the main office need to be coordinatedto ensure seamless dialing between the systems. The option you choosewill determine how the user dials the other system or the SRG IP Phones.

• Option 1: DN ranges in the main office and SRG are unique, and DNsfor SRG IP Phones are the same in both Normal and Local mode. Thisis the recommended configuration to support seamless dialing on bothsystems. See “Option 1” (page 69).

• Option 2: DN ranges in the main office and SRG overlap, and DNs forSRG IP Phones are the same in both Normal and Local mode. See“Option 2” (page 74).

• Option 3: DN of SRG IP Phones and DN in the main office overlap inNormal Mode, but are unique in Local Mode. See “Option 3” (page 80).

Call scenariosCall scenarios fall into the following categories:

• Common call scenarios occur in all CDP calls, regardless of whichoption is used.

• Unique call scenarios occur only within certain CDP options.

This section describes the common call scenarios. The unique callscenarios are described with the configuration of the corresponding option,starting with “Option 1” (page 69).

Normal Mode: Main office telephone calls an analog phone at theSRG The call is routed through the NRS and handled by the SRG. Figure17 "Normal Mode: Main office telephone calls an analog phone at theSRG" (page 65) shows how the call proceeds.


NN43001-307 06.01 4 June 2010












Figure 17Normal Mode: Main office telephone calls an analog phone at the SRG

Normal Mode: Main office telephone calls a branch IP Phone Thecall is recognized as a main office number, and the call is directed to theSRG IP Phone using internal routing at the main office.

Normal Mode: Main office telephone makes a call over the PSTNthrough the SRG Routing is configured so the destination code of thePSTN through the SRG is at the start of the dialing string. Figure 18"Normal Mode: Main office telephone makes a call over the PSTN through

the SRG" (page 66) shows how the call proceeds.


NN43001-307 06.01 4 June 2010








Figure 18Normal Mode: Main office telephone makes a call over the PSTN throughthe SRG

Normal Mode: SRG IP Phone makes a call over the PSTN Zonemanagement at the main office recognizes that an SRG IP Phone inNormal Mode is dialing the PSTN. Figure 19 "Normal Mode: SRG IPPhone makes a call over the PSTN" (page 67) shows how the callproceeds.


NN43001-307 06.01 4 June 2010







Figure 19Normal Mode: SRG IP Phone makes a call over the PSTN

A telephone registered to the SRG calls another telephone registeredto the SRG The SRG routes the call internally.

Local Mode: SRG telephone calls an SRG IP Phone The call ishandled by the SRG and is sent directly to the SRG IP Phone.

Local Mode: SRG telephone calls a main office telephone In thiscase, the WAN or NRS is not accessible. Figure 20 "Local Mode: SRGtelephone calls a main office telephone" (page 68) shows how the callproceeds.


NN43001-307 06.01 4 June 2010







The user must have configured the fallback route appropriately. See theSRG 50 Configuration Guide (NN40140-500) for further information.

Figure 20Local Mode: SRG telephone calls a main office telephone

Local Mode: Main office telephone calls an SRG IP Phone Thecall is treated according to main office redirection configuration, such asforwarding to voice mail or continuous ringback.


NN43001-307 06.01 4 June 2010





Option 1DN ranges in the main office and SRG are unique; DNs for SRG IPPhone 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 ineither Normal or Local Mode. The DN for SRG IP Phones are configuredto be the same on both the SRG and main office. This allows seamlessdialing from both the SRG and main office. However, in this configuration,the DN range for telephones registered at the SRG is unique from the DNrange for telephones registered at the main office.

The advantage of this configuration is that the system manages the routingfor the SRG IP Phones, so users in the SRG and main office do not haveto be aware of whether the SRG is in Normal Mode.

See Figure 21 "CDP Option 1" (page 69).

Figure 21CDP Option 1

Call scenarios Common call scenarios for this CDP option are listedin “Call scenarios” (page 64). The following additional call scenarios areunique to this CDP option:

• An SRG analog telephone registered to the SRG calls a telephoneregistered at the main office that can also be an SRG IP Phone inNormal Mode.


NN43001-307 06.01 4 June 2010







Figure 22 "Calls to an SRG IP Phone and a main office IP Phoneregistered to the main office " (page 71) shows the WAN is up. AnSRG analog phone calls an SRG IP Phone and a main office IP Phoneregistered to the main office (Normal Mode).

Figure 23 "Calls to an SRG analog phone, SRG IP Phone, and a main

office IP Phone " (page 72) shows the WAN is down. An SRG analog


NN43001-307 06.01 4 June 2010









phone calls an SRG IP Phone and a main office IP Phone registeredto the SRG (Local Mode).

Figure 22Calls to an SRG IP Phone and a main office IP Phone registered to the main

office


NN43001-307 06.01 4 June 2010





Figure 23Calls 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.


NN43001-307 06.01 4 June 2010





>LD 86

REQ NEW

CUST 0

FEAT ESN

CDP YES

MXSC 50NCDP 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.


For information about configuring H.323/SIP Redirect Server, see IP Peer Networking Installation and Commissioning (NN43001-313).

To configure the SRG:

• Configure DN and BUID as the same number on each of the redirectedIP Phones. For example, DN/BUID = 42XX.

• Set the main office VoIP Trunk Access code to 3. For example, mainoffice VoIP trunk access code = 3.

• Set the destination code for the VoIP trunk to 30 (retain all digits) or 34

(remove first digit). For example, BUID dialout = 342XX.The VoIP route destination codes 30 (no digits dropped) and 34 (1 digitdropped) route any call that starts with 30 or 34 out of the system overthe VoIP trunk to the main office.


NN43001-307 06.01 4 June 2010





The main office access code length is still 0.

• Assign the telephones registered to the SRG (IP Phones or analog[500/2500-type]) telephones to a different range, such as 40XX. Seethe NRS configuration above.

The users in both the main office and the SRG dial only the DN for alltelephones in the main office and the SRG in both Normal Mode andLocal 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 moreinformation on configuring the SRG, see SRG 50 Configuration Guide (NN40140-500).

Option 2DN ranges in the main office and SRG overlap; DNs for SRG IPPhones are the same in Normal and Local Mode

In this configuration, the SRG DN overlap with the main office DN.However, since SRG does not support Vacant Number Routing (VNR), auser registered to the SRG must dial a destination code before the mainoffice DN to call a main office telephone.

To call an SRG IP Phone in either Normal or Local Mode, SRG andmain office users need to dial only the DN for the SRG IP Phone. SRGIP Phone calls are forwarded with the main office Private NetworkID/destination code appended to the BUID, which allows the call to flow to

the VoIP trunks for the main office.

This configuration is not a true CDP dialing plan. A destination code isadded by the system to properly direct the SRG IP Phone calls, since thestart digits of the DN are not unique for SRG and main office users. Usersdialing a telephone registered at the main office must dial a destinationcode before the main office DN. This plan allows all systems on thenetwork to appear to be available within a range of numbers.

Since the SRG DN range is limited to about 200 DN, this configurationonly works if SRG dialing to the main office is limited to the redirected IPPhones and to a small number of main office telephones, such as to acentral attendant and voice mail lines.

See Figure 24 "CDP Option 2" (page 75) shows this CDP option.


NN43001-307 06.01 4 June 2010








• Normal Mode: An SRG analog phone calls an SRG IP Phone and amain office IP Phone registered to the main office.

The WAN is up. SRG analog phone calls an SRG IP Phone and amain office IP Phone registered to the main Office (Normal Mode).

SeeFigure 25 "SRG analog phone calls an SRG IP Phone and a mainoffice IP Phone registered to the main office" (page 76).


NN43001-307 06.01 4 June 2010








Figure 25SRG analog phone calls an SRG IP Phone and a main office IP Phoneregistered to the main office

• Local Mode: SRG IP Phones are registered to the SRG.

In this scenario, the WAN and the NCS are working. However, theSRG IP Phones are redirected to the SRG and are in Local Mode (CallForward All Calls is inactive). The following occur:


NN43001-307 06.01 4 June 2010





— Telephones registered at the SRG dial local DNs (see the commoncall scenarios given in “Call scenarios” (page 64)).

— SRG calls to the main office use VoIP routing. The WAN is down.SRG analog phone calls an SRG IP Phone and a main office IP

Phone registered to the SRG (Local Mode) See Figure 26 "SRGanalog phone calls an SRG IP Phone and a main office IP Phone "(page 78).

— Main office calls to SRG IP Phones in Local Mode cannot completebecause the NRS cannot resolve the numbering.


NN43001-307 06.01 4 June 2010









Figure 26SRG analog phone calls an SRG IP Phone and a main office IP Phone


• Configure the ESN Control Block for CDP in LD 86.


NN43001-307 06.01 4 June 2010





> LD 86

REQ NEW

CUST 0

FEAT ESN

CDP YES

MXSC 50NCDP 4

DLTN YES


REQ NEW

CUST 0

FEAT CDP

TYPE DSC

DSC 50

FLEN 4

RLI 12



• Create H.323 and SIP endpoints: MO, BO.

• Create Numbering Plan entries in CDP Domain:



For information about configuring H.323 Gatekeeper/SIP Redirect Server,

see IP Peer Networking Installation and Commissioning (NN43001-313).


• Configure DN and BUID as the same number on each of the redirectedIP Phones. For example, DN/BUID = 32XX.

• Set the main office VoIP Trunk Access code to 6. For example, mainoffice VoIP trunk access code = 6.

• Set the destination code for the VoIP trunk to 6, the same value as theaccess code. For example, BUID dialout = 632XX.

The main office access code length is still 0.• Assign the telephones registered to the SRG (IP Phones or analog

[500/2500-type] telephones) to a different range, such as 30XX, thanthe telephones registered to the main office.

SRG users must dial the destination code before the DN when makinga call to a telephone in the main office, whether they are in Normal orLocal Mode. When calling another IP Phone in the SRG, SRG users


NN43001-307 06.01 4 June 2010





dial only the DN, whether they are in Normal or Local Mode. The mainoffice uses VNR to route SRG DN to the SRG in both Normal andLocal 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 moreinformation on configuring the SRG, see SRG 50 Configuration Guide (NN40140-500).

Option 3DNs of SRG IP Phones and DNs in the main office overlap in NormalMode, but are unique in Local Mode

In this CDP configuration, each node on the network has unique leadingdigits that is included in the DN range. The unique leading digits indicatethe private network code for the system.

This configuration allows seamless dialing for users registered at the SRG,but main office users must dial a different DN to call SRG IP Phones inNormal and Local mode. Therefore, SRG IP Phones have DNs and BUIDsthat do not match.

In Figure 27 "CDP Option 3 " (page 81), the SRG IP Phones have a DNstarting with 4 on the SRG to accommodate the SRG Private NetworkCode. On the main office, the SRG IP Phones are given a DN (BUID)starting with 3, the main office Private Network Code. The NRS isprogrammed to recognize that 3X numbers go to the main office and that

4X numbers go to the SRG.

In Normal mode, when a call is directed into the SRG, or from a telephoneregistered at the SRG, to the SRG IP Phone in Normal mode, the SRGsystem translates the SRG IP Phone DN (4XXX) to the main office BUID(3XXX) so that the call can route correctly through the main office VoIPtrunk. Users registered at the main office dial the main office DN (3XXX)for the SRG IP Phone.

In Local mode, the users registered to the SRG still dial the SRG IP PhoneDN (4XXX). The main office users can not call the SRG IP Phone by

dialing the main office DN for the telephone (3XXX) because the NRScannot route the call to the SRG. If the main office user dials the SRG IPPhone DN (4XXX), the call goes through.


NN43001-307 06.01 4 June 2010








• Normal Mode: An SRG analog phone calls an SRG IP Phone and amain 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. In Local Mode,the SRG IP Phone is reached only with the SRG DN.

In Normal Mode, the display on the IP Phone displays the main officeDN (3xxx) for the IP Phone. In Local Mode, the SRG DN (4xxx) isdisplayed. The WAN is up: SRG analog phone calls an SRG IP Phoneand a main office IP Phone registered to the main office (NormalMode).

Figure 28 "SRG analog phone calls an SRG IP Phone and a mainoffice IP Phone registered to the main office" (page 82) shows thisscenario.


NN43001-307 06.01 4 June 2010








Figure 28SRG analog phone calls an SRG IP Phone and a main office IP Phoneregistered to the main office

• Local Mode: SRG IP Phones are registered at the SRG.


NN43001-307 06.01 4 June 2010





In this scenario, the WAN and the NCS are working. If the main office userdials the SRG DN (42xx) to call the IP Phone, the call goes through.


• 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


REQ NEW

CUST 0

FEAT CDP

TYPE DSC

DSC 4

FLEN 4

RLI 12




• Create Numbering Plan entries in CDP Domain:— Add 4 for endpoint BO.


For information about configuring H.323 Gatekeeper/SIP Redirect Server,see IP Peer Networking Installation and Commissioning (NN43001-313).


• Set the BUID to the same number that was assigned for the TN by themain office.

• Set the main office VoIP Trunk Access code to 0.

• Do not assign a value to the main office trunk access code field.

For more information on configuring the main office and NRS, see Basic Network Feature Fundamentals (NN43001-579) and IP Peer Networking Installation and Commissioning (NN43001-313). For more information onconfiguring the SRG, seeSRG 50 Configuration Guide (NN40140-500).


NN43001-307 06.01 4 June 2010





Uniform Dialing PlanOverviewFigure 29 "UDP using location codes" (page 84) shows an example of aUniform Dialing Plan (UDP) using location codes (Access Code + LOC+ DN) configuration.

In this type of dialing plan, the DNs on the SRG do not need to be differentfrom the BUID, since the location code (LOC) defines the unique nodecharacteristic. Therefore, in this example:

• The SRG IP Phone has DN 3002 and BUID 3002. (The system addsthe routing code and LOC code to the BUID).

• The local telephone has a DN of 3101.

• The main office has a telephone configured as TN 3001.

• On the main office, the AC1 steering code for the SRG is 6 and the

LOC is 504.• On the SRG, the destination code for the main is 6 and the LOC is

501.

Figure 29UDP using location codes

Call scenariosThis section describes how calls interact between the SRG and main officewith UDP.

Calling from main office to the SRG and SRG PSTN, in Normalmode In this scenario, a telephone registered at the main office calls a


NN43001-307 06.01 4 June 2010






telephone registered to the SRG, or makes a call over the PSTN throughthe SRG. Figure 30 "Calling from the main office to the SRG and SRGPSTN, in Normal Mode" (page 85) shows this scenario.

Figure 30

Calling from the main office to the SRG and SRG PSTN, in Normal Mode

Calling from the SRG to the main office, in Normal Mode In thisscenario, a telephone registered at the SRG calls an SRG IP Phone anda 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 Phoneregistered to the main office (Normal Mode). Figure 31 "SRG analog


NN43001-307 06.01 4 June 2010








phone calls an SRG IP Phone and a main office IP Phone registered to themain office" (page 86)shows this scenario.

Figure 31SRG analog phone calls an SRG IP Phone and a main office IP Phone

registered to the main office

Calling in Local Mode In this scenario, the IP Phones at the SRGare in Local Mode because the WAN is down. The SRG IP Phones


NN43001-307 06.01 4 June 2010







are reregistered to the SRG and call forward BUID is inactive on thesetelephones. These IP Phones are registered at the SRG, and call forwardBUID 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 Phone (6002 instead of 3002). In this case, theuser dialing is different in the following ways:

• DN 3001 can call DN 3002 by dialing 65043002, instead of 3002.

• DN 3101 can call DN 3002 by dialing 3002, instead of 65013002 dialedin Normal Mode.

• DN 3002 can call DN 3001 by dialing 65013001, instead of 3001 dialedin Normal Mode.

• DN 3002 can call DN 3101 by dialing 3101 instead of 65043101 dialedin Normal Mode.

The WAN is down. SRG analog phone calls an IP Phone and a main officeIP Phone registered to the SRG (Local Mode). Figure 32 "SRG analogphone calls an IP Phone and a main office IP Phone registered to the SRG" (page 88) shows a call from the SRG to an SRG IP Phone and a mainoffice IP Phone registered at the SRG.


NN43001-307 06.01 4 June 2010








Figure 32SRG analog phone calls an IP Phone and a main office IP Phone registeredto the SRG

Configuration examplesThe following configurations are based on the examples provided inthis section. For further information, see Branch Office Installation and Commissioning (NN43001-314).


NN43001-307 06.01 4 June 2010





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 NEWFEAT 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 HLOCHLOC 501

DMI 6

• Configure the HLOC in the Customer Data Block in LD 15.> LD 15

REQ CHG

TYPE CDB

NET_DATA YES

ISDN YES

CLID YES

ENTRY <xx>

HLOC 501

• Configure the Virtual Trunk route in LD 16.


NN43001-307 06.01 4 June 2010





> LD 16

REQ NEW

TYPE RDB

CUST 00

ROUT 120

DES VTRKNODE51TKTP TIE

VTRK YES

ZONE 101

NODE 51

PCID H323

ISDN YES

MODE ISLD

DCH 12

IFC SL1

INAC YES



• Create Numbering Plan entries:

— Choose type UDP-LOC.



For information about configuring H.323 Gatekeeper/SIP Redirect Server,see IP Peer Networking Installation and Commissioning (NN43001-313).


• Create route and destination code to main office.

• In the main office screen:

— Set the type of number to ESN LOC.

— The VoIP trunk access code field is empty.

— Set the main office Access Code Length to 1.

You can also include the LOC as the dial out when you configurethe route for the VoIP line pool. This allows users to dial fewernumbers. For example, if 501 is configured as the dialout, and 6 isthe destination code, the user could dial 6+<main office DN>. Oncethe system identifies the route (VoIP trunks) and drops the 6, it addsthe LOC in front of the DN and dials <LOC>+<DN>. In the case ofredirected IP Phones, the BUID is <destination code>+DN. The mainoffice Access code length, in this circumstance, is set to 1.

• Dialing plan:


NN43001-307 06.01 4 June 2010




Network using Uniform Dialing Plan 91

— Set Type to UDP.

— Set LOC to 504.

• Set the BUID on the IP Phones to <VoIP trunk destination code> +<LOC> + <DN>.

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 moreinformation on configuring the SRG, see SRG 50 Configuration Guide (NN40140-500).

Routing callsSRG user call to an SRG PSTN

The SRG user telephone is registered at the main office. The SRG usertelephones are physically located at the branch office, so routing of

local PSTN calls back to the branch office is essential, even if they areregistered with the main office.

Branch office behavior of the SRG user telephones at the main office isconfigured by setting branch office zone characteristics through LD 117 atthe main office.

SRG PSTN to an SRG telephone (DID call)If the DN is valid and can terminate, call termination at the branch office istreated differently for IP Phones and non-IP Phones, as follows:

• IP Phones—If the telephone is registered to the SRG (Local Mode),

the call is terminated locally. If the telephone is not registered to theSRG (Normal Mode), the call is routed through a Virtual Trunk to themain office.

• Non-IP Phones—Calls are terminated locally (within the branch office).

Network using Uniform Dialing PlanThe following section provides general network configuration for a networkusing UDP only.

Figure 33 "Scenario 1: UDP throughout the network" (page 92) 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 placecalls between systems. Callers also use UDP to place calls across the IPnetwork to the other main office(s) and its (their) branch offices.


NN43001-307 06.01 4 June 2010






In a typical network, a full region uses a single Home Location Code(HLOC). However, it is also possible, where the number of users requiresit, to have two or more codes, although using one for the main office andone for each branch office is unlikely at best.

Figure 33Scenario 1: UDP throughout the network

Common detailsIn general, if an HLOC is shared between two or more systems, theprovisioning at the main office gets more complex, unless all branch officesshare HLOC with the main office. That is, if the main office has two ormore HLOC, and one or more of these (but not necessarily the sameone) is used by every branch office, then provisioning is relatively straightforward.

Table 11 "Configuration details for the general case" (page 92) describesthe network configuration and the steps that a call takes during its setup.

Table 11Configuration details for the general case

RegionCall progresssteps

Configuration detail and call progressduring call setup

1, 2, 3 UDP used for all calls within the region.

1, 2, 3 UDP used for region to region calls.

1, 2, 3 Prefixes for branch offices for regular calls are required forall branch offices. May have additional prefixes for E-911calls, if required, or may share prefixes.


NN43001-307 06.01 4 June 2010






Table 11Configuration details for the general case (cont’d.)

RegionCall progresssteps

Configuration detail and call progressduring call setup

1 1 All branch offices are provisioned at the NRS to route alloutbound calls (from the branch office) through the mainoffice. (NRS tandem configuration).

1 2 Main office sends all UDP calls to destinations that are notits own branch office to the NRS with unchanged dialleddigits.

1 3 Main office sends all UDP calls to destinations that areits own branch office to the NRS with a specific gatewayprefix in front of the dialled digits.

1 4 All branch offices delete the prefix and any LOC codes,and terminate the calls. May be to a local set or to a trunk.

2,3 Similar call setup steps take places for calls within region2 and 3.

Differences when every branch office HLOC is shared with the mainoffice

Table 12 "Provisioning details for this case" (page 93) shows theconfiguration when the branch office HLOC is shared with the main office.

Table 12

Provisioning details for this case

Region Provisioning detail

1 Provisioning on the main office requires parsing to only normal LOCidentification and HLOC deletion.

1 LOC values that are on branch offices may be provisioned asextended LOC (> 3 digit codes).

1 The DMI for the branch office LOC inserts a gateway routing prefixin front of the number.

2,3 Similar configuration, as above, applies to regions 2 and 3.

Call between two branch offices associated with the same main officeThe following scenarios describe calls between two branch offices that

belong to the same main office. The different scenarios described belowvary in the manner in which the HLOC is architected; branch offices havesame HLOC as the main office, branch offices have a different HLOC thanthe main office, and so on.


NN43001-307 06.01 4 June 2010






Every branch office HLOC is shared with the main officeIn the following example, the HLOC of all the branch offices and the HLOCof the main office are all the same. See Figure 34 "Call flow for Scenario 1- local call" (page 94).

Figure 34Call flow for Scenario 1 - local call

1. The branch office user dials 6-395-3456. The system transmits395-3456 to the NRS. The NRS checks its provisioning, anddetermines that all calls are to be sent to the main office; it directs thecall 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 branchoffice, with gateway routing prefix 552. The system inserts theprefix and transmits 552-395-3456 to the NRS. The NRS checks its

provisioning, and determines that all calls to prefix 552 are to be sentto branch office A2; it directs the call to the branch office.

4. The main office sends the call to 552-395-3456 to the branch office.The branch office deletes the prefix and the HLOC, and rings set 3456.


NN43001-307 06.01 4 June 2010







No branch office HLOC is shared with the main office, but can beshared with another branch office

In this example, the HLOC of the branch offices are the same but theHLOC of the main office is different. See Figure 35 "Call flow for Scenario1 - local call" (page 95).




3. The main office determines that this is LOC 39534 to another branchoffice, with gateway routing prefix 552. The system inserts theprefix and transmits 552-395-3456 to the NRS. The NRS checks its

provisioning, and determines that all calls to prefix 552 are to be sentto branch office A2; it directs the call to the branch office.

4. The main office sends the call to 552-395-3456 to the branch office.The branch office deletes the prefix and the HLOC and rings set 3456.


NN43001-307 06.01 4 June 2010







No branch office HLOC is shared with the main office or anotherbranch office

In this example, the HLOC is unique between all the branch offices and themain office. See Figure 36 "Call flow for Scenario 1- local call" (page 96).

Figure 36Call flow for Scenario 1- local call

1. The branch office user dials 6-395-3456. The system transmits399-3456 to the branch office user dials 6-399-3456. NRS. The NRSchecks its provisioning, and determines that all calls are to be sent tothe main office; it directs the call to the main office.


3. The main office determines that this is to another branch office,with office prefix 552. The system inserts the prefix and transmits552-399-3456 to the NRS. The NRS checks its provisioning, anddetermines that all calls to prefix 552 are to be sent to branch officeA2; it directs the call to the branch office.

4. The main office sends the call to 552-399-3456 to the branch office.The branch office deletes the prefix and the HLOC, and rings set 3456.


NN43001-307 06.01 4 June 2010






Call between branch offices associated with different main officeThe following scenarios describe calls between two branch offices thatbelong to different main offices. Note that the different scenarios describedbelow vary in the manner in which the HLOC is architected; branch officeshave same HLOC as the main office, branch offices have a different HLOC

than the main office, and so on.

Every branch office HLOC is shared with the main officeFigure 37 "Call to a remote branch office on the originator side " (page97) shows the first half of the call setup (the originator side is side A). Inthis example, the branch office and the main office share the same HLOC.Figure 38 "Call to remote branch office on the destination side" (page98) shows the second half of the call (the terminating side is side B).

Figure 37Call to a remote branch office on the originator side

1. The branch office user dials 6-444-3456. The system transmits444-3456 to the NRS. The NRS checks its provisioning, and


NN43001-307 06.01 4 June 2010









determines that all calls are to be sent to the main office; it directs thecall to the main office.


3. The main office determines that this is to another main office.

The system transmits 444-3456 to the NRS. The NRS checks itsprovisioning, and determines that this call goes to main office B.

Figure 38Call to remote branch office on the destination side

1. Main office B determines that this is to LOC 44434, which is a localbranch office with prefix 225. The system transmits 225-444-3456 tothe NRS. The NRS checks its provisioning, and determines that thiscall 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 HLOC444, deletes the HLOC, and rings set 3456.

No branch office HLOC is shared with the main office, but canbe shared with another branch officeFigure 39 "Call to remote branch office on the originator side" (page99)shows the first half of the call (originator side of the call). Figure 40"Call to remote branch office on destination side" (page 100)shows thesecond half of the call (destination side of the call).


NN43001-307 06.01 4 June 2010









Figure 39Call to remote branch office on the originator side

1. The branch office user dials 6-444-3456. The system transmits444-3456 to the NRS. The NRS checks its provisioning, anddetermines that all calls are to be sent to the main office; it directs the

call to the main office.


3. The main office determines that this is to another main office.The system transmits 444-3456 to the NRS. The NRS checks itsprovisioning, and determines that this call goes to main office B.


NN43001-307 06.01 4 June 2010





Figure 40Call to remote branch office on destination side

1. Main office B determines that this LOC plus digits is to a local branchoffice with prefix 225. (If sharing this LOC with another branch office,the extended LOC is 44434.) The system transmits 225-444-3456 tothe NRS. The NRS checks its provisioning, and determines that thiscall 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, and the HLOC, and rings set3456.

No branch office HLOC is shared with the main office or anotherbranch office

The following example shows a call between two branch offices. In thisexample, the HLOC is unique between the main office and branch office.Figure 41 "Call to remote branch office on the originator side" (page101)shows the first half of the call (originator side of the call). In Figure 42"Call to remote branch office on destination side" (page 102) shows thesecond half of the call (destination side of the call).


NN43001-307 06.01 4 June 2010









Figure 41Call to remote branch office on the originator side



3. The main office determines that this is to another main office. Thesystem transmits 444-3456 to the NRS. NRS checks its provisioning,and determines that this call goes to main office B.


NN43001-307 06.01 4 June 2010





Figure 42Call to remote branch office on destination side

1. Main office B determines that LOC 444 is to a local branch office withprefix 225. The system transmits 225-444-3456 to the NRS. The NRSchecks its provisioning, and determines that this call goes to branchoffice 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.

Summary of provisioning procedures for Tandem BandwidthManagement

Use Procedure 3 “Provisioning Tandem Bandwidth Management” (page104) to provision the network.

Step Action

1 Enter the main office Gateway endpoint identifier in the TandemEndpoint field for each branch office gateway configured on theNRS. This provides tandeming for outbound calls from a branchoffice through its main office. See Step 1.

2 Plan the gateway routing prefixes, if not already done. At leastone prefix is needed for each branch office, although any branchoffices that have a prefix for ESA 911 calls does not necessarilyrequire another. (These prefixes are Special Number [SPN]entries.) See Step 2.

3 Provision the NRS to send all calls to a LOC without a gatewayrouting prefix to the main office of that LOC, or to the main office


NN43001-307 06.01 4 June 2010









which provides service for the branch office using the LOC. SeeStep 3.

4 Provision the NRS to send all calls to a LOC with a gatewayrouting prefix to the branch office directly. Using the gatewayrouting 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 theprefixes and set the Type of Number correctly. Create RLB RLIentries to use these DMI for the VTRK route(s). One RLI foreach branch office is the minimum requirement. Note that callsfrom remote systems will typically have the HLOC prefix, so thisis defined here. See Step 5.

6 Provision the main office with CDP DSC (mapped by the RLI intoLocation Codes) sufficient to uniquely identify all of its branchoffices (using extended location codes, if required); use the RLIindex defined for each branch office as the RLI value of the LOC

definition. This is the route to the branch office. See Step 6.7 Provision the main office and branch office with a home location

code (HLOC) or multiple codes to terminate all calls that shouldterminate on this system. See Step 7.

8 Provision the main office to send all other LOC to the IP networkwithout prefixes. These are going to a remote main office. SeeStep 8.

9 Provision the branch office with a terminating RLI with a DMI todelete the LOC prefixes. See Step 9.

--End--

Provisioning Example of Tandem Bandwidth ManagementFigure 43 "Provisioning example" (page 104) shows an example of thenetwork configuration.


NN43001-307 06.01 4 June 2010













Figure 43Provisioning example

Procedure 3Provisioning Tandem Bandwidth Management

Step Action

1 Enter the main office Gateway endpoint identifier in the TandemEndpoint field for each branch office GW configured on the NRS.This provides tandeming for outbound calls from a branch officethrough its main office.

Figure 44 "Tandem endpoint configuration in Element Manager"(page 105) shows the tandem endpoint configuration in ElementManager.


NN43001-307 06.01 4 June 2010







Figure 44Tandem endpoint configuration in Element Manager

2 Plan the gateway routing prefixes. At least one prefix is neededfor each branch office, although any branch offices that have aprefix for ESA 911 calls does not necessarily require another.(These prefixes will be SPN - Special Number - entries if you areusing ESA 911. In the example these are LOC codes becausenetwork 911 is not being used.) In our example the Branch officeprefixes are 741 (branch office B) and 742 (branch office A).

3 Provision the NRS to send all calls to a LOC without a gateway

routing prefix to the main office of that LOC, or to the main officewhich provides service for the branch office using the LOC. Inour example the NRS is provisioned with 841 (for main office B)and 842 (for main office A).

4 Provision the NRS to send all calls to a LOC with a gatewayrouting prefix to the branch office directly. Using the gatewayrouting prefix and the Type of Number as used (LOC or SPN),the entries can be differentiated from the normal LOC easily.In our example the NRS is provisioned with 741-841 at branchoffice B and 742-842 for branch office A.

5 Provision the main office with the DGT table DMI to insert the

prefixes and set the Type of Number correctly. Create RLB RLIentries to use these DMI for the VTRK route(s). One RLI foreach branch office will be the minimum requirement. Note thatcalls from remote systems will typically have the HLOC prefix, sothis is defined here

Table 13 "Main office B DMI and RLI provisioning for calls inbranch office B" (page 106) lists main office B DMI and RLIprovisioning.


NN43001-307 06.01 4 June 2010







Table 13Main office B DMI and RLI provisioning for calls in branch office B

Create a DMI Create an RLI

LD 86 LD 86

REQ new REQ new

CUST 0 CUST 0

FEAT dgt FEAT rlb

DMI 50 RLI 50

DEL 0 ENTR 0

ISPN no LTER no

INST 741841 ROUT 71

CTYP loc DMI 50

6 Provision the main office with CDP DSC (mapped by the RLI intoLocation Codes) sufficient to uniquely identify all of its branchoffices (using extended location codes, if required); use the RLIindex defined for each branch office as the RLI value of the LOCdefinition. This is the route to the branch office.

Table 14 "Main office B LOC provisioning for LOC 741 841"(page 106) lists main office B LOC provisioning.

Table 14Main office B LOC provisioning for LOC 741 841

Create a CDP mapped to the LOC:

LD 87

REQ NEW

CUST 0

FEAT CDP

TYPE DSC

DSC 4030

FLEN 4

RLI 50

Create a CDP mapped to the LOC:

LD 87

7 Provision the main office and branch office with a home locationcode (HLOC) or multiple codes to terminate all calls that shouldterminate on this system.

Table 15 " Main office B and branch office B" (page 107) listsmain office and branch office HLOC provisioning.


NN43001-307 06.01 4 June 2010








Table 15Main office B and branch office B

Create a DMI Create an HLOC

LD 86 LD 90

REQ new REQ new

CUST 0 CUST 0

FEAT dgt FEAT net

DMI 61 TRAN ac1

DEL 3 TYPE hloc

ISPN no HLOC 841

DMI 61

Repeat the above for all the main offices and branch offices.

8 Provision the main office to send all other LOC to the IP networkwithout prefixes. These are going to a remote main office.

Table 16 "Main office B LOC provisioning for LOC to remotemain office system " (page 107) lists main office B LOCprovisioning for LOC to remote main office. The Main Office A isLOC 842.

Table 16Main office B LOC provisioning for LOC to remote main officesystem

Create an RLI Create a LOC

LD 86 LD 90

REQ new REQ NEW

CUST 0 CUST 0

FEAT rlb FEAT NET

RLI 51 TRAN AC1

ENTR 0 TYPE LOC

LTER no LOC 842

ROUT 71 FLEN 7

RLI 51

Table 17 "Main office A LOC provisioning for LOC to remotemain office systems " (page 108) lists main office A LOCprovisioning for LOC to the remote office. The Main office B isLOC 841


NN43001-307 06.01 4 June 2010









Table 17Main office A LOC provisioning for LOC to remote main officesystems

Create an RLI Create a LOC

LD 86 LD 90REQ new REQ NEW

CUST 0 CUST 0

FEAT rlb FEAT NET

RLI 71 TRAN AC1

ENTR 0 TYPE LOC

LTER no LOC 841

ROUT 75 FLEN 7

RLI 71

9 Provision the branch office with a terminating RLI with a DMI todelete the LOC prefixes.

Table 18Branch office terminating RLI provisioning

Create a DMI Create an HLOC

LD 86 LD 90

REQ new REQ NEW

CUST 0 CUST 0

FEAT dgt FEAT net

DMI 61 TRAN ac1

DEL 6 TYPE hloc

ISPN no HLOC 741

DMI 61

--End--

Network using mixed Coordinated Dialing Plan and Uniform DialingPlan

The following section provides general details of the network setup. showsan example of a mixed network configuration.


NN43001-307 06.01 4 June 2010





Figure 45UDP between main offices and CDP inside the main office region

Table 19 "Provisioning details for this case" (page 109) lists provisioningdetails for a mixed network.

Table 19Provisioning details for this case


1, 2, 3 CDP used for all calls within the region.

1, 2, 3 UDP used for region to region calls.

1, 2, 3 Prefixes for branch offices for regular calls not required. May

still have prefixes for E-911 calls, if required.1 All branch offices are provisioned at the NRS to route all calls

through the main office.

1 Main office sends all UDP calls to destinations that are not itsown branch office to the NRS with unchanged dialled digits.


NN43001-307 06.01 4 June 2010






Table 19Provisioning details for this case (cont’d.)


1 Main office sends all UDP calls to destinations that are its

own branch office to the NRS after deleting the HLOC andconverting to CDP.


Call between two local branch officesFigure 46 "Local call dials CDP" (page 110) shows the NRS Configurationweb page in Element Manager.

Figure 46Local call dials CDP

1. The branch office user dials 3456 (CDP). The system transmits 3456to the NRS. The NRS checks its provisioning, and determines that allcalls are to be sent to the main office; it directs the call to the mainoffice.

2. The branch office sends the call to 3456 to the main office.

3. The main office determines that this is to another branch office. Thesystem transmits 3456 to the NRS. The NRS checks its provisioning,

and determines that all calls to 3456 in this CDP domain are to be sentto branch office A2; it directs the call to the branch office.

4. The main office sends the call to 3456 to the branch office. The branchoffice rings set 3456.


NN43001-307 06.01 4 June 2010






Abnormal case - calls originating using UDP, but terminatingusing CDPFigure 47Call flow for Scenario 2 - local call dial UDP



3. The main office determines that this is to another branch office, usingCDP. The system deletes the HLOC and transmits 3456 to the NRS.The NRS checks its provisioning, and determines that all calls to 3456from this CDP region are to be sent to branch office A2; it directs thecall to the branch office.


Call between branch offices associated with different main officesIn the following diagram, the first half of the call is shown (the originator

side of the call).


NN43001-307 06.01 4 June 2010





Figure 48Call flow for Scenario 2 - local call to remote branch office (originator side)


2. The branch office sends the call to 444-3456 to the main office. Themain office determines that this is to another main office. The systemtransmits 444-3456 to the NRS. The NRS checks its provisioning, anddetermines that this call goes to main office B.

Figure 49 "Call to remote branch office on the destination side" (page113) shows the second half of the call (destination side of the call).


NN43001-307 06.01 4 June 2010







Figure 49Call to remote branch office on the destination side

1. The main office B deletes the HLOC, and determines that this is to alocal branch office. The system transmits 3456 to the NRS. The NRSchecks its provisioning, and determines that for this CDP region thiscall goes to branch office B1.


Network using Coordinated Dialing PlanThe following section provides general details of network setup.

The following diagram shows a full CDP network configuration.


NN43001-307 06.01 4 June 2010





Figure 50Full CDP network

The following table lists the provisioning details for a full CDP network.

Table 20Provisioning details for this case


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 uniquetermination of the calls. That is, every main office/branch officeregion requires its own LSC to ensure that all numbers are

unique.

1, 2, 3 Prefixes for branch offices for regular calls are required. Mayhave additional prefixes for E-911 calls, if required, or mayshare prefixes.

1 All branch offices are provisioned at the NRS to route all callsthrough the main office.


NN43001-307 06.01 4 June 2010





Table 20Provisioning details for this case (cont’d.)


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 frontof the dialled digits.

1 All branch offices delete the prefix and terminate the calls. Maybe to a local set or to a trunk.


Call between two local branch officesThe following diagram shows the call flow of a call between two localbranch offices.


1. The branch office user dials 43456. The system transmits 43456 to theNRS. The NRS checks its provisioning, and determines that all callsare to be sent to the main office; it directs the call to the main office.


3. The main office determines that this is to another branch office,with office prefix 552. The system inserts the prefix and transmits


NN43001-307 06.01 4 June 2010





552-43456 to the NRS. The NRS checks its provisioning, anddetermines that all calls to prefix 552 are to be sent to branch officeA2; 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.

Call between branch offices associated with different main officesIn the following diagram, the first half of the call is shown (originator sideof the call).

Figure 52Call flow for Scenario 3 - calls to remote branch office (originator side)

1. The branch office user dials 53456. The system transmits 53456 to theNRS. The NRS checks its provisioning, and determines that all callsare to be sent to the main office; it directs the call to the main office.


3. The main office determines that this is to another main office. Thesystem transmits 53456 to the NRS. The NRS checks its provisioning,and determines that this call goes to main office B.

In the following diagram, the second half of the call is shown (destinationside of the call).


NN43001-307 06.01 4 June 2010





Figure 53Call 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 prefix225. The system transmits 225-53456 to the NRS. The NRS checks itsprovisioning, and determines that this call goes to branch office B1.

2. The main office sends the call to 225-53456 to the branch office. Thebranch office deletes the prefix and LSC, and rings set 3456.


NN43001-307 06.01 4 June 2010






NN43001-307 06.01 4 June 2010




119.

Emergency Services configuration


• “Overview” (page 119)

• “Emergency Services Access” (page 120)

• “Emergency Services for Virtual Office” (page 131)

• “On-Site Notification” (page 131)

• “Configuring the NRS for ESA SPN” (page 131)

• “Testing the ESDN number” (page 132)

• “Configuring ESA using Element Manager” (page 133)

• “Emergency Service using Special Numbers (SPN)” (page 133)

Overview Support for access to emergency services by branch users in NormalMode is configured at the main office.

The key difference between the main office user and the branch user is theroute selected for the emergency call. An emergency call must be handedoff to the PSTN over a trunk at the central office that is geographicallyclosest to the caller—this means that there is normally an emergency trunkin the main office, and one in each of the branch offices. An emergencycall originating from an SRG IP Phone must route from the main office CallServer to the SRG so that the call can be sent on the SRG PSTN Trunks.

In Normal Mode, an IP Phone must have a Virtual Trunk available andconfigured between the main office and branch office to complete anemergency services call.

ATTENTIONDo not route ESA calls to a node that has no direct ESA trunks.


NN43001-307 06.01 4 June 2010












120 Emergency Services configuration

Nortel recommends using the Emergency Services Access (ESA) feature.This is the preferred method in North America, the Caribbean and LatinAmerica (CALA), and in those countries that are members of the EuropeanUnion (EU). ESA provides specific features and capabilities required bylegislation in these jurisdictions.

The ESA feature provides the following advantages:

• recognizes special Emergency Service Directory Number (ESDN)

• overrides calling restrictions

• provides optional assignment of ESA CLID for each DN

• provides optional selection of a special emergency route

• provides optional routing digits (for NRS resolution)

• provides optional assignment of an Emergency Location Identification

Number (ELIN)• provides On Site Notification (OSN) through an external tool, which

traps the emergency call event and records an alarm when anemergency calls are placed at the branch office

For more information about ESA, see Emergency Service Access Fundamentals (NN43001-613).

The main office Call Server forwards emergency services calls to the SRGusing a virtual trunk.

Emergency Services AccessThe Emergency Services Access (ESA) configuration specifies the digitsequence (a DN) that the user dials to start an emergency call, known asthe Emergency Services Directory Number (ESDN). There can only be oneESA configuration for each customer and thus only one ESDN for eachcustomer, which means that all telephones on the same network must bein the same numbering plan.

With all sites using the same ESDN, a conflict occurs in the NRS becausethe same ESDN may need to route to different gateways. The conflict isresolved by using a routing digit for each site that the main office adds asit routes the call. The suggested routing digit is the ESN home locationcode of the SRG, or alternately, the Numbering Plan Area (NPA) code ofthe SRG if there is not more than one Call Server in the NPA. Virtually anyunique digit string (maximum 15 digits) can be used as a routing digit,because the call is sent to the NRS as a Private/Special Number (SPN). Inthe NRS, SPN have their own separate numbering plan.


NN43001-307 06.01 4 June 2010





The Automatic Number Identification (ANI) data sent to the Public SafetyAnswering Point (PSAP) identifies the location of the caller. In someconstituencies, legislation requires one ANI (DID) for each fixed area, sothe physical location of the emergency can be approximated based onthe telephone number delivered to the PSAP. The ESA feature has a

comprehensive scheme that can be used to convert an extension into anappropriate DID.

If the branch office is relatively small, it can be easier to use a single ANInumber for the branch office. For more information on this command, seeSoftware Input Output Reference - Maintenance (NN43001-711).

Routing Emergency Services Access (ESA) calls

ATTENTIONDo not route ESA calls to a node that has no direct ESA trunks.

Ideally, route ESA calls directly over Central Office (CO) trunks to thePublic Safety Answering Point (PSAP). In those cases where this routingis not possible, do not route ESA calls to nodes that have no direct ESAtrunks.

The implications of routing calls to nodes without direct ESA trunks are asfollows:

• At the node without the direct ESA trunks, the node cannot route theESA call directly to the PSAP. Instead, that node must reroute the callto another node. This rerouting is an unnecessary use of resources.

• If the node is a CS 1000E node, the only tandem trunks are IP Peer

trunks. There is no way to specify the appropriate rerouting digits (thatis, Prepend Digits) to reroute the ESA call to another node with directESA trunks.

Therefore, if unable to route ESA calls directly to the PSAP, the next bestpractice is to route ESA calls to nodes with direct ESA trunks.

Emergency call routingA Call Server can provide service to IP phones across multiple emergencyjurisdictions. This can also occur with traditional non-IP equipment in theform of remote peripheral equipment (for example, Carrier Remote, Fiber

Remote).

An emergency call should be handled by the designated means for thephone location (for example, local security desk or local PSAP). Theemergency call should be routed to a service at the current location of thephone.


NN43001-307 06.01 4 June 2010





Configuring ESA for the branch officeFor ESA, the main office Call Server forwards the call to the branch officefor termination. Calls are redirected over a Virtual Trunk using the NRS.The NRS routes the calls using a special number, referred to in thissection as the ESA Special Number.

ESA must be configured and tested on the main office Call Server andthe SRG to differentiate between emergency calls originating from IPPhones at each location and calls originating on trunks, which refers tothe forwarded emergency call that the SRG receives from the main officefor an IP Phone in Normal Mode.

Use the following steps to configure ESA for emergency access at eachlocation:

At the main office:

Step Action

1 Determine the dialing plan (for example, numbering plan) forESA calls.

2 Configure the main office emergency trunk (CAMA or PRI).

For EMEA, the following trunks are supported:

• BRIE (Basic Rate Interface–ETSI based)

• PRI (Primary Rate Interface per EURO ISDN)

• QSIG on PRI• DPNSS

• IP tandem trunks on ISDN

3 Configure the Virtual Trunk at the main office.

4 Configure ESN at the main office.

5 Configure ESA at the main office.

6 Configure the SRG zone on the main office.

Configure a zone for each branch office which is used in

conjunction with ESA parameters to route an emergency call tothe SRG.

7 Test ESDN using a main office telephone.

8 Configure the SRG emergency trunk (CAMA or PRI).

9 Configure the Virtual Trunk at the MG 1000B.

10 Configure ESN at the branch office.


NN43001-307 06.01 4 June 2010





11 Configure ESA at the branch office.

12 Configure the branch office zone on the branch office.

The branch office zone is required for bandwidth managementbut 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 locatedat the branch office.

16 Test ESDN using an SRG IP Phone in Normal Mode and inLocal Mode.

--End--

At the SRG, or branch office:

Step Action

1 Configure the SRG emergency trunk (CAMA or PRI).

2 Configure the Virtual Trunk at the MG 1000B.

3 Configure ESN at the branch office.

4 Configure ESA at the branch office.

5 Configure the branch office zone on the branch office.

The branch office zone is required for bandwidth management

but does not require ESA parameters.

6 Configure the ESN SPN on the branch office.

7 Configure the NRS for the ESA Special Number used.

8 Test ESDN using an analog (500/2500-type) telephone locatedat the branch office.

9 Test ESDN using an SRG IP Phone in Normal Mode and inLocal Mode.

--End--

Reregistering to minimally configured branch officeA branch user in Local Mode but who is not physically at the branch canget incorrect emergency service handling.


NN43001-307 06.01 4 June 2010





If the SRG is not provisioned with knowledge of all the ERL in theenterprise, one of two scenarios occurs when an IP Phone reregisters tothe branch (either by VO ESA redirection or by fallback to Local Mode):

• If the local TN is provisioned as Manual Update, then the phone

inherits the static location data. The static location data probablyindicates basic ESA processing (LD 24) if this is a small branch.

• If the local TN is provisioned as Auto Update, then cached locationdata in the phone is rejected if undefined locally, and unknown locationvalues (ERL = 0, ECL = 0, LocDesc = Unknown) are assigned.Unknown location indicates default (basic) emergency processing (LD24), which is acceptable for a small branch. A system message isalso generated to indicate that the phone location data was actuallyunknown and defaults were used, but emergency calls should behandled correctly.

Minimally configured branches (without LIS support) can be configured asmanual update.

Routing configuration for ESA calls on SRG 50Use the following steps to configure routing for ESA calls for the SRG 50:

Procedure 4Configuring routing for ESA calls

Step Action

1 Build a destination code corresponding to the ESA SPN for the

branch office.2 Configure the destination code to absorb the leading digits for

the SPN, leaving just the ESDN.

3 Configure the destination code to use a public route to the PSTNtrunks.

4 Ensure the Remote access package (00 to 15 under CallSecurity) assigned to the VoIP trunks has the appropriate LinePool Access/Bloc for PRI.

5 Ensure there is a Public Prefix of 911 with a length of 3 to matchto outgoing digits. This eliminates any delay. As soon as the 3digits are collected, the call is sent.

--End--


NN43001-307 06.01 4 June 2010





Determining the dialing plan for ESA callsIn many jurisdictions of the United States and Canada, the emergencynumber must be “911”. The call processor cannot have a DN that conflictswith these digits, but since “9” is often used for NARS AC2 (the local callAccess Code), this is not usually a problem.

ESA for international deployment must support the standard emergencynumber 112 and any emergency numbers in use prior to the EU directive.

In general, ESA calls should leave the network through a trunk at thebranch office where the originating telephone is located. To enable this,it is necessary for telephones at each branch office to supply a uniqueidentifying prefix to the NRS when the ESA calls are being routed so thatthe NRS can select a distinct route for each branch office. This prefix canbe configured with the zone data for the SRG telephones. The provisioningof this prefix is an enhancement for branch office.

While a variety of numbering schemes are available, Nortel recommendsthat customers use 0 + the ESN location code of the SRG + ESDN, whereESDN is:

• for North America and CALA—911

• for members of the European Union—112 and any other emergencynumbers in use prior to the EU directive

This number, referred to here as the ESA Special Number, is configuredas a special number (SPN) in the NRS so that the Virtual Trunk routes thecall to the branch office.

Use Element Manager or the Command Line Interface for the followingprocedure. See IP Peer Networking Installation and Commissioning (NN43001-313) for details.

Procedure 5Configuring the main office

Step Action

1 Configure the main office emergency trunk (CAMA or PRI).

Configure either analog CAMA or digital PRI to correctly signalthe call identification.

ESA overrides all restrictions. Configure the trunk withrestrictions so that other features cannot access the trunk.

2 Configure the Virtual Trunk using the procedure from IP Peer Networking Installation and Commissioning (NN43001-313).


NN43001-307 06.01 4 June 2010





The Virtual Trunk must be configured to enable emergency callsoriginating from SRG IP Phones registered at the main office toreach 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.

Table 21LD 24 Configure Emergency Services Access


REQ:NEW CHG

Add new data, or change existing data.

TYPE:ESA

Emergency Services Access data block

CUST

xx

Customer number as defined in LD 15

ESDNxxxx

Emergency Services DN (for example, 911). Up to four digits

are accepted.

ESRT ESA route number

0-511

0-127

Range for Large Systems

Range for MG 1000B

DDGTx…x

Directing Digits (for CAMA Trunks) (for example, 1, 11, or 911).

Up to four digits are accepted.

DFCLx…x

Default ESA Calling Number. The input must be the following

lengths:

• On a system that is not FNP equipped, 8 or 11digits are accepted if the first digit of the input is ’1’;otherwise the input must be 7 or 10 digits.

• On a system that is FNP equipped, up to 16 digits areallowed.

OSDNx…x

On-Site Notification station DN. The input must be a valid single

appearance internal DN.

You configure OSDN to alert the local security personnel about

an emergency call in progress. Leave the ESA route numberblank to make test calls without using any trunk resources. If theroute number has been configured, remove it by entering “x” atthe prompt. Nortel recommends that the system administratorarrange a test call with the Public Services Access Point (PSAP).

5 Test ESDN using a main office telephone to confirm that mainoffice calls exit the main office trunks. The ESA ConfigurationAudit feature provides CLID Verification (CLIDVER) reports that


NN43001-307 06.01 4 June 2010





determine how an emergency call is routed, without actuallyrouting the call. Use LD 20 to generate a CLIDVER report.

Table 22LD 20 Generate a CLIDVER report

Prompt Response DescriptionREQ:

PRTPrint

TYPECLIDVER

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. If the

response is TN, the overlayprompts the user to enter the

TN and the output is sorted by

the TN.

ESA_ONLY(YES) NO

Flag used to decide if

the report should contain

information for ESA call type

only or for all call types.

If the ESA package is

restricted, this input prompt

does not appear. The reportcontains non-ESA data only.

SHORT(YES) NO

Flag used to decide if the

output report should be a Short

report of a Detail report.

TN Terminal Number

lscuFormat for Large System,

where l = loop, s = shelf, c =

card, and u = unit

CUSTxx

Customer number as defined in

LD 15.

DNx…x

Directory Number. If no

value is entered, the report

includes all supported Directory

Numbers.

DATEdd mmm yyy

Date


NN43001-307 06.01 4 June 2010





PAGE(NO) YES

Data printed on a per page

basis.

DESd…d

Designator

For more information about CLIDVER reports, see Emergency Service Access Fundamentals (NN43001-613).

6 Configure the branch office zone on the main office.

a Configure the branch office zone ESA dialing information inLD 117.

Table 23LD 117 Configure branch office zone ESA route

Command Description

CHG ZESA <Zone><ESA Route #><AC><ESA Prefix><ESA Locator>

Defines the ESA parameters for the branch office zone, where:

• Zone = Zone number for the branch office.

• ESA Route # = Virtual Trunk route to SRG.

• AC = Access Code to add to dialed digits. If no AC is required,enter AC0 in place of AC1 or AC2.

• ESA Prefix = Digit string added to start of ESDN. This is aunique prefix in the NRS. Nortel recommends that users use 0+ ESN location code of the branch office node. An example forlocation code 725 would be: 0725.

• ESA Locator = Direct Inward Dial telephone number sent aspart of ANI for use by the PSAP to locate the source of the call.

b Enable the branch office zone ESA in LD 117.

ENL ZBR <Zone> ESA

7 Configure the ESA Special Number at the main office.

Configure the ESA Special Number in the NRS. Using NRS,configure the ESA Special Number defined for the branch officezone. See IP Peer Networking Installation and Commissioning (NN43001-313).

Nortel recommends that customers use “0” + the ESN Location

code + ESDN. An example for location code 725 would be0725911. The zero is recommended to prevent a collision in theESN data with the HLOC entry.

8 Do the following:

a In LD 86, configure Emergency Service Access DigitManipulation for AC + ESDN dialing to allow recognition ofthe ESDN even if AC1 or AC2 is used.


NN43001-307 06.01 4 June 2010





Table 24LD 86


REQNEW CHG

Add, Change

CUSTxx


FEATDGT

Digit Manipulation

… … …

DMI1- 1999

Digit Manipulation Table numbers.

ATTENTIONDo not use Digit Manipulation Table 0, as it results in theincorrect call termination treatment.

b Configure the system to trap the ESDN within the AC1 andAC2 translation tables to reprocess the ESDN locally.

Table 25LD 86 Configure the system to trap the ESDN and reprocess it locally


REQNEW CHG

Add, Change

CUSTxx


FEATRLB

Route List Block

… … …

RLIxxx

Route List Index to be accessed

ENTRxxx

Entry number for NARS/BARS Route List

LTERYES

Local Termination entry. This allows the AC + ESDN call to be

recognized as an Emergency Services Access call.

DMI1 - 1999

Digit Manipulation Table.

Use the table configured in LD 86. This allows the digits after

the AC to remain in the call register as a called number.

ATTENTIONDo not use Digit Manipulation Table 0, as it results in theincorrect call termination treatment.

c Configure Emergency Service Access call recognition for AC+ ESDN dialing in LD 90.


NN43001-307 06.01 4 June 2010





Table 26LD 90


REQNEW CHG

Add, Change

CUSTxx


FEATNET

Network translation tables

TRANaaa

TYPESPN

- SPN911

AC + ESDN is recognized as an Emergency Service Access

call.

112Use the number configured for ESDN.

- RLI xxx Route List Index.

Use Route List Index configured in LD 86.

--End--

Procedure 6Configuring the branch office zone

Step Action

1 Configure the branch office zone on the branch office.In the branch office, only the zone number and bandwidth/codecselection is configured.

Use the same zone number between the branch office and mainoffice. The main office configuration (Procedure 5 “Configuringthe main office” (page 125), step 6) provides the branch officezone characteristics (local time, local dialing, and ESA).

2 Configure the routing tables on the SRG.

The SRG must recognize the incoming digits on the VirtualTrunk and remove all but the ESDN. The call is routed to a local

termination.

--End--


NN43001-307 06.01 4 June 2010







Configuring the NRS for ESA SPN 131

Emergency Services for Virtual OfficeThe E911 Virtual Office feature allows Virtual Office users, whetherthey are logged in or logged out of Virtual Office to place an emergency(E911) call to the correct Public Safety Answering Point (PSAP) for theirgeographical location.

The use of the terms Normal Mode and Local Mode apply to SRG branchuser only.

Emergency Services while logged in to Virtual OfficeThe E911 Virtual Office feature recognizes when a user dials an ESDNand it forces the Virtual Office IP Phone to log out of Normal Mode (intoLocal Mode) in order to place the emergency call directly from the branchoffice location to the PSAP. When the IP Phone in Local Mode, if it is notengaged in a call, is redirected back in Normal Mode after a 10-minuteinterval.

Emergency Services while logged out of Virtual OfficeIf 911 is dialed while logged out of Virtual Office the LTPS redirects the911 call to the local 911 service (PSAP), not the remote Call Server 911service. The Call Server is provisioned with Emergency Services AccessTerminal Numbers (ESTN). The ESTN is used to register the IP Phonewith the Call Server. The logged out IP Phone can make ESA calls only.

For more information on emergency services for Virtual Office, seeEmergency Service Access Fundamentals (NN43001-613) and Branch Office Installation and Commissioning (NN43001-314).

On-Site NotificationThe ESA On-Site Notification (OSN) function notifies local securitypersonnel when an emergency call occurs. When an emergency call isplaced at the branch office, an external tool traps the notification andrecords an alarm. This applies to IP Phones that the main office returns inlocal mode when an emergency call is made, as well as locally connectedanalog (500/2500-type) telephones.

The OSN is enabled by a third-party tool that connects to the SRG througha LAN CTE interface. A single LAN CTE interface must be enabled onthe SRG by applying an keycode. (The LAN CTE interface is enabled by

default by the SRG 50 Release 5.0 Authorization keycode.) For moreinformation, see SRG 50 Configuration Guide (NN40140-500).

Configuring the NRS for ESA SPNThe NRS must be configured for the ESA Special Number (SPN). TheNRS uses the ESA SPN to route the emergency call from the main officeto the branch office.


NN43001-307 06.01 4 June 2010





Nortel recommends that a consistent pattern be followed for all ESA calls.For example, use 0 + ESN Location code of the branch office node + theESDN. An example for location code 725 would be: 0725911. The zero isrecommended to prevent a collision in the ESN data with the HLOC entry.

For more information, see IP Peer Networking Installation and Commissioning (NN43001-313).

Testing the ESDN numberUse Procedure 7 “Testing ESDN using an SRG telephone” (page 132) totest the ESDN number from any telephone in the branch office.

Procedure 7Testing 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 thebranch office.

b Dial the ESDN on an SRG IP Phone in Normal Mode.

The calls must tandem over the Virtual Trunk to the branchoffice and go out on the emergency trunk(s) in the branchoffice. The following configuration problems can occur:

• The call can receive overflow tones. Use LD 96 to view

the digits sent to the Virtual Trunk (ENL MSGO dch#).• If the digits look correct on the main office, the NRS might

not be properly configured. If the NRS rejects the call, adiagnostic message is displayed on the NRS console.

• If the call makes it to the correct branch office (check thatit is not going to the wrong node if the NRS is configuredincorrectly), the branch office is probably rejecting itbecause it does not know the digit string.

2 For analog (500/2500-type) telephones, dial the ESDN on anSRG analog (500/2500-type) telephone.

The calls must go out on the emergency trunk(s) in the branchoffice.

--End--


NN43001-307 06.01 4 June 2010





Emergency Service using Special Numbers (SPN) 133

Configuring ESA using Element ManagerTo configure Emergency Services Access in Element Manager, seeElement Manager System Reference - Administration (NN43001-632).

Emergency Service using Special Numbers (SPN)Determining the dialing plan for emergency access calls is critical.

In many jurisdictions, the emergency number is a fixed number (forexample, 112 or 999). The main office Call Server or SRG cannot have aDN that conflicts with these digits.

Access to Emergency Service using SPN should be configured in thefollowing circumstances:

• When the Emergency Service number at the branch office is differentfrom that at the main office.

• When there is more than one number used for accessing EmergencyService; for example, when there are different numbers for Police, Fire,and Ambulance services.

• In markets where the ESA feature is not available (outside of NorthAmerica, CALA, and EMEA).

To configure Emergency Service using SPN, follow the process outlinedin “Dialing Plan configuration” (page 59). If SRG PSTN access is correctlyconfigured, Emergency Service from the branch office will already bepresent.

Branch office access to Emergency Service using SPN must be configuredand tested the main office Call Server and the SRG to differentiatebetween emergency calls originating from IP Phones at each location andemergency calls originating on trunks.

The special handling provided by ESA is not available in this scenario,such as OSN and zone-based routing.

For information on emergency services for Virtual Office, see Emergency Service Access Fundamentals (NN43001-613).


NN43001-307 06.01 4 June 2010







NN43001-307 06.01 4 June 2010




135.

Enhanced UNIStim Firmware Download


• “Description” (page 135)

• “Firmware upgrade” (page 139)

DescriptionThis section applies to the main office and the following IP Phones:

• IP Phone 2001

• IP Phone 2002

• IP Phone 2004

• IP Phone 2007

• IP Phone 1110

• IP Phone 1120E

• IP Phone 1140E

• IP Phone 1210

• IP Phone 1220

• IP Phone 1230

This section does not apply to the IP Softphone 2050, IP AudioConference Phone 2033, and WLAN 2210/2211/2212/6120/6140.

Note: This release supports only IP Phones supporting the UFTPfirmware download as commanded by a Call Server using the UNIStimprotocol. IP Phones that do not support the UNIStim protocol must havetheir firmware version managed outside the context of the SRG.

The following list provides a summary of the enhance firmware downloadprocess:


NN43001-307 06.01 4 June 2010






136 Enhanced UNIStim Firmware Download

• The main office has IP Phones s that are directly connected to it, aswell as IP Phones that are redirected to the main office through theSRG branch office.

• Whenever new IP Phone firmware is released and the same firmware

version is intended to be loaded on all the IP Phones connectedto the main office. The firmware is loaded to the main office andumsUpgradeAll command is issued in the main office. (See “Firmwareupgrade” (page 139).)

• The IP Phones connected directly to the main office are downloadedwith this firmware.

• The IP Phones redirected through SRG branch office are redirectedto the branch office.

• Before redirection, the new firmware version to which the IP Phone hasto be upgraded is written in DRAM of the redirected IP Phone.

• The SRG system reads the firmware version and checks if it has it inits repository.

• If found, the firmware is downloaded to the IP Phone or the firmware issent (using FTP) from main office.

The redirected IP Phones at the SRG 50 are under the control of the mainoffice Call Server for the majority of the deployment (Normal Mode). Usersof the SRG IP Phones receive the features, key layout, and tones of themain office Call Server. Therefore, the version of the IP Phone firmwaremust align with the requirements of the CS 1000 main office Call Server.When an IP Phone requires firmware upgrade, the CS 1000 uses the

umsUpgradeAll command, or variant, to redirect the IP Phone back tothe SRG 50 for upgrading.

The SRG allows the main office to facilitate deployment of its baseline IPPhone firmware to the IP Phones located in the branch office.

The main office indicates that the IP Phone is being sent back for firmwareupgrading, setting the state variable in the IP Phone DRAM accordingly(including a string indicating the required firmware version). The SRG doesthe following when an IP Phone boots with the DRAM status indicatingthat a firmware upgrade is required:

• Reads the required firmware version string from the DRAM of the IPPhone.

• Reads the current firmware version of the IP Phone.

• Reads the firmware ID (FW_ID) from the IP Phone. (This occurs whenthe IP Phone boots and identifies the firmware platform of the IPphone.


NN43001-307 06.01 4 June 2010









— The first attempt of FTP would be a Secure FTP. If it fails, the CallServer may not be CS 1000 Release 6.0 or greater and normalFTP is invoked.

— If the session fails it could be due to lack of support for automatic

FTP of firmware or it could be due to FTP being blocked by afirewall.

— An alarm is raised indicating that the FTP (or SFTP ) session hasfailed.

— All IP Phones waiting on the FTP session are redirected back tothe main office without being upgraded.

For CS 1000 Release 4.5 and later, if the required firmware file does notexist on the SRG 50, or the version of the file is incorrect, the SRG 50initiates an FTP session to the TPS for the IP Phone to retrieve therequired file. The SRG 50 upgrades the IP Phone and redirects the IP

Phone back to the CS 1000.

For CS 1000 Release 4.0, ensure MPLR21148 is installed on the SignalingServer.

Firmware download does not occur when IP Phones register to the TPSby a Virtual Office Login or branch office redirection to the main office.Instead, SRG IP Phones are redirected back to the SRG TPS for firmwarefiles upgrade. This redirection occurs only if the umsUpgradeAll commandis issued from the main office TPS, and the current firmware files aremissing.

If an IP Phone is in use when the umsUpgradeAll command is issued,the call is not interrupted. Its firmware version is checked against themain office TPS firmware policy, and if there is no match, the IP Phone isflagged, then redirected to the MG 1000B TPS when the call is completed.The umsUpgradeAll command has no immediate impact on IP Phones thatare logged in or out by Virtual Office. However, the firmware files may beupgraded, if required, when the Virtual Office session is terminated.

For information on Enhanced UNIStim Firmware, see Signaling Server IP Line Applications Fundamentals (NN43001-125).


NN43001-307 06.01 4 June 2010





Firmware upgradeThe following naming convention is used to identify the different firmwareversion strings that must be checked during the course of firmwareupgrade operation.

• Set FW version: The version of firmware currently loaded in the IPPhone.

• File FW version: The version of the firmware present in the local file.

• DRAM FW version: The version of the firmware required by the mainoffice. The main office writes this version to the DRAM of the IPPhone. The main office also sets the redirect reason field in the DRAMto FW Upgrade before redirecting the IP Phone for firmware upgrade.

The IP Phone is upgraded when the Set FW version does not match theFile FW version.

Use Procedure 8 “Upgrading firmware” (page 139) to upgrade thefirmware. For information about upgrading IP Phone firmware, seeSignaling Server IP Line Applications Fundamentals (NN43001-125).

Procedure 8Upgrading firmware

Step Action

1 At the main office, upgrade the IP Phone firmware on theSignaling Server. For instructions, see Signaling Server IP Line Applications Fundamentals (NN43001-125).

2 Issue the CLI command umsUpgradeAll at the main office. IPPhones at the main office and branch office are upgraded asnecessary.

--End--


NN43001-307 06.01 4 June 2010







NN43001-307 06.01 4 June 2010




141.

AppendixMedia redirection scenarios

In addition to basic call scenarios, Network Bandwidth Management alsosupports the following media redirection scenarios:

• Scenario 1: Codec switches correctly during media redirection. See

Table 27 "Codec switches correctly during media redirection" (page142).

• Scenario 2: Call transfer works correctly with IP Phones:

— Scenario 2.1: Call Transfer from an SRG IP Phone in Normal Modeto main office IP Phone. See Table 28 "Call transfer from SRG IPPhone in Normal Mode to main office IP Phone" (page 142).

— Scenario 2.2: Call Transfer from main office IP Phone to an SRGIP Phone in Normal Mode. See Table 29 "Call transfer from mainoffice IP Phone to SRG IP Phone in Normal Mode" (page 142).

• Scenario 3: Conference Call works correctly with a branch office:— Scenario 3.1: Conference call between branch office and main

office, initiated by an SRG IP Phone in Normal Mode. See Table 30"Conference call between branch office and main office, initiated bySRG IP Phone in Normal Mode" (page 143).

— Scenario 3.2: Conference call between main office and branchoffice, initiated by main office IP Phone. See Table 31 "Conferencecall between main office and branch office, initiated by main officeIP Phone" (page 144).

The zone table is examined using the commands in LD 117. See

Software Input Output Reference - Maintenance (NN43001-711) for moreinformation on these commands.

In these scenarios, consult the zone table at the main office for accuratebandwidth usage information.


NN43001-307 06.01 4 June 2010
















142 Media redirection scenarios

Table 27Codec switches correctly during media redirection

Event Result

1 An incoming Direct Inward Dial (DID) call

to branch office uses IP Peer to reach thesymposium controller Control DirectoryNumber (CDN) in the main office.

The external caller hears music and

announcements with a G.729 codec. Bandwidthusage 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.711

codec. Bandwidth usage in the main office

indicates the call is an intrazone call. The ACD

agent is an SRG IP Phone registered to the main

office.

2 The call is released. The zone table indicates the bandwidth usage for

the call is removed correctly on the main officeCall Server and in the branch office.

Table 28Call transfer from SRG IP Phone in Normal Mode to main office IP Phone

Event Result

1 An SRG TDM telephone calls an IP Phoneregistered to the main office.

A speech path is established between the SRGTDM telephone and the IP Phone registeredto the main office. The zone table indicatesintrazone bandwidth usage.

2 The SRG IP Phone registered to the main

office initiates a call transfer to a main officeIP Phone.

The SRG TDM telephone is put on hold. A

speech path is established between the SRGIP Phone registered to the main office and themain office IP Phone. The zone table indicatesinterzone bandwidth usage.

3 The Call Transfer key on the SRG IPPhone registered to the main office ispressed to complete the call transfer.

A speech path is established between the SRGTDM telephone and the main office IP Phone.

The zone table indicates interzone bandwidthusage.

4 The call is released. The zone table indicates bandwidth usage for thecall is unreserved correctly.

Table 29

Call transfer from main office IP Phone to SRG IP Phone in Normal Mode

Event Result

1 An SRG TDM telephone calls a main officeIP Phone.

A speech path is established between the SRGTDM telephone and the main office IP Phone.The zone table indicates interzone bandwidthusage.


NN43001-307 06.01 4 June 2010





Table 29Call transfer from main office IP Phone to SRG IP Phone in Normal Mode (cont’d.)

Event Result

2 The main office IP Phone initiates a call

transfer to an SRG IP Phone registered tothe main office.

The SRG TDM telephone is put on hold.

A speech path is established between themain office IP Phone and the SRG IP Phoneregistered to the main office. The zone tableindicates interzone bandwidth usage.

3 The Call Transfer key on the main officeIP Phone is pressed to complete the calltransfer.

A speech path is established between the IPPhone registered to the main office and theSRG TDM telephone. The zone table indicatesintrazone bandwidth usage.

4 The call is released. The zone table indicates bandwidth usage for thecall is unreserved correctly.

Table 30

Conference call between branch office and main office, initiated by SRG IP Phone in NormalMode

Event Result

1 An SRG TDM telephone calls an SRG IPPhone registered to the main office.

A speech path is established between theSRG TDM telephone and the SRG IP Phoneregistered to the main office. The zone tableindicates intrazone bandwidth usage.

2 The SRG IP Phone registered to the mainoffice initiates a conference call to a mainoffice IP Phone.

The SRG TDM telephone is put on hold. Aspeech path is established between the SRGIP Phone registered to the main office and themain office IP Phone. The zone table indicates

interzone bandwidth usage.

3 The Conference key on the SRG IP Phoneregistered to the main office is pressed to

complete the conference call.

Speech paths are established among the SRGTDM telephone, the SRG IP Phone registered to

the main office, and the main office IP Phone.The zone table indicates interzone and intrazonebandwidth usage.

4 The SRG TDM telephone releases the call. A speech path is established between themain office IP Phone and the SRG IP Phoneregistered to the main office. The zone table

indicates interzone bandwidth usage.

5 The call is released. The zone table indicates bandwidth usage for

the call is unreserved correctly.


NN43001-307 06.01 4 June 2010




144 Media redirection scenarios

Table 31Conference 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 bandwidthusage.

2 The main office IP Phone initiates aconference call 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 Phoneregistered to the main office. The zone tableindicates interzone bandwidth usage.

3 The Conference key on the main officeIP Phone is pressed to complete theconference call.

Speech paths are established among the SRGTDM telephone, the SRG IP Phone registered tothe main office, and the main office IP Phone.The zone table indicates interzone and intrazone

bandwidth usage.

4 The SRG TDM telephone releases the call. A speech path is established between the SRGIP Phone registered to the main office and themain office IP Phone. The zone table indicatesinterzone bandwidth usage.

5 The call is released. The zone table indicates bandwidth usage forthe call is unreserved correctly.


NN43001-307 06.01 4 June 2010




145.

AppendixCall features available in Local Mode

When an IP Phone is Normal Mode, it is serviced by the CS 1000 systemand all the features that are available to an IP Phone that is directlyconnect to the CS 1000 are rendered to IP Phones in Normal Mode as

well. However, in Local Mode, only the basic services are being offeredto the IP Phone.

These restrictions are achieved through the following:

• “Keycodes” (page 145)

• “Element Manager” (page 146)

KeycodesThe SRG keycode carries a restricted bundle that sets the mode of theBCM to SRG, along with seats for IP trunks and IP clients. The following isa list of features and capabilities that is enabled by the SRG keycode:

• All 80 survivable IP users

• Up to 24 H.323 or SIP VoIP trunks

• 4 PSTN trunks (analog)

• 2 BRI trunks (M50b platforms)

• 4 analog station interfaces

• 12 digital station interfaces (for ATA use only)

• 2 ports for expansion

• MCDN Networking Feature Code

• NCM Feature Code

• LAN CTE Feature Code (only one seat to be used by RSI tool forOSN)


NN43001-307 06.01 4 June 2010






146 Call features available in Local Mode

The other keycodes that are generally available in BCM mode that notavailable to SRG systems are as follows:

• Unified Messaging seats

• Voice Mail seats

• Intelligent Contact Centre (ICC)-related codes

• Voice Profile For Internet Messaging (VPIM) and Audio Messaginginterchange Specification (AMIS) seats

• Meet Me suites

• APP pack

Element ManagerSome features are masked in the Element Manager in SRG mode.

For example, options for IVR. A snapshot of the configuration tree in aBCM mode and an SRG mode machine is shown in Figure 54 "ElementManager in BCM mode and SRG mode" (page 147). Note that theApplications node is available on the BCM system; however, it is maskedin SRG systems, rendering the applications out of bounds” for the useron an SRG system.


NN43001-307 06.01 4 June 2010






Element Manager 147

Figure 54Element Manager in BCM mode and SRG mode

Set-based restrictions

Features can be invoked by using the Feature * key from the IP Phone, aswell as through the Button Programming section in Element Manager. Thepath is Configuration tab > Telephony > Sets > All DNs > Capabilities andPreferences > Button Programming.

The feature programming requires the programmed keys to be active inthe respective IP Phone. However, in SRG mode, only the basic keysare available and only those keys can be programmed. Certain keys can


NN43001-307 06.01 4 June 2010




148 Call features available in Local Mode

accept only specific features and only those features can be programmed.Table 32 "Local mode features based on provisions in the IP Phone" (page148) provides a short list of available features for the IP Phones in LocalMode. Only basic features such as Hold, Transfer, Call Forward, LastNumber Redial, Intercom/ DN key, and Inbox key can be programmed.

Table 32Local mode features based on provisions in the IP Phone

IP Phone type

Sl.No.

Featurecode

Featurename

2001,1110,2033, WLAN2210, 2211,2212, 6120,and 6140

2002,1120

2004,2007,2050,1140

1210 1220 1230

1 *79 Hold Yes Yes Yes Yes Yes Yes

2 *3 Transfer(BlindTransfer)

No Yes Yes No Yes Yes

3 *4 CallForward


4 *5 LastNumberRedial


5 — Intercom/ DN Key


6 — Line Keys No Yes Yes No Yes Yes

In SRG mode, the feature filtering on the IP Phone is achieved by maskingthe Feature key. None of the feature invocation that is available throughthe IP Phone by using this key is available to the user. For example, Norteldoes not recommend the Button Programming action because the featurefiltering options in effect in Local Mode makes the Button Programmingdone in Element Manager useless. For a list of Button Programmingfeatures and for a complete list of the BCM feature names and codes thatcan be invoked in BCM mode (which are not available in SRG mode),seeNortel Business Communications Manager 5.0 Configuration —Devices (NN40170-500).

Note: The Hold, Transfer (Blind Transfer), Call Forward, and LastNumber Redial features are available in Local Mode.


NN43001-307 06.01 4 June 2010






149.

List of terms

Branch officeAn SRG that is remote from the main office. The SRG providestelephony services using the main office servers (for NormalMode) or local system services when the SRG loses IPcommunication with the main office (Local Mode).

CDPCoordinated Dialing Plan. Under the recommended CoordinatedDialing Plan, the Branch User ID can be an extension (forexample, 4567). For more information about CDP, see Dialing Plans Reference (NN43001-283).

dialing planEach system uses a specific numbering configuration (dialingplan) that determines how calls will be handled over a private orpublic network.

DSPDigital Signal Processing, which refers to manipulating analoginformation, such as sound or photographs that have beenconverted into a digital form. DSP also implies the use of a datacompression technique.

When used as a noun, DSP stands for Digital SignalingProcessor, a special type of coprocessor designed for performingthe mathematics involved in DSP. Most DSP are programmable,which means that they can be used for manipulating differenttypes of information, including sound, images, and video.

ESAEmergency Services Access is a feature that places a customerin compliance with federal legislation that requires the Private 911type of functionality provided by ESA. Please note, however, thatthe ESA feature is also generally useful for users who are notsubject to legislation, and is broad enough to be used in different


NN43001-307 06.01 4 June 2010




150 List of terms

countries. For example, it will be appreciated by any customerwho wants to route emergency calls in a special manner, or whowants to be notified when a telephone user makes an emergencycall. It would also appeal to a customer who wishes to have ESAcalls answered on-site,

on the business premises, rather than being forwarded to thePublic Services Answering Point (PSAP). See Emergency Service Access Fundamentals (NN43001-613) for complete information.

GatekeeperThe Gatekeeper is a separate application on an IP network thatdirects IP traffic to all the systems on the network. Parametersfor both the main office and SRG must be assigned to allgatekeepers active on the network. If the Gatekeeper is down, theSRG attempts to connect to the Alternate Gatekeeper, if there is

one. If the Alternate Gatekeeper is down as well, or there is noAlternate Gatekeeper, the SRG IP Phones remain registered withthe main office but calls cannot be sent to the SRG.

gatewayIn networking, a combination of hardware and software thatlinks two different types of networks. Gateways between e-mailsystems, for example, enable users on different e-mail systemsto exchange messages.

H.323

A standard approved by the International TelecommunicationUnion (ITU) that defines how audiovisual conferences data istransmitted across networks. In theory, H.323 enables users toparticipate in the same conference even though they are usingdifferent video conferencing applications. Although most videoconferencing vendors have announced that their products conformto H.323, it is too early to say whether such adherence actuallyresults in interoperability.

IPAbbreviation of Internet Protocol, pronounced as two separateletters. IP specifies the format of packets, also called datagrams,

and the addressing scheme. Most networks combine IP with ahigher-level protocol called Transport Control Protocol (TCP),which establishes a virtual connection between a destination anda source.


NN43001-307 06.01 4 June 2010




151

IP by itself is something like the postal system. It enables you toaddress a package and drop it in the system, but there’s no directlink between you and the recipient. TCP/IP, on the other hand,establishes a connection between two hosts so that they can sendmessages back and forth for a period of time.

LANLocal Area Network.

Local ModeThe SRG is in Local Mode when:

• The IP Phones are first installed and not yet reregistered withthe main office

• The SRG cannot communicate with the main office and the IPPhones are reregistered with the SRG

• A user deliberately puts the IP Phone in the Test Local Modecondition.

Main officeThe CS 1000 system that has been programmed to acceptredirection of the SRG IP Phones and provide call service for theSRG in Normal Mode.

NCSNetwork Connection Service. It provides a TPS interface to theNRS, allowing the TPS to query the NRS using the UNIStim

protocol. It is required to support the main office, branch office,Virtual Office, and Geographic Redundancy features.

Normal ModeThe SRG is in Normal Mode when the IP Phones on the SRG arecorrectly redirected to the main office Call Server.

NRSNetwork Routing Service. The software application where allsystems in the network are registered. The NRS consists of theH.323 Gatekeeper and the Network Connection Service (NCS).

PSTNPublic Switched Telephone Network. The international telephonesystem based on copper wires carrying analog voice data. Thisis in contrast to newer telephone networks based on digitaltechnologies.


NN43001-307 06.01 4 June 2010




152 List of terms

Telephone service carried by the PSTN is often called plain oldtelephone service (POTS).

QoSQuality of Service, a networking term that specifies a guaranteed

throughput level. One of the biggest advantages of ATM overcompeting technologies, such as Frame Relay and Fast Ethernet,is that ATM supports QoS levels. This enables ATM providers toguarantee to their customers that end-to-end latency does notexceed a specified level.

There are several methods to provide QoS, as follows:

• high bandwidth

• packet classification

• DiffServ

• IP fragmentation

• traffic shaping

• use of the platform’s queuing mechanisms

routingThe process of selecting the correct path for packets transmittedbetween IP networks by using software-based algorithms. Eachpacket is processed by the algorithm to determine its destination.

SRG 50Survivable Remote Gateway 50. This describes the equipmentused to create an IP branch office with a CS 1000 system actingas the main office. The base system for SRG is a BusinessCommunication Manager running BCM 3.6 software.

TPSIP Phone Terminal Proxy Server. This server controls theconnection of IP Phones. It resides on the Signaling Server withan emergency backup on the Voice Gateway Media Card.

UDP

Uniform Dialing Plan. Each location within the network is assigneda Location Code, and each telephone has a Directory Numberthat is unique within the network. Under the UDP, the SRG mustinclude the location code in the Branch User ID (BUID).


NN43001-307 06.01 4 June 2010




153

VoIPVoice over IP trunk. This IP pathway between two system IPvoice gateways allows the system to exchange telephone callsover the Internet.

WANWide Area Network. A computer network that spans a relativelylarge geographical area. Typically, a WAN consists of two or morelocal area networks (LAN).

Computers connected to a wide area network are often connectedthrough public networks, such as the telephone system. They canalso be connected through leased lines or satellites. The largestWAN in existence is the Internet.

ZDP

Zone Digit Prefix. This is the number that the main office appendsto a local SRG PSTN call dialed from an SRG IP Phone in NormalMode. This number differentiates the call from a main office PSTNcall dialed by the main office telephones. The ZDP routes the callthrough VoIP trunk to the SRG.


NN43001-307 06.01 4 June 2010




154 List of terms


NN43001-307 06.01 4 June 2010




155.

Index

BBranch office 149Branch office dialing plan 27

CCapacity 27CDP 149Configuring ESA for branch office 122Configuring ESA using Element

Manager 133Configuring the NRS for ESA SPN 131Configuring zone parameters using

Element Manager 38Coordinated Dialing Plan 63

Ddialing plan 149Dialing plan configuration 59DSP 149

EEmergency Service using Special

Numbers 133Emergency Services Access (ESA) 120Emergency Services configuration 119Emergency Services for Virtual Office 131ESN Access Codes 28

GGatekeeper 150Gateway 150

HH.323 150

Hardware description 15

IIP 150

IP Phone calls 26

LLocal Mode 151

MMain office 151Main office configuration 31Main office hardware description 15Main office information required by the

SRG 33

Main office requirements 19Media Redirection Scenarios 141, 145Music on hold 28

NNCS 151Normal Mode 151Normal Mode and Local Mode overview 20NRS 151

OOff-net dialing plan 61On-net dialing plans 59Optional features to enhance SRG

functionality 20

PPSTN 151


NN43001-307 06.01 4 June 2010























































































156

QQoS 152

RRouting 152Routing calls 91Routing ESA calls 121

SSignaling Server 16SIP Redirect Server Network Routing

Service 17SRG 152SRG information required by the main

office 32SRG PSTN to an SRG telephone (DID

call) 91SRG user call to an SRG PSTN 91Supported IP Phones 17Survivable Remote Gateway 11

TTesting the ESDN number 132Testing the phone in Local Mode 26TPS 152

UUDP 152Uniform Dialing Plan 84

VVirtual Trunks capacity 27VLAN 153VoIP 153

ZZDP 153


NN43001-307 06.01 4 June 2010



















































Date post:	10-Apr-2018
Category:	Documents
Upload:	techfolkcmr
View:	221 times
Download:	0 times

NN43001-307 06.01 Commissioning Main Office Config SRG50

Documents