[asterisk-bugs] [Asterisk 0016054]: Asterisk 1.6.1.6 not closing RTP ports after connection

Asterisk Bug Tracker noreply at bugs.digium.com
Mon Oct 12 12:36:46 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16054 
====================================================================== 
Reported By:                alexrecarey
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16054
Category:                   Core/Channels
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1.6 
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-10-11 18:53 CDT
Last Modified:              2009-10-12 12:36 CDT
====================================================================== 
Summary:                    Asterisk 1.6.1.6 not closing RTP ports after
connection
Description: 
At the start of the day, asterisk is using a couple of ports and
filehandles. After every call, the number of used file handles (lsof)
increases, and the number of open ports (netstat -a) also increases. At the
end of the day, with no calls in the system, after one full day of traffic,
the system shows 13000 open files and 12500 open ports. When asterisk is
restarted (not reloaded, it must be closed and reopened) all of the ports
and file handles are closed. If this is not done every night the system
will run out of ports and stop accepting calls.
====================================================================== 

---------------------------------------------------------------------- 
 (0112214) alexrecarey (reporter) - 2009-10-12 12:36
 https://issues.asterisk.org/view.php?id=16054#c112214 
---------------------------------------------------------------------- 
I am sorry, I don't understand what you mean by SIP timers. 

I have the kernel timer set to 1000Mhz. My sip.conf is as follows:

[general]
context=default    
realm=asterisk
bindport=5060
bindaddr=130.117.110.6
;bindaddr=0.0.0.0
srvlookup=yes
disallow=all                 
allow=g729
allow=gsm
mohinterpret=default
mohsuggest=default
language=es
callevents=no
matchexterniplocally = no
maxexpiry=7250       
defaultexpiry=1200             
amaflags=billing
trustrpid=yes
generaterpid=yes
sendrpid=yes
maxexpirey=7250
defaultexpirey=1200
notifymimetype=text/plain
rtptimeout=60
rtpholdtimeout=300
notifyringing=yes
localnet=130.117.110.0/25
rtcachefriends=yes
rtupdate=yes
allowexternaldomains=yes
progressinband=yes


My rtp.conf

[general]
rtpstart=5000
rtpend=64000


If you point me in the right direction I'll investigate the sip timers
issue. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-12 12:36 alexrecarey    Note Added: 0112214                          
======================================================================




More information about the asterisk-bugs mailing list