McDewey

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

Page 962

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

Expected Events Action For A: • LINECALLSTATE CONNECTED • Caller = A, Called =B Connected B For B: • LINECALLSTATE CONNECTED • Caller = A, Called =B Connected A A calls B For A: • LINECALLSTATE_RINGBACK For C: • LINECALLSTATE_OFFERING / LINECALLSTATE_ACCEPTED Application sends CciscoLineDevSpecificRedirectEx on B to redirect call to C and C' with the redirectDeviceName as of C. • PARAM: hLine • PARAM: dwAddressID • PARAM: hCall • PARAM: FeaturePriority • PARAM: m_DestDirn • PARAM: m_SetOriginalCalledTo • PARAM: m_FAC • PARAM: m_CMC • PARAM: m_RedirectBitMask • PARAM: m_RedirectDeviceName = C • PARAM: m_ApplicationXMLDataSize • PARAM: m_ApplicationXMLData • PARAM: m_callingSearchSpace • PARAM: returnCode For C: • LINE_CALLSTATE CONNECTED ACTIVE For C': • LINE_CALLSTATECONNECTEDINACTIVE C answers the call Scenario 2: A calls B and B redirects the call to C, C' with invalid device name. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 930 Message Sequence Charts Message Sequence Charts

Page 962 diagram