
ASAI and Call Control
Third Party Reconnect
The adjunct uses this controlling capability to reconnect an
Information Flow
The adjunct expects a response to its request.
The ECS either:
—Reconnects the party to the call after validating the parameters, or
—Denies the request
Third Party Reconnect Parameters
party_id | Identifies the party to be reconnected |
ACK (Positive Acknowledgment) 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:
■Invalid association (CS0/81) The association does not exist.
■Invalid number/domain (CS0/28) The party_id is incorrect or invalid.
■Invalid Information Element contents (CS0/100)
The party_id value of the request is invalid. For example, a Third Party Reconnect is sent for the destination of a ringing call (the call is ringing and not yet answered at that endpoint). The party_id specified in the party_id Information Element has not passed through the connected stage and is therefore invalid.
■Message not compatible with call state (CS0/98)
The party is not currently in the “hold” state so it cannot be reconnected. The party was
■Resources not available (CS3/40)
The host attempted to connect a seventh party to a