REST Call with userPhone and callerPhone params

[Lenny]

Hello guys

Is there any possibility to configure a REST call (GET/POST) and send the userPhone(client) number and the callerPhone number? How can I do that?

Is there the possibility to pass the session.ani vairable to the URL? For example: https://xyz.com/3cx?userPhone=session.callid&userPhone=session.ani

 

[edossantos_sipcaller]

You should create a CRM template for this. The Call Journaling functionality is what you need. Check this:
https://www.3cx.com/docs/crm-integration/

 

[Lenny]

Thank you for your answer. But we don't make a look up. All we want is to make a simple restcall with the phoneNumber of the caller and the phoneNumber of the agent.

Is there any possibility?

 

[edossantos_sipcaller]

Well, in my opinion is much simpler to do a dummy lookup, so you can run that HTTP request when the call ends, that creating a service using the Call Control API to do just what you need..... So I would go this way anyway.

 

[VoIPTools]

I'm pretty certain the new XAPI has call control methods including MakeCall. Have you looked at this API? We have built our own REST API with multiple ways to initiate a phone call. Our standard MakeCall API is free without a license key.

The one thing to note is that in V18 you could call the outside party first, and then when they answer, connect to the internal party. In V20 the first leg of the call always has to be the internal extension, and the 2nd parameter has to be the outside party. For example: --good-- MakeCall(100, 8016424655) --bad-- MakeCall(8016424655, 100).

 

[edossantos_sipcaller]

I'm pretty certain the new XAPI has call control methods including MakeCall. Have you looked at this API? We have built our own REST API with multiple ways to initiate a phone call. Our standard MakeCall API is free without a license key.

The one thing to note is that in V18 you could call the outside party first, and then when they answer, connect to the internal party. In V20 the first leg of the call always has to be the internal extension, and the 2nd parameter has to be the outside party. For example: --good-- MakeCall(100, 8016424655) --bad-- MakeCall(8016424655, 100).

The user is not trying to make a call, they need to trigger a notification when a call is received. You have 3 options here:
1) Create a CRM template, so the call is notified when it ends.
2) Use the Call Control API to get a notification of this event, and pass it to the external system.
3) Configure the "Launch external URL" in the Web Client, however, this is a GET request triggered by the browser, probably not what they want if they need a POST request or they don't want the user to see this request in the browser, and having to manually close the tab.

 

[VoIPTools]

Ah, in that case, with option 3, it does not have to be a browser that is invoked (I assume that is still true). They could call a custom exe that accepts the two parameters, and then have the exe make the post.