[Home]

Summary:ASTERISK-09057: Event: keep-alive header returns a 489 Bad Event response
Reporter:a3ulafia (a3ulafia)Labels:
Date Opened:2007-03-20 15:50:00Date Closed:2007-04-10 09:05:50
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) verbosedebug.txt
Description:A NOTIFY event of keep-alive from a Linksys SPA1001 is returned with a 489 Bad Event by Asterisk. Here's the exchange:

<--- SIP read from <Client-IP>:50204 --->
NOTIFY sip:<Server-IP> SIP/2.0
Via: SIP/2.0/UDP <NAT-Client-IP>:5060;branch=z9hG4bK-395c72fb
From: <sip:111@<Server-IP>>;tag=b400b7953c035897o0
To: <sip:<Server-IP>>
Call-ID: 321de0b5-fd5341f7@192.168.1.47
CSeq: 28 NOTIFY
Max-Forwards: 70
Event: keep-alive
User-Agent: Sipura/SPA1001-2.0.13(SEg)
Content-Length: 0


<------------->
--- (10 headers 0 lines) ---

<--- Transmitting (no NAT) to <Client-IP>:50204 --->
SIP/2.0 489 Bad event
Via: SIP/2.0/UDP <NAT-Client-IP>:5060;branch=z9hG4bK-395c72fb;received=<Client-IP>
From: <sip:111@<Server-IP>>;tag=b400b7953c035897o0
To: <sip:<Server-IP>>;tag=as4238ef70
Call-ID: 321de0b5-fd5341f7@<NAT-Client-IP>
CSeq: 28 NOTIFY
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0

****** ADDITIONAL INFORMATION ******

This is enabled on the SIP UA by checking a box labled "enable NAT keep alive". This is necessary for some of my clients as they have UAs behind NAT with a dynamic WAN IP that changes often. They register to Asterisk on a real IP. Their registrations will time out for hours at a time and the peers will be unreachable despite their network being online and rechable with a new public IP.
Comments:By: Serge Vecher (serge-v) 2007-03-20 16:01:58

Please redo the log with debug turned on as per following:
1) Prepare test environment (reduce the amount of unrelated traffic on the server);
2) Make sure your logger.conf has the following line:
  console => notice,warning,error,debug
3) restart Asterisk with the following command:
  'asterisk -Tvvvvvdddddngc | tee /tmp/verbosedebug.txt'
4) Enable SIP transaction logging with the following CLI commands (1.4/trunk commands in parenthesis):
set debug 4 (core set debug 4)
set verbose 4 (core set verbose 4)
sip debug (sip set debug)
5) Reproduce the problem
6) Trim startup information and attach verbosedebug.txt to the issue.
By: a3ulafia (a3ulafia) 2007-03-20 16:18:54

Uploaded file. thanks for the extra debug infos.
By: Joshua C. Colp (jcolp) 2007-03-20 22:52:58

chan_sip presently does not support NOTIFY packets like this so it would have to be a new feature in trunk only, provided someone would like to do it.
By: Serge Vecher (serge-v) 2007-04-10 09:05:49

well, we can't leave feature patches open on the bug-tracker for more than a week without a patch. If somebody implements this in the future and has a disclaimed patch, please feel free to ask a bug-marshall on #asterisk-bugs to reopen the issue.