McDewey

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

Page 652

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

TAPI structures TAPI messages Action LINE_CALLSTATE -Param1 = DIALTONE LINE_CALLSTATE -Param1 = DIALING Calls on Enterprise Phone[B] : Call1 [C ' A1]: LINE_CALLSTATE -Param1 = ONHOLD Call1 [A1 ' D]: LINE_CALLSTATE - Param1 = CONNECTED Param2 = 0x02 (Inactive) Consult Call on CTI Remote Device[A] [A1 ' D]: LINE_CALLSTATE -Param1 = PROCEEDING LINE_CALLSTATE -Param1 = RINGBACK LineDial() on Consult call with DN -D Secondary Call on CTI Remote Device: Call1 [A1 ' D]: LINE_CALLSTATE -Param1 = CONNECTED Param2 = 0x01(active) Answer the Call on Device D Remote Destination and D will be talking/ will have Media connection Both the Calls on CTI Remote Device Drop Primary Call on CTI Remote Device : Call1 [C ' A1]: LINE_CALLSTATE -Param1 = DISCONNECTED LINE_CALLSTATE -Param1 = IDLE Secondary Call on CTI Remote Device: Call1 [A ' D]: LINE_CALLSTATE -Param1 = DISCONNECTED LINE_CALLSTATE -Param1 = IDLE Complete Transfer on the Primary Call[C ' A]with [A ' D ] call as consult call LineCompleteTranfer() on the call [c ' A1] on Device A D and C will be talking/ will have Media connection Expected result would be same as observed on CTI Remote Device Variation : Test the same with CSF Device in Extend Mode Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 620 Message Sequence Charts Message Sequence Charts

Page 652 diagram