Error #2 in asterisk logs after upgrade to 9.1.2-37

Submitted by thirdlane on Sun, 02/10/2019 Permalink

Was this just once or it happens frequently?

Log in to post comments

Submitted by mcampbell@1poi… on Tue, 02/12/2019 Permalink

I see it in the logs 14 times yesterday...

Log in to post comments

Submitted by mcampbell@1poi… on Fri, 02/15/2019 Permalink

Every day this error comes up multiple times & I can't correlate it to any specific event in the logs. Again, we never saw this error -ever- until post-upgrade...

Log in to post comments

Submitted by mcampbell@1poi… on Fri, 03/01/2019 Permalink

Again - this and other related errors *never* surfaced until the latest upgrade to Thirdlane Unified Communications Platform 9.1.2.37

Anyone else seeing it in their logs? Any resolution other than hoping it's not an issue?

Thanks in advance...

Log in to post comments

Submitted by matthewmalk248 on Mon, 03/11/2019 Permalink

I get it just a couple times a day, haven't paid much attention to it.

Log in to post comments

Submitted by eugene.voityuk on Wed, 03/13/2019 Permalink

We are looking into this. I will follow-up results here.

Log in to post comments

Submitted by volodya on Tue, 03/19/2019 Permalink

Hello everyone!

We just prepared new Asterisk package version 13.25.0-4 to fix this problem. Please run following commands to update and start using it:

yum clean all
yum update asterisk13
service asterisk restart

Make sure to do this outside of business hours as this will drop active calls.

Please let us know in case of any issues.

Log in to post comments