McDewey

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

Page 723

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

TSP Message to application data Action LineSetStatusMessages returns Success LineInserviceEvent reports to Application Line_LineDevState Dwparam1 = x040, InService LineSetStatusMessages() – with dwLinestates – 0xcc Line_Reply with Success Application sends lineDevSpecific(CciscoLineDevSpecificEnableFeatureSupport) with m_Feature – 0x00000001, m_Feature_Capability - 0x00000001 Line_Reply with Success Application sends lineDevSpecific(CCiscoLineDevSpecificSetStatusMsgs) with m_DevSpecificStatusMsgsFlag=DEVSPECIFIC_GET_IP_PORT -0x00000400 A: LINE_CALLSTATE (LINECALLSTATE_PROCEEDING) LINE_DEVSPECIFIC dwParam1 = SLDSMT_RTP_GET_IP_PORT dwParam2 = 0x00000xyy x (ninth Bit from LSB) – 0 – SetRTP (1-App has to set RTP / 0 – App need not set RTP) yy – IPAddressing Mode Note On this new Notification, applications has to Open the Port. Application calls LineMakeCall() on A dialing a Party in Cluster2 Call is routed through SIP trunk with Early Offer Enabled A: LINE_CALLSTATE (LINECALLSTATE_CONNECTED) Media will be set and Media Events will be reported to Application Other Party answers the Call Mutiple Applications Statically Register CTI Port Configuration A – CTI Port in Cluster 1 Cluster1 and Cluster2 connected via SIP trunk SIP trunk Supports Early Offer Applications: • App1 – Statically Registers CTI Port/RP with Early Offer Support • App2 – Statically Registers CTI Port/RP without Early Offer Support Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 691 Message Sequence Charts Mutiple Applications Statically Register CTI Port

Page 723 diagram