ATT DEFINITY Communications System Generic 3V4 Instructions Manual

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party
ReconnectThis controlling capability enables the adjunct to
direct the switch to reconnect a specified station
to the controlled call.
Third Party MergeThis controlling capability enables the adjunct to
direct the switch to merge two controlled calls at a
specified station into one call on behalf of that
party.
Third Party
Selective DropThis controlling capability enables the adjunct to
direct the switch to drop a party from the
controlled call.
Third Party
Relinquish ControlThis terminating capability enables the adjunct to
relinquish control of a specific call and direct the
switch to stop sending event reports for this call.
Third Party Clear CallThis terminating capability enables the adjunct to
direct the switch to disconnect all parties on a
controlled call.
Third Party Send DTMF
SignalsThis capability enables the adjunct to transmit a
sequence of DTMF tones on behalf of a party on
the call.
Third Party
Call EndedThis terminating capability is used by the switch
when all parties on a controlled call are
disconnected.
Redirect CallThis capability enables the adjunct to direct the
switch to redirect an alerting call away from the
alerting station extension and route it to another
number.
Event ReportsSee Chapter 3, ``Common Capabilities.
U-Abort (User Abort)See Chapter 3, ``Common Capabilities.
Call Control capabilities are accepted only when the call is in the proper call state
with respect to the specified party.  The following table specifies which call
control requests are accepted and which are denied, depending on the state of
the call or the affected party.  In addition, the switch restricts Call Control
requests based on the call originators and destinations Class of Restriction
(COR).
4-2  Issue 4  September 1995 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Table 4-1.  Call Control Acceptance in Various Call/Station Statesbbbbbbbbbbbbbbbbbbbbbbbb
Call Control Request Active St Held St Alerting St Idle St Dialing St Bridged St
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Make Call no yes
1yes1yes yes2yes1bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Take Control yes yes yes 3 yes yes
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Relinquish Control yes yes yes 3 3 yes
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Clear Call yes yes yes 3 yes yes
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Selective Drop yes no no 3 yes no
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Reconnect yes yes no 3 no yes
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Merge
4yes yes no 3 no no
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Redirect Call no no yes no no no
c c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
1 If the state of the other calls at the station is as specified and there is an idle call
appearance
2 Call appearance previously selected for call origination
3 Call_id does not exist
4 Request should be made over the held call association; if made over the active call
association, it is denied.
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Issue 4  September 1995  4-3 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Make Callbbbbbbbb
The adjunct uses this initiating capability to establish a call between two parties.
Information Flowbbbbbbbbbbbbbbb
An acknowledgement (ACK) is optional for the Third Party Make Call capability.
If requested, an ACK is sent to the adjunct when the switch successfully
originates the call (a call identifier has been assigned).  If conditions prohibit a
call from being established, a Negative Acknowledgement (NAK) is returned.
Third Party Make Call Parametersbbbbbbbbbbbbbbb
orig_addrThe calling stations address.  For non-switch-classified
calls, the request is denied unless the calling party is off-
hook, idle, dialing, listening to dial tone, goes off-hook
within five seconds of the request, or is forced off-hook by
the switch (through a speakerphone). See ``Denial (NAK)
Causes that follows.
dest_addrThe called partys address.
dest_route_select[optional] The trunk access code or feature access code
(for example, Automatic Route Selection [ARS], or
Automatic Alternate Routing [AAR]) of a called endpoint
that is not directly connected.  Alternately, this information
may be included in the dest_addr.
return_ack return_ack[optional] If this parameter is present, it indicates that the
switch should return an acknowledgement to the request.
If this parameter is not present, then the switch does not
return an acknowledgement.
call_optionsCall options are listed below and described in detail in the
Third Party Make Call overview later in this section.
dalert_orderdpriority_calling
dans_machdservice_circuit
danw_treatdsupervisor_assist
ddirect_agent_callduui_info
dmax_ring_cycle
ACK (Positive Acknowledgement)
Parameters
bbbbbbbbbbbbbbb
If the return_ack is present in the adjuncts request, the switch returns an ACK
containing the party_id, call_id, and connected_number_id of the originator on
the call.  If the return_ack is not present, no ACK is returned.
4-4  Issue 4  September 1995 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Denial (NAK) Causesbbbbbbbbbbbbbbb
The following causes may be issued for non-switch-classified calls.  For NAKs for
switch-classified calls, see ``Third Party Make Call and Supported Call Types
that follows.
Invalid association (CS0/81)
The association does not exist.
Requested facility not subscribed/provisioned (CS0/50)
The user has not subscribed for the requested capability.
Out of Service (CS3/27)
The originator of the call is out of service.
Switching Equipment Congestion (CS0/42)
The PBX equipment is experiencing congestion due to traffic overload.
Call Rejected (CS0/21)
The COR check for completing the call failed.
Mandatory Information Element missing (CS0/96)
A required parameter is missing in the request.
Resources not available (CS3/40)
Ð The request cannot be executed because a call classifier is not
available or no trunks are available in the requested trunk group.
Ð The maximum number of calls being controlled has been
exceeded.
Incompatible Options (CS3/80)
The designated call options are not compatible with the Third Party Make
Call request.
User busy (CS0/17)
The user is busy on another call and cannot originate this call.
No user responding (CS0/18)
The originating address does not pick up the call and cannot be forced
off-hook.
Invalid number/domain (CS0/28)
An invalid address or extension number is present in the request.
Agent not member of split (CS3/11)
The agent is not a member of the split in this Direct Agent call.
Agent not logged in (CS3/15)
The agent is not currently logged into a split for this Direct Agent call.
Bearer capability not presently available (CS0/58)
There are incompatible bearer services for the originating or destination
addresses.  For example, the originator is administered as a data hotline
station or the destination is a data extension.
Answering Machine Detected (AMD) (CS3/24)
The call was answered by an answering machine.
Issue 4  September 1995  
4-5 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Outgoing calls barred (CS0/52)
The requested Third Party Make Call is being attempted over a trunk that
has been restricted from use by the originator.
Invalid Information Element contents (CS0/100)
The call_id specified by the Third Party Take Control capability is beyond
the maximum allowable call_id value.  For example, you could get this
cause value if the switch received a User to User Information (UUI)
Information Element longer than 32 bytes in an ASAI message or one that
did not include the header.
Message not compatible with call state (CS0/98)
The message is not compatible with the CRV state.
Service or option not subscribed/provisioned (CS0/50)
If an adjunct requests a Third Party Make Call (switch-classified call) with
Answering Machine Detection and AMD is not enabled, the switch denies
the request.
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 switch allows only one adjunct to control a call.  Additional requests to
control a call by other adjuncts are denied by the switch.
When a multifunction station user is receiving a dial tone on a call appearance
and the adjunct invokes a Third Party Make Call for that station, the switch
selects the same call appearance and call_id to establish the call.
The sum of the dest_addr and dest_route_select parameters can equal 32 digits. |
4-6  Issue 4  September 1995 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Third Party Make Call and Supported
Call Types
bbbbbbbb
The Third Party Make Call capability is used by the adjunct to request the switch
to set up a call between two parties (calling endpoint and the called endpoint).
Four types of controlled calls are supported for the Third Party Make Call
capability:
1. Switch-classified call
2. User-classified call
3. Direct-agent call
4. Supervisor-assist call
1. Switch-Classified Callbbbbbbbbbbbbbbb
A switch-classified call is the only call type used primarily by OCM applications
for Predictive Dialing when the destination is alerted first (using the 
alert_order
parameter
).  The administrator determines which calls are given to the agent
based on voice energy or the returned SIT or AMD tones from the call.  All other
calls are dropped by the switch and the classification reported to the adjunct (via
event reporting and/or call ended capabilities).
See Table 4-2 for SIT and AMD tone definitions.
This is the only type of call placed with the alerted order and the service circuit
(classifier) options specified.
The originator of a switch-classified call must be a valid on-PBX extension
number associated with a split, hunt group, announcement, or VDN.  The
originator cannot be a station extension.  (However, in an EAS environment, a
VDN extension must be the originator for a predictive dialing application.  See
the 
DEFINITY Communications System Generic 3 Call Vectoring/EAS Guide,
555-230-520, for more information.)
The destination can be either a valid station extension (except Distributed
Communications System [DCS] or Uniform Dial Plan [UDP] extension), or an
off-PBX number.  ISDN-PRI trunk types are the preferred facilities for these
outbound calls.  It is recommended that trunks with answer supervision be used
for switch-classified outbound calls.  Answer supervision from the network over
the trunk facility provides an accurate and timely indication when the far end
answers. Otherwise the switch relies on the call classifier to do the call
classification.
Issue 4  September 1995  
4-7 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Call Parameters for Switch-Classified Calls
This section contains the ASAI interface call parameters for switch-classified
calls.
orig_addr[mandatory] The originator must be a valid local extension
number associated with a split, hunt group, or
announcement, or a VDN in an EAS environment.
dest_addr[mandatory] The destination can be a valid switch
extension or an off-PBX destination.  It may include
TAC/ARS/AAR information.
dest_route_select[optional] This parameter contains TAC/ARS/AAR
information for off-PBX destinations if the information is
not included in the dest_addr.
priority_calling[optional] If present, a priority call is placed if the
destination is an on-PBX extension.  If the priority flag is
specified for an off-PBX destination, the call is denied.
max_rings[optional] This parameter designates the number of rings
that are allowed before classifying the call as no answer.
The minimum number is two, the maximum number is 15,
and the default is 10 (if not present).
direct_agent_callThis parameter must not be present.
supervisor_assistThis parameter must not be present.
alert_order[mandatory] This parameter must be set to indicate
``destination first.
ans_machThis parameter indicates if answering machine detection
is desired or not. Values are ``On or ``Off.  If ``On is
selected, the anw_treat parameter specifies the treatment
for an answering machine call.
anw_treatThis parameter is mandatory if ans_mach is ``On. It
specifies the call treatment when an answering machine
is detected. The values are ``drop, ``answer, or ``blank.
If blank, the value defaults to the administered value.
4-8  Issue 4  September 1995 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
service_circuit[optional] This parameter must be set to ``classifier if the
destination is off-PBX and the trunk access code is
contained in the dest_route_select.
This parameter is optional if the destination is on-PBX or
the trunk access code is included in the dest_addr
parameter.  If the trunk access code is part of the
destination address and no service circuit parameter is
included, then answer may not be detected over non-
ISDN trunks.  This may lead to the call being hung for up
to ten minutes if the call is not answered.
return_ack[optional] If this parameter is present, it indicates that the
switch should return an acknowledgement to the request.
If this parameter is not present, then the switch does not
return an acknowledgement.
uui_info[optional] UUI information received in a successful Third
Party Make Call 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.
UUI from a Third Party Make 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.
Call Classification
The switch uses the Call Classification process, along with a variety of internal
and external events, to determine a switch-classified calls outcome.  Whenever
the called endpoint is external, a call classifier is used.
The classifier is inserted in the connection as soon as all the digits have been
outpulsed.
A call is classified as either ``answered or ``dropped (Third Party Call Ended).
Ringing is reported to the adjunct as an Alerting Event Report, but in and of itself
is not a final classification.  ``Non-classifiable energy is always treated as an
answer classification and reported to the adjunct as such.  The modems answer
back tone results in a Third Party Call Ended.  The SIT detection is reported to
the adjunct as an Answered Event Report or Third Party Call Ended depending
on the customers administration preference.  Answering Machine Detection
(AMD) is reported as answered or call ended, depending on administration or call
options. See 
DEFINITY Communications System Generic 3 V4 Implementation,
555-230-655 for more information regarding administration of SIT reporting to the
adjunct.
Issue 4  September 1995  
4-9 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
The conditions detected are as follows:
Table 4-2.  Detected SITs
bbbbbbbbbbbbbbbbbbbbb
SIT Name Cause Value Reported
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
SIT Reorder CS0/42 Switching Equipment Congestion
SIT No Circuit CS0/34 No Circuit or Channel Available
SIT Intercept CS0/22 Number Changed
SIT Vacant Code CS0/01 Unassigned Number
SIT Ineffective Other CS0/28 Invalid Number/Domain
SIT Unknown CS0/31 Normal Unspecified
AMD Treatment CS3/24 Answering Machine Detected
Talk Duration
(seconds)---
Pause Duration
(seconds)---
c c c
c
c
c c c
c
c
c c c
c
c
c c c
c
c
c c
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Answer Classification
The Answer Classification applies only to the destination (either internal or
external).  For off-PBX destinations, the answer event at the far end can be
determined either by the call classifier or the network answer supervision.
A call is considered answered if one of the following occurs (whichever is first):
Network Answer Supervision ÐThe network provides answer
notification to the switch (for trunks supporting answer supervision).  For
outbound calls over ISDN-PRI facilities, the CONNect message is
interpreted as ``far end answered the call.  If Answering Machine
Detection (AMD) has been requested for the call, the Network Answer
Supervision (non-ISDN-facilities) and the CONNECT message (ISDN
facilities) are ignored.  For these cases, the call classifier determines
whether a call has been answered, depending on the AMD treatment
requested for the call.
Call Classifier ÐThe call classifier detects an answer when:
Ð Voice energy is detected by the call classifier.
Ð A ``SIT-detected message is received from the call classifier
reporting a specific Special Information Tone (SIT) which must be
treated as an answered call (administered option).
Ð A ``non-classifiable energy detected message is received from the
call classifier.
4-10  Issue 4  September 1995 
						

							ASAI and Call Controlbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Ð The ``timeout message is received from the software and told by
