v20 and Windows Server 2016

[simonatkins]

Can't get the CallControl API to connect to 3CX v20 on Windows Server 2016. It's failing after calling the Reset function. the event viewer gives this info:

Application: TCXWindowsTestApp.exe
CoreCLR Version: 8.0.1124.51707
.NET Version: 8.0.11
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stack:
at TCX.Configuration.PhoneSystem.RegisterListener(MyPFN_UPDATE_LISTENER)
at TCX.Configuration.PhoneSystem.RegisterListener(MyPFN_UPDATE_LISTENER)
at TCX.Configuration.PhoneSystem..ctor()
at TCX.Configuration.PhoneSystem.Reset(System.String, System.String, Int32, System.String, System.String, TCX.Configuration.NotificationEventHandler, TCX.Configuration.NotificationEventHandler, TCX.Configuration.NotificationEventHandler)
at TCXWindowsTestApp.Form1.connectTo3CX()
at TCXWindowsTestApp.Form1.Button1_Click(System.Object, System.EventArgs)

As you can see it's just a test app that uses the latest API and .net 8.0 (also does the same for .net 7.0). We click a button to connect and call the Reset function which crashes whilst registering the listener.
This same code works fine in Windows 11 and Linux. It's not a bad image x64 problem as I've tried targetting both x64 and AnyCPU.

any ideas greatly appreciated.

 

[fxbastler]

@simonatkins
There is still a lot of information missing (development environment, libraries used and so on).

A first basic test: can you establish a working connection using Powershell?

on the 3CX platform as you are probably trying:
https://www.3cx.de/forum/threads/automatischer-statuswechsel-problem.121456/post-439013

via Web API:

Post in thread 'Updated Call Control API for V20'

Sep 19, 2024

Powershell:

$tcxurl="mypbx.mydomain.de"     # needs port if not 443

$jsonauthbody = (@{
    Username="988"              # 3CX user, maybe email address
    Password="Super_Secret0815" # 3CX user password
    SecurityCode=""
} | ConvertTo-Json)

$LoginResponse = Invoke-RestMethod -Uri "https://$tcxurl/webclient/api/Login/GetAccessToken" -Body $jsonauthbody -Method POST -ContentType "application/json"

$headers = @{Authorization = "Bearer $($LoginResponse.Token.access_token)"}

# get information about endpoints
(Invoke-RestMethod -uri "https://$tcxurl/xapi/v1" -headers $headers -Method...

• fxbastler

• 

 

[simonatkins]

Thanks for the reply @fxbastler but I think you may have misunderstood the OP. We're not using the web api and this wouldn't help us. We are using the .NET call control api. It works fine in Windows 11 3CX v20 but not Windows Server 2016 3CX v20. I would have thought they were the same 3CX versions on both OSs but It's like there's a module missing in 2016 that allows third parties to connect.

Real head scratching stuff.

 

[simonatkins]

Is it possible to switch off or disable third party connections to 3CX in the 3CX admin console? I've looked and can not see anything obvious but you never know...

 

[fxbastler]

We're not using the web api and this wouldn't help us. We are using the .NET call control api.

Yes, I thought so. Hence the first link and the question whether you can access the API via Powershell and 3cxpscomcpp2.dll.

 

[simonatkins]

Looks like one more thing broken in v20 3CX

 

[NicholasP_3CX]

Looks like one more thing broken in v20 3CX

Windows Server 2016 is an 8.5 year old operating system.

And as it works for Windows 11 and Linux, I will assume you can get it to work on Windows server 2022 as well.

I dont see that as the fault of Version 20