Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual

							ASAI Capabilities
Issue  3  May 1998
5-31
Interactions with Event Reports
This capability can be requested for a party when the party is in any state except 
null. After the capability is successfully acknowledged, the party goes to the null 
state. This capability is the only one allowed for a party that is in the 
seized state. 
						

							ASAI Capabilities
5-32Issue  3  May 1998 
Third Party Selective Hold
Description
The Third Party Selective Hold capability allows the client to request the server to 
invoke this service on behalf of a specified party. The effect is the same as if the 
identified party directly invoked the hold service. The client continues to receive 
feedback regarding the call and may continue to control the call with further Third 
Party capabilities.
The server sends a C_3PSH_POS_ACK when it has placed the party on hold. The 
client must use feedback to determine the state of the call with respect to each 
endpoint.
The server sends a C_3PSH_NEG_ACK if the parameters of the request are invalid 
or if it cannot attempt the hold operation.
Request/Confirmation Parameters
Depending on conditions, the request must specify the following parameters:
nParty Identifier — The party on the call to be placed on hold. This 
parameter must be specified if the association is started with a 
Third Party 
Make Call or a Third Party Take Control capability; it can be inferred if the 
association is started with a 
Third Party Domain Control capability.
nCall Identifier — The call on which this capability operates. This 
parameter must be specified if the capability is requested over an 
association started with a 
Third Party Domain Control capability; otherwise, 
it must not be used.
Notes
Some third party servers may have to be directly connected to the specified party.  
The party must be in the active state on the call.
Interactions with Event Reports
This capability can be requested for a directly connected party when that party is 
in the 
active state. After the capability is successfully acknowledged, the party 
goes from the 
active state to the held state.  
						

							ASAI Capabilities
Issue  3  May 1998
5-33
Third Party Send DTMF Signals
Description
The Third Party Send DTMF Signals capability allows a client to request the 
server to issue a sequence of DTMF tones on behalf of a party on the call. The 
DTMF sequence to be generated may contain any digit as well as the # and * 
characters. A maximum string of 32 characters may be sent from the client to the 
server in a single service request message.
The client invokes this capability by issuing a C_3PSDS request to which the 
server will respond with a C_3PSDS_CONF. The server sends positive 
acknowledgment when it has validated the parameters.
The server sends a C_NEG_ACK if the parameters of the request are invalid or if it 
cannot apply the tones to the call.
Request/Confirmation Parameters
Depending on conditions, the request must specify the following parameters:
nCall Identifier — The call on which this capability operates. This 
parameter must be specified if the capability is requested over an 
association started with a 
Third Party Domain Control capability; otherwise, 
it must not be used.
nParty Identifier — The party on the call for whose benefit the tones will be 
sent. This parameter must be specified if the association is started with a 
Third Party Make Call capability; it can be inferred if the association is 
started with a 
Third Party Domain Control capability.
nUser Data — A substructure containing the user digit data. The structure 
contains the following usable fields:
nLeng field — An integer value that indicates the number of octets 
(digits) of user data included in the request. Currently, the ECS will 
accept up to 32 bytes of data (leng = 32).
ntype field — Indicates the type of information and is restricted to
C_UU_IA5, which indicates IA5 or ASCII characters.
ndigits field — A pointer to an ASCII string of no more that 32 
characters in length. 
						

							ASAI Capabilities
