ATT DEFINITY Communications System Generic 3V4 Instructions Manual

							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
result_call_id[mandatory]  The call_id after the call is merged (provided
by the switch)
party_id[mandatory] The list of party_ids for the merged call
provided by the switch
Connected
number[mandatory] The list of extensions for the parties on the
call
Denial (NAK) Causesbbbbbbbbbbbbbbb
The switch issues one of the following reasons as the cause for ending the
association:
Invalid number/domain (CS0/28)
The controlling party has not been specified correctly.
Message not compatible with call state (CS0/98)
The common party is not in a valid state for the operation (merge) to take
place.  For example, the common party does not have one call active
(talking) and one call in the held state.
Invalid information element contents (CS0/100)
The party_id value of the request is invalid.
Mandatory information element missing (CS0/96)
Resources not available (CS3/40)
The host attempted to add a seventh party to a call with six parties active
(bridging and held cases only).
Reorder/Denial (CS3/42)
Both calls are alerting, or both calls are being service observed, or an
active call is in a vector processing stage.
Protocol Error (NAK) Causesbbbbbbbbbbbbbbb
The switch issues the following causes for returning a protocol processing error.
Invalid association (CS0/81)
The association does not exist.
Protocol error (CS0/111)
The Q.932 protocol has been violated or the capability invoked is not
consistent with this association.  For example, invoking a Third Party
Domain Control Request over a Call 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.
5-20  Issue 4  September 1995 
						

							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Considerationsbbbbbbbbbbbbbbb
The Third Party Merge capability may also be used by the adjunct to transfer to
the supervisor.  A sample scenario is presented below.  Note that this is not the
only way in which to effect a transfer to the supervisor.
An ACD agent handling the transfer may request (via data keyboard) that the call
be transferred to the supervisor.  The adjunct:
1. Places the existing call on hold
2. Issues a Third Party Make Call capability (with the ``supervisor-assist
option) to the supervisors extension
3. When the supervisor is either alerted or answers, the adjunct may merge
the supervisor call and the previously held call using the Third Party
Merge capability.  (This capability is requested on the same association
with the held call).
Since this was a transfer request, the conf/trans_flag parameter is set to
TRANSFER and the switch drops the ACD agent from the connection after the
merge takes place.
If the ACD agent requested a supervisor conference, the same procedure would
have taken place but the conf/trans_flag would have been set to CONFERENCE.
The switch does not drop the ACD agent from the resulting connection, and a
three-party call is created.
Issue 4  September 1995  
5-21 
						

							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Selective Dropbbbbbbbb
The adjunct uses this controlling capability to drop a controlled extension from a
call.
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
call_id specified does not exist (invalid parameter).
Third Party Selective Drop Parametersbbbbbbbbbbbbbbb
call_id[mandatory] Identifies the call to be disconnected
uui_info[optional] If an ASAI adjunct provides UUI in a 3rd Party
Selective Drop, then the switch stores that UUI with the
call.
ACK (Positive Acknowledgement)
Parameters
bbbbbbbbbbbbbbb
None for this capability
Denial (NAK) Causesbbbbbbbbbbbbbbb
The switch issues one of the following reasons as the cause for ending the
association:
Mandatory information element missing (CS0/96)
The call_id is missing from the request.
Invalid association (CS0/81)
The association does not exist.
Message not compatible with call state (CS0/98)
The call is not currently active or in a hold state and therefore cannot be
dropped.
Invalid information element contents (CS0/100)
The call_id value is invalid (for example, it is alerting).
Invalid Information Element contents (CS0/100)
The UUI IE is longer than 32 bytes.
5-22  Issue 4  September 1995 
						

							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Protocol Error (NAK) Causebbbbbbbbbbbbbbb
The switch issues the following cause for 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 a Third Party
Domain Control Request over a Call 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 capability may not be used to drop a party in the alerting or held state from a
two-party or a multi-party call.
On a Domain Control association, only the Domain-Controlled extension can be
dropped, not other parties as with the Third Party Selective Drop capability of the
Call Control capability group (see Chapter 4, ``Call Control Capability Group).
If a call has User to User Information (UUI) that came from an ISDN
DISCONNECT message or in a Third Party Drop Request stored with it, and a
party drops from the call and a Drop Event Report is sent, then the UUI is
included in the report.  The UUI passed in this request is only reported with other
Drop Event Reports for the same call.
Issue 4  September 1995  
5-23 
						

							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Auto Dialbbbbbbbb
