BARIX Streaming Client Guia do Utilizador descarregar pdf (Página 5)

service.

1.2.3 Device startup and configuration update

On startup, a device must first find out what its configuration is. To do this, it works its way

through the list of known Configuration Servers defined to the device, pinging each in turn

until it receives a positive response. If the device is unknown to a Configuration Server, the

server returns an 'unrecognised device' message and the device moves to the next entry

in the list.

If no positive response is received from any of the known configuration servers, the device

will pause and then start querying the list again, repeating this behaviour until it gets a

positive response.

By default, the devices use DNS names to address the servers, so it is important either

that the network they are connected to supports DHCP / DNS, or that the device is

configured with the relevant network settings to be able to reach a DNS server.

When a registered device contacts a configuration server, the server responds by sending

the device's current configuration, the device receives this and applies it.

During operation, devices regularly ping their configuration server with a 'keepalive'

message: this information is used to update the device status of the project on the

Reflector web UI.

If a user updates the configuration of a device, the Configuration Server will immediately

send an update to the device concerned, which will apply it.

1.2.4 Device operation

Once a device has started up and successfully received its configuration, it then operates

according to the configuration.

The principle configuration element is whether the device is an Encoder, or a Decoder (this

cannot be auto-detected as several Barix hardwares can operate as both).

Barix Reflector User Guide.doc Page 5 of 22

1 2 3 4 5 6 7 8 9 10 ... 21 22

Sem comentários

BARIX Streaming Client Guia do Utilizador Página 5