McDewey

Call Info Events Action 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 TermD. The API returns -1, indicating telepresence is UNKNOWN for TermA. The API returns -1, indicating telepresence is UNKNOWN for TermC. The API returns -1, indicating screen count is UNKNOWN for TermA. The API returns -1, indicating screen count is UNKNOWN for TermC. App does CiscoCall. getCallingTerminal MultiMediaCapabilityInfo(). getVideoCapability() on GC1. App does CiscoCall. getCalledTerminal MultiMediaCapabilityInfo(). getCallingTerminalVideoCapability() on GC1. App does CiscoCall. getCallingTerminal MultiMediaCapabilityInfo(). getTelepresenceInfo() on GC1. App does CiscoCall. getCalledTerminal MultiMediaCapabilityInfo(). getTelepresenceInfo() on GC1. App does CiscoCall. getCallingTerminal MultiMediaCapabilityInfo.getScreenCount() on GC1. App does CiscoCall. getCalledTerminalMulti MediaCapabilityInfo. getScreenCount() on GC1. Video On Hold Pre-conditions to all video on hold use cases, unless specified otherwise: • Provider is in IN_SERVICE state • All addresses and terminals are already in service. • Device A (IP Phone – Name: “SEP2401C7824EA3”, Line A1 (dn: 9000)) • Device B (IP Phone – Name: “SEP2401C7824EAE”, Line B1 (dn: 9001)) • The content id corresponding to VoH stream is contentID1. • User1 has in its control list: Devices A and B. All devices and lines are observed. Scenario One Invoke hold() on basic call between two ip phones to stream video to the held party Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1581 Message Sequence Charts Video On Hold