NEW Incredible 16-15.2 for CentOS 7

[wardmundy]

@Chinaso: RUN: /root/resetting-module-repository

It explains how to switch to the FreePBX repos so long as you are not reselling the server commercially.

 

[tbrummell]

But I am not restoring a 13-13 backup. My tables should be fine, my conf files should be fine. I'm a little lost at this point.

 

[wardmundy]

But I am not restoring a 13-13 backup. My tables should be fine, my conf files should be fine. I'm a little lost at this point.

Me, too. Is something not working for you??

 

[kenn10]

@kenn10: It turns out the restore from 13 trashes the entire indications_zonelist table in the asterisk database. The easiest way to fix this is simply to restore the clean 15 version of the table so we've added it to newbackup16-15.tar.gz and it gets restored when you run restore-fix after restoring a 13-13 server. Coupled with fwconsole reload, that gets everything squared away without having to resort to custom file overrides which only fix the problem for a single country. We've added all the pieces for this so that everything gets put in place when you build any new 16-15 server.

If you want to update your existing 16-15 server with the new pieces, just download, untar, and then remove newbackup16-15.tar.gz from incrediblepbx.com. Then fix your existing indications_zonelist table like this:

cd /root
wget http://incrediblepbx.com/newbackup16-15.tar.gz
tar zxvf newbackup16-15.tar.gz
rm -f newbackup16-15.tar.gz
mv /etc/asterisk/indications_custom.conf /etc/asterisk/indications_custom.conf.no-longer-needed
mysql -u root -ppassw0rd asterisk < /root/indications_zonelist.sql
fwconsole reload

Works like a charm. Great news!

 

[kenn10]

@wardmundy I have found another small issue. When voicemail greetings are copied from 13-13, they are terminated with lower-case .wav. For some reason, the 16-15 system wants them in upper-case format like greeting.WAV. I renamed the files and they work when the .wav suffix is changed to a .WAV suffix. This is another difference between FreePBX 13 and FreePBX 15.

 

[wardmundy]

@wardmundy I have found another small issue. When voicemail greetings are copied from 13-13, they are terminated with lower-case .wav. For some reason, the 16-15 system wants them in upper-case format like greeting.WAV. I renamed the files and they work when the .wav suffix is changed to a .WAV suffix. This is another difference between FreePBX 13 and FreePBX 15.

What directory or directories do these files reside in?? I don't have any to test.

 

[kenn10]

What directory or directories do these files reside in?? I don't have any to test.

/var/spool/asterisk/voicemail/default/<extension>/

 

[wardmundy]

@kenn10: Interesting. My "pure" 16-15 server creates both greeting.wav and greeting.WAV with different file sizes no less.

 

[wardmundy]

I've added the following to restore-fix before the fwconsole commands:

