ATT DEFINITY Communications System Generic 3V4 Instructions Manual

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Facility Restriction Levels (FRLs)bbbbbbbb
Third Party Make Calls are placed using the originators COR, the stations COR,
or the splits COR.
Forced Entry of Account Codesbbbbbbbb
Third Party Auto Dial or Third Party Make Call call attempts to Trunk Groups with
the Forced Entry of Account Codes feature assigned are allowed.  It is up to the
originating station user to enter the account codes via the touch-tone pad.
Account codes may not be provided via the ASAI.  If the originator of such a call
is logged into an adjunct-controlled split (and therefore has the voice set locked),
such a user is unable to input the required codes and will eventually get denial
treatment.
Holdbbbbbbbb
Manually holding a call (either by using the Hold, Conference, Transfer buttons,
or switch-hook flash) results in the Hold Event Report being sent to all active
associations for this call, including the held extension.  A held party is considered
connected on the call for the purpose of receiving events relevant to that call.
Hot Linebbbbbbbb
A Third Party Auto Dial or a Third Party Make Call request made on behalf of a
controlled extension that has this feature administered is denied by the switch.
Integrated Services Digital Network
(ISDN)
bbbbbbbb
The Third Party Auto Dial calls follow Integrated Services Digital Network (ISDN)
rules for the originators name and number.  The Call Initiated Event Report is
not sent for 
en-bloc BRI sets.
Last Number Dialedbbbbbbbb
The called party address (dest_addr) provided in a Third Party Make Call or Third
Party Auto Dial capability is the last number dialed for the calling party
(orig_addr) until the next call origination from the calling party. Therefore, the
user can use the ``last number dialed button to originate a call to the destination
provided in the last Third Party Make Call or Third Party Auto Dial capability. This
does not apply to switch-classified calls.
12-34  Issue 4  September 1995 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Leave Word Callingbbbbbbbb
When activated at the callers extension, Leave Word Calling will attach itself to
the principals extension, even if the call was redirected via Redirect Call.
Lookahead Interflowbbbbbbbb
When a DEFINITY switch attempts to send a monitored call to another
DEFINITY using the Lookahead Interflow capability, the second switch may
reject the interflow attempt. If this happens, any ASAI message associated with
this call that contains Called Party Number information sent by the first
DEFINITY will contain the administered extension of the VDN that received the
call, instead of the original dialed number as presented by the network. If the
interflowed call is accepted by the other switch, however, the Called Party
Number presented in the Alerting and Connected event reports, by the first
switch, will be the default trunk extension.
Multiple Split Queuingbbbbbbbb
When a call is queued in multiple ACD splits, the party query provides, in addition
to the originator, only one of the split extensions in the party list.  When the call is
de-queued, the Alerting Event Report provides the split extension of the alerting
agent.  No other events are provided for the splits from which the call was
removed.
Music On Holdbbbbbbbb
Music on hold (if administered and available) is given to a party placed on hold
from the other end either manually or via the adjunct.
Personal Central Office Line (PCOL)bbbbbbbb
Members of a Personal Central Office Line (PCOL) may be domain-controlled.
PCOL behaves like bridging for the purpose of ASAI event reporting.  When a
call is placed to a PCOL group, the Alerting Event Report is provided to each
members domain-control associations.  The called number information passed in
the alerting message is the default station characters.  When one of the
members answers the incoming call, the Connected Event Report provides the
extension of the station that answered the call. If another member connects to
the call, another Connected Event Report is provided.  When a member goes
on-hook but the PCOL itself does not drop from the call, no event is sent but the
state of that party changes from the connected state to the bridged state.  The
Disconnect/Drop Event Report is not sent to each members domain-control
associations until the entire PCOL drops from the call (as opposed to an
individual member going on-hook).  Members that are not connected to the call
while the call is connected to another PCOL member are in the bridged state.
Issue 4  September 1995  
12-35 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
When the only connected member of the PCOL transitions to the held state, the
state for all members of the PCOL changes to the held state even if they were
perviously in bridged state. No event report is sent to any domain-control
association(s) for bridged users for this transition.
All members of the PCOL may be individually domain-controlled.  Each receives
appropriate events as applicable.  Call Control requests are not recommended
for PCOL endpoints.  Third Party Selective Hold, Third Party Merge, Third Party
Reconnect, and Third Party Selective Drop are not permitted on parties in the
bridged state and may also be more restrictive if the exclusion option is in effect
from a station associated with the PCOL.
A Third Party Auto Dial or Third Party Make Call originates at the primary
extension number of a user.  For a call to originate at the PCOL call appearance
of a primary extension, that user must be off-hook on the PCOL call appearance
at the time the request is received.
If a party_id query is requested while the PCOL is alerting or on hold, one party
member is reported for the group with the extension number specified as the
default extension.
If a call query is requested on an extension while the PCOL call is active, only
one call appearance is associated with the particular call_id.
Third Party Call Control should not be used in conjunction with the PCOL feature.
Primary Rate Interface (PRI)bbbbbbbb
Primary Rate Interface (PRI) facilities may be used for either inbound or
outbound adjunct-monitored calls.
An incoming call over a PRI facility provides the calling and called party
information (CPN/BN/DNIS), which is passed on to the adjunct in the Call
Offered to Domain Event Report and the Route capabilities as well as to events
(for example, Alerting or Connected.)
An outgoing call over a PRI facility provides call feedback events from the
network.
Switch-classified calls always use a call classifier on PRI facilities, whether the
call is interworked or not.  Although these facilities are expected to report call
outcomes on the ``D channel, often interworking causes loss or delay of such
reports.  Progress messages reporting ``busy, SITs, ``alert, and
``drop/disconnect cause the corresponding event report to be sent to the
adjunct.  For switch-classified calls, the ``connected number is interpreted as
``far end answer and is reported to the adjunct as the Answered Event Report
when received before the call classifiers ``answer indication.  When received
after the call classifier has reported an outcome, it is not acted on. All outbound
adjunct-monitored calls over PRI facilities do not generate the Trunk Seized
Event Report.  They may, however, generate the Alerting, Connected,
12-36  Issue 4  September 1995 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Disconnect/Drop, and/or Call Ended Event Reports.  If such a call goes ISDN
end-to-end, other events are possible (for example, Alerting, Connected Event
Reports).  If such a call interworks, the PROgress message is mapped into a
Cut-Through Event Report.  In this case, only the Disconnect/Drop or Call Ended
Event Reports may follow.
ASAI may provide UUI for inclusion in the Setup message for an outgoing ISDN-
PRI call.  This UUI can be provided in the ASAI Third Party Make Call, Auto Dial,
or Route Select message.  ASAI may receive UUI that was included in an
incoming ISDN-PRI Setup message.  This UUI will be included in any of the
following messages, if they are sent for the call:  Call Offered to Domain Event
Report, Alerting Event Report, Route request.
ASAI may provide UUI for inclusion in an ISDN Disconnect message by including
that UUI in the 3rd Party Drop message.  ASAI may receive UUI that was
included in an ISDN Disconnect message.  The UUI would be included in a Drop
event report, if one is sent to ASAI.
Priority Callingbbbbbbbb
Calls originated via the Third Party Auto Dial or the Third Party Make Call
capability can be priority calls, if the adjunct specifies the 
priority-call option in the
Third Party Auto Dial request.  The user can also originate a priority call by going
off-hook, dialing the feature access code for priority calling, and requesting a
Third Party Auto Dial or a Third Party Make Call capability.
Privacy-Manual Exclusionbbbbbbbb
Activation of this feature affects all call control requests associated with other
members of the bridge, TEG, or PCOL, if they try to originate on the bridged,
TEG, or PCOL line appearance and affects the use of the analog principals
station if activated by a bridging user.
The exclusion feature can be activated associated with bridges, TEGs, or
PCOLs.  An exclusion button must be defined for the station that wishes to utilize
this feature.  Analog stations cannot utilize this feature since they do not have
feature buttons.  Activation of this feature when the station is a member of a
bridge, TEG, or PCOL causes all other connected members of the group to
transition to the bridged state.  In addition, other members receive denial when
they attempt to manually connect to the call.
Pressing the exclusion feature button toggles the feature from on to off as
indicated by the green light associated with the button.
Issue 4  September 1995  
12-37 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Ringback Queuingbbbbbbbb
Adjunct-routed or switch-classified calls are allowed to queue on busy trunks or
stations.
When activated, the call back call reports events on the same call_id as the
original call.
Send All Calls (SAC)bbbbbbbb
The adjunct can activate this feature by issuing a Request Feature capability. An
adjunct can request a Third Party Make Call or Third Party Auto Dial capability
for a station that has SAC activated.
12-38  Issue 4  September 1995 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
A Third Party Auto Dial call to a station with the SAC feature active redirects to
the covering station.
For incoming calls, the Alerting Event Report is sent only for multifunction sets
receiving calls while having SAC activated. The Alerting Event Report is not
generated for analog sets when the SAC feature is activated and the set is
receiving a call.
Direct-agent calls existing in the agent queue when this feature is activated are
not sent to coverage.  Only the new direct-agent calls are affected by activation
of this feature.
While SAC is active at a station, agent status value queries will show that an
agent is busy.
SAC is ignored for priority direct-agent call and for switch-classified call
destinations.  If a SACed call rings at a station with Domain Control, then the
Alerting event includes a cause value indicating SAC as the reason the call
redirected.
Service Observingbbbbbbbb
Domain-controlled stations may be service-observed and may also be observers.
When a domain-controlled station is the observer, and is bridged onto a call for
the purpose of service observing, the Connected Event Report is sent on
domain-controlled associations for the observers adjunct as well as to all other
associations for that call.
Single-Digit Dialing and Mixed
Station Numbering
bbbbbbbb
A call initiated using the Third Party Auto Dial capability is permitted to use single
digit dialing.
Station Message Detail Recording
(SMDR)
bbbbbbbb
Calls originated by the adjunct via the Third Party Auto Dial or Third Party Make
Call capabilities are marked with the condition code ``B.  Adjunct-originated calls
include: calls originated by forcing the user off-hook after a Third Party Auto Dial
or Third Party Make Call request; calls originated by the user going off-hook and
then requesting Third Party Auto Dial or Third Party Make Call; and calls
originated by the user going off-hook, dialing a few digits, and then requesting
Third Party Auto Dial or Third Party Make Call.
Calls originated manually from a domain-controlled station are not marked with
Issue 4  September 1995  
12-39 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
condition code ``B.  Switch-classified calls are marked with condition code ``B
and show either the ACD split or the agents extension (depending on how it has
been administered) as the originator.
System Reportsbbbbbbbb
The list station command indicates whether or not a given BRI link is ASAI.
Temporary Bridged Appearancesbbbbbbbb
The operation of this feature has not changed with ASAI. No event is provided
when a temporary bridged appearance is created at a multifunction set.  If the
user is connected to the call (becomes active on such an appearance), the
Connected Event Report is provided.  If a user goes on-hook after having been
connected on such an appearance, a Disconnect/Drop Event Report with cause
CS0/16 (normal clearing) is generated for the disconnected extension (bridged
appearance).
If the call is dropped from the temporary bridged appearance by someone else, a
Disconnect/Drop Event Report is also provided.
Temporary bridged appearances are not supported with analog sets.  Analog
sets get the Call Redirected Event Report when such an appearance would
normally be created for a multifunction set.
The call state provided to queries about extensions with temporary bridged
appearances is ``bridged if the extension is not active on the call or ``connected
if the extension is active on the call.
The Third Party Selective Drop request is denied for a temporary bridged
appearance that is not connected on the call.
Calls alerting at temporary bridged appearances may be redirected via Redirect
Call. In this case the principal and temporary bridge will be dropped if redirection
is successful.
Terminating Extension Group (TEG)bbbbbbbb
Members of a Terminating Extension Group (TEG) may be domain-controlled.
A TEG behaves similarly to bridging for the purpose of ASAI event reporting.  If
controlled stations are members of a terminating group, an incoming call to the
group causes an Alerting Event Report to be sent to all domain-control
associations for members of the terminating group. On the domain-control
association for the member of the group that answers the call, a Connected
Event Report is returned to the answering members domain-control
association(s) that contains the station that answered the call. All domain-control
associations for the other group members (nonanswering members without TEG
12-40  Issue 4  September 1995 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
buttons) receive a Call Redirected Event Report.  When a button TEG member
goes on-hook but the TEG itself does not drop from the call, no event is sent but
the state of that party changes from the connected state to the bridged state.
The Disconnect/Drop Event Report is not sent to each members domain control
associations until the entire TEG drops from the call (as opposed to an individual
member going on-hook).
Members not connected to the call while the call is connected to another TEG
member are in the bridged state.  When the only connected member of the TEG
transitions to the held state, the state for all members of the TEG changes to the
held state even if they were previously in the bridged state.  There is no event
report sent over the domain-control associations for the bridged user(s) for this
transition.
All members of the TEG may be individually domain-controlled.  Each receives
appropriate events as applicable to the controlled station.  Call Control requests
work normally if invoked over the station domain.  However, Third Party Selective
Hold, Third Party Merge, Third Party Reconnect, and Third Party Selective Drop
are not permitted on parties in the bridged state and may also be more restrictive
if the exclusion option is in effect from a station associated with the TEG.
Third Party Auto Dial or Third Party Make Call requests cannot specify the TEG
group extension.  TEGs can only receive calls, not originate them.
If a party_id query is requested while the TEG is alerting or on hold, one party
member is reported for the group with the extension number specified as the
TEG group extension (as the originator).
If a call query is requested on an extension while the TEG call is active, only one
call appearance is associated with the particular call_id.
Timed Reminderbbbbbbbb
Third Party Auto Dial calls extended by an attendant and not answered redirect
back to the attendant when the timed reminder interval expires.  See ``Attendant
Call Waiting earlier in this chapter for events returned to the adjunct.
Issue 4  September 1995  
12-41 
						

							ASAI and Feature Interactionsbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Transferbbbbbbbb
