Nortel SRG200, SRG400, 1000 Configuration Manual
Nortel Communication Server 1000
Nortel Communication Server 1000 Release 5.0
Main Office Configuration for SRG200/
400 Release 1.5
Configuration Guide
Document Number: NN43001-308
Document Release: Standard 01.02
Date: May 2007
Copyright © 2005–2007 Nortel Networks
All Rights Reserved.
Produced in Canada.
The information in this document is subject to change without notice. The statements, configurations, technical
data, and recommendations in this document are believed to be accurate and reliable, but are presented
without express or implied warranty. Users must take full responsibility for their applications of any products
specified in this document. The information in this document is proprietary to Nortel Networks.
Nortel, Nortel (Logo), the Globemark, SL-1, Meridian 1, and Succession are trademarks of Nortel Networks.
Title page
Page 3 of 254
Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide
4
Revision history
May 2007
Standard 01.02. This document is up-issued to support
Communication Server 1000 Release 5.0. This document is also up-issued to
include updated information due to CR Q01587820. See “Codec negotiation”
on page 108.
June 2006
Standard 01.01. This document is issued to support SRG200/400 Release 1.5
with Communication Server 1000 Release 4.5. This document reflects the
new document number.
June 2006
Standard 2.00. This document is released to support SRG200/400 Release 1.5
with Communication Server 1000 Release 4.5.
August 2005
Standard 1.00. This document is a new document to support
Communication Server 1000 Release 4.5.
Page 4 of 254 Revision history
NN43001-308 Standard 01.02 May 2007
Page 5 of 254
Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide
8
Contents
List of procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 9
New in this release . . . . . . . . . . . . . . . . . . . . . . . . . 11
Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Subject .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Related information .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Survivable Remote Gateway .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Main office hardware description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Main office requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Optional features to enhance SRG functionality .. . . . . . . . . . . . . . . . . 22
Normal Mode and Local Mode overview . . . . . . . . . . . . . . . . . . . . . . . 23
Bandwidth Management Overview .. . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Capacity .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Branch office dialing plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Branch office and SRG200/400 Release 1.5 terminology . . . . . . . . . . 34
Setting up the main office . . . . . . . . . . . . . . . . . . . 37
Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
SRG information required by the main office .. . . . . . . . . . . . . . . . . . . 38
Page 6 of 254 Contents
NN43001-308 Standard 01.02 May 2007
Main office information required by the SRG . . . . . . . . . . . . . . . . . . . 39
Zone parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Branch office IP Phone configuration at the main office . . . . . . . . . . . 46
Dialing Plan configuration . . . . . . . . . . . . . . . . . . . 49
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Overview .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
On-net dialing plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Off-net dialing plan .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Routing calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
H.323 zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Zone-based digit manipulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Configuring the dialing plan for PSTN
access to SRG users in Normal Mode . . . . . . . . . . . . . . . . . . . . . . . . . 55
Dialing plan examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Bandwidth Management . . . . . . . . . . . . . . . . . . . . 107
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Codec negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Configuring Bandwidth Management parameters . . . . . . . . . . . . . . . . 114
Adaptive Network Bandwidth Management . . . . . . . . . . . . . . . . . . . . 124
Tandem Bandwidth Management overview . . . . . . . . . . . . . . . . . . . . . 148
Dialing Plan Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Network using Uniform Dialing Plan . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Network using Coordinated Dialing Plan . . . . . . . . . . . . . . . . . . . . . . . 178
Alternative Call Routing for Network Bandwidth
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Operating parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Contents Page 7 of 254
Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide
Feature interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Feature packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Feature implementation using Command Line Interface . . . . . . . . . . . 205
Feature implementation using Element Manager . . . . . . . . . . . . . . . . . 207
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Emergency Services configuration . . . . . . . . . . . . 221
Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Emergency Services Access (ESA) .. . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Configuring the NRS for ESA SPN . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Testing the ESDN number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Configuring ESA using Element Manager . . . . . . . . . . . . . . . . . . . . . . 235
Emergency Service using Special Numbers (SPN) .. . . . . . . . . . . . . . . 235
Enhanced UNIStim Firmware Download . . . . . . . . 237
Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Firmware upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Appendix A: Media Redirection Scenarios . . . . . . 241
List of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Page 8 of 254 Contents
NN43001-308 Standard 01.02 May 2007
Page 9 of 254
Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide
10
List of procedures
Procedure 1
Configuring ESN and SRG zones . . . . . . . . . . . . . . . . .42
Procedure 2
Configuring branch office IP Phones at the
main office using LD 11 . . . . . . . . . . . . . . . . . . . . . . . . .47
Procedure 3
Configuring the main office . . . . . . . . . . . . . . . . . . . . . . 57
Procedure 4
Configuring the NRS database . . . . . . . . . . . . . . . . . . . 66
Procedure 5
Configuring the branch office . . . . . . . . . . . . . . . . . . . .69
Procedure 6
Testing PSTN access using an SRG IP Phone . . . . . . .74
Procedure 7
Printing intrazone and interzone statistics
for a zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Procedure 8
Displaying CAC parameters for one or more zones . . 142
Procedure 9
Provisioning Tandem Bandwidth Management . . . . . .166
Page 10 of 254 List of procedures
NN43001-308 Standard 01.02 May 2007
Procedure 10
Accessing the Zones web page . . . . . . . . . . . . . . . . . . . 207
Procedure 11
Printing zone ALTPrefix . . . . . . . . . . . . . . . . . . . . . . . . . 212
Procedure 12
Show Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Procedure 13
Enabling a zone’s branch office behavior . . . . . . . . . . 217
Procedure 14
Suppress Alternative Call Routing for
NBWM alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Procedure 15
Configuring the main office . . . . . . . . . . . . . . . . . . . . . . 227
Procedure 16
Configuring the branch office zone . . . . . . . . . . . . . . . . 233
Procedure 17
Testing ESDN using an SRG telephone . . . . . . . . . . . . 234
Procedure 18
Upgrading firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Page 11 of 254
Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide
14
New in this release
The following sections detail what is new in Main Office Configuration
Guide for SRG200/400 (NN43001-308) for CS 1000 Release 5.0.
Other
Main Office Configuration Guide for SRG200/400 (NN43001-308) includes
the following changes
• Replaced instances of OTM 2.2 with TM 3.1.
• Updated Element Manager with enhancements.
• Added support for new IP Phones.
• Removed instances of CS 1000S and Small Systems.
Subject
This document describes the main office configuration for SRG200/400
Release 1.5. Information in this document complements information found in
documents in the Communication Server 1000 documentation suite, as listed
in “Related information” on page 12.
For information about how to configure the SRG200/400 Release 1.5, see the
SRG200/400 Release 1.5 Configuration Guide at www.nortel.com. Select
Support and Training > Technical Documentation > Communication Servers
> BCM > Survivable Remote Gateway 200/400 > Documentation and search
for Survivable Remote Gateway 200/400.
Page 12 of 254 New in this release
NN43001-308 Standard 01.02 May 2007
Note on legacy products and releases
This NTP contains information about systems, components, and features that
are compatible with Nortel Communication Server 1000 Release 5.0
software. For more information about legacy products and releases, click the
Technical Documentation link under Support & Training on the Nortel home
page:
www.nortel.com
Intended audience
This document is intended for individuals responsible for configuring the
main office for Survivable Remote Gateway for organizations using CS 1000
systems.
Related information
This section lists information sources that relate to this document.
NTPs
The following NTPs are referenced in this document:
• Converging the Data Network with VoIP Fundamentals (NN43001-260)
• Electronic Switched Network Reference—Signaling and Transmission
Guidelines (NN43001-280)
• Dialing Plans Reference (NN43001-283)
• Signaling Server Installation and Commissioning (NN43001-312)
• IP Peer Networking Installation and Commissioning (NN43001-313)
• Branch Office Installation and Commissioning (NN43001-314)
• Telephony Manager 3.1 Installation and Commissioning
(NN43050-300)
• Software Input Output Administration (NN43001-611)
• Emergency Services Access Fundamentals (NN43001-613)
• Telephony Manager 3.1 System Administration (NN43050-601)
New in this release Page 13 of 254
Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide
• Element Manager System Reference—Administration (553-3001-332)
• IP Line Fundamentals (NN43100-500)
• ISDN Primary Rate Interface Fundamentals (NN43001-569-B1)
• ISDN Primary Rate Interface Fundamentals (NN43001-569-B2)
• ISDN Primary Rate Interface Fundamentals (NN43001-569-B3)
• Basic Network Features Fundamentals (NN43001-579)
• SRG200/400 Release 1.5 Configuration Guide
• Communication Server 1000M and Meridian 1 Small System Planning
and Engineering (NN43011-220)
• Communication Server 1000M and Meridian 1 Large System Planning
and Engineering (NN43021-220)
• Communication Server 1000E Planning and Engineering
(NN43041-220)
• Software InputOutput Reference—Maintenance (NN43001-711)
Online
To access Nortel documentation online, click the Technical Documentation
link under Support & Training on the Nortel home page:
www.nortel.com
CD-ROM
To obtain Nortel documentation on CD-ROM, contact your Nortel customer
representative.
Page 14 of 254 New in this release
NN43001-308 Standard 01.02 May 2007
Page 15 of 254
Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide
36
Overview
Contents
This section contains information about the following topics:
Survivable Remote Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Main office hardware description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Main office requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Optional features to enhance SRG functionality. . . . . . . . . . . . . . . . . . 22
Normal Mode and Local Mode overview . . . . . . . . . . . . . . . . . . . . . . . 23
Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Branch office dialing plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Branch office and SRG200/400 Release 1.5 terminology . . . . . . . . . . 34
Survivable Remote Gateway
The Survivable Remote Gateway (SRG) extends the desktop feature and user
interface of the CS 1000 to remote IP branch office users and gives them full
access to the same applications as the main site. CallPilot, Contact Center
Management Server (CCMS), and other central applications are shared by
remote users to deliver state-of-the-art features and functionality to small
remote offices.
The SRG 50 Release 1.0 solution complements the existing SRG200/400
Release 1.0 and Release 1.5 product and is intended to be positioned as a costoptimized platform for small branch offices with up to 32 survivable IP users.
The existing SRG200/400 solution continues to provide branch support for up
Page 16 of 254 Overview
NN43001-308 Standard 01.02 May 2007
to 90 survivable IP users and the MG 1000B solution is positioned for larger
branch offices for up to 400 users.
The SRG200/400 solution is supported on CS 1000 Release 4.0, CS 1000
Release 4.5, and CS 1000 Release 5.0 systems.
Table 1 on page 16 shows supported software at the branch office.
The SRG200/400 is implemented on a BCM200/400 platform and is
connected to a CS 1000 at the main office over a LAN or a WAN. This
configuration allows the call processing for the IP Phones at the SRG site to
be centralized at the main office. The Call Server at the main office provides
the call processing for the IP Phones in both the main office and branch
offices. The SRG provides call processing functionality to telephones in local
Tabl e 1
Supported software at the branch office
IP Branch office solution
Number of
survivable users
Feature description
SRG 1.0 up to 90 VoIP and Application Gateway
Local Mode = Basic telephony features
SRG 50 Release 1.0 up to 32 VoIP and Application Gateway
Local Mode = Basic telephony features
A more cost effective small branch office
solution.
SRG200/400 Release 1.5 up to 90 VoIP and Application Gateway
Local Mode = Basic telephony features
Feature Parity with SRG 50, new OS, and
extended IP Phone support.
SRG 50 Release 2.0 up to 80 VoIP and Application Gateway Local
Mode = Basic telephony features
Extended IP Phone support and
survivable IP users from 32 to 80.
MG 1000B up to 400 100% CS 1000 feature and application
redundancy in survivable mode. Designed
and positioned for larger IP branch offices.
Overview Page 17 of 254
Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide
mode and local analog devices. The SRG also provides digital and analog
trunk access to the local Public Switched Telephone Network (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 over the LAN/
WAN.
If the main office fails to function, or if there is a network outage, the SRG
provides service to the telephones located at the branch office. This enables
the IP Phones to survive the outage between the branch office and the main
office.
The SRG is designed to work with a main office only if the main office and
the SRG use a common dialing plan. Any other configuration is not
guaranteed to work reliably. Since the Call Server and the SRG handle dialing
slightly differently, ensure that any settings you use for the main office, that
need to interact with the SRG, can be accommodated by the SRG call
processing.
Figure 1 on page 18 shows the networking among the main office, SRG, and
IP Phones.
Page 18 of 254 Overview
NN43001-308 Standard 01.02 May 2007
Figure 1:
SRG network
Main office hardware description
The main office must be one of the following systems:
• CS 1000E
• CS 1000M Cabinet
• CS 1000M Chassis
• CS 1000M HG
• CS 1000M SG
• CS 1000M MG
Throughout this document, references to CS 1000 systems encompass all
CS 1000 system types.
Overview Page 19 of 254
Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide
The diagrams throughout this documentation show a CS 1000S main office.
All of the systems appearing in the list perform identical main office
functions as far as the SRG is concerned. For information about the SRG, see
the SRG200/400 Release 1.5 Configuration Guide.
Signaling Server
The Signaling Server is required at the main office only. It provides the
following functions:
• Terminal Proxy Server (TPS)
— The TPS provides a connection from the IP Phones to the Call
Server. It also provides a connection path from a virtual trunk to the
Call Server.
• Web server for Element Manager and Network Routing Service (NRS)
Manager
A second Signaling Server can be used to provide redundancy in the case of
failure in the primary Signaling Server at the main office.
A similar function to the Signaling Server exists at the SRG.
The Signaling Server supports en bloc signaling, which is standard on the
Signaling Server.
For more information about the Signaling Server, see Signaling Server
Installation and Commissioning (NN43001-312). For more information
about H.323, see IP Peer Networking Installation and Commissioning
(NN43001-313).
Network Routing Service
The NRS application provides network-based routing, combining the
following into a single application:
• H.323 Gatekeeper — provides central dialing plan management and
routing for H.323-based endpoints and gateways.
NRS also contains SIP Redirect Server but SIP Trunks are not supported
on an SRG.
Page 20 of 254 Overview
NN43001-308 Standard 01.02 May 2007
• NRS Database — stores the central dialing plan in XML format for the
H.323 Gatekeeper. The H.323 Gatekeeper accesses this common
endpoint and gateway database.
• Network Connect Server (NCS) — used only for Media Gateway
1000B (MG 1000B), SRG, Geographic Redundancy and Virtual Office
solutions. The NCS allows the Line TPS (LTPS) to query the NRS using
the UNIStim protocol.
• NRS Manager web interface — the NRS provides its own web
interface to configure the H.323 Gatekeeper and the NCS.
The NRS application provides routing services to H.323 devices. The H.323
Gatekeeper can be configured to support H.323 routing services. The H.323
Gatekeeper can reside on the same Signaling Server.
Each system in an IP Peer network must register to the NRS. The NRS
software identifies the IP addresses of systems based on the network-wide
numbering plan. NRS registration eliminates the need for manual
configuration of IP addresses and numbering plan information at every site.
When configuring the NRS it is necessary to enable the NCS. Ensure that the
check box Network Connection Server enabled is checked in the NRS
configuration window of CS 1000 Element Manager.
For information about configuring the NRS, see IP Peer Networking
Installation and Commissioning (NN43001-313).
Supported IP Phones
The SRG supports the following IP Phones:
• IP Phone 2001
• IP Phone 2002
• IP Phone 2004
• IP Phone 2007
• IP Audio Conference Phone 2033
• IP Softphone 2050
• Mobile Voice Client (MVC) 2050
Overview Page 21 of 254
Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide
• IP Phone 1110
• IP Phone 1120E
• IP Phone 1140E
• IP Phone 1150E
• WLAN Handset 2210/2211/2212/6120/6140
• Analog (500/2500-type) telephones
Throughout this document, IP Phones are referred to collectively as
IP Phones.
Main office requirements
The branch office requires the following at the main office:
• CS 1000 hardware, running CS 1000 Release 4.0, CS 1000 Release 4.5,
or CS 1000 Release 5.0.
• IP Peer H.323 Trunk (H323_VTRK) package 399. This package is
required to support H.323 functionality. Package 184 is included with
package 399.
• The main office must have a software Service Level of 2 or higher to
work with the branch office.
• Ensure that you have ordered enough IP user and Virtual Trunk licenses
at the main office to support the SRG 50 or the capacity of your branch
office. The two different IP user licenses at the main office are:
— Basic IP License for the IP Phone 2001, IP Audio Conference Phone
2033, and IP Phone 1110
— IP User License for the IP Phone 2002, IP Phone 2004, IP Phone
2007, IP Phone 1120E, IP Phone 1140E, IP Phone 1150E, IP
Softphone 2050, Mobile Voice Client (MVC) 2050, WLAN
Handset 2210, WLAN Handset 2211, WLAN Handset 2212,
WLAN Handset 6120, and WLAN Handset 6140
• MPLR21148 patch is required for CS 1000 Release 4.0 systems to
support Enhanced UNIStim Firmware Download feature for branch user
IP Phones.
Page 22 of 254 Overview
NN43001-308 Standard 01.02 May 2007
The main office requires the following software packages to support the
specified Basic Network features. For more information, see Basic Network
Features Fundamentals (NN43001-579).
• Network Call Back Queuing (MCBQ) package 38. This package is
required for SRG IP Phones to invoke any queuing feature or ringback
when free.
• Network Speed Call (NSC) package 39. This package is required for
SRG IP Phones to invoke the Network Speed Call feature.
The main office requires the following software packages to support the
specified ISDN Primary Rate Interface features. For more information, see
ISDN Primary Rate Interface Fundamentals (NN43001-569).
• Network Attendant Service (NAS) package 159. This package is
required for analog (500/2500-type) telephones in the branch office to
access attendant services when the attendant is configured on the main
office.
• Network Message Services (NMS) package 175. This package is
required for analog (500/2500-type) telephones in the branch office to
share the voice mail system in the main office. For any configurations
using centralized CallPilot on the main office with one or more branch
offices in separate time zones, the NMS package is required at the main
office for the branch IP Phones.
Optional features to enhance SRG functionality
• Network Alternate Route Selection (NARS) package 58. See Basic
Network Features Fundamentals (NN43001-579).
• Overlap Signaling (OVLP) package 184. This package is optional; it is
required for overlap signaling. It is packaged with H.323 Virtual Trunk
(H323_VTRK) package 399 (Release 4.0 only).
• Emergency Services Access (ESA) package 329. This package is
optional; it is required only to receive 911/ESA features in North
American and some Caribbean and Latin American (CALA) markets.
See Emergency Services Access Fundamentals (NN43001-613).
• Virtual Office (VIRTUAL_OFFICE) package 382. This package is
optional; it is required only for Virtual Office functionality.
Overview Page 23 of 254
Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide
• Network Signaling (NSIG) package 37. This package is optional for
SRG IP Phones to access set-based Network Class of Service (NCOS)
features.
• Adaptive Network Bandwidth Management package 407.
• Alternative Call Routing for Network Bandwidth Management.
For software and hardware requirements for SRG, see the SRG200/400
Release 1.5 Configuration Guide.
Normal Mode and Local Mode overview
Normal Mode and Local Mode overview provides a description of the
following sections:
• Normal Mode
• Local Mode
• Survivability
• Recovery to Normal Mode
• Local Mode operation
• Virtual trunks
IP Phones that are physically located at the SRG but are registered with the
main office are in Normal Mode. The main office provides centralized call
processing for the SRG IP Phones. These telephones are registered to the
main office TPS and are controlled by the Call Server at the main office.
Users of the SRG IP Phones receive the features, key layout, and tones of the
main office Call Server. This provides feature and application transparency
between the branch office and the main office.
Normal Mode
IP Phones that are physically located at the SRG but are registered with the
main office are operating in Normal Mode. In Normal Mode, the main office
provides centralized call processing to all applications transparently to all IP
Phones at the Branch Office. All IP Phones at the Branch, in Normal Mode,
Page 24 of 254 Overview
NN43001-308 Standard 01.02 May 2007
are registered to the main office TPS and are controlled by the Call Server at
the main office.
Users of the SRG IP Phones receive the features, applications, key layout, and
tones of the main office Call Server. This provides feature and application
transparency between the branch office and the main office.
Local Mode
An IP Phone at the SRG may be in Local Mode for different reasons:
1 IP Phone has just booted up and the Main office parameters are not yet
configured.
2 IP Phone cannot communicate to the main office because of a WAN
failure or a failure of the main office components.
In the event that the IP Phones at the branch office lose the connection to the
main office CS1000 call server for any reason (WAN failure, main office call
server failure, main office Signaling Server failure), the SRG 50 reverts to
Local Mode automatically. Essentially, when VoIP connectivity is lost, each
IP Phone loses its Reliable UDP (RUDP) connection with the main office
terminal proxy server (TPS). The IP Phones at the branch office 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 by
installers to meet local language and usage norms.
In Local Mode, the IP users connected at the branch office are under the
control of the SRG 50 call services. As such, the normal main office call
server features are not available. The SRG 50 offers a basic feature set when
in Local Mode which allows IP Phones to continue to make and receive calls
IMPORTANT!
When a telephone or trunk in the main office calls an SRG IP Phone
that has switched to Local Mode due to WAN failure, the call is treated
according to the main office call redirection configuration (such as
forwarding to voice mail or continuous ringback).
Overview Page 25 of 254
Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide
internally within the branch office and over the provisioned local PSTN
interfaces. Basic services, such as transfer, last number redial, and single key
access through the PSTN to a centralized voice messaging system are
supported. Local PSTN access and local Emergency Services access is also
supported. No local applications or Business Communication Manager
features are supported in Local Mode operation.
Analog devices continue to be under the control of the SRG 50 system. It is
the intent of Local Mode to provide continued access to the PSTN for critical
calls and emergency services.
In Local Mode, since the SRG 50 handles all call processing, calls between
two IP phones at the SRG 50 are handled locally as a simple station-to-station
call. When an IP Phone initiates a local PSTN call, the SRG 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 on the appropriate IP Phone.
In the event of a WAN failure, in Local Mode, the IP Phones do not have
access to the main office network over the VoIP trunks. If the appropriate
alternate routes are configured, calls will be routed to the main office or other
branch offices using the available PSTN trunks.
While in Local Mode, the SRG 50 system continues to monitor for a main
office CS 1000 heartbeat signal, and once detected, automatically redirects
phones on an individual basis back to Normal Mode of operation. If a call is
active, the SRG waits until the call is completed before redirecting the
phones; calls in progress are not interrupted. This switch-hitter occurs almost
immediately once the SRG determines that an individual phone can be
redirected. This reinstates the CS 1000 normal user interface and feature set
for the IP Phone user, on a user by user basis.
The SRG 50 system implements the same interface used by the MG 1000B
system to interact with the main office CS 1000 system. This allows the main
office to identify attached clients and the local PSTN as branch office entities,
enabling proper operation of dial plans and E911 access.
In Local Mode, devices that are physically located at the branch office, that
are controlled by the local system and receive a basic telephony feature set,
provide business continuity for the branch office during the WAN or system
failure. The SRG supports a main office heartbeat or reliable UDP signaling
Page 26 of 254 Overview
NN43001-308 Standard 01.02 May 2007
which automatically reregisters users once WAN or system failure has
recovered.
For information about the features supported in Local Mode, see the SRG200/
400 Release 1.5 Configuration Guide.
Survivability
SRG is specifically designed to provide automatic survivability against WAN
failure, main office Call Server failure, main office Signaling Server failure,
and Gatekeeper failure.
SRG supports the Geographic Redundancy feature. For further information
about Geographic Redundancy, see System Redundancy Fundamentals
(NN43001-507).
In the event of a WAN failure, the SRG IP Phones lose communication with
the main office. This causes the SRG IP Phones to reset and register with the
SRG. The IP Phones then operate in Local Mode, providing basic telephony
services delivered by the local SRG system. For further information about
services and features supported on the SRG, see the SRG200/400 Release 1.5
Configuration Guide.
If the main office Call Server fails and call processing services are provided
by an Alternate Call Server, the SRG IP Phones reset and reregister with the
Alternate Call Server and receive call processing services from it. If no
Alternate Call Server is available, the SRG IP Phones go to Local Mode while
the SRG attempts to find an Alternate Call Server by way of the NCS.
If the main office Signaling Server fails and an Alternate Signaling Server is
available, the SRG IP Phones reset and reregister with the SRG. The SRG will
then query the NCS for the Alternate Signaling Server’s IP address. The SRG
will redirect the IP Phone to the Alternate Signaling Server and continue to
receive call processing services from the main office Call Server. If no
Alternate Signaling Server is available, the SRG IP Phones reset and register
with the SRG in Local Mode.
When an IP Phone at the SRG first boots up, the IP Phone attempts to
communicate with the SRG. After communication with the SRG is
established, the SRG redirects the IP Phone to the main office. When the SRG
Overview Page 27 of 254
Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide
IP Phone attempts to register with the main office, the SRG first queries the
Primary NRS (NCS) for the main office Virtual Trunk node IP address to
redirect the IP Phone. If the Primary NRS (NCS) is down or unreachable, the
SRG queries the Alternate NRS (H.323 Gatekeeper), if one is specified. If it
receives a positive response, the SRG IP Phone is redirected to the specified
main office. Otherwise, if neither a Primary or an Alternate NRS (H.323
Gatekeeper) is available, the SRG IP Phone remains in Local Mode, and
receives call processing services from the SRG until communication can be
reestablished.
SRG IP Phones in Normal Mode remain registered with the main office if the
Primary NRS fails and no Alternate NRS is available. They can call any main
office telephone or IP Phones in Normal Mode in other branch offices.
However, they cannot call any SRG analog (500/2500-type) telephones or
any external numbers through the SRG trunks because the Virtual Trunks are
not available. (SRG analog [500/2500-type] telephones are accessible if
alternate routing is available through the PSTN.)
Recovery to Normal Mode
After communication is reestablished with the main office call server, all IP
Phones 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 reestablished complete the call
in Local Mode, and then reregister with the main office after the call is
complete.
Local Mode operation
When an SRG IP Phone is in Local Mode, the user has full access to the
services configured at the SRG (analog devices or analog or digital trunks)
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 IP Phones can access
Page 28 of 254 Overview
NN43001-308 Standard 01.02 May 2007
the main office IP Phones or other branches by routing through the local
PSTN.
Testing the telephone in Local Mode
From Normal Mode, the branch user has the option of going to Local Mode
manually using the Test Local Mode feature, or when the telephone is powercycled. The test can be performed by the user at any time and does not require
a password. This test is invoked from any IP Phone at the branch office.
Nortel recommends testing Local Mode operation after changing the
provisioning for a telephone on the SRG.
To ensure that users do not forget to resume Normal Mode operation, the
SRG redirects the telephone to the main office to return the telephone to
Normal mode. This occurs if the telephone remains registered to the SRG in
Test Local Mode for ten minutes (default setting). Alternatively, the user can
press the Quit key on the phone to return to Normal Mode.
For further information about Local Mode functionality for SRG, see the
SRG200/400 Release 1.5 Configuration Guide.
Virtual Trunks
In order for endpoints in the CS1000 network to access endpoints in local
mode at the SRG or to access the PSTN at the SRG, Virtual Trunks are used
over the LAN/WAN.
Virtual Trunks are software components that provide the trunking features of
the Meridian Customer-Defined Network (MCDN) feature set. Access to
PSTN digital or analog trunks at the branch office occurs through the MCDN
Virtual Trunk.
IMPORTANT!
When a telephone or trunk in the main office calls an SRG IP Phone that
has switched to Local Mode due to WAN failure, the call is treated
according to the main office call redirection configuration (such as
forwarding to voice mail or continuous ringback).
Overview Page 29 of 254
Main Office Configuration for SRG200/400 Release 1.5 Configuration Guide
For more information about Virtual Trunks, see IP Peer Networking
Installation and Commissioning (NN43001-313).
Virtual Trunks are sometimes referred to as H.323 IP Peer Trunks. In the
SRG200/400 Release 1.5 Configuration Guide, Virtual Trunks are referred to
as IP Trunks.
IP Phone calls
When an IP Phone calls another IP Phone, each telephone receives the
address of the other to exchange media directly between the telephones.
When in Normal Mode, an SRG IP Phone calling a main office IP Phone does
not require any trunking to set up the call. However, LAN/WAN bandwidth
is used to provide a media path for the call. For more information on Direct
IP media path functionality, see IP Peer Networking Installation and
Commissioning (NN43001-313).
Bandwidth Management Overview
For a complete overview of Bandwidth Management, see Converging the
Data Network with VoIP Fundamentals (NN43001-260), and for details on
configuration, see “Bandwidth Management” on page 107.
Network Bandwidth Management
Network Bandwidth Management allows for a limit to be placed on the
amount of interzone bandwidth allowed between IP Phones in Normal Mode
at the SRG and the rest of the CS 1000 network.
As well, it allows for the selection of interzone bandwidth codecs for calls
between the IP Phones in Normal Mode and the rest of the CS 1000 network.
Adaptive Network Bandwidth Management
Adaptive Network Bandwidth Management allows the system to dynamically
react to Quality of Service (QoS) degradation and take corrective action.
Page 30 of 254 Overview
NN43001-308 Standard 01.02 May 2007
Network Bandwidth Management Zones
A zone is a collection of IP Phones that:
• share similar IP bandwidth restrictions
• are geographically close to one another
• are all in the same time zone
• are all in the same PSTN dialing plan
The Network Bandwidth Management Zone is made up of the VPNI and the
zone. The VPNI of the main office and all the SRG associated with it must be
the same.
Each SRG must have its own unique zone number and configured in the main
office Call Server and the SRG.
Throughout this document, the term zone is defined as a Bandwidth
Management Zone, not an NRS (H.323 Gatekeeper) Zone. See “Bandwidth
Management” on page 107.
Time of Day
Because the SRG IP Phones, in Normal Mode, receive their clock information
from the main office, which may be located in a different time zone, the main
office must be able to provide a different time of day for these phones.
The time zone of the SRG is configured with the SRG zone at the main office.
The time zone adjusts the main office time for display at the SRG. SRG
telephones then display the correct time of the SRG, rather than that of the
main office. For any configurations using centralized Call Pilot on the main
office with one or more branch offices in separate time zones, the NMS
package is required at the main office for the branch IP Phones.
SRG IP Phone to local PSTN calls
When an SRG IP Phone in Normal Mode dials a local PSTN number, the call
is processed by the main office Call Server. The dialed digits are modified
according to the dialing plan information configured in the zone for the SRG
IP Phone.
Loading...