[asterisk-bugs] [Asterisk 0014185]: [patch] Setting registration expiry in registration string does not work

[Asterisk Bug Tracker]

The following issue is now READY FOR TESTING. 
====================================================================== 
http://bugs.digium.com/view.php?id=14185 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   14185
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.6.0 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-07 05:09 CST
Last Modified:              2009-01-12 09:49 CST
====================================================================== 
Summary:                    [patch] Setting registration expiry in registration
string does not work
Description: 
In some applications it is necessary for an asterisk pbx to have very short
registrations with a voip trunk provider if for example the asterisk pbx is
behind a nat firewall and the provider does not provide other udp binding
keep alive mechanisms.

According to sip.conf the format for the registration string is
[transport://]user[:secret[:authuser]]@host[:port][/contact][~expiry]
so that it should be possible to set a shorter registration by appending a
~ and an expiry value e.g. http://bugs.digium.com/view.php?id=22#c60 for a one
minute registration

However the chan_sip.c code does not seem to make use of the [~expiry]
portion so the default expiry value is always used for all registration
strings.


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

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-12 09:49 blitzrage      Status                   confirmed => ready for
testing
======================================================================