Call direction on Call Journaling in calls made by MakeCall

[Isaac Pires]

I'm using the 3CX Call Control API for use click2call (MakeCall) function.

When I send the request to the API the Call Control makes the system call the origin set, and when I answer the call on the set it starts a call the destination sent on the request.

In the same PBX I'm using the Call Journaling function. When the PBX sends the register of the call to the end point configured on the Call Journaling integration, this is send as an incoming call, what doesn't make sense, once the call is outbound, it was just started from a external request, but still being an outgoing call from the set.

In the call log we can see that the IVR makes the call to the origin set and when this set answer the call is initiated to the destination.

Is this a particularity of the PBX to register as incoming on the journaling the outgoing calls made through MakeCall?

Is there a way to change this?

 

[edossantos_sipcaller]

The Call Journaling will show what really happened. In order for this to work as you need, you will need to change the invocation of the MakeCall method, and use the variant that receives the RegistrarRecord as first argument. You will need to get the RegistrarRecord for the extension from which you want to initiate the call, and then start the call from it. This way the user will not see the "MakeCall" caller ID in the phone display.

 

[Isaac Pires]

Thank you too much.

I changed to RegistrarRecord and it works.

 

[edossantos_sipcaller]

The only thing you need to consider in that case, is that each device registered for the extension will be a different RegistrarRecord. So for example, if you are using an extension with a desk phone and the 3CX client for Android or iOS, then you could be selecting any of these records and you might be starting the call from the wrong device. You would need to check the details of the RegistrarRecord in that case to choose the correct item.

 

[Isaac Pires]

Thanks for the tip.

I made the code to start the call on all endpoint of the extension (3CX Mobile and a Yealink, for example), and when on of then answer the "makecall" the other will finish the call imediatly.

But now has another problem. When answer the MakeCall on the Yealink the PBX journall the call correctly as an outbound call as it is. But when answer the MakeCall on the 3CX Mobile the PBX journal the call as an inbound call.

Any idea of how to make the 3CX Mobile journall as an outbound call?

 

[edossantos_sipcaller]

Thanks for the tip.

I made the code to start the call on all endpoint of the extension (3CX Mobile and a Yealink, for example), and when on of then answer the "makecall" the other will finish the call imediatly.

But now has another problem. When answer the MakeCall on the Yealink the PBX journall the call correctly as an outbound call as it is. But when answer the MakeCall on the 3CX Mobile the PBX journal the call as an inbound call.

Any idea of how to make the 3CX Mobile journall as an outbound call?

Do you see the "MakeCall" caller ID when you start the call from this mobile app?