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

[Asterisk Bug Tracker]

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:                     assigned
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:              
====================================================================== 
Date Submitted:             2008-10-07 16:54 CDT
Last Modified:              2008-10-29 16:48 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.

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

---------------------------------------------------------------------- 
 (0094381) putnopvut (administrator) - 2008-10-29 16:48
 http://bugs.digium.com/view.php?id=13644#c94381 
---------------------------------------------------------------------- 
It should be easy to test if that commit is what is causing the issue for
you. From your trunk source directory, issue the following command.

#svn diff -c -148376 | patch -p0

That will revert the commit you are talking about and you can see if the
same issue still exists. I have done a quick check, and there are no
conflicts when attempting to execute the above command. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-29 16:48 putnopvut      Note Added: 0094381                          
======================================================================