About: Ingest credentials for external devices follow the rules and mechanisms described in this article. Ingest URLs can be manually adjusted to not use the default latency-based ingest points.
Not sure how to start?
→ Learn how to create external devices.
Latency-based ingest points
The following ingest points are looking for the nearest data center location based on EDNS0.
See also extension mechanism for DNS, RFC2671, and RFC7871.
The default ingest point for everything that does not specify a data center or a cloud provider is:
rtmp://ingest.live/ingest/{$stream_key}
Other latency based ingest points are:
rtmp://latency.aws.ingest.live/ingest/{$stream_key}
The {$stream_key} or "stream name" is the six character (A-Z, 0-9) unique identifier provided by the external devices.
Direct ingest points
Direct ingest points follow the directive:
{$datacenter}.{$cloud_provider}.ingest.live
For example:
rtmp://eu-west-3.aws.ingest.live/ingest/{$stream_key}
Hint: Direct ingest points do not failover. If a data center goes dark, you will not be redirected to a different, healthy location.
AWS
- latency.aws.ingest.live (global)
- ap-northeast-1.aws.ingest.live (Asia Pacific, Tokyo)
- ap-southeast-1.aws.ingest.live (Asia Pacific, Singapore)
- ap-southeast-2.aws.ingest.live (Asia Pacific, Sydney)
- ca-central-1.aws.ingest.live (Canada, Central)
- eu-central-1.aws.ingest.live (EU, Frankfurt)
- eu-west-2.aws.ingest.live (EU, London)
- eu-west-3.aws.ingest.live (EU, Paris)
- sa-east-1.aws.ingest.live (South America, São Paulo)
- us-east-1.aws.ingest.live (US East, N. Virginia)
- us-east-2.aws.ingest.live (US East, Ohio)
- us-west-1.aws.ingest.live (US West, N. California)
- us-west-2.aws.ingest.live (US West, Oregon)
Azure
Azure ingest for external devices is available upon request. Contact support or your contact person at LTN Global.
Google Cloud (GCP)
GCP ingest for external devices is available upon request. Contact support or your contact person at LTN Global.