ATT DEFINITY Communications System Generic 3V4 Instructions Manual

							ASAI and Value Query Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Agent not logged in (CS3/15)
The agent is not logged in to the specified split.
Switching Equipment Congestion (CS0/42)
The switch is not accepting the request at this time because of traffic
overload. The adjunct or user may wish to retry the request but should not
do so immediately.
Feature Request Rejected (CS3/53) Ð Station Feature Query
This value is generated whenever the switch cannot return queried feature
information even though the feature information may be defined for the
specified extension.
Service or Option not Implemented (CS3/79)  Ð Station Feature Query
This value is returned whenever the queried feature has not been defined
for the specified extension.
Facility Reject (CS0/29)
The applications processor attempted an ASAI query with the billing
change request feature specified in the Item IE.  This is not allowed.
Mandatory Information Element Missing (CS0/96)
For an Internally Measured Data Value Query, either data_domain,
domain_element, or a data_item is missing.  For an Integrated Directory
Database query, the domain_element is missing.
Invalid Information Element Contents (CS0/100)
For an Internally Measured Data Value Query, the split reference or
interval is outside the ranges specified for each information element.  For
an Integrated Directory Database query, the domain element is not one of
the supported types.  Also sent on an Internally Measured Data query and
an Integrated Database query if the switch release is earlier than G3V4.
Incompatible options (CS3/80)
For an Internally Measured Data Value Query, an object is specified in a
domain element with a type not matching that in the data domain, or an
object on the switch is not the specified type.
Unassigned Number (CS0/1)
An item in an Internally Measured Data Value Query does not exist.
Service not Available (CS3/63)
The agent, split/skill, trunk group, or VDN queried in an Internally
Measured Data Value Query is not measured.
9-12  Issue 4  September 1995 
						

							ASAI and Value Query Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
The following is a list of instances where a CS3/79 is returned for a specific
feature.
A negative acknowledgement with cause value CS3/79 is returned whenever the
MWI has not been defined for the specified station.  Examples of extensions for
which the MWI query is not defined are:
Attendant extension
Data extension
VDN extension
Announcement extension
DCS extension
A negative acknowledgement with cause value CS3/79 is returned whenever the
Send All Calls feature has not been defined for the specified extension. A partial
list of extensions not supporting Send All Calls is:
Hunt groups
VDNs
Announcements
Data modules
DCS extensions
A negative acknowledgement with cause value CS3/79 is returned whenever the
Call Forwarding feature has not been defined for the specified extension.
A partial list of extensions not supporting Call Forwarding is:
VDNs
Announcements
PCOLs
Data extensions
DCS extensions
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.
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  
9-13 
						

							ASAI and Value Query Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Considerationsbbbbbbbbbbbbbbb
For the Internally Measured Data (IMD)  and Integrated Directory Database
(IDD) features, applications are responsible for controlling traffic on ASAI links.
They should attempt to minimize traffic in the following ways:
For the IMD feature, they should request only needed data items, poll as
infrequently as possible, and retain data items in their own memory rather
than retrieve static data items from the switch.
For the IDD feature, they should request names only when needed. For
example, the IDD feature is not intended for use by an application to
create its own copy of the ID database (by effectively downloading the
entire ID database).  Note that returned names may not be complete since
names are a maximum of 15 characters in the ID database.
Since the IMD feature does not provide a way of informing an application which
ACD operating environment is in effect (EAS, IMD Login IDs active, or traditional,
no login IDs), the application must permit itself to be administered to adapt to
these possibilities.  The main impact is on the information sent to identify a target
agent.  In a traditional environment this is an extension, but in the other two
cases, listed previously, appropriate login IDs must be used in the Query
message.
Concurrent operation of VuStats and the IMD feature reduces the operating
capacities of both.  This is a function of the load on the switch CPU.
For Internally Measured Data:
Numerical items that result in a division by zero are returned, but the IE
holding that item has a length of zero and no data bytes (for example,
average acd talk time, when no ACD calls have been made).
Numerical items are returned in base 128. The most significant bit is first,
with an extension bit set in the last byte.
ASCII items are returned with an extension bit set on the last byte.  Thus,
only 7-bit ASCII values are supported.
Certain data items may not be available when a query for IMD is made.  If
so, these data items will not be returned.  Other items in the same request
will be unaffected.  The association is terminated with the normal
RELease COMPlete Acknowledge message.  For example, percent-in-
service-level will not be returned if the service level is not administered.
If all of the requested items are unavailable, then the association is still
terminated with the RELease COMPlete Acknowledge.  In that case, no
FACility messages are sent, since there are no data items to return.
VuStats (G3V4 Enhanced) is required to receive those data items that are
part of the G3V4 enhancement to VuStats.  The affected items are:
call-rate, split-call-rate, total-acd-call-time, and average-acd-call-time.
If VuStats (G3V4 Enhanced) is not enabled on the DEFINITY Customer-
Options form and one of these items is requested, then the affected items
will not be returned, as in the above bullet item.
9-14  Issue 4  September 1995 
						

							ASAI and Value Query Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Value Query Responsebbbbbbbb
