RTSP camera auto start not working after server restart

[yashtandon113]

Multiple RTSP cameras are broadcasting on my server, but when I restart the server, the streams do not automatically restart. I had to manually start the streams. Is there a way to fix this issue?

[asharamseervi]

In AMS v2.5.3 and later, the stream auto-fetcher is disabled by default so streams do not start themselves after a server restart. Change the following flag to true in the Advance application settings so that streams start fetching automatically.

"startStreamFetcherAutomatically": true,

The streams should now begin to function automatically.

[klasadoroty]

Hi. I'm not proficient in this... but a question like this: does it matter which line we put the entry in?
Where exactly to put it?
Thank you in advance.

[yashtandon113]

@klasadoroty
You can put the property/settings in any line under /usr/local/antmedia/webapps/app-name/WEB-INF/red5-web.properties.

[klasadoroty]

Thank you for your reply. It does work.

But, how to secure the publisher?
Publisher IP Filter - this does not seem to work.
How to do it properly?
It should work with Community Edition?
Can you give in a practical, simple way: how to secure the publisher?
Currently, anyone will connect to AMS, without problems.

[yashtandon113]

@klasadoroty
Check out https://antmedia.io/docs/guides/developer-sdk-and-api/rest-api-guide/stream-security/ for more information about Stream Security.

The Stream Security feature is only available in AMS Enterprise Edition. Ant Media Server is available for a five-day free trial on the AWS marketplace. Check out https://www.youtube.com/watch?v=EH6v-yUyzjU for more information.

You can also get a 14-day self hosted trial license from https://antmedia.io/free-trial/.

[klasadoroty]

Thanks.
Hash-Based Token - is only available in AMS Enterprise Edition?
Publisher IP Filter - is only available in AMS Enterprise Edition?
... no security in the non-commercial version?

[yashtandon113]

@klasadoroty
Yes, it is possible that the Community Edition will not meet your needs, in which case you might consider the Enterprise Edition.

There are further methods for restricting traffic on your server firewall. For example, if you're intending to use RTMP to publish streams, only enable TCP Port 1935 for a certain publisher's public IP address and block it for everyone else.

[klasadoroty]

I did. It's Ok.
But I still find an approach like yours not very logical.
Thank You.
Best Regards

[mekya]

Hi @klasadoroty,
I appreciate your involvement into this conversation.

Just let me give some comments and try to make you happy.

Our idea is that if anyone want to have secure streaming then it's something premium and it requires enterprise edition.
For community edition, as you mention, yes it's like a toy for testing and doing some hobby projects.

Lastly, if you need enterprise edition and you're from a church/education institute that you don't have budget for this, let us know.
We can help you ;)

This is related to one of the item in the manifesto

Always seek win-win relationships. If a user can’t afford a license, let’s find alternative win-win solutions.

https://antmedia.io/about-us/

Cheers

[klasadoroty]

Hi, Thank you for the information.
Community edition is a fully working server, that's my understanding.
There is only no premium feature.
In my opinion it works very well.
We just don't know how it will perform with a larger application - 1000 - 4000 recipients.
But we will test that too.
At the moment we are very satisfied.
..And we have a comparison with others.... e.g. wowza.
Best Regards

[mekya]

Thank you for your response @klasadoroty

It's our pleasure to help you.

Why don't we have some coffee together as mentioned in the about us?
https://antmedia.io/about-us/

Cheers