McDewey

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

Page 277

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

• Change in called party - In scenarios like Shared Lines or redirect, where the called party changes, the application will be notified of the new called party capability only if they configure the called party with unique display names. • HuntList - Cisco JTAPI will not deliver correct multimedia capabilities for calls involving huntlist in broadcast mode. Interface Changes See the following sections for interface changes: • CiscoCall, on page 332 • CiscoMasterKeyIndicator, on page 445 • CiscoMultiMediaCapabilityInfo, on page 468 • CiscoMultiMediaConnectionMode, on page 470 • CiscoMultiMediaEncryptionKeyInfo, on page 470 • CiscoMultiMediaProperties, on page 471 • CiscoMultiMediaStreamsInfoEv, on page 472 • CiscoMultiMediaType, on page 473 • CiscoProvTerminalMultiMediaCapabilityChangedEv, on page 489 • CiscoRTPPayload, on page 577 • CiscoRTPProperties, on page 578 • CiscoTermEvFilter, on page 614 • CiscoTerminal, on page 617 Message Sequences See Video Capabilities and Multi-Media Information, on page 1542. Backward Compatibility This feature is backward compatible. Video On Hold Support In Cisco Unified Communications Manager Release 10.01, existing CiscoTerminalConnection.hold() API is enhanced to take an additional parameter - contentID. This enhancement was designed/developed for the Remote Expert solution. This newly added contentID is a pass through from application (JTAPI) to CCM. JTAPI will not process or manipulate this value. The contentID will reference a VoH stream to be played when the call is placed on hold. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 213 Features Supported by Cisco Unified JTAPI Video On Hold Support

Page 277 content