ATT DEFINITY Communications System Generic 3V4 Instructions Manual

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Selective Dropbbbbbbbb
The adjunct uses this controlling capability to disconnect a specific party from a
call.  The party may be a station or a trunk.  For G3V3 and later, a tone resource
(other than ringback) may be dropped from a connection.
Information Flowbbbbbbbbbbbbbbb
The adjunct expects a response to its request.
The switch either:
Ð Drops the party once it has validated the parameters, or
Ð Denies the request if it could not execute the disconnect operation or if the
party_id specified does not exist (invalid parameter)
Third Party Selective Drop Parametersbbbbbbbbbbbbbbb
party_id[mandatory] Identifies the party on the call to be
disconnected.
uui_infoIf there is UUI stored with a call, and if that UUI came from an
ISDN DISCONNECT message or in an ASAI Third Party Drop
Request, and if a party drops from the call and a Drop Event
Report results, then the switch will include the UUI stored with
the call in the Drop Event Report.
UUI received in a successful Third Party Selective Drop on
the ASAI link is stored by the switch with the call for the life of
the call or until overwritten due to a later UUI IE associated
with the call.
resource_id[optional]  Identifies a tone resource to be dropped. If
specified, do not specify party_id.
ACK (Positive Acknowledgement)
Parameters
bbbbbbbbbbbbbbb
None for this capability
Denial (NAK) Causesbbbbbbbbbbbbbbb
The switch 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.
4-42  Issue 4  September 1995 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
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) Causesbbbbbbbbbbbbbbb
The switch 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 Communications
System CallVisor ASAI Protocol Reference
, 555-230-221.
Considerationsbbbbbbbbbbbbbbb
The adjunct must know the association and the party_id of the party on the call
to be dropped.  When a party is dropped from an existing conference call with
three or more parties (directly connected to the switch), the other parties remain
on the call.  If this is a two-party call, the entire call is dismantled.
Only 
connected parties and trunks (in any state) can be dropped from a call.
Held, bridged, and alerting local parties cannot be dropped by the adjunct.
Third Party Selective Drop cannot be used to drop parties from a switch-
classified call while the call is in the process of being classified.  Third Party
Clear Call should be used instead.
Third Party Selective Drop may not be used to drop a call/party out of queue.
Third Party Selective Drop may not be used with resource_id if the tone provided
is not a local tone on the switch (for example, a network-provided tone).
Issue 4  September 1995  
4-43 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Relinquish Controlbbbbbbbb
The adjunct uses this capability to terminate a Call Control association.  The call
itself is not affected by this capability.
Information Flowbbbbbbbbbbbbbbb
The adjunct expects a response to its request.  The switch:
Ð Relinquishes control of the call if the request is valid
Third Party Relinquish Control Parametersbbbbbbbbbbbbbbb
None for this capability
ACK (Positive Acknowledgement)
Parameters
bbbbbbbbbbbbbbb
None for this capability
Denial (NAK) Causebbbbbbbbbbbbbbb
This request receives a NAK for a switch-classified call if the request is made
while the call is being classified (CS0/98).
Protocol Error (NAK) Causebbbbbbbbbbbbbbb
None for this capability
Considerationsbbbbbbbbbbbbbbb
After an adjunct has invoked Third Party Relinquish Control for a call, the same
adjunct or another adjunct can take control of the same call by invoking the Third
Party Take Control capability.
If this call is being monitored (Event Notification active), the adjunct continues to
receive event reports over the event notification association.
This operation does not disconnect any parties from the call; switch call
processing continues for the duration of the call.
4-44  Issue 4  September 1995 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Clear Callbbbbbbbb
The adjunct uses this controlling capability to drop all parties from a controlled
call.
Information Flowbbbbbbbbbbbbbbb
The adjunct expects a response to its request.
The switch either:
Ð Clears the entire call (for example, disconnects all parties) and
acknowledges, or
Ð Denies the request
As the switch is clearing the call:
Every station dropped is in the off-hook idle state.
Any lamps associated with the call are off.
The displays are cleared.
Third Party Clear Call Parametersbbbbbbbbbbbbbbb
None for this capability
ACK (Positive Acknowledgement)
Parameters
bbbbbbbbbbbbbbb
None for this capability
Denial (NAK) Causebbbbbbbbbbbbbbb
The switch issues the following reason as the cause for denying the request and
ending the association:
Invalid association (CS0/81)
The association does not exist.
Issue 4  September 1995  
4-45 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Protocol Error (NAK) Causebbbbbbbbbbbbbbb
The switch 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 Communications
System CallVisor ASAI Protocol Reference
, 555-230-221.
Considerationsbbbbbbbbbbbbbbb
The Third Party Clear Call capability can only clear calls controlled by the Call
Control capabilities.
4-46  Issue 4  September 1995 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Send DTMF Signals
(G3V4)
bbbbbbbb
The adjunct uses this controlling capability to transmit a sequence of DTMF
tones on behalf of a party on the call.
Information Flowbbbbbbbbbbbbbbb
The adjunct expects a response to its request.
The switch either:
Ð Transmits the tones on the senders talk path after it has validated the
parameters, or
Ð Denies the request if it is unable to service it
Third Party Send DTMF Signals Parametersbbbbbbbbbbbbbbb
tx_party_id[mandatory] Identifies the party on whose behalf the DTMF
signals are to be sent. This party must map to a valid,
physical endpoint on the call.
rx_party_id[optional] If present, this parameter is ignored.  A list of up to
5 party_ids that will receive the DTMF signals. If this list is
null, then all parties on the call receive the DTMF signals if
otherwise eligible (that is, if they are connected via ports that
support end-to-end signaling).  See ``Considerations.
char_seq[mandatory] Identifies the character sequence to be
generated (maximum 32).
tone_dur[optional] If present, this parameter is ignored.
pause_dur[optional] If present, this parameter is ignored.
ACK (Positive Acknowledgement)
Parameters
bbbbbbbbbbbbbbb
An acknowledgement is sent when it is determined that the DTMF digits could be
transmitted, not when done transmitting.  There are no parameters contained in
this ACK.
Issue 4  September 1995  
4-47 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Denial (NAK) Causebbbbbbbbbbbbbbb
The switch issues the following reasons as the cause for denying the request
and ending the association:
Mandatory Information Element missing (CS0/96)
The char_seq is missing from the request.  A denial may be sent if
another parameter is missing as well.
Invalid number/domain (CS0/28)
Party_id is out of range or is a party o whose behalf ASAI cannot send
DTMF tones (that is, a party other than a station or a trunk).  Or, call_id is
out of range.
Invalid association (CS0/81)
The request is supported only over call control and domain control
associations.  An attempt has been made to request this service over
another type of association.
Invalid Information Element contents (CS0/100)
A value of an IE is outside the range specified, or a character sequence
with a length of 0 or invalid characters has been supplied.
Service or Option Not Available (CS3/63)
The provided call ID does not exist.
Message Not Compatible with Call State (due to call state) (CS3/98)
DTMF signals can be generated only for active calls on which no other
signaling tones are present.  Or, the switch capacity for simultaneous
sending of DTMF digits is full.  Also, the call must not be in vector
processing or in a non-active state.  The switch has detected that local,
audible signals, including (PBX) dial tone, busy tone, ringback tone,
intercept tone, or Music-on-Hold/Delay are currently being received.
Reorder/Denial (CS3/42)
A request to send DTMF on a conference call with more than 5 parties is
denied.
Protocol Error (NAK) Causebbbbbbbbbbbbbbb
The switch 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 Communications
System CallVisor ASAI Protocol Reference
, 555-230-221.
4-48  Issue 4  September 1995 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Considerationsbbbbbbbbbbbbbbb
The Send DTMF Signals feature conforms to the CSTA Send DTMF Digits
service specification in CSTA Version II.
DTMF signals may be sent to any extension type on the call.
If a character sequence with a length greater than 32 is supplied, only the
first 32 characters in the sequence will be accepted (the remaining
characters will be ignored).
The switch does not provide any signal to the adjunct when transmission
has completed.
Each digit sent will require 350 ms.  Interdigit timing is 100 ms.
While DTMF signals are being transmitted, all parties on the call will be
disconnected from the talk path.
If a party drops from the call while tones are being sent and others remain
on the call, signals will continue to be sent to the remaining parties.
If a party is added to a call while signals are being sent, this party will hear
the remaining digits but will not be talk path disconnected. As a result,
clicking noises may be heard.
Issue 4  September 1995  
4-49 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Call Endedbbbbbbbb
The switch uses this terminating capability to inform the adjunct that a controlled
call has ended and to clear the call control association that was controlling the
call.  It is also used when two calls are merged since one call control association
terminates when the calls merge.
Information Flowbbbbbbbbbbbbbbb
The switch does not expect a response.
Third Party Call Ended Parametersbbbbbbbbbbbbbbb
call_idIdentifies the call that has terminated
Causesbbbbbbbbbbbbbbb
The switch issues one of the following reasons as the cause for ending the
association.
Normal clearing (CS0/16)
The call having the requested call identity has been cleared.  The call is
no longer active.  The extraneous call is dropped as the result of merging
the call.
User busy (CS0/17)
The first alerted party on the call is busy and the call is dropped.
Classifiers not available (CS3/21)
Ð The call is dropped because no call classifiers are available.
Ð COR check failed.
Call with requested identity has been terminated (CS3/86)
Two calls have been merged into one.
Trunks not available (CS3/20)
The call is dropped because no trunks are available.
Split Queues full (CS3/22)
The call is dropped because it cannot be queued.
Denial/Reorder (CS0/42)
The reorder tone is detected. |
Outgoing calls barred (CS0/52) |
The calling party number of a switch-classified call has an FRL lower than |
that of the trunk group.
Call rejected (CS0/21)
The switch drops the call due to an illegal action and/or request by the
user (for example, attempting to merge two outbound calls without
disconnect supervision).
4-50  Issue 4  September 1995 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
No answer (CS3/19)
The classifier does not detect answer within the allowed number of rings.
Answering Machine Detected (CS3/24)
The call was answered by an answering machine.
Incompatible Destination (CS0/88)
The classifier detects answer back tone.
No Circuit or Channel Available (CS0/34)
Unassigned Number (CS0/01)
Invalid Number/Domain (CS0/28)
Normal Unspecified/SIT Ð Vacant (CS0/31)
Normal, Unspecified (CS0/127)
This value is a normal drop cause value when something other than an
ISDN endpoint drops out of a connection.  For example, when the host
issues a Third Party Make Call (User-Classified) from a station to an
announcement extension and the call is successfully completed.  The
calling party hears the announcement and the call is dropped.  The
Disconnect/Drop Event Report is also generated.  See Chapter 3,
``Common Capabilities, for more information on the Disconnect/Drop
Event Report. |
Denial/Reorder (CS3/42) |
Provided when a switch-clasified call (that has been answered by the far |
end) cannot be transferred to the intended split/VDN.
ACK (Positive Acknowledgement)
Parameters
bbbbbbbbbbbbbbb
None for this capability
Denial (NAK) Causesbbbbbbbbbbbbbbb
None for this capability
Protocol Error (NAK) Causebbbbbbbbbbbbbbb
None for this capability
Issue 4  September 1995  
4-51