[asterisk-bugs] [Asterisk 0012668]: [patch] fix module loading of chan_oss when you already got chan_console loaded (channel type conflict)

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12668 
====================================================================== 
Reported By:                caio1982
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12668
Category:                   Channels/chan_oss
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 116795 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-16-2008 13:37 CDT
Last Modified:              05-18-2008 10:25 CDT
====================================================================== 
Summary:                    [patch] fix module loading of chan_oss when you
already got chan_console loaded (channel type conflict)
Description: 
Until now chan_oss didn't handle its own loading very well. As it has the
same channel type 'Console' as chan_console, if you use autoload=yes at
modules.conf and chan_console loads up before chan_oss, the later would
fail miserably and Asterisk wouldn't start up. Hopefully this patch will
fix it by making it act more like chan_console when handling this.
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 05-18-08 10:25  
---------------------------------------------------------------------- 
That's fine, but note that chan_jingle doesn't actually allocate anything
before that point, so when it returns the DECLINE status, it leaves memory
in exactly the same state as it was before.  This is very important. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-18-08 10:25  Corydon76      Note Added: 0086991                          
======================================================================