Sourced in Canada.
The information in this document is subject to change without notice. The statements, configuration, technical
data, and recommendations in this document are believed to be accurate and reliable, but are presented without
express or implied warranty. 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.
All other trademarks are the property of their respective owners.
Revision history
December 2007
Standard 02.02. This document is up-issued to support CS 1000 Release
5.0 for SRG 50 Release 3.0. This document includes
configuration at the main office.
August 2007
Standard 02.01. This document is up-issued to support CS 1000 Release
5.0 for SRG 50 Release 3.0.
June 2007
Standard 01.02. This document is up-issued to remove the Nortel Networks
Confidential statement.
May 2007
Standard 01.01. This document is up-issued to support Communication
Server 1000 Release 5.0. This document contains information previously
contained in the following legacy document, now retired: (553-3001-207).
This document is up-issued to include updated information due to CR
Q01587820. See "Codec negotiation" (page 95).
3
SIP Trunks
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.
Other9
Subject9
Intended audiences9
Related information9
Description11
Contents11
Survivable Remote Gateway11
Main office hardware description14
Main office requirements 17
Optional features to enhance SRG functionality 18
Normal Mode and Local Mode overview 19
Time of Day 24
SRG IP Phone to local PSTN calls25
IP Phone to analog (500/2500-type) telephone calls 25
Setting up the main office31
Contents31
Introduction31
SRG information required by the main office31
Main office information required by the SRG 32
Zone parameters34
Branch office IP Phone configuration at the main office38
SIP IP Trunks configuration at the main office 40
Contents43
Overview43
On-net dialing plan 43
Off-net dialing plan 45
Routing calls45
SIP/H.323 zones45
Zone-based digit manipulation 46
Configuring the dialing plan for PSTN access to SRG users in Normal Mode48
Dialing plan examples 65
Bandwidth Management95
Contents95
Introduction95
Codec negotiation95
Configuring Bandwidth Management parameters 101
Adaptive Network Bandwidth Management110
Tandem Bandwidth Management overview 129
Dialing Plan Overview 130
Network using Uniform Dialing Plan132
Network using Coordinated Dialing Plan154
Alternative Call Routing for Network Bandwidth Management159
Contents159
Description159
Operating parameters174
Feature interactions175
Feature packaging176
Feature implementation using Command Line Interface176
Feature implementation using Element Manager 178
Diagnostics180
Maintenance184
Feature operation187
Emergency Services configuration189
Contents189
Overview189
Emergency Services Access190
Emergency Services for Virtual Office200
On-Site Notification201
Configuring the NRS for ESA SPN 201
Testing the ESDN number 202
Configuring ESA using Element Manager202
Emergency Service using Special Numbers (SPN) 202
Appendix A Media Redirection Scenarios209
List of terms213
Index218
Procedures
Procedure 1Configuring ESN and SRG zones34
Procedure 2Configuring branch office IP Phones at the main office using
LD 1139
ProcedureConfiguring SIP IP Trunks 40
Procedure 3Configuring the main office49
Procedure 4Configuring the NRS database 57
Procedure 5Configuring the branch office 60
Procedure 6Testing PSTN access using an SRG IP Phone64
Procedure 7Printing intrazone and interzone statistics for a zone106
Procedure 8Displaying CAC parameters for one or more zones124
Procedure 9Provisioning Tandem Bandwidth Management145
Procedure 10Accessing the Zones web page 178
Procedure 11Printing zone ALTPrefix 181
Procedure 12Show Status183
Procedure 13Enabling behavior at a zone185
Procedure 14Suppress Alternative Call Routing for NBWM alarms187
Procedure 15Configuring the main office195
Procedure 16Configuring the branch office zone 200
Procedure 17Testing ESDN using an SRG telephone 202
Procedure 18Upgrading firmware207
The CS 1000 Main Office Configuration for SRG50 (NN43001-307) for CS
1000 Release 5.0 includes support for SRG 50 Release 3.0.
The following sections detail what is new in CS 1000 Main OfficeConfiguration for SRG50 (NN43001-307) for CS 1000 Release 5.0 .
Other
CS 1000 Main Office Configuration for SRG50 (NN43001-307) includes
the following changes:
•
Replaced instances of OTM 2.2 with TM 3.1.
•
Updated Element Manager with enhancements.
•
Added support for new IP Phones.
•
Removed instances of CS 1000S and Small Systems.
•
Removed instances of Terminal Numbers (TN) in "c u" format. Only TN
in "l s c u" format are supported.
9
Subject
This document describes the CS 1000 Main Office Configuration for
SRG50 (NN43001-307) for software Release 3.0 for CS 1000 Release 5.0.
Information in this document complements information found in documents
in the Communication Server 1000 documentation suite. For information
about how to configure the SRG 50, see SRG50 Configuration Guide(NN40140-500) at w
Documentation > Communication Servers > BCM.
Intended audiences
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.
This section contains information about the following topics:
•
"Survivable Remote Gateway" (page 11)
•
"Main office hardware description" (page 14)
•
"Main office requirements" (page 17)
•
"Optional features to enhance SRG functionality" (page 18)
•
"Normal Mode and Local Mode overview" (page 19)
•
"Capacity" (page 26)
•
"Branch office dialing plan" (page 27)
•
"Branch office and SRG 50 terminology" (page 28)
Survivable Remote Gateway
The Survivable Remote Gateway (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.
11
SRG 50 Release 2.0 provides the following:
•
extends the supported number of survivable IP users from 32 to 80
•
extends support for the IP Phone 1120E, IP Phone 1140E, IP Audio
Conference Phone 2033, and WLAN 2212
See "Supported IP Phones" (page 16) for a complete list of supported
IP 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
VoIP and Application Gateway
Local Mode = Basic telephony
features
VoIP and Application Gateway
Local Mode = Basic telephony
features
A more cost effective small branch
office solution.
Provides H.323 trunking.
For more information, see CS
1000 Main Office Configuration
Guide for SRG 50 (553-3001-207).
VoIP and Application Gateway
Local Mode = Basic telephony
features
Feature Parity with SRG 50,
new OS, and extended IP Phone
support.
Provides H.323 trunking.
For more information, see Main
Office Configuration Guide for
SRG 200/400 Release 1.5
(NN43001-308).
VoIP and Application Gateway
Local Mode = Basic telephony
features
Extends IP Phone support and
survivable IP users from 32 to 80.
Provides H.323 and SIP trunking.
For more information, see CS
1000 Main Office Configuration
Guide for SRG 50 (553-3001-207).
The SRG is implemented on a BCM 50 platform and is connected to a CS
1000 at the main office through Virtual Trunks over a reliable IP WANaccess
facility. 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 registered to
both the main office and branch offices. The SRG provides call processing
functionality to phones in local mode and local analog devices. The SRG
supports business continuity and call failover through digital and analog
trunk access to the local Public Switched Telephone Network (PSTN).
VoIP and Application Gateway
Local Mode = Basic telephony
features
Extends IP Phone support to
include the IP Phone 1110.
Supports On Site Notification for
E-911 calls.
Provides H.323 and SIP trunking.
100% CS 1000 feature and
application redundancy in
survivable mode. Designed and
positioned for larger IP branch
offices.
Provides H.323 and SIP trunking.
Provides survivability with the
addition of Call Processor Pentium
Mobile (CP PM).
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/WAN outage, the
SRG automatically switches to Local mode and provides basic telephony
service to the phones located at the branch office. This enables the IP
Phones to survive the outage between the branch office and the main office.
To ensure proper operation of the SRG solution it must be configured to
support a common dialing plan with the CS 1000 main office. 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 "SRG network" (page 14) shows the networking among the main
office, SRG, and IP Phones.
Figure 1
SRG network
Main office hardware description
The main office must be one of the following systems:
•
CS 1000E
•
CS 1000M Cabinet
•
CS 1000M Chassis
•
CS 1000M HG
•
CS 1000M SG
•
CS 1000M MG
Throughout this document, references to CS 1000 systems encompass
all CS 1000 system types.
The diagrams throughout this documentation show a CS 1000E main
office. 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 SRG50 Configuration Guide (NN40140-500).
The following Signaling Servers are available for CS 1000 Release 5.0 :
•
ISP1100
•
HP-DL320-G4
•
IBM-X306m
•
Common Processor Pentium Mobile (CP PM)
The Signaling Server is required at the main office only. It provides the
following functions:
•
Terminal Proxy Server (TPS)
The TPS provides a connection from the IP Phones to the Call Server
and a connection from a Virtual Trunk to the Call Server.
•
H.323 Gateway (Virtual Trunk)
•
SIP Gateway (Virtual Trunk)
•
CS 1000 Element Manager Web Server and Network Routing Service
(NRS)
Main office hardware description15
•
NRS, consisting of:
— SIP Redirect Server NRS
— H.323 Gatekeeper
— Network Connection Service (NCS)
•
Personal Directory
A second Signaling Server can be used to provide redundancy in the case
of a failure in the primary Signaling Server at the main office.
A similar function to the Signaling Server is used at the SRG when the
phones are in local mode.
The Signaling Server supports en bloc signaling which is standard on the
Signaling Server.
For more information about the Signaling Server, see Signaling ServerInstallation and Commissioning (NN43001-312). For more information
about H.323 and overlap signaling, see IP Peer Networking Installationand Commissioning (NN43001-313).
Network Routing Services
•
The Network Routing Service (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.
•
SIP Redirect Server NRS — provides central dialing plan management
and routing for SIP-based endpoints and gateways. SIP Trunks are
used for Voice packet traffic alone.
•NRS Database— stores the central dialing plan in XML format for the
H.323 Gatekeeper, and the SIP Redirect Server. The H.323 Gatekeeper
and the SIP Redirect Server accesses this common endpoint and
gateway database.
•
Network Connect Server (NCS) — used only for Media Gateway
Controller (MGC) based MG 1000B, SRG, Geographic Redundancy,
and Network-wide Virtual Office solutions. The NCS allows the Line
TPS (LTPS) to query the NRS.
•
NRS Manager web interface— the NRS provides its own web interface
to configure the H.323 Gatekeeper, SIP Redirect Server, and the NCS.
The NRS application provides routing services to H.323 devices and
SIP-compliant devices. The H.323 Gatekeeper can be configured to
support H.323 routing services, while the SIP Redirect Server NRS can be
configured to support SIP routing services. The H.323 Gatekeeper and the
SIP Redirect Server NRS 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 NetworkingInstallation and Commissioning (NN43001-313).
Supported IP Phones
Table 2 "IP Phone support " (page 16) shows the supported IP Phones
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 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
— IP User License for the IP Phone 2002, IP Phone 2004, IP Phone
2007, IP Phone 1120E, IP Phone 1140E, IP Softphone 2050, Mobile
Voice Client (MVC) 2050, WLAN Handset 2210, WLAN Handset
2211, and WLAN Handset 2212
The main office requires the following software packages to support
the specified Basic Network features. See Basic Network FeatureFundamentals (NN43001-579) for more information about these features.
•
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. See ISDN Primary RateInterface Fundamentals (NN43001-569) for more information about these
features.
•
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.
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.
•
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.
•Alternative Call Routing for Network Bandwidth Management.
Forsoftware and hardware requirements for SRG, see SRG50 Configuration
Guide (NN40140-500).
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
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, 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
Users at the branch office may be in Local Mode, or survivable mode for
two different reasons:
1. IP Phone has just booted up.
2. IP Phone cannot communicate to the main office because of a WAN
failure or a failure of the main office components.
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).
In the event that the IP Phones at the branch office lose the connection to
the main office CS 1000 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 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-over 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 which automatically reregisters users once WAN or system failure
has recovered.
For information about the features supported in Local Mode, see SRG50Configuration Guide (NN40140-500).
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 SRG50Configuration Guide (NN40140-500).
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 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 IP Phone attempts to register with the main office, the SRG first
queries the Primary NCS for the main office Virtual Trunk node IP address
to redirect the IP Phone. If the Primary NCS is down or unreachable, the
SRG queries the Alternate NRS (H.323 Gatekeeper/SIP Redirect Server),
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/SIP Redirect Server) 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 NCS fails and no Alternate NCS 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 an
H.323 Gatekeeper/SIP proxy server, which could route call properly in case
of an NRS failure, is not available.
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 the main office IP Phones or other branches by routing
through the local PSTN.
From Normal Mode, the branch user has the option of going to Local Mode
manually using the Test Local Mode feature, or when the telephone is
power-cycled. The test can be performed by the user at any time and
does not require a password. This test is invoked from any IP Phone at
the branch office.
Nortel recommends testing Local Mode operation after changing the
provisioning for a telephone on the SRG.
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 SRG50Configuration Guide (NN40140-500).
Virtual Trunks
In order for endpoints in the CS 1000 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.
Normal Mode and Local Mode overview23
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.
Virtual Trunks are sometimes referred to as SIP or H.323 Virtual Trunks. In
the SRG50 Configuration Guide (NN40140-500), Virtual Trunks are referred
to as IP Trunks.
For more information about Virtual Trunks, see IP Peer NetworkingInstallation and Commissioning (NN43001-313).
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 Installationand Commissioning (NN43001-313).
For a complete overview of Bandwidth Management, see the Converging
the Data Network with VoIP (NN43001-260) and for details on configuration,
see "Bandwidth Management" (page 95).
Network Bandwidth Management
Network Bandwidth Management allows for a limit to be placed on the
amount of interzone bandwidth allowed between IP Phones in Normal Mode
at the SRG and the rest of the CS 1000 network.
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.
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"
(page 95).
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 phones then display the correct time of the SRG, rather than that of
the main office. For any configurations using centralized Call Pilot on the
main office with one or more branch offices in separate time zones, the
NMS package is required at the main office for the branch IP Phones.
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.
The call is configured to be routed over the Virtual Trunk to the branch
office. The SRG then tandems the call to the local PSTN. Likewise, long
distance calls can also be configured.
If you use one Access Code for both local and long distance calls, and that
Access Code is associated with a branch office zone, all calls (local and
long distance) are routed through the SRG
Bandwidth Management Overview25
IP Phone to analog (500/2500-type) telephone calls
When an IP Phone in Normal Mode at the SRG calls an analog
(500/2500-type) telephone of the same SRG, the call is processed at the
main office Call Server. A Virtual Trunk route is selected according to the
digits dialed. The call is routed over a Virtual Trunk to the branch office. The
SRG processes the incoming Virtual Trunk call and terminates it to the
local analog (500/2500-type) telephone. Since this is a call between IP and
circuit-switched devices, a DSP resource on a Media Card is allocated and
connected to the analog (500/2500-type) telephone. The IP address of the
DSP resource is returned to the main office Call Server so a direct media
path between the IP Phone and the DSP resource can be set up when the
call is established. See IP Peer Networking Installation and Commissioning(NN43001-313) for details.
Conference calls
When an SRG user initiates a conference call, the conference facilities of
the main office are used. This means that in a conference among three
SRG users, the LAN/WAN bandwidth of three media paths is used. The
calls are controlled by the main office, except in Local Mode. In Local Mode,
SRG users do not have access to conferencing.
Networking consideration
A fault condition can occur if IP Phones use a different route to the main
office than that used by the SRG.
If the network is planned so that IP Phones use a different route
to the main office than that used by the SRG, a fault condition
can occur. When the SRG can reach the main office but the IP
Phone cannot ping the main office due to a network outage, an
IP Phone registration can force the telephone into a cycle of
registering locally, being redirected to the main office, rebooting,
and then registering locally again. When this cycle occurs, further
diagnose the network outage.
Each CS 1000 main office can support up to 255 branch offices, which can
be made up of any combination SRG and MGC based MG 1000B. SRG 50
Release 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 the
maximum 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 greater
than the capacity of the main office. See one of the following documents to
determine the total number of phones your system can support:
•
CommunicationServer 1000E Planning and Engineering (NN43041-220)
•Communication Server 1000M and Meridian 1 Large System Planning
and Engineering (NN43021-220)
Virtual Trunks capacity
The SRG capacity to support a number of simultaneous calls depends on
the 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 Virtual Trunks (H.323 or SIP) are supported.
In Normal Mode, the codec selection used is controlled by specific
programming of the CS 1000.
In Local Mode, if the WAN has failed, Virtual Trunks between the SRG
and CS 1000 cannot be established. However, the SRG will continue to
convert calls from IP terminals for communication through the PSTN. Nortel
recommends you use G.711 codec.
Since IP Phone users can be located at a branch office equipped with an
SRG, the routing of calls to the local gateway is important (especially when
toll charges apply to calls made from the central Call Server that controls
the telephone). The administrator can configure digit manipulation through
zone attributes for IP Phones to select a main office or branch office that
provides PSTN access local to the destination of the call.
Calls from the PSTN to users within the network can be routed with the
various ESN numbering plan configurations.
To access local PSTN resources, outgoing calls can be routed using ESN
as well as zone parameters that enable digit insertion. The zone parameters
force calls made by an SRG user to be routed to the desired local PSTN
facilities.
Outgoing calls can include local and, optionally, long distance calls.
Branch office dialing plan27
ATTENTION
Nortel recommends that the Branch User ID (BUID) be the same at the
branch office as the DN at the main office. A BUID has a maximum of 15
digits. Under the recommended Coordinated Dialing Plan (CDP), the BUID
can 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 must be
an ESN compliant DN. See "ESN Access Codes" (page 27).
The SRG only supports only one dialing plan option at a time. CDP and
UDP dialing plan options cannot be configured at the same time in the
same system.
For more information about dialing plans and configuration, see "Dialing
Plan configuration" (page 43). For more information about the branch
office dialing plan, see CS 1000 Main Office Configuration for SRG50
(NN43001-307).
ESN Access Codes
ESN data is configured with two Access Codes, called AC1 and AC2.
AC1 normally applies to long distance calls, whether placed on or off the
customer’s private network (for example, dialing 6). AC2 normally applies to
local calls (for example, 9). For more information, see Electronic SwitchedNetwork Reference—Signaling and Transmission (NN43001-280).
For SRG users in Normal Mode, the main office provides music to the user
if Music on Hold is provisioned. The use of the G.729A/AB codec between
the main office and the branch office can impact the music quality.
The following is a list of limitations for SRG 50 Release 3.0:
•
When an IP Phone is in Local Mode, the SRG 50 does not provide all
the features as those provided by the CS 1000 main office. In Local
Mode, the SRG provides basic features, basic call handling, and basic
routing capabilities only.
•
When an IP Phone is in Local Mode, the SRG 50 does not support IP
Phone Key Expansion Module or Expansion Module for IP Phone 1100
Series.
•
You cannot configure the BUID and MOTN using the IP Phone.
Configure the BUID and MOTN using SRG Element Manager.
•
The SRG and the CS 1000 are configured separately. There is no
single management paradigm or application to update both the CS 1000
and the SRG. Use Element Manager to configure the SRG, and use
standard configuration tools to configure the CS 1000.
SRG 50
•
Virtual Office Login is not supported in Local Mode.
•Language, Volume, and Contrast settings in the SRG are not
synchronized with the CS 1000 settings which causes a potential
mismatch in settings between Normal Mode and Local Mode.
•
Language options available on the CS 1000 may not be available on
the SRG.
•
For the CS 1000 Release 5.0 Alternate Routing for Network Bandwidth
Management feature, the SRG does not support an automatic
redirection of IP trunk calls through the PSTN when such calls are
blocked by the CS 1000 due to bandwidth availability.
•
Multiple ESDN is not supported.
•
VLAN tagging is not supported. However, VLAN tagging is achieved
by using an external router.
•
Active Call Failover is not supported.
•
SIP trunks are used only for voice packet traffic alone. H.323 trunking
is used for main office and Gatekeeper/NRS discovery, polling of WAN
link, as well as voice traffic.