/mcpCall Info Events Action B does GC1.transfer (GC2). C answers The API returns 3 (INACTIVE) CiscoMultiMediaStreamsInfoEv. getProperties ().getMultiMediaConnectionMode () on Terminal B The API returns 0 (ACTIVE) CiscoMultiMediaStreamsInfoEv. getProperties ().getMultiMediaConnectionMode () on Terminal C The API returns 0 (ACTIVE) CiscoMultiMediaStreamsInfoEv. getProperties ().getMultiMediaConnectionMode () on Terminal A The API returns 1, indicating video capability is known (CiscoMultiMedia CapabilityInfo.ENABLED ) for TermC ( far-end party). App does CiscoCall. getCalledTerminal MultiMediaCapabilityInfoon GC2. The API returns 1, indicating video capability is known (CiscoMultiMedia CapabilityInfo.ENABLED ) for TermA ( far-end party). App does CiscoCall. getCallingTerminalMultiMediaCapabilityInfo () on GC2. The API returns 1, indicating video capability is known (CiscoMultiMedia CapabilityInfo.ENABLED ) for TermC ( far-end party). App does CiscoCall. getCalledTerminalMultiMediaCapabilityInfo ().getCallingTerminalVideoCapability () onGC1. The API returns 1, indicating video capability is known (CiscoMultiMedia CapabilityInfo.ENABLED ) for TermA ( far-end party). App does CiscoCall. getCallingTerminalMultiMediaCapabilityInfo () on GC1. Scenario Fifteen Negotiated video capability will be reported to the called party across a cluster call (over SIP – ICT trunk) using early offer (Phone A is a video disabled SIP Phone in cluster 1 and Phone B is a video enabled SIP Phone in cluster 2). User1 has Phone A in the control list, Phone A is observed. Call Info Events Action ProvInServiceEv User1 Opens Provider and adds a provider observer Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1566 Message Sequence Charts Scenario Fifteen