[asterisk-bugs] [Asterisk 0014518]: Asterisk stop responding after unsuccesfull registration

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
http://bugs.digium.com/view.php?id=14518 
====================================================================== 
Reported By:                apsaras
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14518
Category:                   Channels/chan_sip/Registration
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.23-rc1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-02-20 08:55 CST
Last Modified:              2009-02-24 13:03 CST
====================================================================== 
Summary:                    Asterisk stop responding after unsuccesfull
registration
Description: 
We have an asterisk box set it up on realtime with Postgresql and ODBC as a
back end. The server is publicly to the internet having a few sip users
(20) registering on it and some iax trunks (5). The problem that appear is
that after a registration of a user with unknown parameters and not always
the same user the asterisk stops responding and keep looping.

-------A normal call just before the problem -----------
[Feb 19 10:20:33] VERBOSE[13333] logger.c:     -- Executing
Dial("IAX2/microbasecc-13020", "SIP/vn/92202625|60|r")
[Feb 19 10:20:33] VERBOSE[13333] logger.c:     -- Called vn/92202625
[Feb 19 10:20:34] VERBOSE[13333] logger.c:     -- SIP/vn-19b38490 is
ringing
[Feb 19 10:20:34] VERBOSE[13333] logger.c:     -- SIP/vn-19b38490 is
making progress passing it to IAX2/mbcc-13020
[Feb 19 10:20:43] VERBOSE[13333] logger.c:     -- SIP/vn-19b38490 answered
IAX2/mbcc-13020
------------------------------
-----And the problem starts here
[Feb 19 10:21:05] VERBOSE[1580] logger.c:     -- Added extension
'8467422068' priority 1 to sipregistrations
[Feb 19 10:21:09] NOTICE[1656] chan_sip.c: Peer '8467422068' is now
UNREACHABLE!  Last qualify: 0
[Feb 19 10:21:13] NOTICE[1656] chan_sip.c: Peer '8467422068' is now
UNREACHABLE!  Last qualify: 0
[Feb 19 10:21:13] VERBOSE[1580] logger.c:     -- Added extension
'8467422068' priority 1 to sipregistrations
[Feb 19 10:21:17] NOTICE[1656] chan_sip.c: Peer '8467422068' is now
UNREACHABLE!  Last qualify: 0
[Feb 19 10:21:21] NOTICE[1656] chan_sip.c: Peer '8467422068' is now
UNREACHABLE!  Last qualify: 0
[Feb 19 10:21:25] NOTICE[1656] chan_sip.c: Peer '8467422068' is now
UNREACHABLE!  Last qualify: 0
[Feb 19 10:21:27] NOTICE[1656] chan_sip.c: Peer '8467422068' is now
UNREACHABLE!  Last qualify: 0
..................

This is keep going for ever and it seems to loop back because each time an
Unreachable status is reported the reports are more offer. For example see
what happen after two minutes

[Feb 19 10:23:10] NOTICE[1656] chan_sip.c: Peer '8467422068' is now
UNREACHABLE!  Last qualify: 0
[Feb 19 10:23:10] NOTICE[1656] chan_sip.c: Peer '8467422068' is now
UNREACHABLE!  Last qualify: 0
[Feb 19 10:23:10] NOTICE[1656] chan_sip.c: Peer '8467422068' is now
UNREACHABLE!  Last qualify: 0
[Feb 19 10:23:10] NOTICE[1656] chan_sip.c: Peer '8467422068' is now 
...............

We have more than 50 status reports for the same issue in a sec.

It seams that for unknown reason the user registeres with our IP? or with
loop back IP ? I can realy tell because the system is not responding.

The system comes back only with restart of the service.
====================================================================== 

---------------------------------------------------------------------- 
 (0100653) file (administrator) - 2009-02-24 13:03
 http://bugs.digium.com/view.php?id=14518#c100653 
---------------------------------------------------------------------- 
Okay if you would like to explore this more we will definitely need to see
a SIP debug to see what the packets are like. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-24 13:03 file           Note Added: 0100653                          
2009-02-24 13:03 file           Status                   new => feedback     
======================================================================