McDewey

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

Page 1627

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

Call Info Events Action The API returns 1, indicating video capability is enabled (CiscoMultiMediaCapabilityInfo.ENABLED) for TermA (far-end party). App does CiscoCall. getCallingTerminal VideoCapability() on GC1. The API returns 1, indicating video capability is enabled (CiscoMultiMedia CapabilityInfo.ENABLED) for TermC (far-end party). App does CiscoCall. getCalledTerminalMult iMediaCapabilityInfo() on GC2. The API returns 1, indicating video capability is enabled (CiscoMultiMedia CapabilityInfo.ENABLED) for TermA (far-end party). App does CiscoCall. getCallingTerminal VideoCapability() on GC1. The API returns 1, indicating video capability is enabled (CiscoMultiMedia CapabilityInfo.ENABLED) for TermC (far-end party). CiscoMultiMediaStreamsInfoEv. getCalledTerminalMult iMediaCapabilityInfo on GC2. Scenario Fourteen Transfer: Phone A, B and C have video enabled, and A, B phones are in User1's control list and C is in User2's control list, A, B and C are in cluster1. Call Info Events Action ProvInServiceEv User1 Opens Provider and adds observer CiscotermInServiceEv TermA CiscotermInServiceEv TermB CiscotermInServiceEv TermC User1 adds terminal observers on Phone A and Phone B User2 adds terminal observers on Phone C. CiscoAddrInServiceEv A CiscoAddrInServiceEv B CiscoAddrInServiceEv C User1 adds callObserves on the address A and B User2 adds callObserves on the address C Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1563 Message Sequence Charts Scenario Fourteen

Page 1627 diagram