McDewey

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

Page 44

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

Also, see Unified Communications Manager XML Developers Guide for relevant release of Unified Communications Manager at the following location: http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_programming_reference_guides_list.html. Routing Rules Interface Unified Communication Manager 8.0(1) and later supports the external call control (ECC) feature, which enables an adjunct route server to make call-routing decisions for Unified Communications Manager by using the Cisco Unified Routing Rules Interface. When you configure external call control, Unified Communications Manager issues a route request that contains the calling party and called party information to the adjunct route server. The adjunct route server receives the request, applies appropriate business logic, and returns a route response that instructs Unified Communications Manager on how the call should get routed, along with any additional call treatment that should get applied. For more information, see the Routing Rules Interface Tech Center on the Cisco Developer Network http://developer.cisco.com/web/curri/home. Cisco Unified TSP Overview The standard TAPI provides an unchanging programming interface for different implementations. The goal of Cisco in implementing TAPI for the Unified Communications Manager platform remains to conform as closely as possible to the TAPI specification, while providing extensions that enhance TAPI and expose the advanced features of Unified Communications Manager to applications. As versions of Unified Communications Manager and Cisco Unified TSP are released, variances in the API should be minor and should tend in the direction of compliance. Cisco stays committed to maintaining its API extensions with the same stability and reliability, though additional extensions may be provided as new Unified Communications Manager features become available. The following figure shows the architecture of TAPI. Figure 1: Architecture of TAPI Service Process Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 12 Overview Routing Rules Interface