Lucent Technologies 555-230-220 User Manual
ASAI and Feature Interactions
12-12
Issue 7 May 1998
Interflow
This occurs when a split redirects all calls to another split on another ECS by
activating off-premises call forwarding. This can also be done by vectoring with
the route to number command to a destination off the ECS.
activating off-premises call forwarding. This can also be done by vectoring with
the route to number command to a destination off the ECS.
When an adjunct-monitored call interflows, adjunct notification ceases except for
the Trunk Seized (for a non-PRI trunk) and Disconnect/Drop Event Reports.
However, it is possible to receive other events for PRI trunks.
the Trunk Seized (for a non-PRI trunk) and Disconnect/Drop Event Reports.
However, it is possible to receive other events for PRI trunks.
Switch-classified calls can be interflowed but no call classification is done since
the original call was to a local extension. The originator of the switch-classified
calls should not be interflowed, since the adjunct would no longer be able to
control the call.
the original call was to a local extension. The originator of the switch-classified
calls should not be interflowed, since the adjunct would no longer be able to
control the call.
Intraflow
This occurs when a call is redirected from one split to another split within the
same ECS by following the split’s coverage path. When an adjunct-monitored call
intraflows, it retains the adjunct-monitored call status. Switch-classified calls can
also be intraflowed.
same ECS by following the split’s coverage path. When an adjunct-monitored call
intraflows, it retains the adjunct-monitored call status. Switch-classified calls can
also be intraflowed.
If a call leaves (that is, covers to) an adjunct-monitored split and enters another
adjunct-monitored split, then a redirected event report is sent over the first
monitoring association. Events will continue to be reported over the other
monitoring association.
adjunct-monitored split, then a redirected event report is sent over the first
monitoring association. Events will continue to be reported over the other
monitoring association.
Also, this occurs when a call is directed from one split to another by: 1) following
the split’s coverage path, 2) Call Forwarding, or 3) Call Vectoring via
Queue-to-Main steps or Check Backup Split steps.
the split’s coverage path, 2) Call Forwarding, or 3) Call Vectoring via
Queue-to-Main steps or Check Backup Split steps.
Note that the direct-agent call does not intraflow since it follows the agent’s
coverage path rather than the split’s.
coverage path rather than the split’s.
Night Service
Third Party Make Calls to splits in night service go to night service. A
switch-classified Third Party Make Call originated from a split with the Night
Service feature active is delivered to the night service extension. Calls in queue
when this feature is activated remain in queue. The Call Offered to Domain Event
Report is sent when a call that is not an adjunct-monitored call enters an ACD split
(not adjunct-controlled) with active notification and also has night service active.
switch-classified Third Party Make Call originated from a split with the Night
Service feature active is delivered to the night service extension. Calls in queue
when this feature is activated remain in queue. The Call Offered to Domain Event
Report is sent when a call that is not an adjunct-monitored call enters an ACD split
(not adjunct-controlled) with active notification and also has night service active.
Direct-agent calls are routed to the hunt group’s night service extension if night
service was activated for the specified split, even if the priority calling option is
enabled. This is the same as regular ACD calls.
service was activated for the specified split, even if the priority calling option is
enabled. This is the same as regular ACD calls.