184 Chapter 8 Troubleshooting213346.02Consider a second scenario, where agent C disconnects prior to the completion ofthe conference call. Meridian Link Services does not send any message indicatingthat agent C disconnected. In this situation Symposium TAPI SP, andsubsequently the TAPI application, lose track of the true state of the call. In such ascenario Symposium TAPI registers the call events as follows:• Agent A establishes a call to agent B — CallHandle1 = CONNECTED.• Agent A places a consultation call to agent C resulting in the following:— CallHandle1 = CONFERENCED— CallHandle2 = DIALTONE— CallHandle3 = ONHOLDPENDCONF• Agent C answers the consultation call and all call handles remain the same.• Agent C disconnects before agent A completes the conference call and all callhandles remain the same.The behavior in this scenario is not typical and would not be expected by a TAPIapplication. CallHandle2 and CallHandle3 ought to change to the idle state, whileCallHandle1 ought to change to the onhold state.The same problem can occur with a supervised transfer, given the same threephones as described in the earlier scenarios. No messages are sent when agent Canswers the consultation call, or when agent C drops a call prior to completion ofthe supervised transfer.Status change messages not deliveredIf a transfer consultation call is dropped after it is answered but before it iscompleted, Symposium TAPI SP does not deliver status change messages exceptin the following circumstances:• The third party does not answer.• The consultation call is to an AST-monitored telephone set.If the consultation call is to an AST-monitored telephone set, the internal status isrelayed back to the telephone set that initiated the call, enabling proper recovery.When a three-party conference is manually created and put on hold, MeridianLink Services does not send a status change message to Symposium TAPI SP,with the result that the service provider does not know the call is on hold.
