ASAI and Feature Interactions

Queue Status Displays/Indications

Adjunct-monitored calls (except direct-agent) are included in all existing measurements affecting queue status display and buttons.

Direct-agent calls are not included in any of the existing measurements affecting queue status displays and buttons.

Timed ACW/Agent Pause Between Calls

This feature can not be invoked through ASAI (that is ASAI can not place an agent in timed ACW).

Automatic Callback on Busy/No

Answer

This feature cannot be activated by the adjunct over the ASAI interface.

This feature can be activated by a controlled station user. The callback appears as an incoming call to the controlled station association having the same call_id as the call which had been queued on busy. This call may not be redirected via ASAI Redirect Call. If Automatic Callback is activated after Redirect Call, it will still apply to the principal, not the currently alerting party.

Switch-classified calls and adjunct-routed calls are not allowed to queue on busy Trunk Groups or stations.

Auto-Available Split

Auto-available splits are designed to keep agents logged in and available at all times. Consequently, ASAI agent login, logout, and change work mode requests are disallowed for agents in auto-available splits.

The ECS denies (NAKs with cause CS3/41 — Split not Administered Correctly) any request from the adjunct to:

a.Change the work mode of a member of an auto-available split

b.Log out any member of an auto-available split

An auto-available split can be a notification domain and members of auto-available splits (agents) can be domain-controlled stations. Auto-available splits may be administered as adjunct-controlled splits; however, in such a configuration, adjunct requests to log in, log out, or change work mode for an agent are denied with cause value CS3/41.

Issue 7 May 1998 12-13

Page 315
Image 315
Lucent Technologies 555-230-220 manual Automatic Callback on Busy/No Answer, Auto-Available Split