Sipek throws System.AccessViolationException in Windows Service, at CallManager.onUserAnswer, CallManager.onUserRelease etc.

55 views

Skip to first unread message

truli...@gmail.com

unread,

Feb 4, 2016, 1:08:49 PM2/4/16

to SIPek

I am using Sipek in Windows Service, I receive same exception i.e. System.AccessViolationException at CallManager.onUserAnswer, CallManager.onUserRelease, CallManager.onUserTransfer etc.

An unhandled exception of type 'System.AccessViolationException' occurred in SipekSdk.dll
Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

having stack trace
   at Sipek.Sip.pjsipCallProxy.dll_serviceReq(Int32 callId, Int32 serviceCode, String destUri)
   at Sipek.Sip.pjsipCallProxy.serviceRequest(Int32 code, String dest)
   at Sipek.Common.CallControl.CIncomingState.xferCall(String number)
   at Sipek.Common.CallControl.CCallManager.onUserTransfer(Int32 session, String number)
   at Call_Service.Phone.CallTransfer(String otherDn, Boolean complete) in D:\Call_Service\Call_Service\Call_Service\Phone.cs:line 529
   at Call_Service.Phone.blindtransferCall(String extension) in D:\Call_Service\Call_Service\Call_Service\Phone.cs:line 564
   at Call_Service.Phone.Do() in D:\Call_Service\Call_Service\Call_Service\Phone.cs:line 1901
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

When I run the same code in Windows Application no issue faced and things run fine in Windows Application.