Manual transfer from a domain-controlled station is allowed subject to the
features restrictions.  The Hold Event Report is provided as a result of the first
button push (or switch-hook flash for analog sets).  The Call Transferred Event
Report is provided as a result of the second button push (or on-hook for analog
sets), and only if the transfer is successfully completed.  The Transfer Event
Report is sent to all active associations for the resultant call.
Trunk-to-Trunk Transferbbbbbbbb
Existing rules for trunk-to-trunk transfer from a station user remain unchanged for
adjunct-monitored calls.  In such cases, transfers requested via Third Party
Merge are negatively acknowledged (NAKed).  When this feature is enabled,
adjunct-monitored calls transferred from trunk to trunk are allowed, but there is
no further notification (except for the Trunk Seized and Disconnect/Drop Event
Reports sent to the adjunct).
Voice (Synthesized) Message
Retrieval
bbbbbbbb
A recording, ``Please call message center for more messages, is used for the
case when the MWI has been activated by the adjunct through the Set Value
capability.
12-42  Issue 4  September 1995 
						

							bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
bbbbb
CallVisor ASAI Over the
DEFINITY LAN Gateway
13
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
Overviewbbbbbbbb
A new transport option, CallVisor ASAI Over the DEFINITY LAN Gateway, is
available in DEFINITY G3V4, and in DEFINITY G3V2/G3V3 with a field
maintenance upgrade.  This option incorporates a system assembly that uses a
Multi-Function Board (MFB), a DEFINITY LAN Gateway circuit pack that
supports an Ethernet controller and a software environment. The software
environment, in turn, supports the DEFINITY LAN Gateway application that
serves as an ISDN brouter of ASAI messages through a TCP ``tunnel via
10BaseT Ethernet.
1
While CallVisor ASAI over the DEFINITY LAN Gateway supports the same
Q.931 messages used for ASAI-BRI, it replaces the ISDN BRI transport layers
below layer three with a simple TCP protocol described in the 
DEFINITY
Communications System CallVisor ASAI Protocol Reference
, 555-230-221.
aaaaaaaaaaaaaaaaaaa
1.  In  local area networking, a brouter is a device that combines the dynamic routing capability of an internetwork
router with the ability of  a bridge to interconnect dissimilar local area networks (LANs).  It has the ability to
route one or more protocols and bridge all other traffic.  The DEFINITY LAN Gateway application links ISDN
and TCP/IP at both a physical and addressing level.
Issue 4  September 1995  13-1