McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 1282

↗ View in doc context
page
1282
source
cucm/v15/jtapi-dev-guide/jtapi-dev-guide.md
chunk_id
cucm::v15::jtapi-dev-guide::jtapi-dev-guide::1286

Additional Use Cases for Park Monitoring Phone B—Cisco Unified IP Phone 7900 Series with SIP/SCCP Phone A—Future models. Phone A’—Cisco Unified IP Phone 7900 Series with SIP/SCCP Park DN—P1, P2 Phone C—Cisco Unified IP Phone 7900 Series with SIP/SCCP All the default values for the Park Monitoring Reversion timer and Park Monitoring Forward No reversion timers apply. 1. Initial scenario: Application has added Call Observer on A and B. Application has added Address Observer on A. B calls A. A answers. Filter value has been set to ‘true’ through setCiscoAddrParkStatusEvFilter(). Event/Call info Result Action Cause = CAUSE_NORMAL park state = PARKED sub ID = 1234 CiscoCallID = CiscoCallID for GC1 park DN = P1 parked party = B terminal = TA Events received at Call Observer on A, B GC1 TermConnDroppedEv A GC1 CallCtlTermConnDroppedEv TA GC1 ConnDisconnectedEv A GC1 CallCtlConnDisconnectedEv A GC1 ConnCreatedEv P1 GC1 ConnInProgressEv P1 GC1 CallCtlConnQueuedEv P1 Events received at Address Observer on A CiscoAddrParkStatusEv A Step 1 • Application invokes CiscoConnection.park() on connection on A. • Park Monitoring Reversion timer starts Cause = CAUSE_NORMAL park state = REMINDER sub ID = 1234 CiscoCallID = CiscoCallID for GC1 park DN = P1 parked party = B terminal = TA Events received at Address Observer on A CiscoAddrParkStatusEv A Step 2 After step 1, Park Monitoring reversion timer expires after the configured time Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1218 Message Sequence Charts Additional Use Cases for Park Monitoring

Page 1282 diagram