Difference between revisions of "Reflector"

 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Image:Reflector_P2_system_diagram.png|400px|thumb|left]]
'''Reflector Service'''
The Barix Reflector service is a simple way to set up STL, Remote Contribution and Syndication applications, without requiring the user to understand anything about IP, firewalls etc.  
The Barix Reflector service is a simple way to set up STL, Remote Contribution and Syndication applications, without requiring the user to understand anything about IP, firewalls etc.  


== '''How do I get the Reflector up and running?''' ==


The main components of the Reflector are shown in the diagram:
[[Image:Reflector_set_up_steps.png|400px|thumb|centre]]
 
 
 
 
 
 
 
 
 


== How does it work? ==


[[Image:Reflector_P2_system_diagram.png|400px|thumb|centre]]
The main components of the Reflector are shown in the diagram:
'''Database'''  
'''Database'''  
stores all data about accounts, projects and devices
stores all data about accounts, projects and devices
Line 31: Line 26:
*[[reflector server]]
*[[reflector server]]


You can find out more about the service here [http://www.barix.com/Reflector_STL_made_simple/1551/]   
You can find out more about the service here[http://www.barix.com/solutions/broadcast/reflector/]   
 


Back to [[Main_Page]]
Back to [[Main Page#Support - FAQ & Troubleshooting]]

Latest revision as of 09:18, 13 May 2013

Reflector Service The Barix Reflector service is a simple way to set up STL, Remote Contribution and Syndication applications, without requiring the user to understand anything about IP, firewalls etc.

How do I get the Reflector up and running?

Error creating thumbnail: File missing

How does it work?

Error creating thumbnail: File missing

The main components of the Reflector are shown in the diagram: Database stores all data about accounts, projects and devices

Configuration server – assigns project devices to individual Reflector Servers and communicates configuration details to devices

Reflector server(s) – receive details of devices from the config server and handle communications with them; receiving the network audio stream from the Encoder and forwarding it to the Decoder(s)

Web server – handles the User Interface, allowing users to set up and maintain their projects, updating the database accordingly.

Encoder/Decoders. On startup, each Reflector Client device will contact the Reflector Services defined to it in its startup configuration (US / EU ...), requesting the details of its project configuration, it then contacts the appropriate Configuration Server, applies its configuration and operates accordingly.

More about specific components of the Service:

You can find out more about the service here: [1]


Back to Main Page#Support - FAQ & Troubleshooting