Which configuration in the config.lua do I use for pushing an RTSP stream to EvoStream?
BillMalkin asked 8 years ago
Hi
Just a simple question hopefully. I’m attempting to push a stream from an Android app I’m developing to EMS where I want to convert it to RTMP and display the video on a website using FlowPlayer’s JavaScript API. I’m using an API on the Android phone called Libstreaming. This all worked through Wowza and now I’m keen to get it working through EMS. (Admittedly, the code I’m using on the Android phone was developed by a third party as an example of how the Libstreaming API is used and was written specifically to work with Wowza. However, they maintain it “should” also work with other streaming engines.) In config.lua it would appear that I should therefore connect to inboundRTSP, ie — RTSP
{
ip=”0.0.0.0″,
port=5544,
protocol=”inboundRtsp”,
} However, when attempting to get this all working with crtmpserver, I read some documentation that said I should be using inboundLiveFlv, ie — LiveFLV ingest
{
ip=”0.0.0.0″,
port=6666,
protocol=”inboundLiveFlv”,
waitForMetadata=true,
} Could you confirm that I should indeed be using inboundRTSP before proceeding? (I ask because I get an error when trying to connect with either port.) Very much appreciated. Kind regards
Bill
Just a simple question hopefully. I’m attempting to push a stream from an Android app I’m developing to EMS where I want to convert it to RTMP and display the video on a website using FlowPlayer’s JavaScript API. I’m using an API on the Android phone called Libstreaming. This all worked through Wowza and now I’m keen to get it working through EMS. (Admittedly, the code I’m using on the Android phone was developed by a third party as an example of how the Libstreaming API is used and was written specifically to work with Wowza. However, they maintain it “should” also work with other streaming engines.) In config.lua it would appear that I should therefore connect to inboundRTSP, ie — RTSP
{
ip=”0.0.0.0″,
port=5544,
protocol=”inboundRtsp”,
} However, when attempting to get this all working with crtmpserver, I read some documentation that said I should be using inboundLiveFlv, ie — LiveFLV ingest
{
ip=”0.0.0.0″,
port=6666,
protocol=”inboundLiveFlv”,
waitForMetadata=true,
} Could you confirm that I should indeed be using inboundRTSP before proceeding? (I ask because I get an error when trying to connect with either port.) Very much appreciated. Kind regards
Bill
6 Answers
BillMalkin answered 7 years ago
Hi Erika
> So you add this source: “rtsp://139.162.97.151:5544/live” and you gave “myStream2” as the localStreamName.
Yes. Is that the correct way to set it up?
> You used “rtsp://139.162.97.151:5544/live/myStream2” for the playback
No, I haven’t started talking about playback yet. I’m still talking specifically and exclusively about the push-in stream. The Android app pushes the stream into EMS.
Cheers
Bill
Bill
erika Staff answered 7 years ago
Hi Bill,
So you add this source: “rtsp://139.162.97.151:5544/live” and you gave “myStream2” as the localStreamName.
Yes. Is that the correct way to set it up? A: Yes this is correct
You used “rtsp://139.162.97.151:5544/live/myStream2” for the playbackThank you.
No, I haven’t started talking about playback yet. I’m still talking specifically and exclusively about the push-in stream. The Android app pushes the stream into EMS. A: I see, so you will push the stream from your android app to EMS. Maybe this forum post helps.
BillMalkin answered 7 years ago
Hi Erika
Thanks very much for your very quick responses! The post to which you gave me a link says that the Android phone needs to send an RTMP stream to EMS so it seems I can’t send an RTSP stream from my Android app to EMS after all. That’s pretty disappointing news after all the effort we’ve both gone through trying to make this work.
Thanks anyway.
Cheers
Bill
erika Staff answered 7 years ago
Hi Bill,
EMS accepts RTSP.
“In my Android app I’m using rtsp://139.162.97.151:5544/live/myStream2 as my streaming URL. ….”
Please use rtsp://139.162.97.151:5544/myStream2 (remove /live).
Please try also rtmp://139.162.97.151/live/myStream2.
If this doesn’t work, please send us the logs at salesupport@evostream.com
Thank you.
BillMalkin answered 7 years ago
Hi Erika
Just recapping. Once I changed over to my present hosting site I was quickly able to get past the problem with the licence verification and I very soon got an RTMP stream from my Android phone connecting to EMS, and then used FlowPlayer JS to view the stream very nicely on a web page. I was also able to do this using videojs. That was a week or so ago and I haven’t been able to achieve anything else since. I have spent a lot of time trying to do the following with no success:
Bill
- Sending an RTSP stream from my Android phone to EMS. It works well with Wowza but simply will not connect to EMS.
- Viewing streams using the EvoStream players. I can’t get them to work and there are errors in the JS console.
- Sending a stream to Facebook. It all seems to connect but nothing can be seen in Facebook.
- Sending a stream to YouTube. It seems to attempt to connect and then just hangs.
- I haven’t yet been able to view the stream using HTML5 rather than using a JS API that requires Flash.
Bill