[asterisk-bugs] [Asterisk 0014858]: Regular segfault with chan_unistim

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14858 
====================================================================== 
Reported By:                barryf
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14858
Category:                   Channels/chan_unistim
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0.7 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-04-08 07:44 CDT
Last Modified:              2009-04-21 12:30 CDT
====================================================================== 
Summary:                    Regular segfault with chan_unistim
Description: 
Running Asterisk 1.6.0.8 on Ubuntu 8.10 Server. This same crash also
happens on 1.2.26 and 1.4.2x with the chan_unistim drivers. We have approx.
40 unistim handsets, in a callcenter environment. At least once a day,
Asterisk segfaults with the same gdb output.

It appears to happen during attended transfers, using the res_features
atxfer.

gdb output below.
====================================================================== 

---------------------------------------------------------------------- 
 (0103540) tilghman (administrator) - 2009-04-21 12:30
 http://bugs.digium.com/view.php?id=14858#c103540 
---------------------------------------------------------------------- 
chan_unistim is extremely unsupported, mainly because the protocol was
built on reverse-engineering and has no documentation.  We may have
accepted it into the codebase, but it is unlikely to ever be fully
functional. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-21 12:30 tilghman       Note Added: 0103540                          
======================================================================