[asterisk-bugs] [Asterisk 0015701]: [patch] Not possible to specify expiry for peer callback

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15701 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15701
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-08-12 04:57 CDT
Last Modified:              2009-09-03 14:12 CDT
====================================================================== 
Summary:                    [patch] Not possible to specify expiry for peer
callback
Description: 
It is possible in sip.conf to specify a callback extension for a peer.
(This automatically causes a registration to be generated.) However it is
not currently possible to control how long the callback extension is active
for before it expires and is refreshed. This is a problem particularly when
working behind a nat firewall because the nat binding tends to expire
before the callback is refreshed causing the callback to fail to work.

I propose the addition of the callbackexpiry parameter to sip.conf to
provide this functionality
====================================================================== 

---------------------------------------------------------------------- 
 (0110168) oej (manager) - 2009-09-03 14:12
 https://issues.asterisk.org/view.php?id=15701#c110168 
---------------------------------------------------------------------- 
I don't want to add anything more related to REGISTER with the silly stupid
name "callback". That is just going to cause a lot of confusion.

Also, we have the "defaultexpiry" today, which sets reg expiry for
outbound for all registrations. We should propably follow that and have
"regexpiry" per device. That follows existing naming for expiration
settings and makes much more sense. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-03 14:12 oej            Note Added: 0110168                          
======================================================================