Summary: | ASTERISK-16364: Asterisk crash if T.38 negotiation timed out | ||
Reporter: | Alekzander (alekz) | Labels: | |
Date Opened: | 2010-07-14 08:14:45 | Date Closed: | 2011-06-07 14:00:28 |
Priority: | Critical | Regression? | No |
Status: | Closed/Complete | Components: | Resources/res_fax |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | We've got Asterisk 1.6.1.20 and FAX For Asterisk Components: Applications: 1.6.1.5_1.2.0 Digium FAX Driver: 1.6.1.5_1.2.0 (optimized for i686_32) Each time foreign SIP-proxy hangs during T.38 negotiation we've got Asterisk crash: NOTICE[5697]: res_fax.c:1083 receivefax_t38_init: Negotiating T.38 for receive on SIP/teleleoffice-000000be -- SIP/dial_out-000000bc answered SIP/vocal-000000bb -- Packet2Packet bridging SIP/vocal-000000bb and SIP/dial_out-000000bc WARNING[5697]: res_fax.c:1103 receivefax_t38_init: channel 'SIP/teleleoffice-000000be' timed-out during the T.38 negotiation. -- Channel 'SIP/teleleoffice-000000be' FAX session '20' started config136*CLI> Disconnected from Asterisk server Executing last minute cleanups Asterisk ending (0). Linux config136 2.6.29-gentoo-r5 #2 SMP Wed Jun 24 16:53:44 MSD 2009 i686 Intel(R) Xeon(TM) CPU 3.00GHz GenuineIntel GNU/Linux | ||
Comments: | By: Leif Madsen (lmadsen) 2010-07-14 10:59:38 Asterisk 1.6.1.x is no longer supported other than for security issues. Please attempt to reproduce with 1.6.2.x and provide a backtrace per the instructions in the doc/backtrace.txt file located within the Asterisk source. --- Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.6.0 and 1.6.1 branches has ended. For continued maintenance support please move to the 1.6.2 branch. More information on this change can be found in the release announcement: http://www.asterisk.org/node/49924 By: Paul Belanger (pabelanger) 2010-07-24 16:39:33 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines |