McDewey

Event/Call info Result Action Events received at Call Observer on A, B GC1 TermConnDroppedEv A GC1 CallCtlTermConnDroppedEv TA GC1 TermConnDroppedEv TA' GC1 CallCtlTermConnDroppedEv TA' GC1 ConnDisconnectedEv A GC1 CallCtlConnDisconnectedEv A GC1 ConnCreatedEv P1 GC1 ConnInProgressEv P1 GC1 CallCtlConnQueuedEv P1 Note New event is not seen as Cisco Unified IP Phone 7900 Series does park Step 1 Application invokes CiscoConnection.park() on connection on A. Park reversion timer starts Reason = CiscoFeatureReason.PARKREMINDER Events received at Call Observer on A, B GC1 ConnCreatedEv A GC1 ConnInProgressEv A GC1 CallCtlConnOfferedEv A GC1 ConnAlertingEv A GC1 CallCtlConnAlertingEv A GC1 TermConnCreatedEv TA GC1 TermConnRingingEv TA GC1 CallCtlTermConnRingingEvImpl TA GC1 ConnInProgressEv A GC1 ConnAlertingEv A GC1 TermConnCreatedEv TA' GC1 TermConnRingingEv TA' GC1 CallCtlTermConnRingingEvImpl TA' GC1 ConnDisconnectedEv P1 GC1 CallCtlConnDisconnectedEv P1 Note All shared lines including the Cisco Unified IP Phone (future model) phone A receives the incoming call Step 2 Consider Park Reversion timer expires • Call is reverted to parker's line A Use Case 4: Use Case for Snap Shot Scenario Initial scenario: Application has added Call Observer on A, B. Application has NOT added Address Observer on A. B calls A. A answers. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1211 Message Sequence Charts Use Case 4: Use Case for Snap Shot Scenario