[Home]

Summary:ASTERISK-09775: RTCP Read Too Short generate strange DTMF tones on call.
Reporter:Ygor Lemos (ygor)Labels:
Date Opened:2007-08-13 13:24:22Date Closed:2011-06-07 14:03:02
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/RTP
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Randomly Asterisk starts to issue messages like that:

[2007-08-13 15:33:54] WARNING[31849]: rtp.c:887 ast_rtcp_read: RTCP Read too short

and the people hears some DTMF tones on the line.

We have detected that this occurs generally on Linksys PAP2-NA and Linksys PAP2-T when using G729 codec.

Also I got this trouble on some IAX2 gsm trunks.

It appears to be randomly generated and sometimes it floods the CLI with this message. ( generally when somebody inject DTMF tones on the call ).

This issue can be directly linked to the following Asterisk Forum post:
http://forums.digium.com/viewtopic.php?t=13114&highlight=&sid=949335ae5d5eddc10771bea0d7443599

Also from time to time, I get the "RTP Read Too Short" message too.

No jitterbuffers are used on my environment at the moment.
My asterisks are trunked on a voice-only network ( Motorola Canopy ).
There is absolutely no packet losses between the servers.
My environment is mixed, so I have SIP and IAX2 connections coming from several places.
I generally use alaw, g729a and gsm codecs.

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

Asterisk version is 1.4.10.1
Comments:By: Joshua C. Colp (jcolp) 2007-08-14 16:01:59

rtp and rtcp debug is required before this can be looked at. RTCP itself does not carry audio or DTMF either... so I doubt that is the cause.
By: Ygor Lemos (ygor) 2007-08-28 10:28:30

The errors keep going, most notably RTCP Read Too Short, but I also get random RTP Read Too Short Messages.

Currently updated Asterisk to 1.4.11 built on i686 - Core 2 Duo 6400 @ 2.13GHz

gcc version 4.1.3 20070812 (prerelease) (Debian 4.1.2-15)

Running on Debian Lenny (testing) with latest updates.


I think it is something related to Packet Loss on Network.

I think a little more information on the error would be useful, something like the IP Address or peer related to the error so we can trace the network as we have lots of peers on the server.

Something like:


[2007-08-13 15:33:54] WARNING[31849]: rtp.c:887 ast_rtcp_read: RTCP Read too short for 255.255.255.255/24, SIP peer: 10122020


Thanks
By: Ygor Lemos (ygor) 2007-08-28 10:33:16

Is this info useful ?!? (Notice the RTCP Read Too Short on the end!):

   -- Call accepted by 10.0.0.2 (format alaw)
   -- Format for call is alaw
   -- IAX2/GW1A-10 is proceeding passing it to IAX2/16102140-9
* Sent RTCP SR to 200.152.176.73:1232
 Our SSRC: 1234259135
 Sent(NTP): 1188316105.1284825088
 Sent(RTP): 240000
 Sent packets: 1500
 Sent octets: 30000
 Report block:
 Fraction lost: 0
 Cumulative loss: 0
 IA jitter: 0.0017
 Their last SR: 2136254054
 DLSR: 4.8270 (sec)

master*CLI>

Got RTCP from 200.152.176.73:1232
PT: 200(Sender Report)
Reception reports: 1
SSRC of sender: 4210997425
NTP timestamp: 2981721.1717198848
RTP timestamp: 927033888
SPC: 1506I>     SOC: 30110
 Fraction lost: 27
 Packets lost so far: 137
 Highest sequence number: 34730
 Sequence number cycles: 0
 Interarrival jitter: 0
 Last SR(our NTP): 0.0000000000
 DLSR: 0.0000 (sec)
   -- IAX2/GW1A-17 is making progress passing it to SIP/16102136-b3d10458
   -- IAX2/GW1A-10 is ringing
master*CLI> iax2 show pe
peers  peer  
[2007-08-28 12:48:30] WARNING[8255]: rtp.c:887 ast_rtcp_read: RTCP Read too short
   -- Hungup 'IAX2/GW1A-17'
By: Joshua C. Colp (jcolp) 2007-08-28 10:35:57

Nevermind, reread.


By: Zhan Shi (stanshi) 2007-09-14 16:19:18

-- Executing [7804011812@default:1] Set("SIP/192.168.240.12-b6a05958", "temp=") in new stack
   -- Executing [7804011812@default:2] Dial("SIP/192.168.240.12-b6a05958", "SIP/@192.168.240.12|20|Tt") in new stack
   -- Called @192.168.240.12
   -- SIP/192.168.240.12-082091a8 is ringing
   -- SIP/192.168.240.12-082091a8 answered SIP/192.168.240.12-b6a05958
[Sep 14 15:30:40] WARNING[30394]: rtp.c:887 ast_rtcp_read: RTCP Read too short
[Sep 14 15:30:45] WARNING[30394]: rtp.c:887 ast_rtcp_read: RTCP Read too short
[Sep 14 15:30:50] WARNING[30394]: rtp.c:887 ast_rtcp_read: RTCP Read too short
[Sep 14 15:30:55] WARNING[30394]: rtp.c:887 ast_rtcp_read: RTCP Read too short
[Sep 14 15:31:00] WARNING[30394]: rtp.c:887 ast_rtcp_read: RTCP Read too short
[Sep 14 15:31:05] WARNING[30394]: rtp.c:887 ast_rtcp_read: RTCP Read too short
[Sep 14 15:31:10] WARNING[30394]: rtp.c:887 ast_rtcp_read: RTCP Read too short
[Sep 14 15:31:15] WARNING[30394]: rtp.c:887 ast_rtcp_read: RTCP Read too short
[Sep 14 15:31:20] WARNING[30394]: rtp.c:887 ast_rtcp_read: RTCP Read too short
[Sep 14 15:31:25] WARNING[30394]: rtp.c:887 ast_rtcp_read: RTCP Read too short
[Sep 14 15:31:30] WARNING[30394]: rtp.c:887 ast_rtcp_read: RTCP Read too short
[Sep 14 15:31:35] WARNING[30394]: rtp.c:887 ast_rtcp_read: RTCP Read too short
[Sep 14 15:31:40] WARNING[30394]: rtp.c:887 ast_rtcp_read: RTCP Read too short
[Sep 14 15:31:45] WARNING[30394]: rtp.c:887 ast_rtcp_read: RTCP Read too short


It gives tones of the warning, however, looks like I don't have any DTMF?tones problem.
Please help


By: John Covici (covici) 2007-09-29 14:19:31

I was getting this error when I was download an audio stream of 48k (Windows Media) and when I stopped the stream the error went away, so it may indeed have something to do with packet loss.
By: Joshua C. Colp (jcolp) 2007-12-18 10:06:52.000-0600

StanShi: Based on the constant interval of those I would guess the remote device is using it as a keep alive. I have a phone here that does that.

ygor: I can't give you the SIP peer, but I can give you the IP address.

All: The real issue I'm concerned about is the "strange DTMF tones"... does anybody still have those?
By: Joshua C. Colp (jcolp) 2008-01-08 15:52:23.000-0600

Suspended due to lack of feedback. Please reopen if valid, I can certainly try to see what the issue is.