[asterisk-bugs] [Asterisk 0016643]: Setting "timerb" on chan_sip.conf doesn't work at all, in [general] or peer

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16643 
====================================================================== 
Reported By:                nahuelgreco
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16643
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-01-18 18:45 CST
Last Modified:              2010-01-19 10:56 CST
====================================================================== 
Summary:                    Setting "timerb" on chan_sip.conf doesn't work at
all, in [general] or peer
Description: 
Asterisk 1.6.0.20, 1.6.1.12, 1.6.2.0, trunk rev 241145, all come with an
example of the "timerb" usage as a global parameter in sip.conf.sample, but
setting it doesn't work at all, so his documented usage is misleading.

If you change it in the [general] section, then chan_sip.c will do nothing
with that declaration. His global_timer_b variable is only assigned to
"timert1"*64, and there is no presence of "timerb" in the reload_config()
function for the [general] section.

If you instead set this timer for an specific peer, then is treated in the
build_peer() function, but the treatment seems to be incomplete. There are
two possible outcomings: the timer is not valid and the global one is used,
or the timer has a lower setting that the recommended and a warning is
printed... but there is no other usage of the retrieved "timerb" peer
config value, so is lost and never assigned to any variable.

So, doesn't matter how you use the "timerb" parameter in sip.conf, it has
no effects at all. 

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

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-19 10:56 lmadsen        Description Updated                          
======================================================================