, April 14, 2017 12:08:45 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Testing with WebRTC, getting the following error on
the site.
This sender failed our fraud detection checks and may not be who they
appear to be. Learn about spoofing<http:/
From: live-devel on behalf of Ross
Finlayson
Sent: Thursday, April 13, 2017 3:24:06 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Testing with WebRTC, getting the following error on
the site.
Also:
> I assume the registerStream user password should
Also:
> I assume the registerStream user password should be NULL, even though our
> streams require a user password.
Err, no. If the RTSP stream (the one that you are calling “REGISTER” for)
requires a username+password, then you need to pass those strings as parameters
to your call to “regis
Your problem is that you are trying to REGISTER a stream that the WebRTC server
cannot access.
What you are trying to do will work, ***provided that*** it is the back-end
RTSP server itself - *not* a third-party - that sends the “REGISTER” request,
and that it does so requesting streaming over
Error: Inaccessible or unsupported back-end RTSP stream.
I believe I have implemented the registerStream. I followed the example on the
site.
We have a custom proxy (based on the proxy example). It works well for us, I
added the code to registerStream and also changed to using the
RTSPServ
