How to construct Destination URLs for outputs

To construct a destination URL for an output in Spalk, you need to choose a protocol for the output and format the options for that protocol into a single URL.

Jump to: RTMP | SRT | MediaConnect

RTMP

For RTMP outputs, the required syntax is:

rtmp://[username:password@]server[:port][/app][/streamkey]

The accepted parameters are:

• username: an optional username (mostly for publishing).
• password: an optional password (mostly for publishing).
• server: the address of the RTMP server.
• port: the number of the TCP port to use (by default is 1935).
• app: the name of the application to access. It usually corresponds to the path where the application is installed on the RTMP server (e.g. /ondemand/, /flash/live/, etc.). You can override the value parsed from the URI through the rtmp_app option.
• streamkey: the path or name of the resource to play with reference to the application specified in app, may be prefixed by "mp4:". You can override the value parsed from the URI through the rtmp_playpath option.

For example, to send an RTMP stream to a server at rtmp.example.com with the application /flash and streamkey /live, you can use the following URL:

rtmp://rtmp.example.com/flash/live

SRT

For SRT outputs, the supported syntax is:

srt://hostname:port[?options]

where options contains a list of &-separated options of the form key=val or '-key val' options.

The most common options are:

• streamid: stream identifier.
• latency: timestamp-based packet delivery delay in milliseconds.
• passphrase: passphrase for encryption.
• pbkeylen: public key length in bits. (one of 64, 128 or 256)
• mode: connection mode (caller or listener).

The remaining supported options are listed below. For more information on advanced configuration please see the Haivision SRT Documentation.

• connect_timeout: connection timeout in milliseconds.
• ffs: flight flag size (window size) in bytes.
• inputbw: sender nominal input rate in bytes per second.
• iptos: IP type of service.
• ipttl: IP time to live.
• listen_timeout: socket listen timeout in microseconds.
• maxbw: maximum sending bandwidth in bytes per second.
• mss: maximum segment size in bytes.
• oheadbw: overhead bandwidth in percentage.
• polling_interval: socket polling interval in microseconds.
• pkt_size: packet size in bytes.
• rcvlatency: packet delivery delay at the receiver in microseconds.
• recv_buffer_size: receive buffer size in bytes.
• send_buffer_size: send buffer size in bytes.

For example, to send an SRT stream to a server at srt.example.com on port 5555 with passphrase AnExamplePassphrase77 and a latency of 300 milliseconds, you can use the following URL:

srt://srt.example.com:5555?passphrase=AnExamplePassphrase77&latency=300

MediaConnect

For MediaConnect outputs, you have the option of either creating a single-use entitlement or reusing a persistent entitlement.

Single Use

To create a single-use entitlement, the syntax is:

mediaconnect://entitlement?subscriber_account_id=<subscriber_account_id>&name=<name>&region=<region>&static_encryption_key=<static_encryption_key>

The accepted parameters are:

• subscriber_account_id: the AWS account to entitle to receive media.
• name: an identifier for the entitlement Spalk will issue.
• region: the AWS region in which Spalk should create the sending MediaConnect Flow. Note that this region must be the same as the region of the receiving Flow.
• static_encryption_key (optional): a static key to use to encrypt data in transit. The key must consist of hexadecimal digits (0-9, A-F, a-f) and be 32, 48, or 64 characters in length. Note that you will need to configure the receiving Flow with the same key.

For example, to create a single-use entitlement for the AWS account 111122223333 with the identifier ManchesterCityOutput1 in the us-west-2 region, using the static encryption key abcdef0123456789ABCDEF0123456789, you can use the following URL:

mediaconnect://entitlement?subscriber_account_id=111122223333&name=ManchesterCityOutput1&region=us-west-2&static_encryption_key=abcdef0123456789ABCDEF0123456789

Persistent Entitlement

To reuse a persistent entitlement, the syntax is:

mediaconnect://<entitlement_arn>

where entitlement_arn is the Amazon Resource Name (ARN) of the persistent entitlement.

For example, to reuse the persistent entitlement with the ARN arn:aws:mediaconnect:us-west-2:111122223333:entitlement:12345678-abcd-1234-abcd-1234567890ab, you can use the following URL:

mediaconnect://arn:aws:mediaconnect:us-west-2:111122223333:entitlement:12345678-abcd-1234-abcd-1234567890ab

Once you have constructed the destination URL for your output, enter it into the "Destination URL" field in the outputs tab and click Go Live. This will send the output of your commentary team, mixed and synchronised with the video to your downstream player.

 

How to edit destination URLs while the output is live

 

Click on the edit icon (pen) as seen in the image below 

 

Alter the Destination URL and click Update. Note 

Click Update on the warning modal that is displayed. 

IMPORTANT: updating the target destination will cause us to stop sending to the initial destination so proceed with care.