Which configuration in the config.lua do I use for pushing an RTSP stream to EvoStream?
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
OK, thanks Xai. Please close this ticket as I will use the OpenCV/FFMPEG client API on Android and stream RTMP to EMS. I’m now successfully using H.264/AAC HLS to display the stream on web browsers within both the Android/Java app and on iOS and this is looking great. I’ll look again at using RTSP for Android to EMS again later as the OpenCV and FFMPEG APIs have tripled the size of my app and it’s huge, relatively speaking. However, it’s fine for the time being. Thanks for your and Erika’s assistance. I have now purchased the $30/month option for EMS for the time being and will upgrade if any of the apps in which I’m implementing video streaming become popular.
Thanks again!
Kind regards
Bill
Bill