Solved v18 Windows client API?

[mcbsystems]

Hi,

I've written a C# program that uses the 3CXPhone API to connect to another Windows program on the same Windows computer, using events like callHandler_OnCallStatusChanged. This has worked great for several years, from v14 through v16.

I see that the UI of the v18 client has been re-written. What about the back end? Does the MyPhone API carry over from previous versions? If not, what is recommended for client-side integration?

Thanks and regards,

 

[NickD_3CX]

Hi,

I've written a C# program that uses the 3CXPhone API to connect to another Windows program on the same Windows computer, using events like callHandler_OnCallStatusChanged. This has worked great for several years, from v14 through v16.

I see that the UI of the v18 client has been re-written. What about the back end? Does the MyPhone API carry over from previous versions? If not, what is recommended for client-side integration?

Thanks and regards,

Hi!

If you're referring to the new 3CX Windows Desktop App, this one is based on Electron, so the back end is completely different and doesn't resemble the 'legacy' Windows App at all.

This means that any integration you have created using the 3CXPhone API will not work.
Currently there is no new API for the new Desktop App, but you can continue using the 'legacy' Windows App like you did before.

While I can't guarantee that the integration will continue to work using the latest legacy Windows App, you will need to try it out as there is a chance and there haven't been some significant changes compared to the previous version.

 

[VoIPTools]

As an alternative, you could subscribe to the events yourself using the 3CX Call Control API. This could be done on either the server or client side. Then it does not matter what client you use -- Windows, Web, Electron. That is what we do.

It will be interesting to see what functionality 3CX releases with the announced REST API and Gateway service. Perhaps later this year it will be far easier for us to integrate with 3CX.

In the meantime, you can take a look at our APIs. We offer both a REST API and an Events API.

 

[mcbsystems]

While I can't guarantee that the integration will continue to work using the latest legacy Windows App, you will need to try it out as there is a chance and there haven't been some significant changes compared to the previous version.

Thanks Nick. I will set up a v18 server and test. You mention the "latest legacy Windows App." Is that version 16.3.0.220 or is there a legacy app designed for v18?

As an alternative, you could subscribe to the events yourself using the 3CX Call Control API. This could be done on either the server or client side. Then it does not matter what client you use -- Windows, Web, Electron. That is what we do.

It will be interesting to see what functionality 3CX releases with the announced REST API and Gateway service. Perhaps later this year it will be far easier for us to integrate with 3CX.

In the meantime, you can take a look at our APIs. We offer both a REST API and an Events API.

Matthew, thanks for the tips.

 

[NickD_3CX]

Thanks Nick. I will set up a v18 server and test. You mention the "latest legacy Windows App." Is that version 16.3.0.220 or is there a legacy app designed for v18?

The App more or less is the same, but after you install V18 and the 3CX legacy Windows App opens, it will probably update itself to 16.3.0.261.
Mostly small fixes, but to my knowledge, nothing was purposely changed relating to functionality used by the deprecated 3CX Phone API.

 

[mcbsystems]

So my initial testing confirms that with v18 Pro server installed, the legacy 3CXPhone app 16.3.0.261 still connects fine to my Windows program, even if the new Electron app is also running. I am having an issue with 3CX auto-answering; I'm starting a new thread about that.

 

[NickD_3CX]

Excellent! In that case I will just lock this thread.