Remote Websockets w/ Call Control API

[Scrappy]

Simple question, but is this possible?


It seems odd that it wouldn't be, since as a business model, I'd guess that anyone wanting to use it couldn't use the hosted solution for this, but looking at this post from last July, it seems to indicate that it isn't possible ... you have to co-host the app and pbx ( or create relay ) on the same server:

For one, there is no way to subscribe to the real-time events unless (1) your application is installed locally on the 3CX server, or (2) you create some type of relay that is installed on the 3CX server and exposes the events to the outside world. The Call Control API only communicates with Local Host.

I'm running on latest v20 release ( upgraded this past week ), just upgraded to Enterprise/AI license to get access to the API ... if I *have* to create a relay, so be it, just want to make sure since I'd rather not have to add things to the pbx server if I can get away with it.

I've read through both 3CX Call Control API and 3CX Call Control API Endpoint Specification and am finding nothing there to point to any restrictions ...

 

[VoIPTools]

I think you have some confusion about the difference between the traditional .Net Call Control API and the new xAPI Call Control API. These are two very different APIs. For the traditional .Net API, it only replies to requests from "localhost". For this API, you need a relay to talk to it from an external application hosted somewhere other than the 3CX server, but for the xAPI, this is web-based and does not require a relay, and does respond to remote requests (after secure authentication).

 

[Scrappy]

Ah, perfect,thanks ... and yes, that was it.

It took a bit to figure out that when I created the API key as well, that I had to list extensions ... I figured ( erroneously ) that not listing any would translate to 'all' ... once i figured that one out, call control is working beautifully

thanks for taking a sec to followup though, appreciate