[Home]

Summary:ASTERISK-15853: Asterisk 1.6.1.18 and 1.6.2.6 RTP BUG
Reporter:Kenneth Van Velthoven (kvveltho)Labels:
Date Opened:2010-03-22 08:11:04Date Closed:2010-03-22 09:13:17
Priority:BlockerRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:When having more load (about 60 CC calls),  the following message start the flood the console:
[Mar 22 11:43:43] ERROR[10983]: rtp.c:2563 ast_rtp_new_with_bindaddr: No RTP ports remaining. Can't setup media stream for this call.
[Mar 22 11:43:43] WARNING[10983]: chan_sip.c:6806 sip_alloc: Unable to create RTP audio session: Address already in use
[Mar 22 11:43:44] ERROR[10983]: rtp.c:2563 ast_rtp_new_with_bindaddr: No RTP ports remaining. Can't setup media stream for this call.
[Mar 22 11:43:44] WARNING[10983]: chan_sip.c:6806 sip_alloc: Unable to create RTP audio session: Address already in use
[Mar 22 11:43:45] ERROR[10983]: rtp.c:2563 ast_rtp_new_with_bindaddr: No RTP ports remaining. Can't setup media stream for this call.
[Mar 22 11:43:45] WARNING[10983]: chan_sip.c:6806 sip_alloc: Unable to create RTP audio session: Address already in use
[Mar 22 11:43:45] ERROR[10983]: rtp.c:2563 ast_rtp_new_with_bindaddr: No RTP ports remaining. Can't setup media stream for this call.
[Mar 22 11:43:45] WARNING[10983]: chan_sip.c:6806 sip_alloc: Unable to create RTP audio session: Address already in use
[Mar 22 11:43:46] ERROR[10983]: rtp.c:2563 ast_rtp_new_with_bindaddr: No RTP ports remaining. Can't setup media stream for this call.
[Mar 22 11:43:46] WARNING[10983]: chan_sip.c:6806 sip_alloc: Unable to create RTP audio session: Address already in use


We have plenty of RTP ports both on asterisk and our router.  See attached rtp.conf


****** ADDITIONAL INFORMATION ******

I cannot reproduce the issue as we reverted back to 1.6.0.26

It it impossible that we are the only ones reporting this issue.

In which version will this be fixed?  I've read about an almost similar issue,  and it will be fixed in 1.6.2.7.  Can you confirm.
Comments:By: Leif Madsen (lmadsen) 2010-03-22 09:13:16

Duplicate.