Difference between revisions of "Reflector server"
(New page: The Reflector Server component of the Reflector Service receives details of all Reflector projects and devices from the Configuration Server and uses these to service requests from the ind...) |
|||
| Line 1: | Line 1: | ||
The Reflector Server component of the Reflector Service receives details of all Reflector projects and devices from the Configuration Server and uses these to service requests from the individual devices within each project. | The Reflector Server component of the Reflector Service receives details of all Reflector projects and devices from the Configuration Server and uses these to service requests from the individual devices within each project. | ||
Encoders send audio streams to the Reflector Server, identifying the stream as belonging to a specific project, the Reflector Server then forwards the audio to each of the Decoder devices. | Encoders send audio streams to the Reflector Server, identifying the stream as belonging to a specific project, the Reflector Server then forwards the audio to each of the associated Decoder devices. | ||
Decoders call in periodically, a process known as 'keepalives': by sending data OUT through their firewall, this enables the Reflector Server to reply, thus satisfying the firewall that this is legitimate traffic that should be allowed through. | Decoders call in periodically, a process known as 'keepalives': by sending data OUT through their firewall, this enables the Reflector Server to reply, thus satisfying the firewall that this is legitimate traffic that should be allowed through. | ||
Latest revision as of 15:12, 19 November 2010
The Reflector Server component of the Reflector Service receives details of all Reflector projects and devices from the Configuration Server and uses these to service requests from the individual devices within each project.
Encoders send audio streams to the Reflector Server, identifying the stream as belonging to a specific project, the Reflector Server then forwards the audio to each of the associated Decoder devices.
Decoders call in periodically, a process known as 'keepalives': by sending data OUT through their firewall, this enables the Reflector Server to reply, thus satisfying the firewall that this is legitimate traffic that should be allowed through.
As the Reflector and Configuration servers can be on different servers, a failure to connect with one server does not mean that a device is 'broken'. A device that is not in contact with the Reflector Server will either not be sending an audio stream (if it is an Encoder), or receiving one (Decoder). In an STL configuration, these cases have equal significance, but where there are multiple Decoders, failure of the Encoder affects ALL devices, where failure of a Decoder only affects that site.
Back to Reflector