the call classifier reporting that there was no tone detected after a
timeout interval.  This information appears on the System
Parameters-Features form as the ``off-premises tone detect
timeout.
Ð Answering Machine Detection (AMD) is enabled for a call and an
Answering Machine is detected.
Local detection ÐA call placed to an on-PBX endpoint is considered
answered when the called party answers the call.
If the call is answered in one of the ways described above, the Answered Event
Report is sent to the adjunct.  When the call results in a SIT which is to be
treated as answer, a cause value with the particular SIT is included in the
Answered Event Report.  See Chapter 3, ``Common Capabilities for more
information on the Answered Event Reports contents.
If an answering machine is detected, the call is treated according to
administration or to treatment requested in the message.  Treatment in the
message overrides the administered treatment.
Drop Classification
The classifier is immediately disconnected following detection of one of the
conditions described below.
No Answer Condition
For calls placed to off-PBX destinations, the ``no answer condition is the result
of the call classifier detecting ringing energy for the entire duration specified (the
maximum number of rings times six seconds).  The number of rings for each call
may be selected from a range (two to 15) provided as an option in the Third
Party Make Call capability.  Values outside this range will cause the call to be
denied (cause CS3/79 Ð Service or Option Not Implemented).  The default is
60 seconds (10 rings).
For calls placed over ISDN-PRI facilities, if the ISDN ALERTing message is
received from the network, the classifier is expected to detect the ``in band
ringing and provide the ``no answer classification independent of receiving an
ISDN ALERTing message.
For calls placed to on-PBX destinations, the ``no answer classification is done by
counting the number of seconds of ringing.
The adjunct is notified of the no answer outcome in a Third Party Call Ended with
cause CS3/19 Ð No Answer.
Issue 4  September 1995  
4-11