|Summary:||ASTERISK-15287: Asterisk runs out of handles because of stuck SIP dialogs|
|Reporter:||Kirill Katsnelson (kkm)||Labels:|
|Date Opened:||2009-12-07 17:07:23.000-0600||Date Closed:||2009-12-08 09:31:22.000-0600|
|Description:||Asterisk version 18.104.22.168|
A peer sent INVITE packets to our Asterisk box with invalid (in strict sense) SIP URL, containing a space in its username part. Asterisk handled these URL nominally, placed them into a queue, then tried to INVITE an agent member of that queue.
The agent software (based on PJSIP 1.2) rejected the INVITEs without answering (indicated in the log as "malformed header." The dialogs, initiated by Asterisk, however, never went away from the list displayed by "sip show channels". Every new channel was consuming ~2 OS handles. When the number of channels reached about 500, asterisk became unusable.
Next time, when we blocked the peer trunk with 93 dialogs outstanding, they did not go away by themselves for a few days before the Asterisk was restarted.
****** STEPS TO REPRODUCE ******
Unfortunately, a reproduction involves sending an invalid URL in an INVITE packet and having other party ignore the INVITE and drop it. I could not find a software to generate these.
Unfortunately, after the peer fixed their configuration, even I cannot reproduce that anymore.
****** ADDITIONAL INFORMATION ******
|Comments:||By: dant (dant) 2009-12-07 17:52:39.000-0600|
Dupe of ASTERISK-14653 & ASTERISK-14576...
By: Kirill Katsnelson (kkm) 2009-12-07 19:20:50.000-0600
Right, thank you very much dant!
So, what is the state of your patch? Has it made to the branches or not? I see that mmichelson had reservations about it, and never responded to your response to him. Do you consider his reservations valid? I have not read the patch, I am just thinking about applying it.
By: dant (dant) 2009-12-07 19:38:54.000-0600
The patch hasn't as far as I'm aware been applied to any of the branches yet... Issue ASTERISK-14576 has been marked as ready for review by Leif with the comment 'It is marked as Ready for Review, and will be reviewed (and potentially committed) as soon as time allows.' So hopefully when one of the dev's gets time it can be reviewed and committed...