REST API /callcontrol/{dnnumber}/makecall requires manual confirmation (green handset)

[vladimir.marinov@bularias]

Hello,


I am using the 3CX REST API endpoint
POST /callcontrol/{dnnumber}/makecall
to initiate calls programmatically.


The call is successfully created, but the SIP client shows that the destination is calling me, and I have to manually press the green handset button to actually start the call.


Is there a way to make the call connect automatically, without requiring manual confirmation on the SIP phone (auto-answer or immediate dial)?


My goal is to trigger outbound calls via REST API without user interaction on the phone.


Thank you in advance!

 

[fxbastler]

... I have to manually press the green handset button to actually start the call.

That's what makecall does.

 

[vladimir.marinov@bularias]

Thanks for your reply!
Just to clarify — when I use makecall, the call is created, but the SIP client still shows the incoming call screen, and I have to manually press the green handset button to start talking.


Is there a way to make the call start automatically, without the need to press the button on the SIP phone (i.e. true auto-answer or direct connect)?

 

[fxbastler]

Is there a way to make the call start automatically, without the need to press the button on the SIP phone (i.e. true auto-answer or direct connect)?

Maybe, I don't know your SIP client.

 

[vladimir.marinov@bularias]

Thanks! Do you think the change is needed in my SIP application? I’m using the 3CX application for Windows.

 

[edossantos_sipcaller]

The 3CX Client for Windows, which you can download from the Microsoft Store, has the ability to Auto Answer calls. You need to tick the box in Settings > Behavior.

 

[vladimir.marinov@bularias]

Thanks for the suggestion!
Configuring auto answer in the 3CX client isn’t a viable option for us, since someone might call when there’s no one at the computer.


Do you know if there’s a way to pass this as a parameter in the REST API, or to achieve the same behavior using a different type of communication?

 

[edossantos_sipcaller]

Do you know if there’s a way to pass this as a parameter in the REST API, or to achieve the same behavior using a different type of communication?

No, this can't be set when you request the call. It's the client who needs to make this decision, not the server.

You could use the queue status for example to decide. That's what we do in SIP Caller, if the agent is busy or logged out from the queue we don't send calls.

 

[vladimir.marinov@bularias]

Thanks for the clarification.
We’ve been using an older version of 3CX (for Windows) where we used 3cxpscomcpp2.dll, and in that setup the dialing was immediate — no manual confirmation was required.


Unfortunately, that version is no longer supported, so we can’t continue using it.
Does anyone know if this functionality is available in the newer 3CX system, or how it has been migrated in the current versions?

 

[vladimir.marinov@bularias]

We want to achieve the following: when a user clicks a link in our web application, their phone should automatically start calling the destination number, without requiring any additional action from the user.

 

[VoIPTools]

In my experience, when you perform a MakeCall, the PBX is going to call your extension first. Only after you answer the call will it initiate the second leg of the call to the other party. You have to answer the inbound call, before it will make the outbound call.