| Summary: | ASTERISK-11312: RTCP Read too short | ||
| Reporter: | wlloyd (wlloyd) | Labels: | |
| Date Opened: | 2008-01-27 09:33:55.000-0600 | Date Closed: | 2011-06-07 14:02:54 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/RTP |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Reopen of issue 10441 Since upgrading to 1.4.17 from 1.2 I get this with one of my clients 100% of the time. I have a RTP debug saved of a transaction. Please email me for full log. -bill [Jan 27 10:21:56] DEBUG[7398] rtp.c: Got a FRAME_CONTROL (14) frame on channel S IP/kmtel-084102e8 [Jan 27 10:21:56] VERBOSE[7398] logger.c: -- Packet2Packet bridging SIP/64.1 5.69.133-b49145a0 and SIP/kmtel-084102e8 [Jan 27 10:21:56] DEBUG[7398] rtp.c: Got a FRAME_CONTROL (3) frame on channel SI P/kmtel-084102e8 [Jan 27 10:21:56] VERBOSE[7398] logger.c: -- Packet2Packet bridging SIP/64.1 5.69.133-b49145a0 and SIP/kmtel-084102e8 [Jan 27 10:21:56] DEBUG[7398] rtp.c: Got a FRAME_CONTROL (14) frame on channel S IP/kmtel-084102e8 [Jan 27 10:21:56] VERBOSE[7398] logger.c: -- Packet2Packet bridging SIP/64.1 5.69.133-b49145a0 and SIP/kmtel-084102e8 [Jan 27 10:21:58] WARNING[7398] rtp.c: RTCP Read too short [Jan 27 10:22:01] WARNING[7398] rtp.c: RTCP Read too short [Jan 27 10:22:07] WARNING[7398] rtp.c: RTCP Read too short [Jan 27 10:22:14] WARNING[7398] rtp.c: RTCP Read too short [Jan 27 10:22:17] WARNING[7398] rtp.c: RTCP Read too short [Jan 27 10:22:23] VERBOSE[7398] logger.c: Sent RTP P2P packet to 64.69.34.139:72 08 (type 00, len 000160) [Jan 27 10:22:23] VERBOSE[7398] logger.c: Sent RTP P2P packet to 64.15.69.133:16 122 (type 00, len 000160) lines 61-74 | ||
| Comments: | By: Joshua C. Colp (jcolp) 2008-01-28 06:30:33.000-0600 The RTP log will not help, RTCP is carried on a different port. Is this actually causing an issue, and what is the remote device? By: wlloyd (wlloyd) 2008-01-28 12:49:46.000-0600 I had to send the RTP traffic to an 1.2 Asterisk box and then forward it on from there. Then I have no issues. The client is running voipswitch. Currently it causes issues with voice quality. The audio quality is very poor. When I route through 1.2 instead of 1.4 it cleans up and sounds fine. Also the cli error messages disappear. I can do any traces you would like. tcpdump etc. -bill By: jmls (jmls) 2008-02-17 13:08:24.000-0600 file ? By: Joshua C. Colp (jcolp) 2008-04-21 10:11:44 What hardware is the client using? By: Joshua C. Colp (jcolp) 2008-07-02 21:40:06 Any update here? By: Tilghman Lesher (tilghman) 2008-07-25 18:09:23 Suspended due to lack of response. If you're able to provide the requested information, please reopen this issue. If you need assistance, please contact a bug marshal in #asterisk-bugs on the Freenode IRC network. | ||