You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's impossible to support different passphrase for a srt_server, because passphrase is set on transport or srt_server, so you should use http callback if use one srt_server.
But, if support multitple srt_server, it's possible to support multiple passphrase:
srt_server {
listen10080;
method publish; # The default m is publishpassphrase xxx; # The passphrase for publish
}
srt_server {
listen10081;
method request; # The default m is requestpassphrase yyy; # The passphrase for request
}
The multiple srt_server is useful not only for passphrase, bu it also enable user to support default method by port, for example, 10080 is publish, and 10081 is request, which is essential if device doesn't support SRT URL.
Note that the env config can only be applied to the first srt_server.
The text was updated successfully, but these errors were encountered:
To support multiple passphrase for SRT.
It's impossible to support different passphrase for a srt_server, because passphrase is set on transport or srt_server, so you should use http callback if use one srt_server.
But, if support multitple srt_server, it's possible to support multiple passphrase:
The multiple srt_server is useful not only for passphrase, bu it also enable user to support default method by port, for example, 10080 is publish, and 10081 is request, which is essential if device doesn't support SRT URL.
Note that the env config can only be applied to the first srt_server.
The text was updated successfully, but these errors were encountered: