NEW Incredible 16-15.2 for CentOS 7

[kenn10]

Just tested with a DID calling the ring group and the call fails on an incoming call if the send progress is on. Using the experimental dialparties.agi fix does not make any difference.

Question: Will there be any effect if we leave send progress turned off? My concern is that some carriers may not send ringtone back to the caller if the setting is off.

 

[wardmundy]

Aside from the ringtone issue from some carriers, I wouldn't think it would be a problem turning off call progress BUT... mine works as is. Just tested from a DID to the ring group, and it worked as well. Because we build from a snapshot, I would think the default setup would work on any platform. If you test that, then I'd add another ring group and see if the original 777 still works and the new one fails. Very strange.

 

[kenn10]

Aside from the ringtone issue from some carriers, I wouldn't think it would be a problem turning off call progress BUT... mine works as is. Just tested from a DID to the ring group, and it worked as well. Because we build from a snapshot, I would think the default setup would work on any platform. If you test that, then I'd add another ring group and see if the original 777 still works and the new one fails. Very strange.

I've tried adding a new ring group and it still fails. Sounds like something carried over from the 13-13 import is messing with us in 16-15. We may be back a square one using bulk import and a lot of copy/paste but despite this one issue, the import saves a ton of work.

 

[tbrummell]

Mine was not an import, stare and compare reprogram....

 

[tbrummell]

I have a 16-15-1 system up still from the iptables testing, and the ring group in it, with Send Progress = Yes works just fine to the Ring Group, internal & external, all SIP based, no DAHDI devices....

 

[wardmundy]

FYI: I'm keeping a Known Issues list in the Nerd Vittles 13-13 to 16-15 migration article should you need it down the road.

 

[kenn10]

FYI: I'm keeping a Known Issues list in the Nerd Vittles 13-13 to 16-15 migration article should you need it down the road.

I may be on to somthing. The indications.conf set of files seems to differ between 13-13 and 15-16. I'm investigating further. I've restored the original starting 15-16 configuration and I'm digging into differences. My data import indications.conf series of files is different from the original 15-16 files. I'll be experimenting.

 

[wardmundy]

Vultr must love us. I've already spent almost 50 cents on this project.

 

[tbrummell]

WHAT?!?! I'm already at $2.63....

EDIT to add: and that's in USD, and I pay in CDN, so that's closer to ....... 50 bux!!!! LOL OK, more like $3.25....

 

[kenn10]

OK. I may have solved it.

1) I copied the unmodified indications* files from original 16-15.1 load.
2) I restored my 13-13 configuration to the 15-16.1 system and
3) replaced the restored indications* files with the original ones I copied in the first step.
4) I modified my settings > SIP settings > SIP Legacy Settings to look like the original screen in the unmodified 16-15.1 load.
I

The ring group now works with send progress = yes.

EDIT: The SIP settings part may not be necessary. @tbrummell give this procedure a try an comment please.

 

[wardmundy]

@kenn10: I think you'll also need to copy the original indications_additional.conf into indications_custom.conf, or you'll lose the new settings with the first FreePBX reload.

 

[kenn10]

@kenn10: I think you'll also need to copy the original indications_additional.conf into indications_custom.conf, or you'll lose the new settings with the first FreePBX reload.

You're absolutely correct. It has now quit working. Let me edit the files again and report back.

Edit: That was it. The indications_custom.conf got garbled. I have copied the 13-13 indications.conf in to the 16-15 indications_custom.conf and it works. The CLI error that it could not find 'ring' was accurate with the garbled file. The line feeds had been converted into slashes (/) in that file for some reason.

 

[tbrummell]

Doesn't work for me, copied indications.conf from 13-13-10 to _custom.conf on '16. Saved/Applied in GUI, changed Progress to Yes and no go.

I'm not sure what should be in indications.conf, looks like a whole bunch of flash timers to me....

 

[kenn10]

Doesn't work for me, copied indications.conf from 13-13-10 to _custom.conf on '16. Saved/Applied in GUI, changed Progress to Yes and no go.

I'm not sure what should be in indications.conf, looks like a whole bunch of flash timers to me....

This should be in your indications_custom.conf on the 16-15 system. Things are definitely different between 13-13 and 16-15.

[us]
description = United States / North America
ringcadence = 2000,4000
dial = 350+440
busy = 480+620/500,0/500
ring = 440+480/2000,0/4000
congestion = 480+620/250,0/250
callwaiting = 440/300,0/10000
dialrecall = !350+440/100,!0/100,!350+440/100,!0/100,!350+440/100,!0/100,350+440
record = 1400/500,0/15000
info = !950/330,!1400/330,!1800/330,0
stutter = !350+440/100,!0/100,!350+440/100,!0/100,!350+440/100,!0/100,!350+440/100,!0/100,!350+440/100,!0/100,!350+440/100,!0/100,350+440

Also note that if you play with the indications settings on the settings > advanced settings page, it messes up all the files again.

 

[tbrummell]

Yup, that's what it was....

 

[wardmundy]

Yeah, you need indications_additional.conf from 16-15 (not 13-13) copied to indications_custom.conf. Modified newbackup16-15.tar.gz accordingly, and it gets set up as part of a base 16-15 install now.

 

[wardmundy]

@tbrummell: Dahdi updated in 16-15 base install to 3.1.RC1 based upon your testing. Thanks.

 

[kenn10]

If you make any changes to the indications in the advanced settings (in this case, the 1950's US indications file,) it messes up the output and puts it in the indications_additional.conf file. That would be fine if it were formatted correctly but the "\n" for new line scrambles the file so it is not read properly. I assume this to be a FreePBX 15 glitch but it is definitely a gotcha if people play with the indications.

[us-old]
description = United States Circa 1950/ North America
ringcadence = 2000,4000\ndial = 600*120\nbusy = 500*100/500,0/500\nring = 420*40/2000,0/4000\ncongestion = 500*100/250,0/250\ncallwaiting = 440/300,0/10000\ndialrecall = !600*120/100,!0/100,!600*120/100,!0/100,!600*120/100,!0/100,600*120\nrecord = 1400/500,0/15000\ninfo = !950/330,!1400/330,!1800/330,0\nstutter = !600*120/100,!0/100,!600*120/100,!0/100,!600*120/100,!0/100,!600*120/100,!0/100,!600*120/100,!0/100,!600*120/100,!0/100,600*120\n

 

[Chinaso]

Just finished the initial setup and:
I tried to enable the DAHDi module on FreePBX, but got the attached error. Then I tried to the check online option on modules update and got the same screen??
BTW is there any replacement for dahdi_tool? I am trying to configure a digium TE122 PRI card.

Bay hep welcomed. Thanks in advance.

 

[wardmundy]

@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