/mcpCall 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. getCallingTerminalMulti MediaCapabilityInfo(). getVideoCapability() on GC1. App does CiscoCall. getCalledTerminalMulti MediaCapabilityInfo(). getCallingTerminalVideoCapability() on GC1. App does CiscoCall. getCallingTerminalMulti MediaCapabilityInfo(). getTelepresenceInfo() on GC1. App does CiscoCall. getCalledTerminalMulti MediaCapabilityInfo(). getTelepresenceInfo() on GC1. App does CiscoCall. getCallingTerminalMulti MediaCapabilityInfo.getScreenCount() on GC1. App does CiscoCall. getCalledTerminalMulti MediaCapabilityInfo.getScreenCount() on GC1. Scenario Twenty Redirect over H323 trunk (Phone A is video enabled SIP Phone and Phone B and C have video disabled, Phone A is in cluster 1 and Phone B and C are in cluster 2). Phone A and B are in User1’s control list and Phone C is in user2’s control list, Phone A, B and C are observed. Call Info Events Action ProvInServiceEv User1 Opens Provider and adds a provider observer CiscotermInServiceEv TermA CiscotermInServiceEv TermB User1 adds terminal observers on Phone A and Phone B CiscoAddrInServiceEv A CiscoAddrInServiceEv B User1 adds call Observes on the address A and B Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1578 Message Sequence Charts Scenario Twenty