Voice Message Broadcasting

[ZeeTech]

I am using survey option with remote agents (Routing Extension is 8366) I just want to playback my message and then want to hang-up call so I chose ‘HANGUP’ in Survey Method, it is working but there is a 10 seconds of gap between message and call Hang-up, message length is 25 seconds but call disconnects after 35 seconds, I want to remove this 10 seconds gap please help

vicidialnow - standard install | Asterisk: 1.2.30.2. | Vicidial: 2.2.1-237| Build: 110430-1642

[williamconley]

it is likely "waiting for a response". this could likely be reduced to 1 or 2 seconds.

or you could create a special extension that just plays this message and hangs up (since you have no interest in the transfer to an agent portion of the survey). use that extension instead of 8366.

[ZeeTech]

please help me to reduce this "waiting for a response" up to 2 or 3 seconds because when i try my own ext it works well but it didn't generate any logs for reporting purpose so i want to use 8366 for proper call logging at the end i have to check how many number were connected successfully.

Thanks much!

[ZeeTech]

I am trying this following dial pattern and it shows length_in_sec = 0 and status = PDROP in vicidial_log, i need correct status and call length, please help

exten => 8383,1,AGI(agi://127.0.0.1:4577/call_log)
exten => 8383,2,Playback(mymsg)
exten => 8383,3,Hangupp

[williamconley]

you either have to modify the agi script to limit the wait time (script name is in the 8366 extension) or give up logging (which is likely disabled by using your own script) or use a different logging method. there are many logs created, and it is possible the call length is stored somewhere.

another possibility would to put another line in the extension to precede the (misspelled) hangup line that would modify the status of the lead to "listened to the entire message" before the hangup.

[mflorell]

This was fixed a while ago in svn/trunk, you just need to upgrade.

[ZeeTech]

Thanks William, i have changed wait_for_digit parameter in script and it works well for me.
What is PDROP status? should i consider such calls connected to customers?

[mflorell]

PDROP is a pre-routing drop, meaning that the call Answered and then hung up so fast that the script that starts playing a message or routing the call to an agent hadn't even started running yet. We have attempted to time some of these before and saw that they took less than a tenth-of-a-second to Answer and then hang up. Because of this, we usually don't consider these to be human answered.