Filter
Top Products
ASAI and Feature Interactions
12-56 Issue 7 May 1998
is recorded as the originating station in any subsequent Charging Event Reports.
Because CDR Call Splitting changes the charging number, the original charging
number will indicate a charge type of ‘‘split charge’’ in the Charging Event Report.
Regardless of whether CDR Call Splitting is active, if an incoming call is
transferred by a local station to an outgoing AOC trunk, then the charging number
in the next Charging Event Report will be the extension number of the local
station.
If a station originates an outgoing call on an AOC trunk and then transfers the call
to a VDN, any subsequent Charging Event Report sent to the adjunct while the
call is in vector processing will indicate the originating station as the charging
number
Trunk-to-Trunk Transfer
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).
The trunk-to-trunk transfer option does not interact with Redirect Call from
incoming trunk to outgoing trunk.
VDN Override
Incoming ISDN PRI calls routed to multiple VDNs do not observe the VDN
Override field setting, and always provide the called number information from the
SETUP message to ASAI.
Incoming non-ISDN PRI calls do follow the VDN override rules and provide the
corresponding called number information in ASAI events.
Voice (Synthesized) Message Retrieval
A recording, “Please call message center for more messages,” is used for the
case when the MWL has been activated by the adjunct through the Set Value
capability.
World Class BRI
ASAI does not support World Class BRI stations.