-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Each SRS instance is missing a unique identifier for the instance. #1789
Comments
I think this is feasible, right?
}
|
I have added it myself, compiled successfully, and the result is as follows: The code is as follows:
} The official can consider making this more systematic.
|
This is a reasonable demand, see if any friends are willing to implement it.
|
UUID has already been supported here.
|
You need to have an instance identifier for SRS.
Can it be added? It can be passed as a parameter during startup or written in the configuration file.
Currently, the SRS instance only has a device_id at the heartbeat interface, which can identify the requesting SRS instance.
However, various structures in http_hook, including gb28181's webapi, do not have a device_id field. This makes SRS instance management difficult, and identifying them solely based on IP address is not foolproof.
Can the official team add an instance identifier for each SRS instance, which can be specified through the configuration file or startup parameters?
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: