[Live-devel] Maximum interleaved RTP packet size

[Deanna Earley]

If you're interested, here's a patch that adds custom headers to the RequestRecord class, RTSPClient::sendRequest, and the RTSPClient::sendSetupCommand method.
I've only added it to sendSetupCommand() as that's the one I needed to add it to, but I don't see any reason for the other SsendXXXCommand() methods can't accept the same.
I'll leave it up to you which ones you ultimately add it to, if at all :)

-- 
Deanna Earley | Lead developer | icatchercctv

w: www.icode.co.uk/icatcher | t: 01329 835335 | f: 01329 835338
Registered Office : 71 The Hundred, Romsey, SO51 8BZ. Company Number : 03428325

> -----Original Message-----
> From: live-devel [mailto:live-devel-bounces at ns.live555.com] On Behalf Of
> Deanna Earley
> Sent: 15 April 2015 14:20
> To: 'live-devel at lists.live555.com'
> Subject: Re: [Live-devel] Maximum interleaved RTP packet size
> 
> In testing, the limit seems to be 20000 bytes (which matches
> RTSPClient::responseBufferSize but increasing them both in sync doesn't
> work)
> 
> I'd rather not hard code a header string in the liveMedia code so is there
> any nice mechanism to be able to pass additional headers in the RTSP
> request?
> I can't see one, and if not, would you be open to patches that implement
> this?
> 
> Thanks
> 
> --
> Deanna Earley | Lead developer | icatchercctv
> 
> w: www.icode.co.uk/icatcher | t: 01329 835335 | f: 01329 835338
> Registered Office : 71 The Hundred, Romsey, SO51 8BZ. Company Number :
> 03428325
> 
> > -----Original Message-----
> > From: live-devel [mailto:live-devel-bounces at ns.live555.com] On Behalf Of
> > Deanna Earley
> > Sent: 15 April 2015 11:15
> > To: 'live-devel at lists.live555.com'
> > Subject: [Live-devel] Maximum interleaved RTP packet size
> >
> > Hello Ross.
> >
> > We have an open case with one of our RTSP source vendors where RTP
> streams
> > over interleaved TCP seem to be throttled resulting in dropped frames in
> > situations where the camera increases the frame size.
> > This does not happen with UDP unicast.
> > For reference, here's the video explaining the issue to the vendor:
> >
> https://dl.dropboxusercontent.com/u/2931731/Bugs/Axis/501898/20150325_1011
> > 55.mp4
> >
> > The vendor's response suggests it could be a TCP flow control issue and
> > that we can pass a value to increase the RTP packets:
> > "If using unicast in combination with TCP, it is recommended to increase
> > the size of the RTP packets to 64 000 bytes (from the standard 1500
> > bytes), provided that the client can accept larger packets."
> > Is there a specific upper limit to the packet size that liveMedia's
> > interleaved TCP implementation can handle?
> >
> > I'm aware that UDP is preferred, but we do allow the use of TCP to allow
> > for better firewall traversal.
> > (We are discussing internally changing the default to UDP)
> >
> > Thanks
> >
> > --
> > Deanna Earley | Lead developer | icatchercctv
> >
> > w: www.icode.co.uk/icatcher | t: 01329 835335 | f: 01329 835338
> > Registered Office : 71 The Hundred, Romsey, SO51 8BZ. Company Number :
> > 03428325
> >
> >
> > _______________________________________________
> > live-devel mailing list
> > live-devel at lists.live555.com
> > http://lists.live555.com/mailman/listinfo/live-devel
> 
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live555.com
> http://lists.live555.com/mailman/listinfo/live-devel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: customHeaders.patch
Type: application/octet-stream
Size: 5945 bytes
Desc: customHeaders.patch
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20150415/412d31c7/attachment.obj>