1. If a call is opened via TAPI, is the call dialed by the user's phone, or is it initiated by CUCM and the phone is just connected?
2. Is it possible to gather the call duration after hook on via TAPI?
- The call is initiated via the CTI manager and then connects the two phone devices.
- I am pretty sure for this one you could derive the duration time through CTI event messages that are sent to your TAPI app while montioring the devices and the call. You should be getting events for when the call is connected and when it is disconnected.You can view this in your TAPI logs. Beyond that, if you can deal with the data in a less than realtime scenario you can pull the CDR records using the CDRonDemand API in the Serviceability APIs
Cisco TSP supports dialing using directory URIs as the destination address. Cisco TSP uses the @ symbol to differentiate between directory URIs and directory numbers. If an @ symbol is present, the dialed address is a directory URI. Directory URIs can now be returned in the dwDevSpecificData call structure. URI dialing is also supported for CTI Remote Devices. Remote destinations can be configured with directory URIs as the remote destination number.
The following interfaces have changed to support directory URIs:
- lineMakeCall—lpszDestAddress parameter can contain a directory URI
- lineBlindTransfer—lpszDestAddress parameter can contain a directory URI
- lineForward—dwDestAddressOffset in the lineForward structure can now point at a destination address
- lineRedirect—lpszDestAddress parameter can contain a directory URI
Message Sequence Charts
There is no change to the message sequence.
No backwards compatibility issues.