BUG timing for Allison prompts after unavailable message?

[vic peters]

does anyone know how to shorten the gap between the end of the users recorded unavailable message, and when Allison prompts the caller to “leave their message after the tone”. There is a 10 second gap even though the # was pressed immediately at the end of the original unavailable recording. So that’s not the source of dead silence. It appears to be global as every user has been advised to press the # immediately after creating their unavailable message. I have also tested it on my lab set up, and there is a 10 second dead silence gap before Allison prompts the caller to “leave the message after the tone…”.
Is this something that can be adjusted and if so, where is the adjustment found?
Customer system is PIAF green, Asterisk 11, centOS 6.5// quad core CPU, 4 Gb RAM
lab system is smooze distro freePBX running Ubuntu. Virtual machine install. 2 Gb RAM

Same 10 second gap?

 

[kenn10]

Not an issue on any of my systems. No delay at all. You might want to post a bug ticket with Schmooze. Most of us are running Centos so I can't make an apples to apples comparison. Your system certainly has adequate horsepower to not be lagging like that.

 

[vic peters]

have several lab vm's for testing, fired up the centos 6.3 running freePBX2.11 and had ext 201 dial 211 and let it go to voicemail. same 10 second pause before allison's smooth delivery. here's the verbosity at three -vvvr

followme and vmx locator are both enabled. there are no error or warnings. my comments are in red font

-- Executing [vmx@macro-vm:16] Set("SIP/201-00000029", "VMX_REPEAT=") in new stack
-- Executing [vmx@macro-vm:17] Set("SIP/201-00000029", "VMX_TIMEOUT=") in new stack
-- Executing [vmx@macro-vm:18] Set("SIP/201-00000029", "VMX_LOOPS=") in new stack
-- Executing [vmx@macro-vm:19] Answer("SIP/201-00000029", "") in new stack
-- Executing [vmx@macro-vm:20] Read("SIP/201-00000029", "ACTION,/var/spool/asterisk/voicemail/default/211/unavail,1,skip,,") in new stack
-- Accepting a maximum of 1 digits.
caller can choose to have system locate owner of extension 211. if call to cell is not answered caller is returned to 211 busy message and prompted to leave a voicemail
-- <SIP/201-00000029> Playing '/var/spool/asterisk/voicemail/default/211/unavail.slin' (language 'en')
-- User entered nothing.
-- Executing [vmx@macro-vm:21] GotoIf("SIP/201-00000029", "0?checkopt") in new stack
-- Executing [vmx@macro-vm:22] NoOp("SIP/201-00000029", "Timeout: going to timeout dest") in new stack
-- Executing [vmx@macro-vm:23] Set("SIP/201-00000029", "VMX_OPTS=") in new stack
-- Executing [vmx@macro-vm:24] GotoIf("SIP/201-00000029", "1?dotime") in new stack
-- Goto (macro-vm,vmx,28)
-- Executing [vmx@macro-vm:28] Goto("SIP/201-00000029", ",dovm,1") in new stack
-- Goto (macro-vm,dovm,1)
-- Executing [dovm@macro-vm:1] NoOp("SIP/201-00000029", "VMX Timeout - go to voicemail") in new stack
-- Executing [dovm@macro-vm:2] VoiceMail("SIP/201-00000029", "211@default,") in new stack
it's at this point allison delivers here sweet tones
-- <SIP/201-00000029> Playing 'vm-intro.ulaw' (language 'en')
-- <SIP/201-00000029> Playing 'beep.ulaw' (language 'en')
-- Recording the message
-- x=0, open writing: /var/spool/asterisk/voicemail/default/211/tmp/LcOrXf format: wav, 0x1100c88
-- User hung up

 

[vic peters]