5-34Issue  3  May 1998 
Third Party Single-Step Conference
Description
The Third Party Single-Step Conference capability allows the client to add an 
IDLE station into an existing call with a single ASAI operation. It is not necessary 
to place the call on hold or to use the Third Party Merge capability. The party 
being added must either have a speaker phone, or go off-hook on an idle call 
appearance within five seconds, or the request will fail. The positive response to 
the request provides a list of all the parties existing on the call.
Request/Confirmation Parameters
nAlert Destination — Indicates if the station being added should be alerted 
for the conference. See the notes below.
nVisibility — Indicates whether or not the talk path of the station being added 
should be connected to the conference call. In the future, visibility will also 
effect the display.
nNumber of Conferenced Extensions — Indicates the number of parties on 
the call.
nParty list — Contains information about the parties on the call including the 
party identifier, extension number, and the numbering plan information for 
each party on the call. 
nUniversal Call Identifier — Indicates the unique Universal Call ID assigned 
by the ECS for the call if this feature is available in the ECS.
Notes
This capability may be specified on a Call Control association where the extension 
to be added to the existing call is specified by the Station Extension parameter. 
When used on a Domain Control association, the Single-Step request must be 
provided on the Domain Control association and the Call Identifier of the existing 
call is specified in this request.
Single-Step Conference also allows control of the voice path of the call being 
added via the visibility parameter. It allows the station to be added in a listen-only 
connection or with both talk and listen paths connected.
In the initial release of Single-Step Conference, the ECS will always treat the Alert 
Destination parameter as being set to OFF, regardless of how the CallVisor PC 
application sets it. See the DEFINITY ECS Release 6 CallVisor ASAI Technical 
Reference, 555-230-220, for complete details of this capability. 
						

							ASAI Capabilities
Issue  3  May 1998
5-35
Third Party Take Control
Description
The Third Party Take Control capability allows the client to request the server to 
allow it to control a call in progress to which the client is not a party. Once the 
request for 
Third Party Take Control is acknowledged, the client can use other 
third party capabilities (for example, 
Third Party Call Merge) to control the call.
The client invokes this capability by issuing C_3PTC_REQ, to which the server 
responds with a C_3PTC_CONF. The client retains control of the call until one of 
the following conditions is met:
nThe client invokes the Third Party Clear Call capability for the call.
nThe client invokes the Third Party Relinquish Control capability for the 
call.
nThe client invokes or receives a U_ABORT capability for the call.
nThe client receives a P_ABORT capability for the association.
Request/Confirmation Parameters
nCall Identifier — The identifier of the call that the client wants to control.
In addition, the programmer can specify any or all of the following:
nParty Identifier — The identifier for a party to the call. This parameter is 
mandatory if the extension address (below) is specified.
nAddress — The extension address (number) of each party to the call.
Note that the party identifier and the address can be repeated.
Notes
The client must have received an event report (from a different association) that 
included the call identifier. The client can request an event report, receive it and 
then request the 
Third Party Take Control capability.
Interactions with Event Reports
This capability does not affect the state(s) of the parties to the call.
Notes
There are no restrictions on this capability. 
						

							ASAI Capabilities
5-36Issue  3  May 1998 
Set Value Capabilities
The Set Value capability group consists of the Set Value capability and the Abort 
capability which is described later in this chapter.
Set Value allows a client to request a server to set the Message Waiting Indicator 
(MWI) or to activate the Flexible Billing Feature. Both the feature to be set and its 
values are specified as parameters to the capability.
Description
Set Value allows a client to request that an item controlled by the server (for 
example, C_SV_MWI, C_SV_FLEX,SAC, and SCFS) be set to a specified value. 
It is a user-initiated, acknowledged, end-to-end service. The client invokes this 
capability by issuing a C_SV_REQ with the items to be set, additional parameters 
when required and the desired value. 
The server responds by issuing a C_SV_CONF. If the request is not honored, the 
cause parameter is set.
Request/Indication Parameters
nItem — Message Waiting Indicator. To set the MWI, these elements must 
be specified:
nThe station whose MWI is to be set
nThe desired state (Off or On) 
nItem — Flexible Billing Feature. To set the Flexible Rate, these elements 
must be specified:
nThe call (call_id) that this capability is to operate on
nThe type of billing change (for example, NEW_RATE,FLAT_RATE, 
etc.)
nThe rate to apply to the call  
						

							ASAI Capabilities
Issue  3  May 1998
5-37
Value Query Capabilities
The Value Query capability group consists of:
nVa l u e  Q u e r y
nValue Query Confirm
nValue Query Response
The Abort capability is described later in this chapter.
Value Query allows a client to request and receive information about the status or 
value of features or services under server control. The following features or 
services can be queried:
nACD split status
nCall classifier status
nTrunk group status
nTime of day
nACD agent status
nStation status
nACD Agent Login Audit
nParty ID
nUCID
nExtension
nCalls query
nStation Message Waiting Lamp Query
nStation Send-All-Calls Status Query
nStation Call Forwarding Status Query
nName Query (Integrated Directory Data)
nUCID Query (Universal Call ID)
The feature or service is specified as a parameter. The server can send multiple 
replies to a single query. 
						

							ASAI Capabilities
