McDewey

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

Page 676

↗ View in doc context
page
676
source
cucm/v15/tapi-dev-guide/tapi-dev-guide.md
chunk_id
cucm::v15::tapi-dev-guide::tapi-dev-guide::690

Video Capability on Device C After Blindtransfer (A Is a SIP Phone Which Is Video-Disabled, B and C Are Video-Enabled) Expected events Action C: LINEGETCALLINFO::DEVSPECIFIC exposes CallingPartyVideoCapStatus = 0x000000000[CiscoDeviceVideoCapability_None] CalledPartyVideoCapStatus = 0x000000001[CiscoDeviceVideoCapability_Enabled LineInitializeEx A does a LineMakeCall to B. B does a blindtransfers to C, C answers Issue LineGetcallInfo() with Ext version for linedevice C LineShutdown Video Capability on Device C After Consult Transfer (A Is a SIP Phone Which Is Video-Disabled, B and C Are Video-Enabled) Expected events Action C: LINEGETCALLINFO::DEVSPECIFIC exposes CallingPartyVideoCapStatus = 0x000000001[CiscoDeviceVideoCapability_Enabled] CalledPartyVideoCapStatus = 0x000000001[CiscoDeviceVideoCapability_Enabled LineInitializeEx A does a LineMakeCall to B. B does a LineSetupTransfer to C, C answers B does a LineCompleteTransfer Issue LineGetcallInfo() with Ext version for linedevice C LineShutdown Video Capability on Device B on an Existing Call (Both A and B Are SIP Phones Which Are Video-Enabled) Expected events Action B: LINEGETCALLINFO::DEVSPECIFIC exposes CallingPartyVideoCapStatus = 0x000000001[CiscoDeviceVideoCapability_Enabled] CalledPartyVideoCapStatus = 0x000000001[CiscoDeviceVideoCapability_Enabled] A does a Call to B, B answers. LineInitializeEx Issue LineGetcallInfo() with Ext version for linedevice B LineShutdown B: LINEGETCALLINFO::DEVSPECIFIC exposes CallingPartyVideoCapStatus = 0x000000001[CiscoDeviceVideoCapability_Enabled] CalledPartyVideoCapStatus = 0x000000000[CiscoDeviceVideoCapability_None Variation 1: A has video enabled and B has video disabled. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 644 Message Sequence Charts Message Sequence Charts

Page 676 diagram