[Live-devel] Live555 RTP/RTCP Proxy
Ivan Roubíček
Ivan.Roubicek at zld.cz
Tue Nov 11 14:22:15 PST 2014
Hello,
thank you for your anwser. I understand that I can specify server ports and I’m already doing that. The problem is with Microsoft Silverlight Elevated Trust. Because this is a web application which will be used by a lots of clients I just have to deal with restrictions I have. Elevated trust is possible but then my application would run out of browser (which is not acceptable for us) or user would have to change reg key (on MS Windows for example) which is also not acceptable for us. I believe I can do RTP/RTCP proxy myself which would forward RTP/RTCP base on session id or something. I just wanted to discuss best possible way to do that with you guys. Because I believe you have a better knowledge about concept and best practices with live555.
Best regards Ivan Roubíček
From: live-devel [mailto:live-devel-bounces at ns.live555.com] On Behalf Of Ross Finlayson
Sent: Tuesday, November 11, 2014 11:14 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Live555 RTP/RTCP Proxy
The problem I have is with RTP/RTCP server ports. I have a silverlight RTSP player which is running without elevated trust (meaning it can only use port range 4502-4534). So without proxiing RTP/RTCP server ports I could only have 15 connections (32 – 1 port for RTSP).
Note that you can specify the initial port number (to be used by RTP and RTCP) as the “initialPortNum” parameter to the “OnDemandServerMediaSubsession” constructor.
But if the number of available port numbers on your system isn’t sufficient, then you should get a better system! Either ‘elevate your trust’ on your system, or use a Unix system (e.g., Linux, FreeBSD, Mac OS X), which doesn’t have such a draconian restriction.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20141111/696676b8/attachment-0001.html>
More information about the live-devel
mailing list