Lucent Technologies 555-230-220 Life Jacket User Manual


 
ASAI and Feature Interactions
Issue 7 May 1998
12-29
Further, when CDR Call-Splitting changes the charging number, the original
charging number will receive a charging event with charge type, ‘‘split charge.’’
Consult
When the covering user presses the Conference or Transfer feature button and
receives dial tone, a Hold Event Report is returned to all adjuncts monitoring the
call. A Call Initiated Event Report is then sent to the covering user on the
domain-control associations monitoring the covering user. After the Consult
button is pressed by the covering user, Alerting and Connected Event Reports for
the principal are returned to associations monitoring the principal and covering
user. The covering user can then conference or transfer the call.
Selective Listening
Conferencing is not affected by the Selective Listening feature. If a listener was
third party listen-disconnected in the original call prior to the conference, then this
listener will remain listen-disconnected to the talkers on the newly conferenced
call.
Data Calls
Data calls cannot be originated via the Third Party Make Call or Third Party Auto
Dial capabilities. Analog ports equipped with modems can be domain-controlled
and calls to and from these ports can be controlled and monitored. However, Call
Control capabilities may cause the call to be dropped by the modem.
Starting with R5: An implementation option
does
allow outgoing data calls that use
charge advice trunk facilities and that generate charging information from the
network to be presented to the adjunct as Charging Event Reports. No further
ASAI operations on data calls that are referenced by any Charging Event Report
are supported.
DCS
With respect to ASAI event reporting, calls made over a DCS network are treated
as off-ECS calls and only the Call Initiated, Trunk Seized, Call Ended, and/or
Disconnect/Drop Event Reports are returned. DCS/UDP extensions that are local
to the ECS are treated as on-ECS stations. DCS/UDP extensions connected to
the remote nodes are treated as off-ECS numbers.
ASAI does not currently support DCS calls completely. DCS calls may or may not
provide accurate information to an ASAI adjunct. In a pure DCS environment, if
the DCS calling party information is available to the ECS (if a station with a display
gets it), this information is also made available to ASAI. Otherwise, calling party
information is provided as the default (*****).