[asterisk-bugs] [Asterisk 0014366]: [patch] Registration expiry not compatible with some ITSP

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14366 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                mnicholson
====================================================================== 
Project:                    Asterisk
Issue ID:                   14366
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 172234 
Request Review:              
====================================================================== 
Date Submitted:             2009-01-29 11:49 CST
Last Modified:              2009-08-07 05:09 CDT
====================================================================== 
Summary:                    [patch] Registration expiry not compatible with some
ITSP
Description: 
The configured registration expiry value is overwritten by the initial
expiry value from UAS. Subsequent registrations use the new value. This
prevents the UAS from changing its registration expiry value.

Some ITSP use changing registration periods to discover the NAT binding
period at the UAC. Their UAS will set it initially very low and keep
increasing it until they see that the src port number of the registration
has changed. This indicates the nat binding period. The ITSP will then use
an expiry period a little less than this so that the UAC is reregistering
at the minimum required to keep alive the nat binding. However the UAS will
never increase the expiry beyond that requested by the UAC. If the UAC uses
the initial UAS expiry instead of the configured value then the
registration expiry gets stuck at a ludicrously short period.

Issue 14185 contained a patch chan_sip.c-expiryrequest6.patch that dealt
with this in addition to getting the expiry parameter parsed but the
revision r172234 does not implement all of the patch
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0014185 [patch] Setting registration expiry in ...
====================================================================== 

---------------------------------------------------------------------- 
 (0108757) Nick_Lewis (reporter) - 2009-08-07 05:09
 https://issues.asterisk.org/view.php?id=14366#c108757 
---------------------------------------------------------------------- 
We are using a different internet telephony service provider now so it is
not easy for me to test it. 

With your asterisk plus openser server setup would it be possible to
change the min_expiry value on the openser and see what results in the sip
packet capture? (The asterisk registration string would need to be set to a
shorter expiry that min_expiry on the openser.)

The problem (ignoring any authentication) will look like this:

asterisk <-> openser
-> REGISTER
<- 423
-> REGISTER
<- 200
(later)
-> REGISTER
<- 200

With a fix it will look like this:

asterisk <-> openser
-> REGISTER
<- 423
-> REGISTER
<- 200
(later)
-> REGISTER
<- 423
-> REGISTER
<- 200 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-07 05:09 Nick_Lewis     Note Added: 0108757                          
======================================================================