disconnect

Feature Interactions

For Look-Ahead Interflow, the command can be considered either a call acceptance vector command or a call denial vector command.

The command is considered a call acceptance vector command whenever an announcement is included within the command and one of the following is true:

Announcement is available.

Call is queued for an announcement.

Announcement is retried.

The command is considered a call denial vector command whenever one of the following is true:

No announcement is included within the command.

Announcement is included within the command, but the announcement is unavailable.

CMS Interactions

R3 CMS:

Disconnect Command

Database Item

Report Heading

DISCCALLS/DISCTIME

Calls Forced Disc

 

 

 

Calls Busy/Disc

OTHERCALLS/OTHERTIME

Inbound Other Calls

INTIME

Avg Time In Vector

 

 

DISCTIME, OTHERTIME, and INTIME for splits and vectors are tracked according to when the announcement starts. DISCTIME, OTHERTIME and INTIME for VDNs are tracked according to when the trunk idles.

R2 CMS: Calls given forced disconnect are tracked in the FDISCCALLS and FDISCTIME database items. These calls are not shown in standard reports. FDISCTIME is tracked according to when the announcement starts. VECTIME is recorded for the vector, and it is reported as ‘‘Avg Time in Vector.’’

BCMS Interactions

A call that is disconnected via the command is tracked as ‘‘OTHER’’ in the VDN Report.

Issue 4 September 1995 A-47

Page 254
Image 254
AT&T 555-230-520 manual Feature Interactions, Disconnect Command