Delay Between "200 OK" and Bridge/Agent Connection

[marcelo]

Marcelo here.

- ViciBox v.9.0.0 190913-1108 * Released on Friday the 13th during a full moon. So spooky, much wow! |Vicidial
2.14-588c BUILD 190925-1346 | Asterisk 13.27.0-vici | Linux version 4.12.14-lp151.28.16-default | Single Serv
er | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel(R) Xeon(R) CPU E5-2450 0 @ 2.10GHz

Please bear with me.

Call Log

time [s];64.74.129.238;64.124.219.166;64.124.219.133;SIP message
0.000000;;;;INVITE sip:415XXXXXXX@es1.langineers.com:5060 len:1072 [0s]
0.006837;;;;100 trying -- your call is important to us len:440 [0.01s]
1.814675;;;;183 Session Progress len:962 [1.81s]
1.817740;;;;RTP G.711u SSRC:39187691 PORT:15614 packets:537 L:0 J:0.5 [1.82s]
12.625375;;;;200 OK len:948 [12.63s] <<<<<<<<<<<< Acknowledging 200 OK from called phone
12.626401;;;;ACK sip:41XXXXXXX@64.124.219.133:5060 len:531 [12.63s]
12.637800;;;;RTP G.711u SSRC:5e171a64 PORT:15614 packets:622 L:0 J:0.7 [12.64s]
13.718900;;;;RTP G.711u SSRC:698aa077 PORT:14576 packets:626 L:0 J:4.4 [13.72s] <<<<<<<<<<< First RTP sent by ViciDail
26.235069;;;;BYE sip:14158201499@64.74.129.238:5060 len:720 [26.24s]
26.235680;;;;200 OK len:667 [26.24s]

The time difference between the "200 OK" and the first RTP sent by ViciDail is 12.625375 - 13.718900 = -1.093550 seconds. Please note the "ACK" to the "200 OK" happened immediately in 1 millisecond (0.001026s) .

1.1 seconds is a long time between the 200 OK and the first RTP sent, and this is making the gap between the customer "Hello..." and our Agent bridge engagement.

I have AMD disabled (Using Routing extension 8368.)

I understand the system needs to evaluate the call to bridge it or do a system disposition, but the delay to bridge engagement has been noticeable by our agent that most of the time gives no room for Agent/Customer conversation, as the customer is already turned away by the delay. It warns the customer it is a auto-dialing call.

Please advise if there is ways to mitigate this delay.

Many thanks in advance.

********************** Editing after post **************************

What about /usr/share/asterisk/agi-bin/agi-VDAD_ALL_outbound.agi ?????

It is taking 700 milliseconds running.

[mflorell]

System specs?(CPU/RAM/drives/etc...)
Number of leads in your system?
Number of records in vicidial_log table?
Number of agents/lines active at the time of your test call?

[marcelo]

System specs?(CPU/RAM/drives/etc...)
Number of leads in your system?
Number of records in vicidial_log table?
Number of agents/lines active at the time of your test call?

Thanks Matt

----> | Intel(R) Xeon(R) CPU E5-2450 0 @ 2.10GHz
/dev/sda3 154G 5.7G 141G 4% /
/dev/sda2 20M 1.1M 19M 6% /boot/efi
Mem : 8161600 total, 4079264 free, 3258848 used, 823488 buff/cache <<<< top now, NOT at time of test, but system is light.
load average: 0.06, 0.16, 0.20 <<<<<<<<< NO Campaigns running.

----> Two small Campaigns
TESTCAMP campaign- leads to call count: 0
QWERTY campaign- leads to call count: 410


----> /usr/share/astguiclient/AST_VDhopper.pl --count-only
Hopper count: 91

-----> wc -l /var/log/vici* /var/log/asterisk/messages
140 /var/log/vicibox.log
42 /var/log/vicidial.log
6478 /var/log/asterisk/messages

-----> Only one agent operating on Campaign QWERTY
Dial Method: RATIO
hopper_level='50'
auto_dial_level='4' <<< Testing Drop/answered ratio
Auto Dial Level Threshold: LOGGED-IN_AGENTS agents: 1

[marcelo]

Happy to announce we are off into production today!

It took the most to have data migrated to ViciDial from late "Predictive Dialer" service, but we made it alive.

All fingers crossed. I keep we posted.

[mflorell]

Congratulations!

Let us know how your first day of production dialing goes.

[marcelo]

Congratulations!

Thank you, Matt.

FYI... Beforehand we have been playing with ViciDial do adjust to our environment and needs and we did lots of change, so we have a few fine tune going on.

Although changes are mostly related to our particular needs, I am trying to see if is worth publishing back to you our 'diff' code so to you to choose if it is valid contribution, and to incorporate to main code at your discretion.

We have ViciDial In production but we are still considering we are on test phase.

I will keep us posted.

Best regards,