[asterisk-bugs] [Asterisk 0015943]: Registration against a SIP provider fails in 1.6.2.0

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15943 
====================================================================== 
Reported By:                tpsast
Assigned To:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   15943
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Target Version:             1.6.2.0
Asterisk Version:           1.6.2.0-rc2 
JIRA:                        
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-09-22 20:40 CDT
Last Modified:              2009-09-28 11:12 CDT
====================================================================== 
Summary:                    Registration against a SIP provider fails in 1.6.2.0
Description: 
Registration against a SIP provider doesn’t work in 1.6.2.0.

The reply from the registrar:
SIP/2.0 403 Forbidden 
…
WARNING[3584]: chan_sip.c:17273 handle_response_register: Forbidden -
wrong password on authentication for REGISTER …

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

---------------------------------------------------------------------- 
 (0111439) jpeeler (administrator) - 2009-09-28 11:12
 https://issues.asterisk.org/view.php?id=15943#c111439 
---------------------------------------------------------------------- 
tpsast: Glad you found a workaround, but the issue still needs to be
resolved. Can you provide the register line you are using? If you want to
mask it, that's fine. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-28 11:12 jpeeler        Note Added: 0111439                          
======================================================================