Avaya Communication Manager Administrator's Manual page 1769

Scheduled batch processing
Scheduled batch processing applications are used for periodic database updates (for example, retail
inventory) or distributions (for example, airline fare schedules). These updates are primarily done after
business hours and are often referred to as nightly file transfers. Wideband meets the high bandwidth
requirements at low cost for scheduled batch processing. In addition, wideband allows the
dedicated-access bandwidth for busy-hour switching traffic to be used for these applications after
business hours; no additional bandwidth costs are incurred.
The non-ISDN backup data connection is also appropriate for scheduled batch processing applications.
Administered Connections are used to schedule daily or weekly sessions originating from this
application.
Primary data connectivity
Permanent data connections (those always active during business hours), such as interconnections
between local area networks (LANs), are well suited for Communication Manager when ISDN-PRI
endpoints are used. The ISDN end-to-end monitoring and the endpoint's ability to react to failures
provide for critical data availability needs. With ISDN, endpoints can detect network failures and initiate
backup connections through the server; ISDN endpoints can also establish additional calls when extra
bandwidth is needed.
Any failures not automatically restored by Avaya Communication Manager are signaled to the endpoint
application, which can initiate backup data connections over the same PRI endpoint. Avaya
Communication Manager routes the backup data connections over alternate facilities if necessary.
Networking
All of the wideband networking is over ISDN-PRI facilities (and the emulation of them by ATM-CES)
but may connect to a variety of networks, other domestic interexchange carriers' services, private line,
RBOC services, and services in other countries.
ISDN-PRI trunk groups and channel
allocation
Only ISDN-PRI trunks (and the emulation of them by ATM-CES) support wideband calls to the network.
Wideband's bandwidth requirements have necessitated modification of the algorithms by which trunks
look for clear channels. The following section describes the search methods and their relationship to the
available wideband data services.
Facility lists
A wideband call accessing the network must reside on a single ISDN-PRI facility. Trunks within a trunk
group must be organized based on the facility on which they reside. This is accomplished by compiling a
facility list as trunks are administered to a trunk group; if a trunk is added to a trunk group from a facility
not already on that trunk group's list, that facility is added to the list in an order based on the facility's
signaling group number and interface identifier. In other words, the facility list is compiled in an
ascending order based first on signaling group number and second on the interface identifier assigned to
the facility within the signaling group. For example, if three facilities having signaling group/interface
identifier combinations of 1/1, 1/2, and 2/1 were associated with a trunk group, then a call offered to that
trunk group would search those facilities in the order as they were just listed. Also note that since trunks
within a given facility can span several trunk groups, a single facility can be associated with several
different trunk groups.
Administrator's Guide for Avaya Communication Manager
November 2003
Feature Reference
Wideband Switching
1769