[jitsi-dev] ICE4J truncating received DataPacket Size


#1

With regular DatagramSocket my code relays an image perfectly fine, but
with Ice4J the received packet data length is 1500 instead of the expected
25000.... So it isn't the receive buffer array I am using in my code. It
seems to be primarily ice4j or my setup thereof.

The small amount of image seems correct just truncated, so communication is
working. Currently the connection is all behind a router.

I posted more readable code here:
http://stackoverflow.com/questions/29587593/ice4j-datagrampacket-too-small

Let me know if any more information is necessary.

Thank you.


#2

Found the solution.... Ice4J for some reason manually truncates and limits
data sizes in org.ice4j.stack.Connector. You can see a better description
in the link. Is there a reason for that?

Also why is ice4j still on google code it limits contribution, and there
are like 10 github versions, minor oddity I suppose (especially with other
jets projects on github).

···

On Sun, Apr 12, 2015 at 4:55 AM, Matt J <msj242@gmail.com> wrote:

With regular DatagramSocket my code relays an image perfectly fine, but
with Ice4J the received packet data length is 1500 instead of the expected
25000.... So it isn't the receive buffer array I am using in my code. It
seems to be primarily ice4j or my setup thereof.

The small amount of image seems correct just truncated, so communication
is working. Currently the connection is all behind a router.

I posted more readable code here:
http://stackoverflow.com/questions/29587593/ice4j-datagrampacket-too-small

Let me know if any more information is necessary.

Thank you.


#3

Connector doesn't need a bigger buffer because it only reads STUN messages.

Boris

···

On 14/04/15 01:15, Matt J wrote:

Found the solution.... Ice4J for some reason manually truncates and
limits data sizes in org.ice4j.stack.Connector. You can see a better
description in the link. Is there a reason for that?