Search results

noted...the issue is still not totally resolved; we realized if we triggered the RTMP stream with short stream ID from our platform, it will fail. Is there a limitation of the length of RTMP stream ID we should adhere to?

ignore above, i realized it does not matter of the output of console log in developer tool; in Chrome, though I dont see indication of Webrtc session started, the stream was still successful

when i tried streaming using demo codes ( webrtc-as-rtmp-republishing.js and webrtc-as-rtmp-republishing.html), I could see the stream created successfully (refer to below screen shot); however when i did it from our own streaming dashboard (adopted most of the codes from demo code), the stream...

You may hold on from accessing our server, I think I found the root cause....need more time to resolve it; will ping again if I need help.

I'm seeing this error in browser developer tool

I have tried restarting webcallserver and even reboot the server, but to no avail. You may ssh to my server, 54.255.9.27, as user centos using attached private key (you need to rename the file to .ppk).

also whats the range of UDP port RTMP would use?

also thats the range of UDP port RTMP would use?

Now i can't start any stream any all, is there a limitation on number of sessions I can run with trial license?

I'm seeing this even i did not stop the stream from the web client, which worries me.

Hi, At times, I'm seeing below errors in server log indicating RTMP errors (log attached) when I realized the stream failed; would appreciate if you could suggest way to rectify it.

It works after commenting out options that are not supported in Java 12...thanks!

noted..so if if just want to forward the RTMP stream to FB using ffmpeg, could I just use options - c:v copy and -c:a copy?

I could not start up webcallserver once I upgraded JDK to version 12...;O

Hi, May I know what does the below error mean: 03:05:43,603 ERROR HttpServerHandler - HTTPS-pool-4-thread-22 HTTP error javax.net.ssl.SSLException: not an SSL/TLS record: 0300002f2ae00000000000436f6f6b69653a206d737473686173683d41646d696e697374720d0a0100080003000000 at...

Hi, What are the parameters I should used to ensure all RTMP streams are encoded with H.264 & AAC? Best Rgrds, Jason

noted, it works now....thanks

I have stopped nginx, but now seeing this:

sent

yes i did....many times indeed...;(