This capability is used by the switch to provide the adjunct with multiple
responses to requested switch service information.
Currently, the switch replies to an ACD Agent Login Audit Query with up to eight
agent addresses per Value Query Response message.  The switch also replies
to an Internally Measured Data Query with up to 8 data items per Value Query
Response message.
Information Flowbbbbbbbbbbbbbbb
The switch does not expect a response from the adjunct after sending a value
query response.
Value Query Response Parametersbbbbbbbbbbbbbbb
valueThe list of extensions corresponding to logged-in agents
(ACD Agent Login Audit Query).
data_itemIdentifies the type of requested data item and its value.
Up to 8 can be included in the Internally Measured Data
Query message.
ACK (Positive Acknowledgement)
Parameters
bbbbbbbbbbbbbbb
None for this capability
Denial (NAK) Causesbbbbbbbbbbbbbbb
None for this capability
Protocol Error (NAK) Causesbbbbbbbbbbbbbbb
None for this capability
Issue 4  September 1995  
9-15 
						

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
   
						

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbb
ASAI and Set Value Capabilities
10
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
This chapter describes the Set Value Capability Group.  The parameters
available to this group enable the adjunct to set the value of certain
switch-controlled services at an endpoint.
The following capabilities are available:
Set ValueThis capability lets the adjunct set predefined
values for switch-controlled features.
U-Abort (User Abort)See Chapter 3, ``Common Capabilities.
Issue 4  September 1995  
10-1 
						

							ASAI and Set Value Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Set Valuebbbbbbbb
The adjunct uses this capability to set the value of the message waiting indicator
(MWI) and to set the billing rate of a 900-type call.
Information Flowbbbbbbbbbbbbbbb
The adjunct expects a response to its request.
The switch either acknowledges or denies the request.
Set Value Parametersbbbbbbbbbbbbbbb
item[mandatory] Specifies the item to be set. MWI and Flexible
Billing are the only options presently available.
item_params[mandatory for MWI] For MWI, the on-PBX station extension
of the party (station) for which the MWI is to be set
call_id[mandatory for Flexible Billing] For Flexible Billing, this
switch-assigned call identifier is used to associate event
reports and to identify a call that the adjunct wants to control.
The call identifier is unique within the switch.
billing_type[mandatory for Flexible Billing] For Flexible Billing, one of the
following must be present:
New rate: Per minute rate that starts when message is
set
Flat rate: Time-independent rate
Premium charge: Flat charge in addition to existing rate
Premium credit: Flat negative charge in addition to
existing rate
Free call: Self-explanatory
amount[mandatory for Flexible Billing)] Applies to first four values of
billing_type (Flexible Billing); not allowed for free call. Rate of
call in dollars and cents.  Cannot be less than $0.00 or greater
than $999.99.
value[mandatory for MWI]  For MWI, either on or off
10-2  Issue 4  September 1995 
						

							ASAI and Set Value Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
