McDewey

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

Page 1632

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

Call Info Events Action The API returns 0, indicating not a video capable device (CiscoMultiMedia CapabilityInfo.DISABLED) for TermB. App does CiscoCall. getCalledTerminalMulti MediaCapabilityInfo(). getCallingTerminalVideoCapability() on GC1. The API returns 1, indicating video capable device (CiscoMultiMedia CapabilityInfo.ENABLED) for TermA. The API returns 1, indicating video capable device(CiscoMultiMedia CapabilityInfo.ENABLED) for TermA. Variation 1: A and B are SIP Phone and have video enabled. User1 makes a call from A to B. B answers the call. App does CiscoCall. getCallingTerminalMulti MediaCapabilityInfo(). getVideoCapability() on GC1. App does CiscoCall. getCalledTerminalMulti MediaCapabilityInfo(). getCallingTerminalVideoCapability() on GC1 Scenario Sixteen Multiple redirects over SIP trunk (A, B, C and D are video enabled SIP Phones, A is in cluster 1 and B, C, D are in cluster 2). Phone A, B, C and D are in User1’s control list, Phone A, B, C and D are observed. Call Info Events Action ProvInServiceEv User1 Opens Provider and adds a provider observer CiscotermInServiceEv TermA CiscotermInServiceEv TermB CiscotermInServiceEv TermC CiscotermInServiceEv TermD User1 adds terminal observers on Phone A B, C, and D CiscoAddrInServiceEv A CiscoAddrInServiceEv B CiscoAddrInServiceEv C CiscoAddrInServiceEv D User1 adds callObserves on the address A, B, C, and D Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1568 Message Sequence Charts Scenario Sixteen

Page 1632 diagram