[asterisk-bugs] [Asterisk 0016382]: SIP OPTIONS qualify message forever

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16382 
====================================================================== 
Reported By:                lftsy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16382
Category:                   Channels/chan_sip/DatabaseSupport
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.27.1 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-12-03 10:04 CST
Last Modified:              2009-12-04 02:13 CST
====================================================================== 
Summary:                    SIP OPTIONS qualify message forever
Description: 
Hello, I have a trouble with different Asterisk versions (1.4.26, 1.4.27,
1.4.27.1). When I use the steps below, Asterisk starts to send SIP OPTIONS
to the previous IP/port used by a SIP realtime peer (that has been pruned)
and will keep trying to send SIP OPTIONS pings forever, event if the peer
is connected with a new IP/port address.

I have just checked with my old Asterisk 1.2.27 with the same sip.conf and
I do not have the problem, the SIP OPTIONS stops once register timer has
expired.

During my experience to reproduce the bug, I have been able to have 10
IP/port currently pinged by the Asterisk server for one single peer.
And the only way to stop it is to restart Asterisk...

Thank you for your attention!
Marc Leurent
====================================================================== 

---------------------------------------------------------------------- 
 (0114719) c0rnoTa (reporter) - 2009-12-04 02:13
 https://issues.asterisk.org/view.php?id=16382#c114719 
---------------------------------------------------------------------- 
I'm experianced this issue too but only with INVITE messages. Two months
ago, i'v had qualify problem with result as "Too many opened files" and
"Couldn't create socket". Qualify=no solved this. But today i'v got another
"Too many opened files". As I think, reason is too many opened channels for
old peer's IP adress. 
"sip show channels" gives me over 500 opened channels with INVITE message
like this:
10.31.100.119    301         433be6354bc  00102/00000  0x0 (nothing)    No
      Init: INVITE
10.31.100.195    404         5143cfaf114  00102/00000  0x0 (nothing)    No
      Init: INVITE
10.31.10.21      400         41745a2b7d3  00102/00000  0x0 (nothing)    No
      Init: INVITE
10.31.100.119    301         134d0b4c659  00102/00000  0x0 (nothing)    No
      Init: INVITE
10.31.100.195    404         41a9bf4670b  00102/00000  0x0 (nothing)    No
      Init: INVITE
10.31.10.21      400         1d70ecc27d0  00102/00000  0x0 (nothing)    No
      Init: INVITE

But for example my peer 400 already registered with new IP:
  * Name       : 400
  Realtime peer: Yes, cached
  Expire       : 2366
  LastMsg      : 0
  Addr->IP     : 10.31.10.26 Port 50462
  Defaddr->IP  : 0.0.0.0 Port 5060
  Def. Username: 400
  SIP Options  : (none)
  Status       : Unmonitored
  Useragent    : eyeBeam release 1102q stamp 51814
  Reg. Contact : sip:400 at 10.31.10.26:50462;rinstance=65ac9666d82b1e98

And 10.31.10.21 is not ping-able. 
Please notice, that all peers are realtime.

Is my problem have relationship for this issue or i should repost it with
new one? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-04 02:13 c0rnoTa        Note Added: 0114719                          
======================================================================