[asterisk-bugs] [Asterisk 0017622]: [patch] STUN support not reliable

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Aug 4 11:16:30 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17622 
====================================================================== 
Reported By:                philipp2
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   17622
Category:                   Channels/chan_sip/General
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     assigned
Target Version:             1.8.0
Asterisk Version:           1.6.0 - SECURITY ONLY! Test 1.6.2 
JIRA:                       SWP-1842 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-07-11 22:22 CDT
Last Modified:              2010-08-04 11:16 CDT
====================================================================== 
Summary:                    [patch] STUN support not reliable
Description: 
Up front: This is not my report, but I wanted to make sure this does get
recorded. Having searched the bug tracker I found no entries on STUN, so I
assume that the problem is also to be found in trunk.

Taken from:
http://forums.digium.com/viewtopic.php?t=74252

thor: "more sniffing on the network explains why this problem happens.
when sending stun request asterisk uses the sip socket as the source and
the first packet after that, arriving on the sip socket, is assumed to be
the stun reply. If it happens to be another sip message then asterisk
throws an error because it does not verify if the packet is actually a stun
reply and blindly tries to parse it. this makes stun unusable with
asterisk."

Could be related to https://issues.asterisk.org/view.php?id=16323
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0016323 [patch] confusing description in config...
====================================================================== 

---------------------------------------------------------------------- 
 (0125532) dvossel (administrator) - 2010-08-04 11:16
 https://issues.asterisk.org/view.php?id=17622#c125532 
---------------------------------------------------------------------- 
After reviewing further feedback I've discovered that just about every part
of our current sip STUN implementation is done wrong architecturally.  This
all needs to just be re-written.  I'll see what I can do. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-08-04 11:16 dvossel        Note Added: 0125532                          
======================================================================




More information about the asterisk-bugs mailing list