ASAI and Call Control
Denial NAK) Causes
The ECS issues the following reason for denying the request:
■Invalid association (CS0/81)
The association is already in existence.
■Requested facility not subscribed/provisioned (CS0/50) The user has not subscribed for the requested capability.
■Invalid call_id (CS3/86)
The requester has sent an invalid call_id (call does not exist, has been cleared).
■Invalid Information Element contents (CS0/100)
The call_id is outside the range of the maximum call_id value.
■Service or option not available (CS3/63) The call is already being controlled.
■Mandatory Information Element missing (CS0/96) A required parameter is missing in the request.
■Resources not available (CS3/40)
The maximum number of calls being controlled has been exceeded.
■ECS equipment congestion (CS0/42)
The ECS is not accepting the request at this time because of traffic congestion. The adjunct or user may wish to retry the request but should not do so immediately.
Protocol Error (NAK) Cause
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,
