*FMCA-ARC* EchoLink Conference Node
FMCA ARC Conference Schedule
Conference Node Server On-line Schedule
Latest Conference Node Server Status (7/25/15)
The *FMCA-ARC* Conference Node Server uses the software 'TheBridge' configured within an operating system of Raspbian. It is running on a hardware platform consisting of a Raspberry Pi, Model B, with 8GB of flash memory, powered by a 5V, 1A power supply with battery backup. The node is located in Clearwater, Florida and is connected to the internet through the Bright House Networks digital cable system.
The user interfaces with the Conference Node with their normal EchoLink client program. However, you will see a few differences when connected to the Conference node as opposed to a normal EchoLink Conference from a user. The biggest difference is in the users listing. The transmitting user is always at the top of the listing. New users and the last user to transmit will go to the bottom of the listing. The "NEXT-to-TRANSMIT" position will be just below the current transmitting user. Users will propagate upward in the listing to the "NEXT-to-TRANSMIT" position. Therefore, when you are through transmitting, pass the conference to the user listed just below your call. This way, a new user is able to hear what the topics are before they start their transmission. And, the next user to transmit will be the user who has the most time without transmission thereby giving every user a fair chance to transmit.The text mode at the bottom right side of the screen will allow you to send text at any time you like. You can issue a few commands in the text box (try '.help' command) but most users only use the send text function. If a priority for anything comes up, like a question to a specific user, or a user requests to speak via the text box, the current speaker can pass the conference over to that user directly. It does rearrange the listing but that will self correct in the next round. It all goes pretty smoothly. So, just sign into the conference on Tuesday night and listen. Then by the time it gets around to your turn, you should have a pretty good idea how it all works.
The Conference Node will terminate any transmissions greater than 5 minutes.
The SysOp or Admin can allow, ban, mute, connect, disconnect, etc any user.