PIONEERS Asterisk 17 Upgrade for Incredible PBX 2020

[Samot]

@dhoppy Thanks for the new signature though.

 

[markieb]

Personally I'd go with the person whose track record of knowing and pioneering most of what I use today, which spans decades not months.
Thanks for everything you've given us over the MANY years @wardmundy

 

[tbrummell]

Just did a fresh Incredible PBX 2020 install followed by an Asterisk 17 upgrade. All of the latest FreePBX modules were in place as well. Both log*_custom are empty and both log*_additional are populated. CDRs and CELs work as advertised.

I haven't tried to reproduce, BUT, I think it is most likely because I had already modified the logger.conf to not show double entries anymore. Then, when I logged in and the update script ran, I'm assuming it blindly went and erased the remaining line(s) since the typically use sed commands.
Note: I have not reviewed the update script at all.

 

[Samot]

Personally I'd go with the person whose track record of knowing and pioneering most of what I use today, which spans decades not months.

OK, let's not have a bunch of people come into this thread and start playing the "I'm Team Ward" game. There is absolutely no need for it.

Also, it's been 15 years. A decade and a half, not multiple decades. My first experiences with PBX In a Flash was so I could do interop testing of it with our SIP Trunking services back in the day.

 

[wardmundy]

@Samot: Here's another idea. Let's not clutter the forum with a bunch of toxic posts that really don't move us forward.

 

[billsimon]

I thought this forum once it moved to "voip-info.org" would be less partisan.

people should judge each other's posts on tech forum based on their technical merit and accuracy, not their feelings and partisanship.

edit: In that spirit I am not indicating any "side" on debate, and fwiw, have had numerous positive conversations with Ward and at least a few with Samot, but suggest everyone take an objective view of what is being stated and not just incline yourselves toward any one person (or against any other) for subjective reasons.

 

[roundaway]

Remember back in the day when it was the GTO Global Mobile Services thread that would add 3 pages in a day. Ah, good times.

 

[wardmundy]

@roundaway: Looks like you scared everybody away.

 

[dhoppy]

Is the upgrade ready for non-pioneers?

 

[kenn10]

Is the upgrade ready for non-pioneers?

I've upgraded two cloud systems without issue.

 

[roundaway]

@roundaway: Looks like you scared everybody away.

See what you did. Just like children, they always come back.

Thank you for all you do to maintain IncrediblePBX, Nerd Vittles, and provide patient replies to all posters.

 

[hawk#1]

Just upgraded another (4th) system yesterday and have not had any problems with any of them

 

[dhoppy]

Just upgraded another (4th) system yesterday and have not had any problems with any of them

No problems for me either, did 3 systems.

 

[progs_00]

No problems for me either, did 3 systems.

Upgraded a production system yesterday running on virtualbox.
Everything works perfectly (apart from manually having to give fwconsole start to start Asterisk, but that's a Virtualbox+Windows issue)

 

[wardmundy]

Upgraded a production system yesterday running on virtualbox.
Everything works perfectly (apart from manually having to give fwconsole start to start Asterisk, but that's a Virtualbox+Windows issue)

Add it to /etc/rc.local or adjust the timing if it's already there.

 

[progs_00]

Thank you Ward. Internet connection on this remote site is currently down so I'll give it a shot once possible.

 

[dhoppy]

Has anyone ever seen where the asterisk CLI doesn't show anything? Calls are going through, but call processing isn't showing up.

I don't know how it got turned off, I don't do anything custom.
but found this post if anyone else needs the same fix in this thread.

 

[tbrummell]

Has anyone ever seen where the asterisk CLI doesn't show anything? Calls are going through, but call processing isn't showing up.

Yes, your logger conf has been blanked out. It's reported elsewhere on the forum.

 

[geopeterwc]

The "latest version" of the logfiles update (15.0.4) "broke" the default settings for logfiles. The following (might help) is from the FreePBX forums. Under "Advanced Settings: LogFile Settings|LogFiles. Make the required changes and log file information will resume. Click the "save" icon at the right of the table, then clcik on "apply" to apply your changes.

Asterisk Log File Settings

Field	Default​	Information
File Name	​	Name of file, relative to Asterisk log path. Use absolute path for a different location
Debug	?​	Messages used for debugging. Do not report these as errors unless you have a specific issue that you are attempting to debug. Also note that Debug messages are also very verbose and can and do fill up logfiles (and disk storage) quickly.
DTMF	OFF​	Keypresses as understood by asterisk. Useful for debugging IVR and VM issues
Error	ON​	Critical errors and issues
Fax	OFF​	Transmission and receiving of faxes
Notice	ON​	Messages of specific actions, such as a phone registration or call completion
Verbose	ON​	Step-by-step messages of every step of a call flow. Always enable and review if calls don't flow as expected
Warning	ON​	Possible issues with dialplan syntax or call flow, but not critical.
Security	OFF​

​

File Name	Debug	DTMF	Error	Fax	Notice	Verbose	Warning	Security
full​	?​	OFF​	ON​	OFF​	ON​	ON​	ON​	OFF​
console​	?​	OFF​	ON​	OFF​	ON​	ON​	ON​	OFF​

 

[billsimon]

Field	Default​	Information
File Name	​	Name of file, relative to Asterisk log path. Use absolute path for a different location
Debug	ON​	Messages used for debugging. Do not report these as errors unless you have a specific issue that you are attempting to debug. Also note that Debug messages are also very verbose and can and do fill up logfiles (and disk storage quickly.

Debug = ON is a pretty bad idea! Take a look at the information box. Trust me, you do not want debug level logs on all the time.