Ventrilo - Server Properties
The Server Properties window is used for customizing the server configuration. All of the options in this window will be stored in a file called ventrilo_srv.prop on the machine that is running the server. Should the machine or server instance be restarted these settings will be read by the server program and restore the associated settings. You must be logged in with Server Admin rights to change these settings.
A change to any of these options will take effect immediately and the server does not need to be restarted.
Comment
This text input field allows you to enter the comment that will be displayed next to the server name at the top of the User list window when connected to the server. This is similar to the comments that Users can assign their own login names.
Chat filter
This feature has two options. ‘Global to server’ and ‘Per channel’. The ‘Global to server’ option means that when someone opens the chat window they will see all other Users who have the chat window open and their conversations are global to the server. When set to the ‘Per channel’ option you will only see people in the chat window that are in the same channel as you and all text chat will be sent only to those people in the same channel.
Channel ordering
This option allows you to change how channels are ordered. The first and default method is to have channels always sorted no matter which order that you create them in. The second option allows manual ordering and reordering of the channels.
When set to manual ordering, a Server Admin or Channel Admin can use the drag-and-drop feature to move channels up and down. Note: This only applies to parallel (sibling) channels. You cannot move a channel to a different parent. However, if you move a channel up or down and this channel has sub-channels then all sub-channels will be moved along with it in addition to any Users who are in the channel being moved or its sub-channels.
When moving a channel, grab the channel to be moved and then drop it on top of the channel that you want to insert it in front of. There is just one caveat to this mechanism: If you want to make a channel to be the last channel of the current parent then you will need to move it just in front of the current last channel and then drag the last channel on top of the one you just moved. This is because you can only target a valid parallel channel when you are going to perform the drop.
Always display MOTD
This option will force the ‘Message of the Day’ window to always be displayed when a client connects to the server, even if the client has enabled the "Display only if it changes" option in the MOTD window.
Guest logins
Guest logins are those login names that do not exist in the USR file. See the User Editor for details about creating unique account names. Note: There is a (Guest) account in the User Editor that has rights which apply to all Guest accounts.
Above and beyond the (Guest) account rights you also have some global control to prevent Guest accounts from over running your server, or worse, hijacking your servers allotted slots.
Max guest logins
This value controls the maximum number of Guest accounts that can be logged into your server at any given time. A value of 0 means unlimited.
You can always be assured of having access to your server when this options is set to 0 if you give your account the "In reserved list" right. See the User Editor for more details about that right.
Auto kick after (X) minutes
This value means that each Guest account will be automatically kicked off the server after they have been connected for the specified number of minutes. This is useful for hosting companies who are running dedicated test servers but don't want the server to be abused for private use. A value of 0 disables the feature.
Auto ban for (X) minutes
This value specifies how long an IP-address that logged in with the Guest account will be banned after they have been kicked or they disconnect on their own. If a client from the banned IP tries to connect before the ban has elapsed the server will inform them that they are banned and how much longer they need to wait before the ban is automatically lifted.
Note: If you have several people behind a router and both of them use your server, and one has an account while the other does not and connects using the Guest account, then this auto ban will be seen by the person with the account as well if the Guest User has already trigger the auto ban. In cases like this you will need to create an account for everyone coming from the same IP.
Spam Filters
These options allow you to control what happens if a client abuses certain features of the server. When you click on any of these buttons a new dialog box will open and give you the option to either disable the feature or chose to kick or ban the User from the server.
Interval: This parameter specifies the shortest amount of time (in milliseconds) that a client can issue a similar event. Thus, 1000 would mean 1 second.
Times: This parameter specifies how many times a client is allowed to exceed the given event specified interval. A value of 1 would mean that the very first time a client sends two events of the same type within the span of the specified interval then the action will be triggered.
Please note that the effectiveness of these spam options will be limited. If someone wants to spam your server then they will do so but within the bounds of your spam filters. It might be necessary to set the intervals to a higher value and just make sure that your normal Users understand it.
Chat
Controls how fast a User is allowed to send messages via the Chat window.
Comment
Controls how fast a User is allowed to change their comment via the Comment button.
Wave
Controls how fast a User is allowed to send Wave file binds.
TTS
Controls how fast a User is allowed to send Text-To-Speech binds.
Channel
Controls how fast a User is allowed to switch channels.
Bind Filters
Wave
When checked this option will prevent anyone from sending wave file binds. Unlike the spam filters there are no consequences if they try.
TTS
When checked this option will prevent anyone from sending Text-To-Speech binds. Unlike the spam filters there are no consequences if they try.
User inactivity
Timeout (minutes)
This option specifies the number of minutes that a User is allowed to be away from his computer (no mouse, keyboard or game controller activity) before the server will perform the specified action.
A value of 0 disables this feature.
Action
This option specifies what action to take when a User has surpassed the Timeout value.
Channel
This option specifies what channel to move a User to if the Action field is set to "Move to channel". Click the "..." button to select which channel a User should be moved to. Selecting (None) will make this field blank which means that the User will be moved to the lobby.
Remote statusing returns
Ventrilo servers support remote status requests that can be displayed on web pages via the "ventrilo_status" program or in the Ventrilo client itself via the built-in Server Browser window. Ventrilo supports remote statusing by default but sometimes you might want to control how much information is sent back to the requesting program.
Server comment
When checked the server will return the contents of the server comment.
Channel names
When checked the server will return all of the available channels configured for this server.
Note: If you disable this option it automatically prevents the channel comments from being sent as well.
Channel comments
When checked the server will return the associated comments for all channels.
User names
When checked the server will return all of the currently connected User names.
Note: If you disable this option it automatically prevents the User comments from being sent as well.
User comments
When checked the server will return the associated comments for all Users.
Require remote status "Show login name"
When this option is checked, every connecting client, Account based or Guest, must have the "Show login name in remote status requests" option checked in their definition for this server. Otherwise, they will get an error message and automatically kicked from the server.
When not checked the connecting client can decide whether or not they want their name listed in remote status requests.