17:15
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Live555 support for RTSP over TLS
> The use case shown on your website here http://webrtc.live555.com/ is exactly
> what I need. But I would prefer to use Node.js as a web server. Is the source
> co
> The use case shown on your website here http://webrtc.live555.com/ is exactly
> what I need. But I would prefer to use Node.js as a web server. Is the source
> code for the LIVE555 WebRTC Proxy Server in the diagram available?
The LIVE555 WebRTC support is undergoing development and testing.
Sent: Thursday 6th October 2016 21:37
To: live555 Streaming Media - development & use
Subject: Re: [Live-devel] Live555 support for RTSP over TLS
> It sounds like Gaurav wants to use Live555 w/ with a TLS socket for encrypted
> media transmission over a network.
>
> I could b
> It sounds like Gaurav wants to use Live555 w/ with a TLS socket for encrypted
> media transmission over a network.
>
> I could be incorrect, but since I have not seen a network abstraction in
> place in the library, this would require either a fork of the library or some
> nasty trickery to l
Sorry to interject in you guys’ conversation, but I think there’s a bit of
confusion (maybe by me even).
It sounds like Gaurav wants to use Live555 w/ with a TLS socket for encrypted
media transmission over a network.
I could be incorrect, but since I have not seen a network abstraction in pla
> As per your suggestion, in RTSPServer class, I need to pass the TLS socket
> number to RTSPServer constructor.
> I am using OpenSSL for creating TLS socket. When I create TLS socket, it
> returns SSL type object. How can I pass that SSL type object to RTSPServer
> constructor?
Get the (TLS) s
Hi Ross,
As per your suggestion, in RTSPServer class, I need to pass the TLS socket
number to RTSPServer constructor.
I am using OpenSSL for creating TLS socket. When I create TLS socket, it
returns SSL type object. How can I pass that SSL type object to RTSPServer
constructor?
I have attached sam
> Is there any change in RTSP url when we stream RTSP over TLS ?
As I noted before, you can do this between an existing LIVE555 RTSP client and
an existing LIVE555 RTSP server - with no change to the existing LIVE555 code.
If you do things this way, then the answer is no - there's no change in
Is there any change in RTSP url when we stream RTSP over TLS ?
Regards,
Gaurav Badhan
>
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
On 06/24/2014 05:41 PM, Ross Finlayson wrote:
>> Do you intend to supply this feature any time soon ?
> If you already have a (TCP) TLS socket set up between your client and
> server, then you can use it now, using existing code.
>
> In "RTSPClient::createNew()", note the (optional) "socketNumToSe
> Do you intend to supply this feature any time soon ?
If you already have a (TCP) TLS socket set up between your client and server,
then you can use it now, using existing code.
In "RTSPClient::createNew()", note the (optional) "socketNumToServer"
parameter. You can set this to specify the (TL
At the to do list is task:
"Add support for SRTP ('secure' RTP), and perhaps also RTSP-over-TLS."
Do you intend to supply this feature any time soon ?
Regards,
G Badhan
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/ma
12 matches
Mail list logo
