[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-27 13:52 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 …

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

---------------------------------------------------------------------- 
 (0111401) ebroad (reporter) - 2009-09-27 13:52
 https://issues.asterisk.org/view.php?id=15943#c111401 
---------------------------------------------------------------------- 
Your welcome. I had a hunch, as a I ran into a similar issue when
troubleshooting something else altogether. JPeerler, I believe trunk works
correctly with both secret or remotesecret, but you might want to double
check that. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-27 13:52 ebroad         Note Added: 0111401                          
======================================================================