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

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Sep 23 09:23:33 CDT 2009


The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15943 
====================================================================== 
Reported By:                tpsast
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15943
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
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-23 09:23 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 …

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

---------------------------------------------------------------------- 
 (0111252) lmadsen (administrator) - 2009-09-23 09:23
 https://issues.asterisk.org/view.php?id=15943#c111252 
---------------------------------------------------------------------- 
And this works in other versions of Asterisk? Which?

Is there any way you can provide a trace that isn't quite so heavily
modified? I know you're doing it to protect yourself, but at the same time
it makes it pretty difficult to determine if there is a problem with
Asterisk.

Which provider are you attempting to register to. Is it just a single
provider, or are other providers affected? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-23 09:23 lmadsen        Note Added: 0111252                          
2009-09-23 09:23 lmadsen        Status                   acknowledged =>
feedback
======================================================================




More information about the asterisk-bugs mailing list