Supervisory Monitoring Error Conditions - 3Com 3C10402B Administrator's Manual

Supervisory
Monitoring Error
Conditions
You cannot invoke Supervisory Monitoring if the supervisor is already
■
on an active call.
When you invoke Barge-in and either the caller or the agent
■
subsequently puts the call on hold, you are still able to talk to the
remaining party.
The telephone user does not need to be an agent to be in a monitored
■
call, nor does this user have to be logged in.
An agent in a monitored call can transfer a call to another party.
■
A primary telephone configured with bridged extensions could receive
■
a call that an associated secondary telephone, which is not a part of a
hunt group, ACD, or route point, can answer.
Restrictions in Monitoring ACD Calls There are a few cases in which
you cannot monitor an ACD call, though the system is processing the call
as an ACD call.
You cannot monitor ACD calls going through call coverage to voice
■
mail or Auto Attendant.
Multiple supervisors cannot monitor the same agent at the same time.
■
Supervisory Monitoring is limited to one active supervising session per
agent.
This section describes the most common Supervisory Monitoring errors
and the results that occur. If appropriate, the table lists corrective
measures that you might take to recover from errors.
Feature Interaction Errors
■
Validation Errors
■
Supervisory Monitoring Service Errors
■
Device Errors
■
Table 16 Feature Interaction Errors
Event
A feature is active on the supervisor's
phone that prevents Supervisory
Monitoring.
Supervisory Monitoring
Action
The display panel displays an explanatory
error message and the phone returns to
the Ready state.
65