[asterisk-bugs] [Asterisk 0009044]: Sipura 2000 cannot authenticate when both sip identities are in use

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=9044 
====================================================================== 
Reported By:                queuetue
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   9044
Category:                   General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.0 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
====================================================================== 
Date Submitted:             02-12-2007 13:30 CST
Last Modified:              10-23-2007 11:15 CDT
====================================================================== 
Summary:                    Sipura 2000 cannot authenticate when both sip
identities are in use
Description: 
When both lines on a SPA2000 are in use, the first line cannot authenticate
- placing calls results in 

WARNING[1103]: chan_sip.c:8023 check_auth: username mismatch, have <306>,
digest has <305>
NOTICE[1103]: chan_sip.c:13200 handle_request_invite: Failed to
authenticate user

305 is the first line, 306 is the second.  When I disable x306, x305 works
fine.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0010344 Dialing out with multiple extensions re...
has duplicate       0010582 Cisco ATA 186 double sip login problem
====================================================================== 

---------------------------------------------------------------------- 
 leonidf - 10-23-07 11:15  
---------------------------------------------------------------------- 
Defining "insecure=port" will fix the problem 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-23-07 11:15  leonidf        Note Added: 0072411                          
======================================================================