TranscodeWebhook #1472
Pinned
getroot
announced in
Announcement
Replies: 1 comment 2 replies
-
Was this feature removed? I copied the TranscodeWebhook block into my config and pointed the url to a webserver, but no call is being made when I start a stream via RTMP. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm happy to announce that the TranscodeWebhook feature has been added to OvenMediaEngine. You can test this with master branch or
airensoft/ovenmediaengine:dev
.TranscodeWebhook allows OvenMediaEngine to use OutputProfiles from the Control Server's response instead of the OutputProfiles in the local configuration (Server.xml). OvenMediaEngine requests OutputProfiles from the Control Server when streams are created, enabling the specification of different profiles for each individual stream.
Configuration
Enable (required)
You can enable or disable TranscodeWebhook settings.
ControlServerUrl (required)
It's the URL of the Control Server, and it supports both HTTP and HTTPS.
SecretKey (optional)
This is the Secret Key used to pass authentication for the Control Server. To pass security authentication, an HMAC-SHA1 encrypted value of the HTTP Payload is added to the HTTP Header's X-OME-Signature. This Key is used for generating this value.
Timeout (optional, default: 1500)
This is the Timeout value used when connecting to the Control Server.
UseLocalProfilesOnConnectionFailure(optional, default: true)
This determines whether to use the OutputProfiles from Local settings in case of communication failure with the Control Server. If it's set to "false," a communication failure with the Control Server will result in a failure to create the Output stream.
UseLocalProfilesOnServerDisallow (optional, default: false)
When the Control Server responds with a 200 OK, but "allowed" is set to "false," this policy is followed.
UseLocalProfilesOnErrorResponse (optional, default: false)
When the Control Server responds with error status codes such as 400 Bad Request, 404 Not Found, 500 Internal Error, OvenMediaEngine follows this policy.
Protocol
Request (OME → Control Server)
OvenMediaEngine sends requests to the Control Server in the following format.
Response (Control Server → OME)
The Control Server responds in the following format to specify OutputProfiles for the respective stream.
The "outputProfiles" in the JSON is identical to the configuration in Server.xml, and the format is as follows.
Beta Was this translation helpful? Give feedback.
All reactions