Call Control API access outside localhost (disable 127.0.0.1 restriction)

[Netwerkplek]

Hi,

We are developping a small thrid party integration build on the Call Control API. From various 3CX moderators we got that the 3CX phonesystem does not expose the Call Control API to anything outside of 127.0.0.1 / locahost. Something we ascribe to for a production environment. However, during development and debugging it is very frustrating to move testbuild to the test 3cx phonesystem. I would really really help if we could live debug our application against the testserver from the development machines.
I understand the Call Control API itself is outside of the 3CX support scope. However, would it be possible to get a hint as to where we can find the setting to just open up the host of the Call Control API to something more than 127.0.0.1?
It would save us much time setting up another development/debugging environment with yet another 3CX test phonesystem.

Kind regards,
Jori Huisman

 

[StefanW]

I would advice to create a listener outside of 3CX on the host getting your commands and then pushes them via 127.0.0.1 on the host. Even in Production you can secure the connection to your needs later and keep the API client and 3CX as Server separated...

 

[Netwerkplek]

Hi,

You are absolutely right. We want to make a "proxy" that runs on the PBX so it can push the commands via 127.0.0.1 (localhost). And we can indeed even make that more secure later on.

But: we must develop and debug this proxy first.
For that it would be completely unsecure and absolutely not production valid, but extremely handy if we could talk from the Visual Studio box to the 3CX PBX box . Can you point us to where we can find the override setting to enable this?

Kind regards,
Jori Huisman