Calls on the network are classified according to their status at completion or according to their type. Cisco Unified Communications Manager supports many extra phone features, such as hold, forward, and conference. Each feature produces a call of a different type. UC Monitor supports the following types of call.
A call attempt in which an endpoint initiated a call that was disconnected before the call was answered. Abandoned calls have an origination time and a disconnect time, but no connect time.
A call attempt that failed to connect during the setup phase. A call setup failure code is reported.
Calls placed on hold and then taken off hold when call conversation data resumes. Putting a call on hold effectively ends a Call Watch for both phones.
Calls are forwarded automatically, on busy, or on no answer. Calls are forwarded to voice mail or to another number. An auto-attendant is often used. Cisco Unity and Unity Express provide this capability.
The final destination, not the dialed destination, of the forwarded or redirected call is shown as the call leg in reports.
Call that used a conference number and appeared to go into the conference bridge. When the number of callers in the conference is reduced to two, the call server connects them directly to each other to free up the conference resource.
The call is answered by a different extension than the one dialed. The extension that picks up the call receives a ringing signal that is based on membership in the pickup group. Similar to forwarded or redirected calls.
The final destination, not the dialed destination, of the forwarded or redirected call is shown as the call leg in reports.
A call is answered and then forwarded to another extension. Multiple call legs are logged:
Also known as a blind transfer. The call is not answered before it is forwarded.
|
Copyright © 2012 CA.
All rights reserved.
|
|