ASAI and Call Control

ACK (Positive Acknowledgement) Parameters

No parameters are contained in the acknowledgement for this capability.

Denial (NAK) Causes

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

Mandatory Information Element missing (CS0/96) The party_id is missing from the request.

Invalid number/domain (CS0/28)

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

Invalid association (CS0/81) The association does not exist.

Both party_id and resource_id are specified (CS0/80)

Resource_id specifies a tone resource and one is not active on the connection, or the active tone is ringback (CS0/82)

A drop that is not allowed was requested (CS3/12)

A drop was requested while the trunk was in the wrong state (for example, prior to finishing dialing).

Message not compatible with call state (CS0/98)

The call is not currently active or is in a hold state and therefore cannot be dropped.

Invalid Information Element contents (CS0/100)

The party_id value is invalid; for example, it is out of range.

Protocol Error (NAK) Causes

The ECS issues the following cause for generating a protocol processing error:

Protocol error (CS0/111)

The Q.932 protocol has been violated or the capability invoked is not consistent with this association. For example, invoking the Third Party Make Call capability on a Domain Control association is inconsistent.

NOTE:

For more information regarding protocol errors and a complete list of reason codes (cause values), see the DEFINITY Enterprise Communications Server CallVisor ASAI Protocol Reference, 555-230-221.

4-66Issue 7 May 1998

Page 192
Image 192
Lucent Technologies 555-230-220 manual ACK Positive Acknowledgement Parameters