McDewey

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

Page 648

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

TAPI structures TAPI messages Action LineDrop() success Call on C : LINE_CALLSTATE -Param1 = DISCONNECTED LINE_CALLSTATE -Param1 = IDLE Call on CTI Remote Device : LINE_CALLSTATE -Param1 = DISCONNECTED LINE_CALLSTATE -Param1 = IDLE Call on Enterprise Phone : LINE_CALLSTATE - Param1 = CONNECTED Param2 = 0x02 (Inactive) LINE_CALLSTATE -Param1 = IDLE LineDrop() for the call on Device A (CTI-RD) Call on Remote Destination will be dropped Expected result would be same as observed on CTI Remote Device Variation : Test the same with CSF Device in Extend Mode Multiple Calls -Multiple Lines -Answer/Hold/Resume Precondition: same as above usecase TAPI structures TAPI messages Action Lines are Enumerated LineInitializeEx LineOpen() returns Success Open all Lines (A, A', A'' and C) LineOpen() with ExtVer-0x000C0000 EVENT = LINE_DEVSPECIFIC dwParam1 = SLDSMT_LINE_PROPERTY_CHANGED dwParam2 = LPCT_REMOTE_DESTINATION_INFO (0x00004000) Update Remote Destination RD1 "Mobile"on CTI Remote Device A with IsActive set to true CiscoLineDevSpecific UpdateRemoteDestination Req m_RDNumber = "914086271309" m_UnicodeRDName = "Mobile" m_NewRDNumber = "914086271309" m_activeRD = 0x00000001 Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 616 Message Sequence Charts Message Sequence Charts

Page 648 diagram