[asterisk-bugs] [Asterisk 0015996]: [patch] change the order for ACF registration for SMDI

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15996 
====================================================================== 
Reported By:                junky
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   15996
Category:                   Resources/res_smdi
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           SVN 
JIRA:                       SWP-1153 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 220792 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-09-30 21:54 CDT
Last Modified:              2010-06-04 16:21 CDT
====================================================================== 
Summary:                    [patch] change the order for ACF registration for
SMDI
Description: 

Right now, we're doing the registration for the ACF, then check the
validity of the SDMI.
This results in confusion for users:

Like:
before the patch:
shooter*CLI> module load res_smdi.so
Unable to load module res_smdi.so
Command 'module load res_smdi.so' failed.
  == Registered custom function 'SMDI_MSG_RETRIEVE'
  == Registered custom function 'SMDI_MSG'
  == Parsing '/etc/asterisk/smdi.conf':   == Found
  == Unregistered custom function SMDI_MSG_RETRIEVE
  == Unregistered custom function SMDI_MSG
[Sep 30 15:44:56] NOTICE[27241]: res_smdi.c:1420 load_module: No SMDI
interfaces are available to listen on, not starting SMDI listener.

Users are wondering: why do we register these 2 functions, then we are
unregister them?

This patch solves that "confusion":
shooter*CLI> module load res_smdi.so
Unable to load module res_smdi.so
Command 'module load res_smdi.so' failed.
  == Parsing '/etc/asterisk/smdi.conf':   == Found
[Sep 30 15:50:56] NOTICE[29186]: res_smdi.c:1418 load_module: No SMDI
interfaces are available to listen on, not starting SMDI listener.

====================================================================== 

---------------------------------------------------------------------- 
 (0122993) svnbot (reporter) - 2010-06-04 16:21
 https://issues.asterisk.org/view.php?id=15996#c122993 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 268147

_U  branches/1.6.2/
U   branches/1.6.2/res/res_smdi.c

------------------------------------------------------------------------
r268147 | russell | 2010-06-04 16:21:10 -0500 (Fri, 04 Jun 2010) | 14
lines

Merged revisions 266735 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/trunk

........
  r266735 | tilghman | 2010-06-01 13:02:24 -0500 (Tue, 01 Jun 2010) | 7
lines
  
  Don't register functions until the last possible point, so they're not
unloaded unnecessarily.
  
  (closes issue https://issues.asterisk.org/view.php?id=15996)
   Reported by: junky
   Patches: 
         sdmi_wait.diff uploaded by junky (license 177)
........

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=268147 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-04 16:21 svnbot         Checkin                                      
2010-06-04 16:21 svnbot         Note Added: 0122993                          
======================================================================