I am using Cisco TSP (TAPI) on windows platform for CTI integration with Cisco platform.
I am parking a call using undirected call parking feature. When Call Park Reversion Timer expires and the parked call comes back and rings on the extension I am unable to identify which parking device the call has come from. The information provided in the TAPI call ringing-in event does not contain any info about the parking device. Just wondering if it is the right behavior of Cisco TSP that it will not provide any reference to the parking device in the call event or if it is a bug. Please advise.
Device-A calls Device-B Call-1 rings on Device-B and is answered by using TAPI API feature lineAnswer Call-1 is now connected between Device-A and Device-B Call-1 is parked (undirected) from Device-B by using TAPI API feature linePark Call-1 now leaves Device-B. Call-1 is now between Device-A and Parking-Device
Park reversion timer (default 60 seconds) expires Call-1 now leaves Parking-Device and rings-in on Device-B
Below is a TAPI call info of call ringing-in event on Device-B. dwRedirectingID and dwRedirectionID parties both appear to be same which is Device-B. Should not dwRedirectingID be the Parking-Device instead?
After enabling DEVSPECIFIC_PARK_MONITORING flag by using the lineDevSpecific SLDST_SET_STATUS_MESSAGES request I am able to see call park status notifications. However, I got two questions:
Q.1) Why call park status notifications are sent for specific phone and not for all?
TSP sends call park status notifications for line used of this model phone:
Product Type: Cisco DX650 Device Protocol: SIP
TSP does not send call park status notifications for line used for the following model phones:
Product Type: Cisco 8945 Device Protocol: SCCP
Product Type: Cisco 7811 Device Protocol: SIP
Q.2) Although above feature allows to see the parked calls status but original question remains there that why call ringing event does not have any reference of the parking device when it comes back and rings the extension?