We are able to SSC with bridged appearances, but in the past we have ran into issue where the CTI events were not always clear for bridged appearances. It appears that some of the issues have been addressed. In the 6.2 AES release notes it states that "Prior to AE Services 6.2, the TSAPI Service did not always provide a CSTA Established event when a bridged party that had dropped off a call later re-joined the same call." and in the 6.3 AES release notes it states that "Prior to AE Services 6.3.1, in some call scenarios involving bridged appearances administered for a SIP station, the TSAPI Service would generate an extra CSTA Delivered event for the call alerting at the SIP station, and the event cause in the CSTA Delivered events for the call alerting at the SIP station was Redirected instead of New Call."

Maybe a better question for me to ask is what known issues still exist with bridged appearances.

Is recording of bridged appearances through single step conference supported in the latest release? If not are there plans to support it in an upcoming release?

Unfortunately it is hard to troubleshoot using list trace station because we are seeing the issue intermittently. We have found no common denominator in the cases where it does occur. Is there any way to look at historical events for a device after we find an occurrence that might help troubleshoot?

We are attempting to record a device using the Service Observe method by sending the make call request through TSAPI using a DMCC station. This is successful in most cases, but sometimes we are getting a fast busy signal. We are getting any errors. I'm looking for possible reasons why we would get a fast busy signal to start troubleshooting the issue.

Thanks