[Home]

Summary:ASTERISK-23600: rtp packet len wrong size
Reporter:jag (jaflong)Labels:
Date Opened:2014-04-08 05:49:14Date Closed:2014-04-08 07:47:38
Priority:MajorRegression?
Status:Closed/CompleteComponents:
Versions:12.0.0-beta2 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I am using Asterisk 12.2.0-rc1, I updated with this patch file srtp_dtls.patch  07/Jan/14 7:38 AM
from bug isssue ASTERISK-22961
https://issues.asterisk.org/jira/browse/ASTERISK-22961?jql=text%20~%20%22dtls%22

Rtp traffic seems to be sent and received, Asterisk debug log shows

Sent RTP packet to      10.1.xxx.xxx:41143 (via ICE) (type 08, seq 021868, ts 221760, len 4294967284)
Got  RTP packet from    10.1.xxx.xxx:41143 (type 08, seq 001383, ts 1917269534, len 000160)
Sent RTP packet to      10.1.xxx.xxx41143 (via ICE) (type 08, seq 021869, ts 221920, len 4294967284)
Got  RTP packet from    10.1.xxx.xxx:41143 (type 08, seq 001384, ts 1917269694, len 000160)
Sent RTP packet to      10.1.xxx.xxx:41143 (via ICE) (type 08, seq 021870, ts 222080, len 4294967284)
Got  RTP packet from    10.1.xxx.xxx:41143 (type 08, seq 001385, ts 1917269854, len 000160)

However the len is reported as "len 4294967284" which seems to be wrong
No audio is heard on the browser.

This is the sent sdp.

=0
o=root 350315728 350315728 IN IP4 10.31.xxx.xxx
s=Asterisk PBX 12.2.0-rc1
c=IN IP4 10.31.xxx.xxx
t=0 0
m=audio 24316 UDP/TLS/RTP/SAVPF 8 0 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=maxptime:150
a=ice-ufrag:1c5c5d52130f06fd70e1e23f0d6323f2
a=ice-pwd:12611b8146599a9019d59b4b649a7970
a=candidate:Ha1f026f 1 UDP 2130706431 10.31.xxx.xxx 24316 typ host
a=candidate:Ha1f026f 2 UDP 2130706430 10.31.xxx.xxx 24317 typ host
a=connection:new
a=setup:active
a=fingerprint:SHA-256 13:BB:CF:88:C4:75:9B:F0:DA:36:0A:6D:5D:37:C9:26:6B:3C:82:3E:F6:92:AE:A7:AE:CF:FF:78:F5:86:D9:E8
a=sendrecv
Comments:By: Matt Jordan (mjordan) 2014-04-08 07:47:38.848-0500

If you can reproduce this issue without the patch in ASTERISK-22961, please let a bug marshal know in #asterisk-bugs and we will reopen this issue.

Otherwise, please comment on ASTERISK-22961 that the patch caused this issue.

Issues created in the issue tracker must be created against a version/revision of unpatched Asterisk. Creating issues with patched versions creates an impossible moving target for bug marshals and developers.