[asterisk-bugs] [Asterisk 0012542]: REGISTER "deadlock" between SPA's and Asterisk/Non-SPA Interoperability (again)

noreply at bugs.digium.com noreply at bugs.digium.com
Tue Apr 29 07:03:34 CDT 2008


The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=12542 
====================================================================== 
Reported By:                outbackbob
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   12542
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.2.26.1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 suspended
Fixed in Version:           
====================================================================== 
Date Submitted:             04-28-2008 19:22 CDT
Last Modified:              04-29-2008 07:03 CDT
====================================================================== 
Summary:                    REGISTER "deadlock" between SPA's and
Asterisk/Non-SPA Interoperability (again)
Description: 
As discussed here: http://bugs.digium.com/view.php?id=4618

I am currently experiencing exactly the same problem with spa3000 and
spa3102, both with latest firmware.

I did not see a fix for the last issue, so I am reopening in the hope that
someone is able to provide a fix...

This has been working for quite a while and this issue has only started in
the last week or so. I am not sure if it is related to number of sip
clients possibly??? I have < 50 clients connected, so it's not massive.

It appears to be a stale nonce problem... See dip debug attached.

My version of asterisk is 1.2.28


I get the same behaviou on 1.2.15 and I'm pretty sure on 1.4.18 as well.

Thanks,
Leighton.
====================================================================== 

---------------------------------------------------------------------- 
 file - 04-29-08 07:03  
---------------------------------------------------------------------- 
We are no longer accepting 1.2 issues on the bug tracker. I've put this
into the suspended state until you can test with 1.4 and provide debug from
it. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-29-08 07:03  file           Note Added: 0086128                          
======================================================================




More information about the asterisk-bugs mailing list