[asterisk-bugs] [Asterisk 0012329]: [patch] improved proxy challenge support by propagating user credentials

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12329 
====================================================================== 
Reported By:                neutrino88
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12329
Category:                   Channels/chan_sip/NewFeature
Reproducibility:            N/A
Severity:                   tweak
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0-beta9 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             03-28-2008 17:17 CDT
Last Modified:              07-01-2008 08:03 CDT
====================================================================== 
Summary:                    [patch] improved proxy challenge support by
propagating user credentials
Description: 
When trying to send a SIP call to an outgoing proxy or SIP server:

Dial( xxx at proxy )

Asterisk may be challenged. In that case:
- it uses realm authentication if defined.
- if a peer definition matches the "proxy", it uses the credential defined
in the peer record.

I added a new case if neither realm auth nor peer are defined. In that
case it tries to answer the proxy challenge using the credential of the
from user.
====================================================================== 

---------------------------------------------------------------------- 
 oej - 07-01-08 08:03  
---------------------------------------------------------------------- 
This violates the peer/user architecture totally (which is already smashed
into pieces). I will also remove the "user" object within a week or so, so
we need to find another way of doing this. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-01-08 08:03  oej            Note Added: 0089475                          
======================================================================