The following topics are described:
- RTMP Endpoints
- RTMPS (RTMP over SSL)
- Regenerating the Stream Token
- Configuring RTMP Endpoints in your Encoder
- RTMP URL Structure
- Geographical Considerations - Using Regional RTMP Endpoints
RTMP endpoints are the URLs that should be configured on your encoder for streaming live to Kaltura SaaS.
The endpoint contains the following information:
- Primary RTMP URL (mandatory) - This is the primary stream target URL.
- Backup RTMP URL (optional) - This is the backup stream target URL. If it exists, your encoder will broadcast to both primary and backup endpoints for cases when redundancy is required.
- Stream name - This is the unique stream name that is used to identify your stream. Note that if you are broadcasting multiple bit-rate from your encoder, you will need to define several stream names with different suffixes (for example, myStream_1, myStream_2, etc.)
RTMP endpoint: rtmp://1_gdrt137u.p.kpublish.kaltura.com:1935/kLive/?t=b9106yth4
RTMPS endpoint: rtmps://1_gdrt137u.p.kpublish.kaltura.com:443/kLive/?t=b9106yth4
if you try to broadcast with an incorrect token (or without one), your broadcast will be rejected.
There are 2 ways to configure the RTMP endpoints in your encoder:
Copy and paste the RTMP URLs and stream name from the entry page in the Kaltura Management Console (KMC). Click on the Help icon to open the Broadcasting URLs information.
Kaltura can export the RTMP settings into an Adobe FMLE configuration XML that can be imported to several encoders (such as FMLE and Wirecast). If your encoder can import FMLE XML, click "Export XML for FMLE" and save the file on your computer, then import the file into your encoder.
The RTMP URL structure is:
- entryID - the unique identifier of your live stream in Kaltura. The entryID is auto-generated by Kaltura servers when creating a live entry
- p/b - "p" for primary, "b" for backup stream
- token - an auto generated token which is used to secure your RTMP URL. Streaming will be possible only when the token is correct.
Kaltura Geo-redundant data-centers are located in the US (New York and Palo Alto), In some cases, when broadcasting to Kaltura from outside of the US, there may be bandwidth issues and fluctuation.
To overcome this issue, Kaltura has setup up regional RTMP endpoints that maintain persistent connections to our US data-centers to eliminate most of the bandwidth issues that occur due to geography.
The proxies serve the following regions:
- EMEA (Frankfurt, Germany)
- LATAM (Sao Paolo, Brazil)
- APAC (Singapore)
Each regional proxy is fully redundant (primary/backup).
- Kaltura DC - US (New York) - http://ny-publish-speedtest.kaltura.com
- Kaltura DC - US (Palo Alto) - http://pa-publish-speedtest.kaltura.com
- EMEA (Germany) - http://fr-publish-speedtest.kaltura.com
- LATAM (Brazil) - http://br-publish-speedtest.kaltura.com
- APAC (Singapore) - http://sg-publish-speedtest.kaltura.com