Recent content by darndt

Got it working. See here: https://forum.flashphoner.com/threads/mcu-client-rtmp-internal-server-error.13971/post-29924

For anyone interested in seeing this work: I was able to get the RTMP publishing working by issuing the POST with the arguments as a raw text JSON payload, like this: { "streamName": "dwaroom", "rtmpUrl": "rtmp://live.volume.com/live-origin/stream-key", "rtmpTransponderFullUrl"...

Does anyone have any experience getting the publish side of this to work using a POST after starting the stream?

I also tried the post sending the parameters in JSON in the payload. But it still fails. Help! { "streamName": "mystream", "rtmpUrl": "rtmp://live.volume.com/live-origin/stream-key", "rtmpTransponderFullUrl": true }

I'm running the MCU client example: https://demo.flashphoner.com:8888/client2/examples/demo/streaming/mcu_client/mcu_client.html Seems to work nicely, but where / how can I see the output mosaic published through RTMP? I do not see any docs explaining where to find this on Flashphone's site...

Got it. I slammed the entire set of examples under our server and linked in a launch page for the ones I want to run. All is good with this now. Thx.

I tried this, and the POST returns a 500 (Internal Server Error). Here is the fully formulated post...

If NOT using AWS EC2... So first I start publishing to your server with this code: constraints.video.type = "screen"; constraints.video.withoutExtension = true; session.createStream({ name: "mystream", display: document.getElementById("screen-sharing"), constraints: constraints...

I am running the simple screen sharing demo described here: https://flashphoner.com/how-to-embed-webrtc-screen-sharing-into-a-web-page-2/ In screen-sharing-min.js I pass an rtmpUrl to the session.CreateStream() function: function startStreaming() { var constraints = { video: {}...

OK. Yes... the demos have to be run within http server.

I am trying to run the screen-sharing demo locally on a Mac. For some reason, when I click the "connect" button, it doesn't do anything. But when running your demo, from your site, it does work. In the browser debugger, I see this: Which is here in screen-sharing.js: Why might this be...