Event Notification Capabilities
ACK (Positive Acknowledgement) Parameters
No parameters are contained in the acknowledgement for this capability.
Denial (NAK) Causes
ECS issues the following reason as the cause for not executing the request:
■Requested facility (capability) not subscribed/provisioned (CS0/50) The user has not subscribed for the requested capability.
■Service or option not implemented (CS3/63)
■Mandatory information element missing (CS0/96)
A required parameter is missing in the request (for example, domain type).
■Resources not available (CS3/40)
The request cannot be executed because the system limit would be exceeded for the maximum number of event notifications.
■Invalid Number/Domain (CS0/28)
The domain value is not a valid VDN, valid ACD split extension or default value, #####, for all trunk groups.
The call is not monitored by the requesting association.
■ECS not administered correctly (CS3/41)
The domain value is an
■Switching Equipment Congestion (CS0/42)
ECS is not accepting the request at this time because of traffic overload. The adjunct or user may wish to retry the request but should not do so immediately.
■Invalid association (CS0/81)
The association is already in existence.
■Service or option not available (CS3/63)
A maximum of three for R6si, and six for R6r notification associations to monitor an ACD split or VDN domain can be active for a specific ACD split or VDN. Only one notification association can be active for trunk group.
■Invalid Information Element (CS0/100)
The value of a parameter does not match any value to ECS.
Protocol Error (NAK) Cause
■Protocol error (CS0/111)
The Q.932 protocol has been violated.
NOTE:
For more information regarding protocol errors and a complete list of reason codes (cause values), see the DEFINITY Enterprise
