Nortel Networks Remote Gateway 50 - Manual (Page 147)

Alternative Call Routing for Network Bandwidth Management Page 147 of 258
Main Office Configuration for Survivable Remote Gateway 50 Configuration Guide
by the same Central Office, PSTN calls can use the trunks at the main office.
However, if the two systems are located at a great distance from each other,
it may make sense to program the main office to use trunks at the branch
office for alternately routed calls.
If there is a location with multiple NXX codes for DID users, it is possible to
translate and outpulse calls properly as long as each NXX has a unique DN
range. Non-DID users can be reached through the attendant console, by
deleting the ALTPrefix and the DN dialed and inserting the digits in the
Listed Directory Number (LDN).
When calls are rerouted to use the PSTN instead of the station-to-station IP
network, there may be a loss of feature functionality normally available for
station-to-station calls. Features that are not available over the PSTN are not
available to the user.
This feature does not apply to virtual trunk calls. It only applies to
station-to-station calls, and routes them over the PSTN or MCDN network.
Virtual Trunk calls already have this feature and can be alternately routed
using traditional methods (such as NARS), which is outside the scope of this
feature.
Alternative Call Routing for NBWM does not apply to users who are
registered in local mode to the Branch Office.
Calls that are in an ACD queue cannot be alternately routed by this feature.
These calls remain in the ACD queue until an ACD agent and sufficient
bandwidth are available.
Music on Hold is not affected by this feature.
A QoS0038 message prints out when insufficient bandwidth is detected
between two zones. A QoS0039 message prints out when the Alternative Call
Routing for NBWM feature is invoked.
If a user at a branch office attempts to make a conference call, Alternative
Call Routing for NBWM is not invoked.