Interesting.
The problem was that in 1.0.0.32 the TSP would send the connected callstate to Unity too early. Specifically, we only waited for CCM to acknowledge that we were offhook, at which point the TSP would tell the Miu we were connected, and then the Miu would begin playing the first prompt/stream. For the 1.0.0.33 TSP, we made a change to wait until CCM had also sent us a message saying that not only were we offhook, but it had also finished setting up the RTP stream, before the TSP would signal the Miu that it was Connected. So, what could happen in 1.0.0.32 was that the Miu would begin playing wave data before the RTP stream was setup, so the first prompt wouldn't get played correctly. Then, by the time the next prompt began playing, CCM would have finished setting up the RTP stream, so that subsequent prompts would be fine. At any rate, this is fixed in 1.0.0.33 and later (which would explain why the problem is fixed for sites that upgraded to 1.0.0.36).
For TSP 1.0.0.29, a change was made to fix a defect where notifications fail over a gateway. During the investigation of that defect, we found that when placing a call over an analog gateway, CCM would send us the message indicating the RTP stream was setup before the call had actually been answered. The reason for this is that analog DTMF requires a media path. Version 1.0.0.28 of the TSP waited for only the message from CCM indicating the RTP stream was setup before telling the Miu that the call was Connected, so the Miu would think the call was answered before the called party had actually picked up. To fix this problem with 1.0.0.29, we changed it so that the TSP waited for CCM to send the message indicating that it had finished going off hook before signaling to the Miu that we were Connected (rather than the message indicating the RTP stream was setup). Later, we found that depending upon the network configuration, CCM would send these messages (indication of off hook and indication of RTP stream) in different orders, so for 1.0.0.33, the TSP was changed so that it must receive both messages before signaling to the Miu that we were Connected.
We have not had any other sites complain of this issue with 1.0.0.28 or 1.0.0.36. Please verify your TSP version by right clicking on AvSkinny.tsp in the system32 directory and going to properties. Then click the version tab. What does that version number say?
Keith
Keith Chambers
Unity Technical Lead
Unified Voice Team, San Jose
Cisco Systems
kechambe@cisco.com
