McDewey

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

Page 93

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

• For the IPV6 Registered port, GetPort Notification is not reported to the application. For the Dual Mode CTI Port or Route Point the Early Offer is supported with IPV4 addresses capability. • For the Statically Registered CTI port with Legacy Wave driver, the Early Offer feature is not supported and TSP reports error if new LineDevspecific is requested to enable Feature Support. • For the Statically Registered CTI port with New Cisco Wave Driver/User control Registered CTI Port, New Get IP and Port Notification applications has to open the port that is assigned for the CTI Port. • On an Early Offer support registered CTI Port, the applications must send the RTP information about new notification and must not set the RTP information on OpenLogical Channel Notification. If set, it is failed by CTI and an acknowledgement is reported to the application. • When IPv6 support is added, the application receives GetPort Notification twice (one for Ipv4 and one for Ipv6 address) for dual mode device. When a call is answered, the application can close the unused port based on IPAddressingType in Open Logical Channel Notification. Note To support this feature, the application must negotiate line extension 0x000B0000 or above. Note Interface Changes See Early Offer, on page 384, Enable Feature, on page 385, Get IP and Port Event, on page 418, Set Status Messages, on page 355, and Open Logical Channel Events, on page 410. Message Sequences See Early Offer, on page 680. Backward Compatibility This feature is backward compatible. End-to-End Call Trace End-to-End Call Trace allows tracing of calls that traverse multiple Cisco voice products, such as Unified Communications Manager, Cisco IOS Gateway, and Cisco Call Center products. A new tool called System Call Tracing tool is developed to collect call records from all voice platforms to trace specific calls and to troubleshoot call failure or other issues. This tool uses the calling party number, called party number, and time stamp to find at least one call record from any voice product that it can access. From that single call record, System Call Tracing tool traces the call on all the voice products it has traversed. Interface Changes LINECALLINFO::DEVSPECIFIC is modified to include TSP Unique Call Reference ID. For more information, see LINECALLINFO, on page 324. Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 61 Features Supported by TSP End-to-End Call Trace