Obtain custom params in RTMP urls using the API

[danrossi]

I have a group call backend that can support signalling RTMP streams to be added to the room. But to do so I need to encode data like title and roomname as the stream name. This makes it hard for policy token generation having to us an encoded stream name. If there is a way to obtain params added to the rtmp urls it might help.

I have to check active streams with

/v1/vhosts/default/apps/app/streams

But this doesn't give me detail about an rtmp stream hence having to encode in the name,

[bchah]

You could try using AdmissionWebhooks which provides the full incoming URL to your own server: https://airensoft.gitbook.io/ovenmediaengine/access-control/admission-webhooks

[danrossi]

webhooks to the same service as the websocket server may work to notify publish has begun. Or is there another webhook for notifying publishing has begun ? So there is no way to get rtmp params using the rest api of the available streams ?

[bchah]

The webhook can be sent anywhere you choose. You're correct that the API does not store the URL parameters, just the names of the active streams themselves. However you could use the webhook to store the parameters in your own DB or memory when the stream starts and reference that value later.

[danrossi]

I'm testing out the webhook to my "rooms" node server. I have to figure out how to replicate app instances like wowza that partition streams into instances on the app. I'm wondering if I can obtain params from the webrtc streams this way so I know which room its from. So I can use a webhook as a publish notification also. Or else I have to include the room name in the stream name which complicates creating the tokens which requires the entire url and stream name.

[bchah]

AdmissionWebhooks let you provide a 'new_url'. So use a unique identifier as a sort of 'connection key' and store your room info against that in your own database, so there is no need to transmit it in the key itself. Then provide the real stream key as the new url and make whatever calls you need based on what's in the database.

[danrossi]

There is no example how to verify X-OME-Signature for the webhook ? I'll figure out something. The webhook is used as a publish notifier which will notify a room map. So the original connection needs to specify the room name to map to. I hope it can be obtain from params in webrtc like it can for RTMP.

[bchah]

It works similarly to SignedPolicy, check out the example code in misc for how that is generated (HMAC-SHA1 the url or payload, then base64 that).

Or you can just bypass use of the signature and only allow requests from the local host assuming your other endpoint is running on the same server.