Catch 3CX system events in version 16.0.655

Status
Not open for further replies.

Dasha

Forum User
Joined
Nov 10, 2020
Messages
3
Reaction score
0
Hello! Please sorry for my English in advance.

Maybe someone faced such a problem when integrating to 3X:

We configure the 3CX integration to the CRM system. We were start developing the integration to 3CX version 16.0.4.493. Integration was reproduced not using the RESTFUL API. It was used the system library 3cxpscomcpp2.dll and used the connection to the server via the 3cxphonesystem.ini file (CallManagerAPI). This was necessary to track calls in real time by subscribing to the "Inserted"/"Updated"/"Deleted" connection event, since the RESTFUL API provides data only after the call ends. We used libraries that were installed with 3CX-programm (along the path C://Programm File/3CX....).

After updating the version to 16.0.655 a problem occurred: the implemented functionality stop working. When we use the new libraries the project stop running due to incompatibility - System. IO. FileNotFoundException: "Could not load file or assembly "netstandart, Version=2.1.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" or one of its dependencies. The system cannot find the file specified". If in the new version (16.0.655) use the libraries of the old version (16.0.4.493) - the project is started and connected, but we don't detect system events subscription.

We need to be able to catch events in the 3CX system that were previously possible to catch, but cannot be done in the new version. Has anyone ever encountered this? Is it real to implement this? Or is there another way to catch such events in real time in version 16.0.655?
 
With the release of V16 Update 6, 3CX moved from .Net Standard 2.0 to .Net Standard 2.1. I suspect your problem is that your application is written in .Net Framework. Unfortunately, .Net Standard 2.1 is no longer compatible with .Net Framework. If my assumption is correct, you will have to convert your application from .Net Framework to .Net Core.
 
With the release of V16 Update 6, 3CX moved from .Net Standard 2.0 to .Net Standard 2.1. I suspect your problem is that your application is written in .Net Framework. Unfortunately, .Net Standard 2.1 is no longer compatible with .Net Framework. If my assumption is correct, you will have to convert your application from .Net Framework to .Net Core.
Thanks.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
112,324
Messages
591,897
Members
165,475
Latest member
lastshadow