Lucent Technologies 555-230-220 User Manual
ASAI and Feature Interactions
12-54
Issue 7 May 1998
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.
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.
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.
Call. In this case the principal and temporary bridge will be dropped if redirection
is successful.
Terminating Extension Group (TEG)
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 member’s 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 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.
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 member’s 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 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 member’s domain control
associations until the entire TEG drops from the call (as opposed to an individual
member going on-hook).
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.
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.
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 as the originator. TEGs can only receive calls, not originate them.
A TEG is not eligible for a Single-Step Conference request.
group extension as the originator. TEGs can only receive calls, not originate them.
A TEG is not eligible for a Single-Step Conference request.