[asterisk-bugs] [Asterisk 0013644]: insecure doesn't work

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Oct 15 15:59:02 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13644 
====================================================================== 
Reported By:                pj
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   13644
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 143885 
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-10-07 16:54 CDT
Last Modified:              2008-10-15 15:59 CDT
====================================================================== 
Summary:                    insecure doesn't work
Description: 
I have sip peer (callmanager4), that doesn't support authetication, so I
have insecure=port,invite in sip.conf
When I call to asterisk from callmanager peer, from phone, that has
linenumber same, that exist as sip peer entry on asterisk, asterisk then
try to authenticate callmanager peer and call then fail.
Asterisk 1.6.0 branch (and 1.4 branch) is working fine, 
Asterisk 1.6.1 branch and above (trunk) fail.

====================================================================== 

---------------------------------------------------------------------- 
 (0093766) pj (reporter) - 2008-10-15 15:59
 http://bugs.digium.com/view.php?id=13644#c93766 
---------------------------------------------------------------------- 
I must reopen this issue, I haven't tested change thoroughly and now, I
found that change in commit 148376 causes, that successfully registered
peer isn't matched correctly in asterisk.
It's weird, that issue doesn't appears after peer first registering with
asterisk, but if peer unregisters and that registers again from _different_
udp source port, it causes wrong peer matching in asterisk.
Only way, how to restore correct matching for this peer is restarting
asterisk, it will work again until peer is reregistered from different
port.
Maybe asterisk doesn't free memory structures correctly and trying to
match peer according to firstly used source port?
asterisk databaze is updated correctly (according to 'database show')

sip debug when peer is matched correctly (look at source port 10864):

[Oct 15 22:44:13] Sending to 193.85.164.154 : 10864 (NAT)
[Oct 15 22:44:13] Using INVITE request as basis request -
FO8t2cYYoIdpHRCdB7HbpW6kWQisXp
[Oct 15 22:44:13] Found peer '324' for '324' from 193.85.164.154:10864


when peer is registered from different source port asterisk doesn't match
this peer:

[Oct 15 22:36:05] Sending to 193.85.164.154 : 10846 (NAT)
[Oct 15 22:36:05] Using INVITE request as basis request -
zCVgmV3noIegfOJzUgjAngqhh0r9Wc
[Oct 15 22:36:05] No matching peer for '324' from '193.85.164.154:10846'


  Status       : OK (481 ms)
  Useragent    : Nokia RM-49 3.0633.09.04
  Reg. Contact : sip:324 at 193.85.164.154:10846;transport=UDP
 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-15 15:59 pj             Note Added: 0093766                          
======================================================================




More information about the asterisk-bugs mailing list