[asterisk-bugs] [Asterisk 0017304]: [patch] module reload cdr_odbc.so produces an error about not being able to register ODBC method with CDR.

[Asterisk Bug Tracker]

The following issue is now READY FOR TESTING. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17304 
====================================================================== 
Reported By:                jnemeth
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17304
Category:                   CDR/cdr_odbc
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-05-06 22:34 CDT
Last Modified:              2010-05-07 16:50 CDT
====================================================================== 
Summary:                    [patch] module reload cdr_odbc.so produces an error
about not being able to register ODBC method with CDR.
Description: 
If you edit cdr_odbc.conf and do 'module reload cdr_odbc.so' you'll get an
error complaining about not being able to register the ODBC method with the
CDR subsystem.  This is because it is already registered.  Doing a module
unload followed by a module load will work around the issue.  I have used
the viewvc tool to check the latest version of cdr_ocbc.c and the issue is
still there.
====================================================================== 

---------------------------------------------------------------------- 
 (0121601) tilghman (administrator) - 2010-05-07 16:50
 https://issues.asterisk.org/view.php?id=17304#c121601 
---------------------------------------------------------------------- 
Anyway, I believe the better way to solve this is to track the current
state of the registration, and conditionally register or unregister, based
upon the state. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-07 16:50 tilghman       Note Added: 0121601                          
2010-05-07 16:50 tilghman       Status                   feedback => ready for
testing
======================================================================