Set up infrastructure for site-to-site contribution

WAN network

Create a 'wan' network that represents a private WAN that will connect 'stadium' and 'studio' sites:

PUT https://api.mk.io/api/projects/myproject>/v1/infra/networks/wan

{
    "metadata": {
        "displayName": "WAN"
    },
    "spec": {}
}

Stadium site

Create a 'stadium' site to represent a sports stadium where camera content will be sent from, adding a route to the 'wan' network:

PUT https://api.mk.io/api/projects/myproject/v1/infra/sites/stadium

{
    "metadata": {
        "displayName": "Stadium"
    },
    "spec": {
        "routes": [
            { "networkName": "wan" }
        ]
    }
}

📘

Default transports

We can add defaultTransport settings to the route on which the content will enter the network to give more specific instructions on how to transport inter-flow content across the network. However, we will stick with the default behavior, which is an SRT listener sending the content to an SRT caller. To learn more, read Default transports .

Studio site

Create a 'studio' site to represent a production studio which will receive and decode the camera content ready for mixing, again, adding a route to the 'wan' network:

PUT https://api.mk.io/api/projects/myproject>/v1/infra/sites/studio

{
    "metadata": {
        "displayName": "Studio"
    },
    "spec": {
        "routes": [
            { "networkName": "wan" }
        ]
    }
}