...
Parameter | Default value | Type | Description |
|---|---|---|---|
cdn_enabled | false | Boolean | Enable/disable CDN |
cdn_ip | Empty | String | Server address in CDN |
cdn_nodes_resolve_ip | false | Boolean | Resolve server names to IP addresses |
cdn_point_of_enryentry | Empty | String | Address of the server, the entry point to CDN for the given server. If the server is Origin, this parameter should not be set to this servers' IP address or hostname |
cdn_port | 8084 | Int | Port number for CDN |
cdn_role | edge | String | Role of the server in CDN: origin - source of streams for other servers in CDN edge - can receive streams from other servers |
...
Obtaining information about the current status of CDN from the WCS command line is performed with these commands:
...
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 state of RTMP connections state. Those settings in CDN have some following issues:
1. Read timeout can be set on Origin server that is used only to publish streams only, without playing streams , which will not be played directly from the Origin server
| Code Block | ||
|---|---|---|
| ||
keep_alive.algorithm=NONE rtmp.use_server_socket_timeout=true rtmp.serverread_socket_timeout=120 |
2. Write timeout can be used set on Edge server only. In this case, it is possible to play CDN streams from Edge server and to publish local streams on it.that is used only to play CDN streams
| Code Block | ||
|---|---|---|
| ||
keep_alive.algorithm=NONE
rtmp.server_write_socket_timeout=120 |
3. Read and write timeout can be used both on Origin and Edge servers
| Code Block | ||
|---|---|---|
| ||
keep_alive.algorithm=NONE
rtmp.server_write_socket_timeout=120 |
Quick manual on testing
...
On the play page of the Edge server playing of the stream also stops and the message "Stopped by publisher stop" displays.
Known limits
1. It is strongly not recommended to publish streams with same name to two Origin servers in the same CDN.
2. A stream published to one of Origin servers should be played on the same Origin server or any Edge server, but should not be played from another Origin server in the same CDN.
Known issues
1. Changing codec settings on the Edge server can lead to increased load on the server as a result of enabled transcoding.
...