Lucent Technologies 8.2 User Manual

Issue 1

April 2000

Features and technical reference 

1193

Busy Verification 

■

Automatic Callback

Once the called party in an Automatic Callback call hangs up, neither 
extension can be busy-verified until both the calling and called parties are 
connected or the callback attempt is canceled (by the activating party or by 
time-out of the callback interval).

■

Call Coverage

Since the busy-verification call to an extension is originated as a priority 
call, the call does not go to coverage.

■

Call Forwarding

Busy verification made to an extension with call forwarding activated, does 
not busy verify the forwarded-to extension. Only the called extension is 
busy verified.

■

Call Waiting Termination

You cannot verify an extension that called an active telephone and is 
receiving call-waiting ringback tone unless the extension has an idle call 
appearance.

■

Conference

The system denies busy verification of any extension involved in a 
conference call of more than five people. However, the system does allow a 
busy verification of any extension involved in a conference call of 5 or 
fewer parties. The system also denies busy verification of a trunk on a 
6-party call.

■

Data Privacy

Busy verification is denied if it would cause a bridging attempt on a 
telephone that has activated Data Privacy.

■

Data Restriction

The system denies Verify if Data Restriction is active on a call, and a busy 
verification bridging attempt is made on that call.

■

Hold

Busy verification of a multiappearance telephone is denied if all call 
appearances have calls on hold.

■

Individual Attendant Access

An attendant cannot make a busy verification of another individual 
attendant console or of the attendant group.