Summary:	ASTERISK-01452: SIP registration to down machine causes Asterisk to open to many files
Reporter:	vanhorn (vanhorn)	Labels:
Date Opened:	2004-04-22 13:37:39	Date Closed:	2011-06-07 14:10:26
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I have two machines runing Asterisk (in different cities). I'm having problems with one dropping calls using an ADTRAN 600 (I figure it's still my fault). So I take it down for periods of time. Let's call machine "A" is my stable machine. Machine "B" is the machine that I take down for periods of time. Machine "A" registers itself with Machine "B". The link works fine. When I stop Asterisk on Machine "B" for a long period of time (3hrs), I can not get into Asterisk on machine "A" (broken pipe). In the log message file of machine "A" I see: File chan_sip.c, Line 1442 (sip_alloc): Unable to create RTP session: Too many open files The error is there for other files to. many many times! What I do to be normal again is to "kill" the asterisk process, then restart it. any ideas?
Comments:	By: Olle Johansson (oej) 2004-04-22 13:52:55 Please tell us more. Which version of asterisk? * Stable release * CVS stable * CVS head If cvs - date? OS Platform? By: vanhorn (vanhorn) 2004-04-22 14:05:34 Machine A: Asterisk 0.5.0 built ... on a i686 running Linux On Red Hat Linux release 9 (Shrike) Machine B: Asterisk 0.7.2 built ... on a i686 running Linux On Red Hat Linux release 9 (Shrike) By: Olle Johansson (oej) 2004-04-22 14:13:38 There's been quite a lot of changes in the way we handle registrations and SIP re-transmissions lately. Please test CVS head and see if you still have the same problem. 0.5.0 definitely have a lot of problems in the way SIP packets are handled. By: Brian West (bkw918) 2004-04-22 14:20:11 Try 0.9.0 :) By: Brian West (bkw918) 2004-04-22 14:21:32 Down graded to minor pending info after update. By: James Golovich (jamesgolovich) 2004-04-22 16:15:04 I'm not able to reproduce this with CVS Head. I've tested this with a few different registrations happening at the same time. 1 registration that always works 1 registration to a host that is up but not listening on the sip port 1 registration to a host that is not up (unpingable) 1 registration to a host that I randomly filter/unfilter (to reproduce the reported problem) Watching the number of fd's in use (as reported by proc) it always falls back to the normal amount. I suspect when he sees this problem there will also be a bunch of calls listed under 'sip show channels', also it would be very useful to see the output of 'sip show channel <one of the bad channels>' By: vanhorn (vanhorn) 2004-04-23 08:20:55 Loaded 0.9.0 and did the same test, and all works fine. Thanks for the input, case closed. By: Olle Johansson (oej) 2004-04-23 08:23:27 Already fixed.