[Home]

Summary:ASTERISK-07333: RTCP storm while trying out-of-the box echo test
Reporter:hristo (hristo)Labels:
Date Opened:2006-07-13 07:47:04Date Closed:2006-07-14 09:24:46
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/RTP
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I have installed fresh trunk version today and used the sample config files that come with the source (make samples). Without changing anything else I have simply tried direct call to the echo test extension by dialing 600@asterisk-server-ip-address from eyebeam softphone (eyeBeam release 3015c stamp 27107)...at that point the server started flooding me with RTCP (not RTP!) packets and I got as much as over 3,000,000(!) packets for about a minute or so. Codec that was set on eyebeam was GSM. Hardly any RTP packet made it thru - all I was getting was RTCP packets.

I had to restart the server, because I've lost network connectivity, because of the RTCP flood. I tried this once again from another PC and got the same results.

I am unwilling to try it again because I have router in between and its CPU hits 100% as soon as I try this (netowork in the office goes down in the meantime).

I will try to isolate the server so I can test further but I wanted to report it first, because it seems like a serious problem.

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

Fedora Core 5: 2.6.17-1.2145_FC5
ztdummy was also compiled (if it makes any difference)
server has no telephony boards
Comments:By: hristo (hristo) 2006-07-13 07:57:42

Just wanted to add that around the test call time I have nothing in the logs except for the following line, which is quite normal:

Jul 13 13:57:45 NOTICE[2117] rtp.c: Comfort noise support incomplete in Asterisk (RFC 3389). Please turn off on client if possible. Client IP: <ip address here>
By: Serge Vecher (serge-v) 2006-07-13 09:05:16

that notice is ok and shouldn't impact anything. Looks like you will have to isolate that server if you want to help diagnose this problem.

1. First, please isolate the server and see if you can reproduce the problem at will with the latest trunk. If specific actions need to be taken, please post the exact steps here.
2. Then, downgrade to trunk r37459 and see if you can still reproduce this. The next commit r37474 was related to RTCP, so I wonder if that revision is the culprit.

thanks.
By: hristo (hristo) 2006-07-13 10:48:04

This was the latest trunk version at the time I reported the problem. I just did svn up now and I can see only some misdn related files were updated. Anyway, I will test with latest trunk tommorrow. I will have the server placed on a dedicated lan by that time. I will also try the other versions you suggest.
By: Jason Parker (jparker) 2006-07-14 09:24:13

This was very likely fixed in revision 37586.  Please test, and reopen this bug if necessary.
By: Jason Parker (jparker) 2006-07-14 09:24:46

This was very likely fixed in revision 37586.  Please test, and reopen this bug if necessary.