ASAI and Call Control

Denial (NAK) Causes

The ECS issues one of the following reasons as the cause for denying the request:

Invalid association (cause CS0/81).

Request made on other than call control associations (cause CS0/111).

Invalid message (missing IE) (cause CS0/96).

Invalid IE contents (cause CS0/28).

A party specified is not supported by this feature (for example, maps to announcements, extensions without hardware, etc.) (cause CS0/28).

A specified party is not part of the call (cause CS0/100) (for example, a two-party call with the talker still alerting).

Capacity exceeded (CS3/40).

The call is not in the correct state (cause CS3/63).

The request to disconnect from ALL parties was not granted because there were no eligible (talker) parties on the call (cause CS0/98).

The feature has not been administratively enabled (CS0/50).

Considerations

The listener must be listen-disconnected before being listen-reconnected.

All listen-disconnected connections will be automatically restored to normal operation if the ASAI link controlling the call fails.This means that the listener will no longer be disconnected and will be able to hear all speech and tones on the call.

Issue 7 May 1998 4-55

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