5-38Issue  3  May 1998 
Value Query
Description
The Value Query capability allows a client to request and receive information 
about the status of the value of a feature or service under server control.
The client issues a C_VQ_REQ, specifying the feature or service queried. The 
server responds with a C_VQ_CONF when only one reply is needed or a variable 
number of C_VQ_RESP messages when multiple replies are needed.
Request Parameters
Item — The object for which a value is being requested, including:
nACD Split Status — Requests the number of agents logged into the ACD 
split; the number of agents available to receive calls; or the number of calls 
queued in the ACD split.
nCall Classifier Status — Requests the number of idle call classifiers; the 
number of call classifiers that are in use; the number of call classifiers that 
are ‘‘busied-out” for maintenance; or the number of call classifiers that are 
unavailable for reasons other than maintenance.
nTrunk Group Status — Requests the number of idle trunks in the trunk 
group; the number of trunks in use in the trunk group; the number of trunks 
that are ‘‘busied-out” for maintenance; or the number of trunks that are 
unavailable for reasons other than maintenance.
nTime of Day — Requests the time of day, specified in the following fields
nYear: specified as 2 decimal digits (00-99)
nMonth: specified as 2 decimal digits (01-12)
nDay: specified as 2 decimal digits (01-31)
nHour: specified as 2 decimal digits (00-23)
nMinute: specified as 2 decimal digits (00-59)
nSecond: specified as 2 decimal digits (00-59)
nACD Agent Status — Requests ‘‘talk state” of agent with respect to ACD 
split (on call or idle); or current work mode of agent (manual-in, auto-in, 
after call work, auxiliary work)
nStation Status — Requests talk state of extension (on call or idle)
nACD Agent Login Audit — Requests a list of agents currently logged into 
a split/skill
nParty Identifier — Requests list of party identifiers for the call; or the 
extension number of each party to the call 
						

							ASAI Capabilities
Issue  3  May 1998
5-39
nExtension — Requests the kind of extension number (VDN, ACD split, 
announcement, voice station, ASAI, other)
nCalls Query — Requests list of call identifiers for all calls present at the 
station extension; list of party identifiers and identification of station 
extension on the call; or list of endpoint call states (alerting, call initiated, 
connected, held, unknown) for each of the calls present at the station 
extension
nStation Message Waiting Lamp Query — Requests status of the Station 
Message Waiting Lamp for the given extension
nStation Send-All-Calls Status Query — Requests status of the Station 
Send-All-Calls for the given extension
nStation Call Forwarding Status Query — Requests status of the Station 
Call Forwarding for the given extension
nName Query — Requests the name associated with the given extension 
from the Integrated Directory Database
nUCID Query — Requests the Universal Call Id associated with the call 
Notes
There are no restrictions on this capability. 
nThe ECS software, Release 5, now supports up to 27 special 
characters in Integrated Directory Database. Before Release 5 only 
15 characters were supported and only 15 characters will be 
returned, if the ECS software is G3V4, or if it is Release 5 or 6, and 
the ASAI link version is 1 or 2. Correct ASAI link version has to be 
negotiated for this functionality. For Release 5 and 6, the link version 
should be set to 3. 
						

							ASAI Capabilities
5-40Issue  3  May 1998 
Value Query Response
Description
Value Query Response allows the server to provide multiple responses to a 
request.
The server issues a C_VQ_RESP to signal delivery of information requested by the 
client with a C_VQ_REQ. The server terminates this ASE with a C_VQ_CONF after 
all 
Value Query Response requests have been answered.
Request Parameter
Va l u e — Depends on the item(s) specified in the Value Query request
defined previously in this chapter.
Notes
There are no restrictions on this capability.