McDewey

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

Page 1599

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

Scenario 17 Application is observing the devices A, B and C. Phone A is a normal SCCP/SIP phone, B is Cisco Unified IP Phone 6901 and phone C is a normal SCCP/SIP phone. B and C have a shared line. Application initiates a call from phone A to shared line on B and C. B goes off-hook and answers the call. Configuration: • Phone A and C – SCCP/SIP Device • Phone B – Cisco Unified IP Phone 6901 Call info Result Action CiscoAddrInServiceEv – A CiscoAddrInServiceEv – B CiscoAddrInServiceEv - C Application observes A, B and C. GC1: CallActiveEv ConnCreatedEv –A ConnConnectedEv – A CallCtlConnInitiatedEv - ATermConnCreatedEv - [Term A] TermConnActiveEv –[Term A] CallCtlTermConnTalkingEv –[Term A]





A initiates a call to the shared line on B and C ConnConnectedEv B CallCtlConnEstablishedEv B TermConnCreatedEv [Term C] TermConnPassiveEv [Term C] CallCtlTermConnInUseEv [Term C] TermConnActiveEv [Term B] CallCtlTermConnTalkingEv [Term B] B goes off-hook and answers the call. SHA Support for Digital Signatures The following tables display the CallInfo messages for the following three use cases: • SHA-1 is the configured encryption algorithm Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1535 Message Sequence Charts SHA Support for Digital Signatures

Page 1599 diagram