An adjunct uses this capability to set up a two-party call between the domain-
controlled station and an internal or external destination.  This capability can only
be requested by an application having an active domain-control association.
Information Flowbbbbbbbbbbbbbbb
The adjunct expects an acknowledgement to its request only if the return_ack
has been set to yes.
Third Party Auto Dial Parametersbbbbbbbbbbbbbbb
dest_addr[mandatory] This parameter specifies a valid on-PBX
extension (station extension, VDN, ACD split, hunt group,
announcement extension), or off-PBX number.  May
optionally contain the ARS/AAR if not present in the
dest_route_select.
dest_route_selectThis parameter contains the Trunk Access Code
(TAC)/ARS/AAR information for off-PBX numbers.
return_ackThis parameter enables the switch to acknowledge the
request made by the adjunct.  It can be set to ``yes for
acknowledgement or ``no for no acknowledgement.  The
default is ``no.
priority_calling[optional] If present, a priority call is placed if the
destination is a local extension.  If the priority flag is
specified for an off-PBX destination, the call is denied.
The default is non-priority.
uui_info[optional] If an ASAI adjunct provides UUI in a Third Party
Auto Dial, then the switch stores that UUI with the call.
UUI from an Auto Dial Call will be sent in any ISDN PRI
setup for the call, in the Alerting and Call Offered Event
Reports, and in a Route Request, if one is made.
5-24  Issue 4  September 1995 
						

							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
ACK (Positive Acknowledgement)
Parameters
bbbbbbbbbbbbbbb
If the return_ack was present in the adjuncts request, the switch will return an
ACK containing the following:
party_idThe party identifier of originator
call_idThe call identifier of the resulting call
If the return_ack is not present, no ACK is returned.
Denial (NAK) Causesbbbbbbbbbbbbbbb
None for this capability
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 a Third Party
Domain Control Request over a Call 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.
Issue 4  September 1995  
5-25 
						

							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Relinquish Controlbbbbbbbb
The adjunct uses this terminating capability to end a Domain Control association.
The switch continues to process all calls at the domain-controlled station or split
or EAS skill normally. Calls present at the domain-controlled station or split or
EAS skill are not affected by this capability.
Information Flowbbbbbbbbbbbbbbb
The adjunct expects a response to its request.
The switch always ends a domain control association and acknowledges the
request.
Issuing this capability terminates the Domain Control association. Thus, all event
reporting on the association ends.
This capability may be issued any time.
Third Party Relinquish Control Parametersbbbbbbbbbbbbbbb
None for this capability
ACK (Positive Acknowledgement)
Parameters
bbbbbbbbbbbbbbb
None for this capability
Denial (NAK) Causebbbbbbbbbbbbbbb
None for this capability
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 a Third Party
Domain Control Request over a Call 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.
5-26  Issue 4  September 1995 
						

							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Considerationsbbbbbbbbbbbbbbb
Ending one Domain Control association does not affect the other active
associations that may be controlling an extension, or the state of any calls at that
extension.
This capability does not disconnect the domain-controlled station or any other
station from any call.
Issue 4  September 1995  
5-27 
						

							ASAI and Domain Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Send DTMF Signalsbbbbbbbb
The adjunct uses this controlling capability to transmit a sequence of DTMF
tones on behalf of a domain-controlled 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
call_id[mandatory] Identifies the call at the specified domain (station)
for which DTMF signals are to be sent.
rx_party_id[optional] If present, this parameter is ignored.  A list of 1 to 5
parties who 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). Currently not supported
(ignored) by DEFINITY.
char_seq[mandatory] Identifies the DTMF 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.
None for this capability
5-28  Issue 4  September 1995 
						

							ASAI and Domain 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 on 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 (CS3/98)
DTMF signals can be generated only for active calls on which no other
signaling tones are present.  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.  Or,
the switch capacity for simultaneous sending of DTMF digits is full.
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.
Issue 4  September 1995  
5-29