ACK (Positive Acknowledgement)
Parameters
bbbbbbbbbbbbbbb
None for this capability
Denial (NAK) Causesbbbbbbbbbbbbbbb
The switch issues one of the following reasons as the cause for not setting the
MWI:
Invalid association (CS0/81)
The association is already in existence.
Invalid number (CS0/28)
An invalid parameter value has been designated.
Service or option not available (CS3/63)
Messaging is not enabled for the requested station or would exceed ASAI
request limits.
Mandatory information element missing (CS0/96)
A required parameter is missing in the request.
Switching Equipment Congestion (CS0/42)
The switch is not accepting the request at this time because of processor
overload.  The adjunct or user may wish to retry the request but should
not do so immediately.
Facility Reject (CS0/29)
The applications processor attempted a Flexible Billing rate change
request (Set Value capability) for a call that does not include a Flexible
Billing user.
Resources Unavailable, Unspecified (CS0/47)
The applications processor requested a billing rate change and the switch
threshold of unconfirmed requests has been reached.
Message not compatible with call state (CS0/98)
The billing change request is rejected because the call has not yet been
answered or has been disconnected.
No user responding (CS0/18)
A response to a billing request has not been received.
Issue 4  September 1995  
10-3 
						

							ASAI and Set Value Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Protocol Error (NAK) Causebbbbbbbbbbbbbbb
The switch issues the following cause for generating a protocol processing
error(s):
Protocol error (CS0/111)
The Q.932 protocol has been violated.
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
MWI
System cold starts cause the switch to lose the message MWI status. Hot starts
(PE interchange) and warm starts do not affect the MWI status.
To keep the MWI in sync with the other adjuncts, the ASAI adjunct must use the
Set Value capability to update the MWI whenever the link between the switch
and adjunct comes up from a cold start.
When an ASAI adjunct has turned on a stations MWI and the station user
retrieves messages using the station display, then the station display shows the
message ``You have adjunct messages.
The MWI can only be turned on for a station extension.  Starting with G3V4, the
Message Waiting Lamp on a station may track that physical extension or any
other physical extension.  This depends on the administration of the station.  In
an EAS environment, this lamp may track an agents messages, depending on
the system features administration.
The MWI cannot be turned on for an EAS agent through ASAI (a logical
extension may not be specified in the ASAI request for turning on the MWI).
Thus, this means that an ASAI request to turn on a particular MWL at a physical
station may or may not result in that MWL actually turning on.
Flexible Billing
1. When an ASAI adjunct makes a Flexible Billing request, the switch
normally passes the request onto a PRI trunk on the call. The PBX does
not keep a timer while waiting for a response.  ``No user responding is
sent to the ASAI adjunct only when: 1) the PRI trunk providing the Flexible
Billing service is dropped from the call before the response is returned to
the PBX, or 2) a second billing request arrives before the first has been
replied to.
It is recommended that the adjunct keep timers to determine when a
10-4  Issue 4  September 1995 
						

							ASAI and Set Value Capabilitiesbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Flexible Billing request has not received an answer in a reasonable time.
The ``No user responding cause value from the switch will make the
adjunct aware of the problem, but it will be too late to try again.
2. If VDN Return Destination is assigned, the Flexible Billing feature may not
be able to function as desired because the new connection may result in
the need for a different billing option that cannot be overridden, or may
result in different rates that would inappropriately be applied to the
previous connection(s).
Thus if a call with the Returned Destination specified has the Flexible
Billing trunk/call flag set, the Returned Destination is ignored and the call
is forced to disconnect.
3. Flexible Billing works in a conference call arrangement as long as the
identity of the incoming call is recognizable and the ASAI host controlling
the billing change requests reside on the local switch.
If two incoming calls are conferenced together, each with a Flexible Billing
user, the operation of the feature is unpredictable if the proper incoming
trunk call cannot be identified.
4. Subsequent rate requests work as follows:
If original and subsequent requests are ``flat charge or if both are
``new rate, the amount of change is overwritten.  The time stamp
at which the change is to be applied remains the same as when the
original change was requested.
If the original request is ``Premium Charge or ``Premium Credit,
the subsequent request can be either ``Premium Charge or
``Premium Credit.  The amount of the request and the type of
request replaces the original request.  The two requests are not
arithmetically combined.  The time stamp at which the change is to
be applied remains the same as when the original change was
requested.
Issue 4  September 1995  
10-5