ASAI Application Planning and Design
tains the call ID of the original call delivered to Agent 1. Also, for example, the Calling Party Number field of this CONNECT event contains the ANI of the original caller.
■If for some reason calls are transferred to
■The END event that is reported for the transferred call contains information pertinent to the original call. For example, the original ANI for the caller is reported in the Calling Party Number field and the call ID for the original call is reported in the Other Call ID field. This is true even though the second CONNECT event for consult transfers to monitored domains does not con- tain information pertinent to the original call. This is because the END event is reported after consult transfers to monitored domains are com- pleted (that is, after the two calls are merged and can be associated by the internal software on the VIS). Also, an END event is reported for a call only when the call ultimately terminates (that is, an END event is not reported when a call is transferred).These properties for END events allow the host application to consistently use the Other Call ID field of END events to identify when and which calls have left the DEFINITY Generic 3i entirely.
■The call may again be transferred after having been serviced by Agent 2. In this case, an END event is not reported until all transferring is completed and the call terminates normally. As in the single transfer case, the END event contains information pertinent to the original call. Rules for how sub- sequent CONNECT events are reported are as described in this chapter and depend on whether the call is transferred to a monitored domain or to a station and whether consult or blind transfer operation is used.
