I had an issue today where receive_fax caused an asterisk switch to crash. The switch is 1.8.2.3 version. The call was coming from a fax machine. The call started receive_fax answered and then asterisk stopped responding. I was able to log into asterisk but it would not do a core restart now nor would it take any calls or show an peer registrations. I had to kill the asterisk process and restart it. As best we can tell there was no attempt by the sender to intentionally send any malformed packets that should have caused this. I see there is a security patch 1.8.2.4 that lists some RTP security issues. is it possible that this fix may address what I ran into as well? Thanks zktech -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110224/237b007e/attachment.htm>
On Thu, Feb 24, 2011 at 6:05 PM, Bryant Zimmerman <BryantZ at zktech.com> wrote:> I had an issue today where receive_fax caused an asterisk switch to crash. > The switch is 1.8.2.3 version. The call was coming from a fax machine. The > call started receive_fax answered and then asterisk stopped responding. I > was able to log into asterisk but it would not do a core restart now nor > would it take any calls or show an peer registrations. > I had to kill the asterisk process and restart it.? As best we can tell > there was no attempt by the sender to intentionally send any malformed > packets that should have caused this. I see there is a security patch > 1.8.2.4 that lists some RTP security issues. is it possible that this fix > may address what I ran into as well? > > Thanks > > zktechThere are many updates in 1.8.2.4 that may fix your issue. If you are running any version of 1.8 it should be a quick update. ~~~ Andrew "lathama" Latham lathama at gmail.com ~~~
On Fri, Feb 25, 2011 at 9:49 AM, Leif Madsen <leif.madsen at asteriskdocs.org> wrote:> On 11-02-24 08:56 PM, Andrew Latham wrote: >> >> And I go back to triple check and compare revision numbers... ?You are >> 100% correct, the revision numbers in our local repository are wrong, >> someone pushed the 1.8.3 RC3 into our local 1.8.2 branch. ?I apologize >> and will work to better control my trust of other engineers as this is >> twice in one week I have looked like an ass. ?International bandwidth >> limits change how you work and as a business force the mirroring of as >> many sources as possible. > > No worries, you had my heart going there pretty good for a moment! > > Leif!Me, too, when our repository did not match up, my heart skipped a beat. Time for fresh checkouts. ~~~ Andrew "lathama" Latham lathama at gmail.com ~~~