Can't perform answer action

[DanieleOutsiderCode]

I'm trying to get my head around the answer action, without succeeding.

Following the https://www.3cx.com/docs/call-control-api-endpoints specification I keep getting an 422 error

curl --location --globoff --request GET '/callcontrol/{dnnumber}/participants/{id}/{action}'
--header 'Content-Type: application/json'
--header 'Authorization: ••••••'
--data '{
"destination": 3333333333,
"reason": "None"
}'

I'm trying with destination and reason, only destination, only reason or without any of them.

Unfortunately i'm keeping the same 422 error.

Even in the example on the current repository I can't find the answer action to figure out what I'm missing.
When I receive a call the answer button seems to be disabled.

Is it possible to answer a call with the current API? Can I get an example?

Thank you so much!

[kira565]

Hello @DanieleOutsiderCode, thanks for your message!

You don't need to specify a destination for this request — the body can be empty.

Regarding the documentation: to perform the answer operation, the device must be a UACSTA-compatible one. This means a device that supports direct call control (a mechanism by which a phone can be controlled externally, i.e., by a command from the server or an application).

That's also why the Answer button is disabled in the example. In that same example, you can select the current device using the dropdown at the top of the dialer, if you have such devices connected.

You can also check the participant info — if direct_control: false, it means the participant's device does not support remote control operations.

If you have such device to answer this call, and still experiencing the problem, please let me know.

Moreover, if you want, you can provide your datailed user case and I will try to help you with possible solutions.

[DanieleOutsiderCode]

Hello @kira565, thank you for your helpful response.

Our current use case is to allow users to answer incoming calls through a web interface while the 3CX Windows client runs in the background.

As I see the partecipant isdirect_control: false.
Is this expected behavior for the Windows client?
Is there a workaround to support our use case?

Thank you!

[sherlock1982]

You're absolutely correct. Neither of clients have UACSTA support. Mobile clients can't have it by definition (they work via push) and in Windows Softphone this wasn't implemented and not planned.
So for hardphones only (some hardphones)

There's also TAPI implementation but I think "Answer" is not yet implemented there.
We believe there's no need to answer from other sources when you can answer from the app itself.

Alternatively you can answer from the browser itself exactly how 3CX Webclient does it using WebRTC. But note this is not an easy way to implement.

Alternatively you can answer from a supported headphone.

If you can tell us more about your scenario maybe we can help you more. As to why you need this feature