here's the same actions from the log file cut for brevity...
[2014-02-19 16:28:16] VERBOSE[14743][C-0000001b] pbx.c: -- Executing [vmx@macro-vm:16] Set("SIP/201-00000029", "VMX_REPEAT=") in new stack
[2014-02-19 16:28:16] VERBOSE[14743][C-0000001b] pbx.c: -- Executing [vmx@macro-vm:17] Set("SIP/201-00000029", "VMX_TIMEOUT=") in new stack
[2014-02-19 16:28:16] VERBOSE[14743][C-0000001b] pbx.c: -- Executing [vmx@macro-vm:18] Set("SIP/201-00000029", "VMX_LOOPS=") in new stack
[2014-02-19 16:28:16] VERBOSE[14743][C-0000001b] pbx.c: -- Executing [vmx@macro-vm:19] Answer("SIP/201-00000029", "") in new stack
[2014-02-19 16:28:16] VERBOSE[14743][C-0000001b] pbx.c: -- Executing [vmx@macro-vm:20] Read("SIP/201-00000029", "ACTION,/var/spool/asterisk/voicemail/default/211/unavail,1,skip,,") in new stack
[2014-02-19 16:28:16] VERBOSE[14743][C-0000001b] app_read.c: -- Accepting a maximum of 1 digits.
[2014-02-19 16:28:16] VERBOSE[14743][C-0000001b] file.c: -- <SIP/201-00000029> Playing '/var/spool/asterisk/voicemail/default/211/unavail.slin' (language 'en')
[2014-02-19 16:28:50] VERBOSE[14743][C-0000001b] app_read.c: -- User entered nothing.
[2014-02-19 16:28:50] VERBOSE[14743][C-0000001b] pbx.c: -- Executing [vmx@macro-vm:21] GotoIf("SIP/201-00000029", "0?checkopt") in new stack
[2014-02-19 16:28:50] VERBOSE[14743][C-0000001b] pbx.c: -- Executing [vmx@macro-vm:22] NoOp("SIP/201-00000029", "Timeout: going to timeout dest") in new stack
[2014-02-19 16:28:50] VERBOSE[14743][C-0000001b] pbx.c: -- Executing [vmx@macro-vm:23] Set("SIP/201-00000029", "VMX_OPTS=") in new stack
[2014-02-19 16:28:50] VERBOSE[14743][C-0000001b] pbx.c: -- Executing [vmx@macro-vm:24] GotoIf("SIP/201-00000029", "1?dotime") in new stack
[2014-02-19 16:28:50] VERBOSE[14743][C-0000001b] pbx.c: -- Goto (macro-vm,vmx,28)
[2014-02-19 16:28:50] VERBOSE[14743][C-0000001b] pbx.c: -- Executing [vmx@macro-vm:28] Goto("SIP/201-00000029", ",dovm,1") in new stack
[2014-02-19 16:28:50] VERBOSE[14743][C-0000001b] pbx.c: -- Goto (macro-vm,dovm,1)
[2014-02-19 16:28:50] VERBOSE[14743][C-0000001b] pbx.c: -- Executing [dovm@macro-vm:1] NoOp("SIP/201-00000029", "VMX Timeout - go to voicemail") in new stack
[2014-02-19 16:28:50] VERBOSE[14743][C-0000001b] pbx.c: -- Executing [dovm@macro-vm:2] VoiceMail("SIP/201-00000029", "211@default,") in new stack
[2014-02-19 16:28:50] VERBOSE[14743][C-0000001b] file.c: -- <SIP/201-00000029> Playing 'vm-intro.ulaw' (language 'en')
[2014-02-19 16:28:55] VERBOSE[14743][C-0000001b] file.c: -- <SIP/201-00000029> Playing 'beep.ulaw' (language 'en')
[2014-02-19 16:28:56] VERBOSE[14743][C-0000001b] app_voicemail.c: -- Recording the message
[2014-02-19 16:28:56] VERBOSE[14743][C-0000001b] app.c: -- x=0, open writing: /var/spool/asterisk/voicemail/default/211/tmp/LcOrXf format: wav, 0x1100c88
[2014-02-19 16:28:56] VERBOSE[14743][C-0000001b] app.c: -- User hung up

there are NO errors or warnings, just a solid 10 second gap before allison delivers her default prompt.

 

[vic peters]

I guess I’m going to file a bug ticket with freePBX on this issue. It is very easy to verify what’s happening. You don’t even need an additional endpoint device to verify that it exists. It happens when you add the VMX locator service. Just create an extension and instead of the generic sip device option on the pulldown, select None (virtual enten). For illustrative purposes let’s call the new extension number 23. Enable 23’s voicemail and then go to any existing telephone, dial*98 to enter comedian mail because your recording off another phone since 23 is virtual. Dial 23 and record your unavailable message through the standard prompts. Now if you pick up the same phone you used to create the unavailable message, dial 23. It will play the unavailable message and immediately without any delays, Allison’s voice comes in prompting you to leave a message. This is how it should always work.
Now go back to extension 23’s set up options and underneath the voicemail options enable the VMX locator, check the box--use when unavailable , and under press one OPTION enter your cell phone number. This is where if you are unavailable and your recorded message indicates to the caller that they can locate you by pressing one, the system then dials your cell phone utilizing the VMX locator service. Save the config, go back to any phone on the system or the one you used to record your unavailable message, dial 23 and it will play the unavailable message – – but here you will notice that there is a 10 second delay before Allison asks the caller to leave a message. 10 seconds of deadpan silenced that’s irritating my customer. The only change here was the VMX locator service was turned on.
Now if you go back to extension 23 setup options and disable the VMX locator, save the config, and dial 23 again, it plays the unavailable message and the 10 second dead pan silence gap is gone! Allison prompts come in immediately.
Now the question is what can be done about it?

 

[Brian Simmons]

I was going to ask if you have the VX Locator turned on because I have experienced the same issue when turned on. I see from the last post that this is the case with you too. Here is the thread that I started when I first understood the problem. http://pbxinaflash.com/community/in...ng-pause-before-record-tone.13720/#post-87619

 

[vic peters]

While I did file a bug report with freePBX. Don’t know how that process works or who even reads and follows up on such things. But under settings >>voicemail admin>> dial plan behavior, there is a advanced VMX locator setting called message timeout. My lab system had a default of two seconds that was set. I change that to zero seconds, hit submit, and apply config. Went back and tested the gap and now it seems to have been reduced from 10 seconds to six seconds. That is an improvement, but I’d like the “please leave your message prompt” from Allison to come on his fast as it does without VMX locator enabled. But again, the geniuses that create this software and write these complicated scripts will have to deem it important. Six is less than 10. Thanks for the link to your post Brian, and thanks Alai for someplace else to look.

 

[xrobau]

Not a bug. Just lack of documentation (that I'm going to address).

The caller should never be waiting for the timeout. The message should ALWAYS end with '... or press # to leave a message for me'. The timeout is there for people who can't push #, or another button.