App crashes when adding people to conference call - 3CXPhone for Windows

Status
Not open for further replies.

JaredP

Forum User
Joined
Jul 24, 2020
Messages
8
Reaction score
1
We are currently using the '3CX Audio Conferencing' feature that allows internal and external users to dial into the 'Conference Place'.

When we start the conference everything appears normal in the Windows Application; we can see the conference call running and see who is in the Conference Place. However, more often than not when we attempt to add a user (internal or external) through the '3CXPhone for Windows' application it crashes and the attached error appears. The person that we attempted to add still receives the call and can join the 'Conference Place', but we must restart the '3CXPhone for Windows' application every time that this happens.

Has anyone else been having this issue, or does anyone know of a work-around/fix?
 

Attachments

  • 3cxConfCrash.JPG
    3cxConfCrash.JPG
    21.5 KB · Views: 4
Hi Jared,

Have you checked the log mentioned in the Error Message to see if any exceptions were logged?

Also, please tell us
- what version your PBX is
- what version the client is
- and what Windows you are running the client on
 
Hi John;

We had checked the logs, but not 'exceptions' seemed to be found; there are a few errors however:

'Error':
[26.08.2020 08:39:04.552][1] 08:39:04.552 pjsua_core.c Error setting QoS type 3 to SIP UDP socket: Invalid argument (WSAEINVAL)
and
[26.08.2020 08:39:04.552][1] 08:39:04.552 tcplis6 Error setting QoS type 3 to SIP TCP listener socket: Bad protocol option (WSAENOPROTOOPT)

PBX - 16.0.5.622
Client - 16.3.0.144
Windows - Version: 2004 Build: 19041.450 (happens on multiple computers likely with differing builds)
 
Those appeared before the conference took place though, correct?
 
I think that may have been before the conference took place. I did some more testing, and I found the logs relating to unhandled exceptions this time. I replaced our pin and ip addresses with 'omitted', but they were accurate to our system:


[27.08.2020 15:05:19.039][1] ResponseAcknowledge: 'Invalid PIN specified: '[omitted]'' received on MyPhone.Notifications.RequestUpsertScheduledConference
[27.08.2020 15:05:19.084][1] Error event caught, Cannot send request: RequestGetConferenceSchedule, channel [ 65443729 with https://[omitted]/myphone/MPWebService.asmx ]
[27.08.2020 15:05:19.087][1] System.Exception: Conference schedule with pin [omitted] does not have id=0
at MyPhoneClientChannelNet.Implementation.ClientChannelImpl.<RequestAsync>d__67.MoveNext()

[27.08.2020 15:05:19.143][1] Error occurred in application current domain - app domain unhandled exception
[27.08.2020 15:05:19.167][1] System.Exception: Conference schedule with pin [omitted] does not have id=0
at MyPhoneClientChannelNet.Implementation.ClientChannelImpl.<RequestAsync>d__67.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at _3CXWin8Phone.ViewModel.ConferenceAPI.<UpdateScheduledAudioConferenceData>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at _3CXWin8Phone.ViewModel.ConferenceAPI.<>c__DisplayClass3_0.<<CreateOrUpdateAudioConference>b__9>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(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 MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
at System.Windows.Application.RunDispatcher(Object ignore)
at System.Windows.Application.RunInternal(Window window)
at System.Windows.Application.Run(Window window)
at _3CXWin8Phone.App.Main()
 
If we create a fresh extension with all settings left default, and provision the client, can we replicate the problem?
 
Yes, the exact same issue occurs and the same error message appears.
 
Hi Jared,

Do you have inbound rules defined that point a External DID towards your conference extension?
 
Status
Not open for further replies.

Forum statistics

Threads
112,349
Messages
592,026
Members
165,512
Latest member
gmacinit