[asterisk-bugs] [Asterisk 0015084]: [patch] Support for event keep-alive for Linksys NAT pinhole

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15084 
====================================================================== 
Reported By:                IgorG
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   15084
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     assigned
Target Version:             1.6.x Version Tracker
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 193757 
Request Review:              
====================================================================== 
Date Submitted:             2009-05-11 22:34 CDT
Last Modified:              2009-09-02 11:17 CDT
====================================================================== 
Summary:                    [patch] Support for event keep-alive for Linksys NAT
pinhole
Description: 
Two years ago in issue https://issues.asterisk.org/view.php?id=9329 support of
this event was requested, used by
Linksys for NAT keepalive. Actually with current implementation there is no
problem with NAT, but tons of "489 Bad event" errors confusing for user and
make them think that NAT issues exists because this event unsupported
====================================================================== 

---------------------------------------------------------------------- 
 (0110046) dvossel (administrator) - 2009-09-02 11:17
 https://issues.asterisk.org/view.php?id=15084#c110046 
---------------------------------------------------------------------- 
I committed the patch into trunk and 1.6.2...  The patch won't apply for
1.4, 1.6.0, and 1.6.1.  It appears handle_request_notify() contains
different logic for those branches, and after reviewing it, I'm not even
sure a patch is required for them.  Have you tested this with any of those
branches to see if the problem exists there as well?  If so, they will need
a separate patch.  Thanks for the contribution! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-02 11:17 dvossel        Note Added: 0110046                          
======================================================================