Summary:	ASTERISK-00238: WARNING[5126]: File chan_sip.c, Line 1442 (sip_alloc): Unable to create RTP session: Too many open files
Reporter:	skandranon (skandranon)	Labels:
Date Opened:	2003-09-09 14:22:44	Date Closed:	2011-06-07 14:05:05
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	After asterisk is running for several hours to several days, it reports: WARNING[5126]: File rtp.c, Line 708 (ast_rtp_new): Unable to allocate socket: Too many open files WARNING[5126]: File chan_sip.c, Line 1442 (sip_alloc): Unable to create RTP session: Too many open files WARNING[5126]: File rtp.c, Line 708 (ast_rtp_new): Unable to allocate socket: Too many open files WARNING[5126]: File chan_sip.c, Line 1442 (sip_alloc): Unable to create RTP session: Too many open files WARNING[5126]: File chan_sip.c, Line 5188 (sip_send_mwi_to_peer): Unable to build sip pvt data for MWI WARNING[5126]: File rtp.c, Line 708 (ast_rtp_new): Unable to allocate socket: Too many open files WARNING[5126]: File chan_sip.c, Line 1442 (sip_alloc): Unable to create RTP session: Too many open files WARNING[5126]: File chan_sip.c, Line 5188 (sip_send_mwi_to_peer): Unable to build sip pvt data for MWI WARNING[5126]: File rtp.c, Line 708 (ast_rtp_new): Unable to allocate socket: Too many open files WARNING[5126]: File chan_sip.c, Line 1442 (sip_alloc): Unable to create RTP session: Too many open files WARNING[5126]: File chan_sip.c, Line 5188 (sip_send_mwi_to_peer): Unable to build sip pvt data for MWI WARNING[5126]: File rtp.c, Line 708 (ast_rtp_new): Unable to allocate socket: Too many open files WARNING[5126]: File chan_sip.c, Line 1442 (sip_alloc): Unable to create RTP session: Too many open files This is without any music on hold enabled. It nearly always occurs shortly after we lose a network link between a host I have asterisk send registrations to: NOTICE[5126]: File chan_sip.c, Line 2834 (sip_reg_timeout): Registration for '12345@123.123.123.123' timed out, trying again I suspect there is a fd leak in the error case.
Comments:	By: oliver (oliver) 2003-09-09 16:34:05 Seems like it's the same problem as mentioned in tickets "0000188" and "0000055".  You might wish to check those as well.  In short: It indeed seems to be caused by an FD-leak when there's no response to register-requests originated from chan_sip. As far as I understand from speaking to him on IRC, Mark already successfully reproduced this problem.