12.4.3.1. ACD WHISPER ANNOUNCEMENT Feature Activation 
The ACD Whisper Announcement feature can be activated from any properly
classmarked supervisor set from the initial dial state only (see Section 165.4,
"Administration" for AMO commands).
The ACD Whisper Announcement feature can be activated by pressing
a feature key or by dialing a feature access code (see Section 165.4,
"Administration" for AMO commands). If a feature
key is used, then CP will receive DB_CP_E_SC_WHISPER_ANN_KEY event. If
a feature access code was dialed, then digit analysis shall return DB_KZP_WHISPER_ANN.
The supervisor's class of service is checked to determine if the ACD
Whisper Announcement feature can be activated from this line.
If not authorized, negative acknowledgement tone is connected and
a NOT AUTHORIZED display is provided.
If authorized to activate ACD Whisper Announcement, a system flag
is checked to determine whether the target party is to be specified by
extension number or by agent logon id (see Section 165.4,
"Administration" for AMO commands).
The appropriate display (ENTER LOGON ID or ENTER STATION
NO.) will be provided along with Recall dial tone.
If the addressing is to be done by extension number, the directory
number of the target party is collected and digit analysis is called
to verify that a valid extension number has been dialed. A valid extension
number is indicated by the return 'DB_KZP_TLN'. The loden of the target
party is retrieved.
If the addressing is by agent logon-id, then the logon-id digits are
collected. After the agent's logon-id number is collected, the loden
of the device using that logon-id is determined.
A check is made to determine if the target agent has the proper classmark
to be monitored. Otherwise negative acknowledgement tone is connected
and a NOT AUTHORIZED display is sent to the supervisor's set.
If the agent is properly classmarked, the 'ACD_MONITOR_ACT' attribute
is set on in the dev_attribute field and the loden of the monitoring
party is stored in the 'MONITOR_LODEN' field of the DYNAMIC_DEVICE table
of the target party. DB_GEN_ATTR_WHISANN_ACTIVE attribute is set on in
the monitor CPB.
The loden of the target party is stored in the 'MONITORED_LODEN' field
of the CP_DYNAMIC_DEVICE table of the monitoring party.
The call status of the target party is now evaluated to determine
whether a monitor call can be immediately established.
If the current call status of the target party does not permit a monitor
call to be immediately established, the monitoring device enters into
a special call state - 'MONITORING_PTY_WAIT', DB_CP_CDSA640 (or DB_CP_CLS640
if anate).
If the current call status of the target party allows the monitor
call to be established (call is a 'MONITORABLE CALL'), a monitoring conference
call is established between the monitoring party, the target party, and
the non target party.
A 'MONITORABLE CALL' is defined as follows:
- The call is in a stable two party talk call condition. This precludes all non talk conditions such as ringing, ringback, dialing, etc. This also precludes all multiparty call conditions such as consultation and all forms of conferencing.
- The attendant is not a member of the two party call.
- The call is not any type of DATA call.
- The DB_GEN_ATTR_GEST_ZUST attribute is set in the GENERAL_ATTRIBUTES field of the CPB.
- The parties in the call must be in one of the call processing call states as indicated in the following table.
|
DEVICE TYPE
|
MONITORABLE STATE
|
TARGET STATE WHILE MONITORED (WHISPERED)
|
NON TARGET STATE WHILE MONITORED (WHISPERED)
|
|
ANATE
|
DB_CP_CLS500DB_CP_CLS520
|
DB_CP_CLS541DB_CP_CLS543
|
DB_CP_CLS542DB_CP_CLS544
|
|
DIGITE / Phan / KS / SEKR
|
DB_CP_CDSA500T
|
DB_CP_CDSA541T
|
DB_CP_CDSA542T
|
|
Funct device
|
DB_CP_CSF500
|
Not Allowed
|
DB_CP_CSF542
|
|
ANALOG trunks
|
DB_CP_CTS500
|
Not Allowed
|
DB_CP_CTS542_NM
|
|
CORNET
|
DB_CP_CNW500
|
Not Allowed
|
DB_CP_CNW542_NM
|
The monitoring party is responsible for allocating the needed resources
(conference cells, common cpb, and all paths) to establish the monitor
conference call. When all of the resources have been allocated, the monitoring
party sends a 'MONITOR_BEG' event to the target party.
When the target party receives the 'MONITOR_BEG' event, the target
party sends a 'PARTN_MON_BEG' event to the non-targeted member in the
call.
The processing to set up the whisper monitor call is essentially similar
as that for establishing a silent monitor call using an override conference
call with three parties: monitoring party, target and non target. No
override tone is connected to the conference cell.
Feature activation:
- The monitoring party's speech connection is a full path connection to the monitoring conference. The monitoring party enters a 'MONITOR TALK' DB_CP_CDSA540T (or DB_CP_CLS540 if anate) call state.
- The target speech connection is a full patch connection to the monitoring conference. The target enters a 'MONITORED PARTY TALK' call state.
- The non target's speech connection is a half path connection (LISTEN ONLY) to its partner (target). Non target enters a 'NON MONITORED TALK' call state.