I’ll go back and try with a new undertanding of maxsilence actually not being in ms.
And see what I get.
Default settings are 10 and 1 on these.
This is out of the box and works fine - I can leave a 20 second message it works.
It is of course also recording and saving fast hangup salesbot calls where the system just hangs up.
This is my original intention and reason for trying to set minmessage to “5” or “7” require a message to be a bit longer than one second to save it.
I’ve not even touched the other setting to this point as my understanding of it was not clear.
OK, now raise it to 2 or 3, test…raise it again, test…see if there is an issue as you increment it.
The code should convert macro to gosub automatically. if it’s not the case, the use Asterisk 20.x or lower indeed.
I’m using a fresh 17 install and it’s up to date.
I did not import anything from any older installation.
This system is PJSip only.
This should work out of the box (unless it shouldn’t for any reason).
It’s expected to work out of the box and it’s implied in the interface that it does.
Unless I’m missing something.
Newer versions of asterisk as such are being used here use Gosub.
I will try the incrementing starting from 2 seconds as suggested and see what happens.
It works as expected when set to 1,2,3 and 4.
But immediately fails as described in the post when set to “5” or higher.
The voicemails have full audio? What version of Asterisk are you using?
This one.
Don’t use a Certified version; those are only for people with paid support contracts, and only within a subset of the functionality that is covered by the contract.
No idea what that means.
This is a FreePbx17 install and it is using the version of asterisk that it put in place to use.
I have not changed it.
Thanks.
There was a menu of versions given further up. You should not select one that looks like, for example:
I am unable to replicate this. I have the latest versions of the modules and running Asterisk 21.5.0 with the minsecs=5 (so must be 5 seconds in length) and I’ve been able to leave voicemails without issues.
@michiganbroadband Show us the output of /etc/asterisk/voicemail.conf that you have.
Nice.
Mine works fine when set to 4 but dies as soon as I set it to “5” or greater.
[general]
emailbody=${VM_NAME},\n\nThere is a new voicemail in mailbox ${VM_MAILBOX}:\n\n\tFrom:\t${VM_CALLERID}\n\tLength:\t${VM_DUR} seconds\n\tDate:\t${VM_DATE}\n\nDial *98 to access your voicemail by phone.\nVisit /ucp to check your voicemail with a web browser.\n
pollmailboxes=yes
pollfreq=10
forcegreetings=yes
forcename=yes
emailsubject=PBX Voicemail Notification
fromstring=PBX Phone System
charset=UTF-8
envelope=yes
operator=yes
review=no
saycid=no
sayduration=yes
searchcontexts=no
sendvoicemail=yes
tempgreetwarn=yes
usedirectory=yes
hidefromdir=no
moveheard=yes
smdienable=no
nextaftercmd=yes
emaildateformat=%A, %B %d, %Y at %r
pagersubject=PBX Voicemail Notification
pagerbody=New ${VM_DUR} long msg in box ${VM_MAILBOX}\nfrom ${VM_CALLERID}, on ${VM_DATE}
pagerfromstring=PBX Phone System
pagerdateformat=%A, %B %d, %Y at %r
pbxskip=no
attach=yes
maxgreet=60
maxlogins=3
maxmsg=100
minpassword=0
maxsecs=300
maxsilence=10
silencethreshold=128
minsecs=4
imapgreetings=yes
imapclosetimeout=60
imapopentimeout=60
imapreadtimeout=60
imapwritetimeout=60
aliasescontext=pbxaliases
Where is the rest of the file? Obfuscate the passwords.
@michiganbroadband Do this, set minsecs=5, then do asterisk -rvvvvvvvvv, then leave a test voicemail. Once that is done, do a tail -100 /var/log/asterisk/full and give us that output. It should have your voicemail call in the output. I want to see timestamps on things, even with the failure.
I will do both of those…
Give me a bit.
And thanks.
I have a little more work to do.
During this testing I thought to try dialing the extension directly and leaving a voicemail this way.
The way I was testing this was from an IVR that directed the flow to the same extension’s voicemail.
I am now only experiencing this problem when it is directed to the voicemail box via IVR.
So give me a few more to narrow this down better.
Sorry.
I should have already tested this and did not… I figured it didn’t make any difference.
I’m pretty sure there are no upstream timers involved as the handoff to voicemail-extension is the end of the line for the IVR in this case.
I’ll need to look at this more closely 
This flow path seemingly has something to do with it.
Once it is in the voicemail app it is in it. I want to see the timing of everything including how long the call was in the mailbox.
I also have a number of extensions that were on an old system and had BLF buttons subscribed to numbers that are non-existent on this “new” system.
I need to clean this up as it is really cluttering up the log and console.
Making work like this more cumbersome.
I can go ahead and post or try and clean that up a bit first.
The output is full of state subscription failed: Extension does not exist in context ‘from-internal’ or has no associated hint.
Making it hard to read.
I need to fix that.