...
REST queries and response statuses
REST query | REST query example | REST response example | Response states | Description | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
/cdn/show_routes |
| 200 – OK 500 – Internal Server Error | Show active CDN routes |
Parameters
Description | Example |
|---|---|
Route identifier | 1-origin2.flashphoner.com-2 |
Stream name in CDN | stream1 |
Removing stopped servers from CDN nodes list
...
If there is a codec used to publish the stream in subscrbers codecs set then this codec will be used to play the stream (regardless of its priority). Otherwise, the subscribers priority codec will be used for playback, and transcoding will occur.
Read and write timeout settings in CDN for RTMP streams delivery
If CDN is used mostly for publishing and playing RTMP streams, and Keep Alive packets is disabled on CDN servers for some reason (for example, publishers and players do not support Keep Alives), it is necessary to setup read and write timeouts to control RTMP connections state. Those settings in CDN have some following issues:
1. Read timeout can be set on Origin server that used to publish streams only, without playing streams directly from the Origin server
| Code Block | ||
|---|---|---|
| ||
keep_alive.algorithm=NONE
rtmp.use_server_socket_timeout=true
rtmp.server_socket_timeout=120 |
2. Write timeout can be used on Edge server only. In this case, it is possible to play CDN streams from Edge server and to publish local streams on it.
| Code Block | ||
|---|---|---|
| ||
keep_alive.algorithm=NONE
rtmp.server_write_socket_timeout=120 |
Quick manual on testing
1. For testing we use:
...