for d in /var/spool/asterisk/voicemail/default/*; do
  if [ -d "$d" ]; then
    cd "$d"
    cp -np *.wav *.WAV
  fi
done

 

[kenn10]

I've added the following to restore-fix before the fwconsole commands:

for d in /var/spool/asterisk/voicemail/default/*; do
  if [ -d "$d" ]; then
    cd "$d"
    cp -np *.wav *.WAV
  fi
done

Oddly enough, the music on hold files are .wav and they work. This may be an Asterisk issue in the voicemail module more than a FreePBX 15 issue. Let's hope that if they fix it in the appropriate product, it will still accept our uppercase .WAV files.

By the way, UCP will play messages and greetings in either format. It's just the voicemail module requiring that the greetings be in .WAV format.

 

[wardmundy]

@kenn10: But it's not even a different format. It's just a different file extension.

UPDATE: Actually, it apparently is a different format and the .wav files are stored in a different format in 13 than they are in 15/16.

So... I've updated the code above to only overwrite the .WAV file if it doesn't exist. Otherwise, you could end up with .WAV files that don't play by simply overwriting or replacing them. Here's why... I think.

It looks like the Asterisk 13 .wav file is what Asterisk 16 treats as a .WAV file. That's why renaming it from a 13 import worked. But you can't take a.wav file created in Asterisk 16 voicemail and rename it. Otherwise, it won't play. So in Asterisk 16, they created the old version as .WAV and the new version as .wav. What a clusterf***!

 

[jerrm]

@kenn10: But it's not even a different format. It's just a different file extension. Correct??

No it is different encoding. WAV is compressed, wav is raw. Have you confirmed what the format setting is in VM Admin and if it makes a difference?

 

[wardmundy]

I did a little experimenting using @jerrm definitions, I started with:

greet.wav.bak 14444 bytes (uncompressed)
greet.WAV.bak 1490 bytes (compressed)

I copied these in various combinations and tested whether I got a voicemail greeting rather than a hangup when calling the unanswered extension:

WORKS: greet.wav bak -> greet.wav and greet.WAV.bak -> greet.WAV
WORKS: greet.wav bak -> greet.wav and greet.wav.bak -> greet.WAV
WORKS: greet.WAV bak -> greet.wav and greet.WAV.bak -> greet.WAV
WORKS: greet.WAV.bak -> greet.WAV and NO greet.wav
WORKS: greet.wav.bak -> greet.wav and NO greet.WAV
FAILS: greet.WAV.bak -> greet.wav and NO greet.WAV
FAILS: greet.wav.bak -> greet.WAV and NO greet.wav

So it looks like any combination works as long as you have two files even if they are mismatched and incorrectly named. But, if you only have a single file, it has to be named correctly or the answer fails. This still doesn't explain why the Asterisk 13 files are improperly named unless that is happening as part of the restore process. @kenn10: Can you verify the names of the greet files on your Asterisk 13 platform before the restore? If they are .WAV files and being imported and renamed as .wav files, that would obviously be another bug even though we have solved it with restore-fix code above.

 

[kenn10]

No it is different encoding. WAV is compressed, wav is raw. Have you confirmed what the format setting is in VM Admin and if it makes a difference?

In my case, both 13-13 and 16-15 are set to wav|wav49.

 

[wardmundy]

@kenn10: See questions immediately above. We were both posting at the same time.

 

[kenn10]

So it looks like any combination works as long as you have two files even if they are mismatched and incorrectly named. But, if you only have a single file, it has to be named correctly or the answer fails. This still doesn't explain why the Asterisk 13 files are improperly named unless that is happening as part of the restore process. @kenn10: Can you verify the names of the greet files on your Asterisk 13 platform before the restore? If they are .WAV files and being imported and renamed as .wav files, that would obviously be another bug even though we have solved it with restore-fix code above.

Mine works fine with just the .WAV files. I just renamed the old .wav to .WAV. I don't get it.

root@joecloud3:/var/spool/asterisk/voicemail/default/2017 $ ls
INBOX  Old  Urgent  busy.WAV  greet.WAV  tmp  unavail.WAV

I rerecorded an unavailable greeting on this extension and it created the new one as unavail.wav. Go figure:

root@joecloud3:/var/spool/asterisk/voicemail/default/2010 $ ls
INBOX  Old  Urgent  Work  busy.WAV  greet.WAV  tmp  unavail.WAV  unavail.wav

EDIT: Answering the question about the original 13-13 files, surprise! It has both WAV and wav files:

root@joecloud:/var/spool/asterisk/voicemail/default/2017 $ ls
2008   Old     busy.WAV  greet.WAV  tmp          unavail.wav
INBOX  Urgent  busy.wav  greet.wav  unavail.WAV

 

[wardmundy]

@kenn10: Was this on your Asterisk 13 or 16 server?? We need to see what files are on the Asterisk 13 server. Do you have .WAV and .wav or just one or the other? And which are being restored from your backup??

 

[kenn10]

@kenn10: Was this on your Asterisk 13 or 16 server?? We need to see what files are on the Asterisk 13 server. Do you have .WAV and .wav or just one or the other? And which are being restored from your backup??

See my last post before this one. On the 16-15 server, only *.wav files were restored. On the 13-13 server both .wav and .WAV files exist in the directory.

Next i thought maybe my FreePBX backup did not have both, but I just expanded the backup to look and both were in it:

 

[kenn10]

There must be two files generated because of the voicemail settings.

 

[kenn10]

And here is a FreePBX jewel about voice mail format that I just found. I had not seen this before:

Sangoma Documentation

wiki.freepbx.org