[asterisk-bugs] [Asterisk 0016183]: [patch] out of dialog SIP_NOTIFY with event='keep-alive'

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Nov 13 15:01:10 CST 2009


The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16183 
====================================================================== 
Reported By:                under
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   16183
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     resolved
Target Version:             1.8
Asterisk Version:           SVN 
JIRA:                       SWP-363 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-11-05 03:36 CST
Last Modified:              2009-11-13 15:01 CST
====================================================================== 
Summary:                    [patch] out of dialog SIP_NOTIFY with
event='keep-alive'
Description: 
Subj. is not handled by *.

[Nov  5 18:44:44] DEBUG[84521] asterisk/channels/chan_sip.c: Invalid SIP
message - rejected , no callid, len 438
[Nov  5 18:44:44] VERBOSE[84521]
/usr/ports/net/smartswitch/work/smartswitch-5.2.6520/sbc/asterisk/main/logger.c:
<--- SIP read from 150.101.182.62:5063 --->
NOTIFY sip:voip002.dc1.syd.au.ponw.net SIP/2.0
Via: SIP/2.0/UDP 192.168.100.65:5063;branch=z9hG4bK-fa2620d9
From: "user126"
<sip:user126 at voip002.dc1.syd.au.ponw.net>;tag=1d99345272944056o3
To: <sip:voip002.dc1.syd.au.ponw.net>
Call-ID: cf1f062-c96c3386 at 192.168.100.65
CSeq: 91 NOTIFY
Max-Forwards: 70
Contact: "user126" <sip:user126 at 192.168.100.65:5063>
Event: keep-alive
User-Agent: Linksys/SPA962-6.1.5(a)
Content-Length: 0


<------------->
[Nov  5 18:44:44] DEBUG[84521] asterisk/channels/chan_sip.c: Header 0:
NOTIFY sip:voip002.dc1.syd.au.ponw.net SIP/2.0 (46)
[Nov  5 18:44:44] DEBUG[84521] asterisk/channels/chan_sip.c: Header 1:
Via: SIP/2.0/UDP 192.168.100.65:5063;branch=z9hG4bK-fa2620d9 (60)
[Nov  5 18:44:44] DEBUG[84521] asterisk/channels/chan_sip.c: Header 2:
From: "user126"
<sip:user126 at voip002.dc1.syd.au.ponw.net>;tag=1d99345272944056o3 (80)
[Nov  5 18:44:44] DEBUG[84521] asterisk/channels/chan_sip.c: Header 3: To:
<sip:voip002.dc1.syd.au.ponw.net> (37)
[Nov  5 18:44:44] DEBUG[84521] asterisk/channels/chan_sip.c: Header 4:
Call-ID: cf1f062-c96c3386 at 192.168.100.65 (40)
[Nov  5 18:44:44] DEBUG[84521] asterisk/channels/chan_sip.c: Header 5:
CSeq: 91 NOTIFY (15)
[Nov  5 18:44:44] DEBUG[84521] asterisk/channels/chan_sip.c: Header 6:
Max-Forwards: 70 (16)
[Nov  5 18:44:44] DEBUG[84521] asterisk/channels/chan_sip.c: Header 7:
Contact: "user126" <sip:user126 at 192.168.100.65:5063> (52)
[Nov  5 18:44:44] DEBUG[84521] asterisk/channels/chan_sip.c: Header 8:
Event: keep-alive (17)
[Nov  5 18:44:44] DEBUG[84521] asterisk/channels/chan_sip.c: Header 9:
User-Agent: Linksys/SPA962-6.1.5(a) (35)
[Nov  5 18:44:44] DEBUG[84521] asterisk/channels/chan_sip.c: Header 10:
Content-Length: 0 (17)
[Nov  5 18:44:44] DEBUG[84521] asterisk/channels/chan_sip.c: Header 11: 
(0)
[Nov  5 18:44:44] VERBOSE[84521]
/usr/ports/net/smartswitch/work/smartswitch-5.2.6520/sbc/asterisk/main/logger.c:
--- (11 headers 0 lines) ---
[Nov  5 18:44:44] DEBUG[84521] asterisk/channels/chan_sip.c: = No match
Their Call ID: 51f5d2c8-2c84056 at 192.168.100.65 Their Tag 7da234725f923eb6o4
Our tag: as2a6b34a7
[Nov  5 18:44:44] DEBUG[84521] asterisk/channels/chan_sip.c: = No match
Their Call ID: b1911f06-4943130 at 192.168.100.65 Their Tag 1d99345272944056o3
Our tag: as03e9ec0a
[Nov  5 18:44:44] VERBOSE[84521]
/usr/ports/net/smartswitch/work/smartswitch-5.2.6520/sbc/asterisk/main/logger.c:
Sending to 192.168.100.65 : 5063 (no NAT)
[Nov  5 18:44:44] VERBOSE[84521]
/usr/ports/net/smartswitch/work/smartswitch-5.2.6520/sbc/asterisk/main/logger.c:
<--- Transmitting (no NAT) to 192.168.100.65:5063 --->
SIP/2.0 489 Bad event
v: SIP/2.0/UDP
192.168.100.65:5063;branch=z9hG4bK-fa2620d9;received=150.101.182.62
f: "user126"
<sip:user126 at voip002.dc1.syd.au.ponw.net>;tag=1d99345272944056o3
t: <sip:voip002.dc1.syd.au.ponw.net>;tag=as5dda1ac1
i: cf1f062-c96c3386 at 192.168.100.65
CSeq: 91 NOTIFY
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
k: replaces
l: 0

But this is essential to some SPA gateways, which blink ON/OFF as if SIP
gateway to which they are connected to reboots.
====================================================================== 

---------------------------------------------------------------------- 
 (0113812) russell (administrator) - 2009-11-13 15:01
 https://issues.asterisk.org/view.php?id=16183#c113812 
---------------------------------------------------------------------- 
Thank you very much for the contribution.

This functionality is actually already present in Asterisk trunk.  Since
this qualifies as a new feature for chan_sip, it was not put into Asterisk
1.4. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-13 15:01 russell        Note Added: 0113812                          
2009-11-13 15:01 russell        Status                   ready for testing =>
resolved
2009-11-13 15:01 russell        Resolution               open => fixed       
2009-11-13 15:01 russell        Assigned To               => russell         
======================================================================




More information about the asterisk-bugs mailing list