[asterisk-bugs] [Asterisk 0013705]: Can't use type=friend anymore in sip.conf

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13705 
====================================================================== 
Reported By:                blitzrage
Assigned To:                bweschke
====================================================================== 
Project:                    Asterisk
Issue ID:                   13705
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 149559 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-10-15 10:55 CDT
Last Modified:              2008-10-15 16:42 CDT
====================================================================== 
Summary:                    Can't use type=friend anymore in sip.conf
Description: 
Seems I can't authenticate a user in sip.conf when using type=friend. A
very simple definition in sip.conf:

[200]
type=friend
host=dynamic
context=forTesting

In the sip debug from the CLI I get:

No matching peer for '200' from '192.168.128.129:5060'


But if I change it to type=peer this works. Is this part of the "kill the
user" work? If so, shouldn't type=friend still work for backwards
compatibility?

Does this mean the type=user is also entirely gone? (haven't tested this
part yet)
====================================================================== 

---------------------------------------------------------------------- 
 (0093783) putnopvut (administrator) - 2008-10-15 16:42
 http://bugs.digium.com/view.php?id=13705#c93783 
---------------------------------------------------------------------- 
That message you printed, "No matching peer for '200' from
'192.168.128.129:5060'" is dangerously close to a piece of code I changed
in revision 148376 of trunk.

If you have the opportunity, could you revert the change from revision
148376 and see if the problem persists? You can use the below command to
patch your working copy of trunk.

#svn diff -c -148376 | patch -p0; 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-15 16:42 putnopvut      Note Added: 0093783                          
======================================================================