Safe handle has been closed

Aug 3, 2016 at 11:05 PM
Hey, I got the following exception when my program tries to open a tapi line. It works fine for all other users but we always get this error for this user/tapi line. We've tried to remove and then add the user from/to the security group in Cisco Call Manager but the issue remains.

I've done a bit of searching and found issue 11483, which appears to be similar... Does anyone know if I should try the approach stated in 11483?

Exception (ObjectDisposedException) caught in StartMonitorOnLinesToMonitor.
Safe handle has been closed
   at System.Runtime.InteropServices.SafeHandle.DangerousAddRef(Boolean& success)
   at System.StubHelpers.StubHelpers.SafeHandleAddRef(SafeHandle pHandle, Boolean& success)
   at JulMar.Atapi.Interop.NativeMethods.lineGetNewCalls(HTLINE hLine, Int32 dwAddressID, Int32 dwSelect, IntPtr lpCallList)
   at JulMar.Atapi.TapiAddress.CheckForExistingCalls()
   at JulMar.Atapi.TapiLine.Open(Privilege openMode, MediaModes mediaMode, Int32 addressId)
   at CallRecordingService.TapiMonitorManager.StartMonitorOnLine(TapiLine tapiLine, TapiMonitorInfo tapiMonitorInfo, Boolean skipMonitorListMaintenance)
   at CallRecordingService.TapiMonitorManager.StartMonitorOnLinesToMonitor()
Aug 3, 2016 at 11:06 PM
FYI - I'm using ATAPI 1.2.0