latency makecall

automotivedirectmail

Customer
Joined
Jan 7, 2023
Messages
4
Reaction score
0
We have to call out quickly through api using dn_number).

Call is triggered by our software.....

If i see the log in 3cx i see it's using 1 second for even starting to authenticate.

is there a way to eliminate this step?
 

Attachments

  • 3cx_issue.png
    3cx_issue.png
    1,015.8 KB · Views: 6
No, there is no way to avoid that. It's due to how the make call is implemented internally.
 
  • Like
Reactions: Evolute IT
already afraid of that.

maybe you can help me a bit further.

Out of our software a number is supplied to 3cx.... that should be called directly out of server (so not through the 3cx apps).
Speed is essential in this proces to reach the customer first. (i am looking for 1 second improvement).

Besides that:

I want another line to call my 3cx extension 100, where i will put my desktop 3cx app in autoanswer.
This line should be on hold till the first line picks up.
Then i want to take over the line that was connected to my cutstomer.

is this possible ?
 
Out of our software a number is supplied to 3cx.... that should be called directly out of server (so not through the 3cx apps).
Speed is essential in this proces to reach the customer first. (i am looking for 1 second improvement).
In order to improve that, you would need to create a custom SIP client, where you can control all the details of what you do. Not a simple task at all. Not sure how important this is in order to invest a lot of effort on that....

Besides that:

I want another line to call my 3cx extension 100, where i will put my desktop 3cx app in autoanswer.
This line should be on hold till the first line picks up.
Then i want to take over the line that was connected to my cutstomer.
Calling the extension 100 and putting it on hold is something you could do using the same approach (Make Call), and calling a shared parking extension. However, you can't merge both calls later. Instead, I would make the call to the external number, and as soon as the call is answered you connect it to your extension. Actually, this is something you can also do with SIP Caller: add the number to call using a REST API, and once the external party answers you can transfer the call to extension 100, which would have the auto-answer, so you would speak with your customer as soon as they pick up. The blind call transfer is an operation that has barely no delay.
 
  • Like
Reactions: Evolute IT
In order to improve that, you would need to create a custom SIP client, where you can control all the details of what you do. Not a simple task at all. Not sure how important this is in order to invest a lot of effort on that....


Calling the extension 100 and putting it on hold is something you could do using the same approach (Make Call), and calling a shared parking extension. However, you can't merge both calls later. Instead, I would make the call to the external number, and as soon as the call is answered you connect it to your extension. Actually, this is something you can also do with SIP Caller: add the number to call using a REST API, and once the external party answers you can transfer the call to extension 100, which would have the auto-answer, so you would speak with your customer as soon as they pick up. The blind call transfer is an operation that has barely no delay.
"In order to improve that, you would need to create a custom SIP client, where you can control all the details of what you do. Not a simple task at all. Not sure how important this is in order to invest a lot of effort on that...."

this is what i need, so yes it;s important. Do you know anyone who can fix this?
 
this is what i need, so yes it;s important. Do you know anyone who can fix this?
You will need a software developer with experience with SIP & RTP protocols. I don't know anyone to recommend on this...
 
  • Like
Reactions: Evolute IT
I'm not sure we fully understand the actual concern. I'm thinking the concern is more about how quickly we can get a cold-call to an agent, and have the agent answer the phone. I agree, there needs to be an agent available the second the outside party answers the call, otherwise they will hang up.

You should, for example, be able to perform a 3CX MakeCall between an outside party and a queue agent in about 1 second. Certainly fast enough if you have auto-answer turned on. You are saying that you are having a significant delay. Maybe you can explain further precisely what you are doing so we can discuss whether there are alternatives approaches that would work better.

Keep in mind, most of the 1-second delay is consumed by the outside party simply answering the phone and saying "hello". In my experience, if the agent phone is set to auto-answer, the speed at which 3CX can get a caller to an agent is fast enough.