(N.B.: IPFX provide a CTI solution for voicemail and contact centres. We run on a Windows server and interface with the CUCM via the Cisco TAPI/TSP.)
ISSUE: We have a requirement to be able to set the outbound CLI on a call placed from an arbitrary endpoint. What we are doing is forking a call. We issue a MakeCall request to a CTI port which then dials the external party on behalf of a user. We are NOT using their extension - we are using a CTI port with an abitrary extension. What we want to be able to do is set the CLI of that external call to the user's extension/DDI. We are issuing the dial from the CTI Port via a simple MakeCall.
Is it possible for a third party app such as ourselves to perform the MakeCall via the TAPI component and set the CLI on the endpoint which is initiating the call? If so, is there sample code, specific TSP/TAPI versions, etc.??
To be clear - we issue our requests via Cisco TAPI, so we need to know what parameters we have to set in order to specify the CLI on the outbound dial request from an endpoint with an arbitrary extension.
We have a mobile app that is able to establish calls. The user logs into the mobile app as their DN, but as a third-party app, we do the following.
User initiates call from mobile app
Data message sent to IPFX server
IPFX server sends request to CUCM to dial from an arbitrary CTI port to the required number
IPFX server acts as media bridge between mobile app and call on CTI port
We configure a range of CTI ports on the CUCM to act as a pool, and use the lowest free number.
So, we might have CTI ports 570200-570299 configured.
User on extension 1234 logs into IPFX’s mobile app
They want to dial +441189148041
A TCP/IP message goes from the mobile app to the IPFX server to make the call
IPFX server issues a MakeCall request VIA CISCO TSP, e.g., MakeCall from 570200 > +441189148041
Once the call is established, IPFX bridges the two legs from Mobile > Server > CTI Port
What we want to achieve is that the outbound call from the CTI port displays the DDI associated with 1234 (in the above example), instead of the DDI associated with 570200.
We might need to check from application side, that how and which parameter you are taking from the "LinecallInfo object" to populate the DDI .
CiscoTSP lineMakecall is based on the TSPI_linemakecall and we can't add any parameters to to the API as it will break the logic .
Please refer to the Microsoft link:
We do have a use case called "Agent Greeting " which might be useful for you .
So, there is no native way, using TAPI, to set the CLI.
We cannot set it using TAPI.