[asterisk-bugs] [Asterisk 0017532]: Linksys SPA94x keep-alive reply replies to wrong address

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17532 
====================================================================== 
Reported By:                jlamanna
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17532
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.32 
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-06-18 17:41 CDT
Last Modified:              2010-06-23 12:00 CDT
====================================================================== 
Summary:                    Linksys SPA94x keep-alive reply replies to wrong
address
Description: 
It appears as though the 489 Bad Event response to the NAT keep alive event
responds to the local address, instead of responding to the NATted
address.
This causes Linksys phones to go amber (no registration) after a short
amount of time after placing calls.
Turning the Linksys NAT keep alive off is a workound.

SIP trace:

U external.ip:9375 -> asterisk.ip:5060
  NOTIFY sip:asterisk.ip SIP/2.0..Via: SIP/2.0/UDP
10.10.30.65:9375;branch=z9hG4bK-8ebce8bc..From: "xxx-xxx-xxxx"
<sip:9497197231 at asterisk.ip>;tag=3a6a735864619b8bo0..To:
<sip:asterisk.ip>..Call-ID: 19a0bd7
  c-3cb137b7 at 10.10.30.65..CSeq: 395 NOTIFY..Max-Forwards: 70..Contact:
"xxx-xxx-xxxx" <sip:xxxxxxxxxx at 10.10.30.65:9375>..Event:
keep-alive..User-Agent:
Linksys/SPA942-6.1.3(a)-000e08d87445..Content-Length: 0....             
#
U asterisk.ip:5060 -> 10.10.30.65:9375
  SIP/2.0 489 Bad event..Via: SIP/2.0/UDP
10.10.30.65:9375;branch=z9hG4bK-8ebce8bc;received=external.ip..From:
"xxx-xxx-xxxx" <sip:9497197231 at asterisk.ip>;tag=3a6a735864619b8bo0..To:
<sip:asterisk.ip>;tag=as4a
  4466b0..Call-ID: 19a0bd7c-3cb137b7 at 10.10.30.65..CSeq: 395
NOTIFY..User-Agent: Asterisk PBX..Allow: INVITE, ACK, CANCEL, OPTIONS, BYE,
REFER, SUBSCRIBE, NOTIFY, INFO..Supported: replaces..Content-Length: 0.... 
 


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0015084 [patch] Support for event keep-alive fo...
====================================================================== 

---------------------------------------------------------------------- 
 (0123766) jlamanna (reporter) - 2010-06-23 12:00
 https://issues.asterisk.org/view.php?id=17532#c123766 
---------------------------------------------------------------------- 
I have submitted a patch that fixes this issue and provides PROPER "200 OK"
responses for keep-alive messages that are sent.
This patch is against 1.4.32.
The problem is that NOTIFY messages are not allowed to create a dialog.
That ends up with the current 489 Bad Event being sent back to the WRONG
address when the response is sent, as my SIP trace on this bug shows.

This patch allows NOTIFY message with the "keep-alive" event to create a
SIP dialog, thus following the proper NAT rules and allowing the phone
behind NAT to receive a 200 OK reply to the packet. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-23 12:00 jlamanna       Note Added: 0123766                          
2010-06-23 12:00 jlamanna       Status                   closed => new       
2010-06-23 12:00 jlamanna       Resolution               no change required =>
reopened
======================================================================