Avaya Communication Manager Administrator's Manual page 464

Managing Data Calls
Wideband Switching
A WAE is treated as a single endpoint and can support only one call. If all DS0s comprising a wideband
access endpoint are in service, then the wideband access endpoint is considered in service. Otherwise, the
wideband access endpoint is considered out of service. If an in-service wideband access endpoint has no
active calls on its DS0s, it is considered idle. Otherwise, the wideband access endpoint is considered
busy.
Multiple WAEs are separate and distinct within the facility and endpoint applications must be
administered to send and receive the correct data rate over the correct DS0s. An incoming call at the
incorrect data rate is blocked.
Guidelines and examples
This section examines wideband and its components in relation to the following specific customer usage
scenarios:
•
Data backup connection
•
Scheduled batch processing
•
Primary data connectivity
•
Networking
Data backup connection
Using wideband for data transmission backup provides customers with alternate transmission paths for
critical data in the event of primary transmission path failure.
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 LANs, are well suited for Avaya 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 running Communication Manager; 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. Communication
Manager routes the backup data connections over alternate facilities if necessary.
464 Administrator's Guide for Avaya Communication Manager
November 2003