![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(227.2, 10%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMA%3C/text%3E%3C/svg%3E)
Azure Media Services
A group of Azure services that includes encoding, format conversion, on-demand streaming, content protection, and live streaming services.
307 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 59%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
I'm not aware of anyone on the team that has tested out the Node Media Client project's RTMP ingest support.
https://github.com/NodeMedia/react-native-nodemediaclient
I assume that they are using some form of RTMP ingest from FFMPEG project? Can you confirm?
You may need to do some more experimentation with that library settings. FFMPEG works fine with our services, so if it is using that library then I dont see why it would not work.
Are you adding any additional /streamname path to the end of the RTMP ingest path (you should be).
We dont test all the RTMP clients out there to validate that they work (too many), but when we get someone to test them out and validate them (either community or ISV) then we add them to our list up here -
https://learn.microsoft.com/en-us/azure/media-services/latest/recommended-on-premises-live-encoders