WebRTCApp stops publishing, cannot play stream

[Eric Wright]

Hello

I am using the [my ip address]:5080/WebRTCApp

 to try as a basis for my own app, it loads up, I am able to push the "start publishing" button and shortly the live stream appears in the server dashboard. When loading the :5080/WebRTCApp/player.html page no stream appears ( stream name is the same in both publish and play).

If I try the play button within the server console in the entry for the live stream it also does not play it.

Further, after 15 seconds the WebRTCApp stops publishing with an error in the js console of "ICE failed, add a STUN server and see about:webrtc for more details"

please help it is so close yet so far away.

Eric Wright

[Selim Emre]

Hi Eric,
Thank you for your interest. Can you please check UDP Ports (5000-65000) is open in Server and Streaming Side ?

Best Regads,

Selim

[Eric Wright]

Hi

I have checked udp ports and the range 5000-65000 is are open in the firewall, also confirmed that some ports are listening with 19720/jsvc.exec which I assume is the media server.

Still I cannot play a WebRTC stream and I can only publish one from the WebRTCApp if I connect directly via ip address rather than the domain name

please can you point me to some way to fix this

Eric

[Oscar Parzon]

Hi all !

A thousand apologies for intruding, but I ask:

Does WebRTC not play only on SSL?

I say: Eric looks for the stream on port 5080. Should not he look at port 5443 with SSL?

example: https: // domain-o-ip: 5443 / WebRTCAppEE / player.html

A thousand apologies if it is out of place.

[Eric Wright]

Hi Oscar

thanks for your reply

Since the original question was posted I have enabled SSL and indeed look for the stream on the ssl port. I can get it playing now but the broadcaster gets disconnected after a few minutes.

Eric

[Selim Emre]

Hi Oscar,

It's about Google Chrome and Security. Google Chrome force the SSL in Websocket Connection. But Mozilla Firefox allows insecure Websocket Connections. You can use in Mozilla Firefox in WebRTC Playing and Publishing. But Google Chrome using clients will get an error in WebRTC playing side

I'm hoping that I was able to answer your queries. If you have any question, please feel free to ask us. Thanks.

Best Regards,

Selim

[Selim Emre]

Hi Eric,

I think your problem is UDP Ports. Are you sure your UDP ports 5000 to 65535 of your server are open ? If you sure, it's maybe specific problem. Please contact selim@antmedia.io for detailed review.

Ref: https://github.com/ant-media/Ant-Media-Server/wiki/WebRTC-stream-stops-after-a-few-seconds

Best Regards,

Selim

[Oscar Parzon]

Hello Selim, thank you very much for teaching us the benefits of security in Chrome!

Regarding another issue: could you leave a comment on the failures in the compression and distribution of the WebRTCAppEE video described here:?
https://groups.google.com/forum/m/?utm_medium=email&utm_source=footer#!topic/ant-media-server/P4jHtltJWDA


thank you very much for your help