[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 noreply at bugs.digium.com
Sat May 17 16:31:19 CDT 2008


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-17-2008 16:31 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.
====================================================================== 

---------------------------------------------------------------------- 
 caio1982 - 05-17-08 16:31  
---------------------------------------------------------------------- 
I got confused now Corydon, so just to clarify: the FAILURE status
internally does something else like freeing memory and such, different from
DECLINE? I'm saying that because there are other modules with the same
behavior, but they return FAILURE and not DECLINE as I'd like for chan_oss. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-17-08 16:31  caio1982       Note Added: 0086981                          
======================================================================




More information about the asterisk-bugs mailing list