ASAI and Call Control

Denial (NAK) Causes

The following causes may be issued for non-Switch-Classified calls. For NAKs for Switch-Classified calls, see ‘‘Third Party Make Call and Supported Call Types’’ that follows.

Invalid association (CS0/81)

The association does not exist.

Requested facility not subscribed/provisioned (CS0/50) The user has not subscribed for the requested capability.

Out of Service (CS3/27)

The originator of the call is out of service.

ECS Equipment Congestion (CS0/42)

The ECS equipment is experiencing congestion due to traffic overload.

Call Rejected (CS0/21)

The COR check for completing the call failed.

Mandatory Information Element missing (CS0/96)

A required parameter is missing in the request.

Resources not available (CS3/40)

The request cannot be executed because a call classifier is not available or no trunks are available in the requested trunk group.

The maximum number of calls being controlled has been exceeded.

Incompatible Options (CS3/80)

The designated call options are not compatible with the Third Party Make Call request.

User busy (CS0/17)

The user is busy on another call and cannot originate this call.

No user responding (CS0/18)

The originating address does not pick up the call and cannot be forced off-hook.

Invalid number/domain (CS0/28)

An invalid address or extension number is present in the request.

Agent not member of split (CS3/11)

The agent is not a member of the split in this Direct Agent call.

Agent not logged in (CS3/15)

The agent is not currently logged into a split for this Direct Agent call.

Bearer capability not presently available (CS0/58)

There are incompatible bearer services for the originating or destination addresses. For example, the originator is administered as a data hotline station or the destination is a data extension.

4-6Issue 7 May 1998

Page 132
Image 132
Lucent Technologies 555-230-220 manual Denial NAK Causes