Variations on SRT distribution

External SRT listener

If an external system is able to accept incoming SRT requests (i.e. it has a public IP and port(s) available through the firewall), an external SRT listener is possible and sometimes desirable. SRT listeners have the advantage of being able to serve content to multiple downstream SRT callers without reconfiguration, so this may be a preferable architecture.

External SRT listener source

Starting with the configuration we created when we followed Set up content, sources and destinations for SRT distribution, we will add a second source to the content that represents an SRT listener outside the MK.IO system that will send SRT content to the public cloud to be distributed:

PUT https://api.mk.io/api/projects/myproject/v1/flow/sources/sports1-listener

{
    "metadata": {
        "displayName": "Sports 1 - Listener"
    },
    "spec": {
        "contentName": "sports1",
        "networkName": "internet",
        "transport": {
            "type": "SRTListener",
            "url": "srt://42.23.35.199:5000/passphrase=chooseasecret&pkbkeylen=16",
            "encryptionStandard": "AES128",
            "passPhrase": "chooseasecret"
        }
    }
}

Because this source is added to existing, in-use content, it becomes eligible for use by the flow we created immediately. However, it will not be used by the flow if the flow is already using the 'sports1-primary' source. To force the usage of this new source, delete the 'sports1-primary' source.