| Summary: | ASTERISK-18236: Segmentation fault after second chan_h323 unload | ||
| Reporter: | singler (singler) | Labels: | |
| Date Opened: | 2011-08-07 19:29:00 | Date Closed: | 2014-08-12 11:21:04 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_h323 |
| Versions: | SVN 1.8.5.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Debian Squeeze, libopenh323-dev1.18.0.dfs package | Attachments: | ( 0) backtrace.txt ( 1) full ( 2) gdb.txt |
| Description: | Using fresh asterisk install with default config files. After connecting to Asterisk CLI and issuing "module unload chan_h323.so" evryting is fine, "module load chan_h323.so" after that is successfull too, but after that issuing "module unload chan_h323.so" again results in segfault. Segfault does not happen if asterisk -rx"<..>" is used. This affects 1.8.5 release and 1.8 SVN branch | ||
| Comments: | By: singler (singler) 2011-08-07 19:32:29.800-0500 backtrace, asterisk log and gdb log of the segfault By: Gregory Hinton Nietsky (irroot) 2011-09-23 06:41:30.345-0500 This is a known problem and reason i abandoned my work to get chan_h323 to work on h323plus. By: Matt Jordan (mjordan) 2014-08-12 11:20:35.467-0500 Unfortunately, {{chan_h323}} has been unsupported for a long time and was marked deprecated. Due to there being a supported replacement channel driver, {{chan_ooh323}}, {{chan_h323}} was removed from the Asterisk source tree in Asterisk 13: http://lists.digium.com/pipermail/asterisk-dev/2014-June/068363.html As such, this issue will be closed out as "Won't Fix". If you still need H323 support and are using Asterisk, I'd recommend switching to {{chan_ooh323}}, as it has a dedicated module maintainer who can help with patches to that channel driver. | ||