OK, it sounds like you’re basically trying to reproduce most of the
functionality of the existing LIVE555 Proxy Server, which I spent a *lot* of
time developing, so I’m not going to spend any more time helping you
effectively reinvent that.
Also, reviewing your earlier emails, you mentioned that you wanted to pass the
data between your receiving RTSP client and your RTSP server using a
“proprietary network protocol”. 'Proprietary’ things are off-topic for this
(public) mailing list. (However, if your company would like to hire me as a
consultant for your project, then let me know via separate email.)
Personally, I think that your best solution would be to figure out how to use
RTSP/RTP everywhere, rather than trying to use your own protocol in-between
(this protocol would end up having to reproduce much of the functionality of
RTSP/RTP, including signaling, framing, timestamping (and audio/video time
synchronization)).
I.e., rather than trying to do:
RTSP server (media source) -> your-own-RTSP-client -> your-own-protocol
-> your-own-RTSP-server -> RTSP clients
figure out how to do:
RTSP server (media source) -> (unmodified) LIVE555 Proxy Server ->
RTSP/RTP -> (unmodified) LIVE555 Proxy Server -> RTSP clients
or, even better:
RTSP server (media source) -> (unmodified) LIVE555 Proxy Server -> RTSP
clients
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
[email protected]
http://lists.live555.com/mailman/listinfo/live-devel
