Event Reporting and
Event Reporting for Merging Two
Calls
This section covers the rules for sending events when two calls with different characteristics are merged for a transfer or a conference. For the purpose of these rules, it does not matter how the calls were merged (manually or via the Third Party Merge capability).
Call merging rules are as follows:
1.Merging two
■A Third Party Call Ended capability is sent for the call identifier that has been released as a result of the merge on the association that is controlling the call.
■The Call Transferred or Call Conferenced Event Report is sent over the association controlling the resulting call identifier.
■Subsequent event reports for the merged call are sent over the Call Control association controlling the resulting call identifier.
2.Merging two monitored calls (Event Notification is active)
■A Call Ended Event Report is sent over the association monitoring the call for the call identifier that has been dropped.
■The Call Transferred or Call Conferenced Event Reports are sent to the association monitoring the resulting call identifier.
■Subsequent event reports are sent over the Event Notification association monitoring the resulting call identifier.
3.Merging one
■The Call Transferred or Call Conferenced Event Reports are sent over the Third Party Call Control association. This association continues to report subsequent events for the remaining call.
4.Merging one monitored call (Event Notification active) with a nonmonitored call (Event Notification and Third Party Call Control are not active)
■The Call Transferred or Call Conferenced Event Reports are sent over the Event Notification association.
■Subsequent event reports are sent over the Event Notification association of the monitored call. In the case where the resulting call is the nonmonitored call, the Call Conferenced or Call Transferred Event Report is the very first event the adjunct receives with a new call identifier. If the resulting call identifier is from the
