DuVoice Support - vs8:vsconfig:features

Connectors

Anonymous (anonymous@undisclosed.example.com) — 2023-01-07T17:45:18+00:00

2026/04/22 22:33	current
Line 1:	Line 1:
	+	{{indexmenu_n>10}}
	+	====== Connectors ======
	+	This dialog is used to configure the connection settings that DV2000 must use in order to communicate with various external services.
	+
	+	^Page^Description^
	+	\|[[vs8:vsconfig:features:connectors:caslink\|CASLink]]\|Configure settings for communicating with a call accounting system.\|
	+	\|[[vs8:vsconfig:features:connectors:comtrol\|COMTROL]]\|Configure settings for communicating name changes to a COMTROL device.\|
	+	\|[[vs8:vsconfig:features:connectors:clickatell\|Clickatell]]\|Provides an SMS for EAS using the Clickatell interface.\|
	+	\|[[vs8:vsconfig:features:connectors:slack\|Slack Webhooks]]\|Configure Slack integration allowing for EAS alerts to Slack channels.\|
	+	\|[[vs8:vsconfig:features:connectors:twilio\|Twilio]]\|Provides an SMS for EAS using the Twilio interface.\|

Guest DID

Anonymous (anonymous@undisclosed.example.com) — 2023-01-07T17:45:18+00:00

2026/04/22 22:33	current
Line 1:	Line 1:
	+	{{indexmenu_n>30}}
	+	====== Guest DID ======
	+
	+	The Guest DID table is used to manage DID numbers for guest rooms in a hospitality system.
	+
	+	<WRAP round info 75%>
	+	When processing an incoming call, the system processes the call against the call routing table first and then against the guest DID table.
	+	</WRAP>
	+
	+	{{:images:vs8:vsconfig:guestdid.png?direct\|}}
	+
	+	===== General Settings =====
	+
	+	==== How to assign numbers ====
	+
	+	Select how the DID numbers may be assigned:
	+
	+	^Method^Description^
	+	\|//Auto or Manual//\|DID numbers may be assigned automatically at check-in or manually assigned via InnDesk.\|
	+	\|//Automatic only//\|DID numbers may only be assigned automatically at check-in.\|
	+	\|//Manual only//\|DID numbers may only be manually assigned via InnDesk.\|
	+	\|//Fixed//\|DID numbers must be assigned using this dialog. InnDesk is blocked from making assignments and no automatic assignments will be made at any time.\|
	+
	+	<WRAP round info 75%>
	+	//DID assignments from the PMS are always processed regardless of this setting, so a PMS assignment may overwrite a manual or fixed assignment. If the PMS is assigning DID numbers, this setting should be set to// Manual only //or// Fixed.
	+	</WRAP>
	+
	+	==== Default destination ====
	+
	+	Enter the mailbox to direct calls to if the called ID is a currently-unassigned DID number.
	+
	+	//If this field is left blank, calls to unassigned DID numbers will be directed to the automated attendant main greetings for the tenant associated with the line that received the call. If you do not want outside callers accessing the automated attendant, enter the operator's mailbox number (or whichever valid mailbox number you want to receive such calls).//
	+
	+	===== DID Table =====
	+
	+	^Field^Description^
	+	\|//DID//\|Enter the DID number. This is what the caller or called ID must match.\|
	+	\|//Mailbox//\|Enter the mailbox number to receive the call. For unassigned DID numbers, leave this field blank.\|
	+	\|//Last Assigned//\|Displays the date and time the DID was last assigned. Format is: ''YYYY/MM/DD HH:MM:SS'' (24-hour notation).\\ \\ When performing an automatic DID assignment, the system will used this field to find the DID number that has been unassigned for the longest period.\\ \\ //This field is read only.//\|
	+	\|//Action//\|What action to perform when the a call is received from the DID number.<WRAP>
	+	* //Login// - Default action. When somebody calls the DID number they will be placed into the mailbox directly.
	+	* //Transfer// - Caller will be transferred to the assigned mailboxes extension.
	+	</WRAP>\|
	+
	+	===== Add a DID =====
	+
	+	To add a DID to the table, click Insert. This will add a blank row at the top of the table with the default action; click on each field to edit it.
	+
	+	To save your changes without closing the dialog, click Apply. To save and exit the dialog, click OK. To discard your changes, click Cancel.
	+
	+	===== Delete a DID =====
	+
	+	To delete a DID, click on the DID number to select it in the table and then click Delete.
	+
	+	The selected row will be immediately deleted from the table To save your changes without closing the dialog, click Apply. To save and exit the dialog, click OK. To discard your changes, click Cancel.
	+
	+	===== Edit a DID =====
	+
	+	To edit a DID, click on the //Mailbox// field of the row you want to modify and edit it as you wish. You cannot edit the DID number itself nor the //Last Assigned// field.
	+
	+	To save your changes without closing the dialog, click Apply. To save and exit the dialog, click OK. To discard your changes, click Cancel.
	+
	+	If you want to change the DID number itself you will need to delete the entry and then add a new one. The DID field can only be edited in a new entry.

Emergency Alert

Anonymous (anonymous@undisclosed.example.com) — 2023-01-07T17:45:18+00:00

2026/04/22 22:33	current
Line 1:	Line 1:
	+	{{indexmenu_n>20}}
	+	====== Emergency Alert ======
	+	Configuration for the EAS server is managed using System Configuration. From the main menu, select Features \| Emergency Alert. This opens the EAS Server Selection dialog, shown below.
	+
	+	{{:images:vs8:vsconfig:eas.png?direct\|}}
	+
	+	In an environment with multiple IP Office PBX systems, each PBX would require its own connection to the DuVoice. Therefore, the system supports multiple EAS server configurations. The dialog above is used to manage these servers.
	+
	+	For those who wish to alert differently based on the PBX this also provides a separation of alerts.
	+
	+	==== Add a Server ====
	+
	+	To add a new server, click Add. This will open the EAS Configuration dialog with all settings blank, except with 911 entered on the Alert Numbers page.
	+
	+	=== Using DevLink ===
	+
	+	If you are using the DevLink connection:
	+	- Select ''Avaya IP Office DevLink'' from the //PBX// list.
	+	- Enter the PBX IP address or DNS name in the box provided.
	+	- Enter the password in the box provided.
	+
	+	<callout type="warning" icon="true">
	+	If you do not fill in the IP address and password, then when you click OK to save the configuration, it will be listed as disabled even if you checked the //Enabled// box.
	+	</callout>
	+
	+	=== Using SNMP ===
	+
	+	If you are using the SNMP connection:
	+	* Select ''Avaya IP Office SNMP'' from the //PBX// list.
	+
	+	The //PBX DNS Name or IP// and //Password// fields will be grayed-out because they are not used with SNMP.
	+
	+	==== Copy a Server ====
	+
	+	If you need to create a new server to connect to a different IP Office PBX, but using the same alert numbers and address list, you can select the existing server in the list and then click Copy. This will open the EAS Configuration dialog loaded with the selected server's settings.
	+
	+	You will need to change the PBX IP address, password and description settings on the Details page before you click OK or they will be blanked out and the server will be marked as disabled.
	+
	+	Editing the configuration settings is discussed in the Edit a Server section below.
	+
	+	<callout type="info" icon="true">
	+	If you want to create a new server that connects to the same PBX but alerts on different numbers to different addresses, then you should just Add a server instead because the Copy option assumes you will change the PBX IP address, password and description.
	+	</callout>
	+
	+	==== Edit a Server ====
	+	Whether you are adding a new server or copying or editing an existing one, the EAS Configuration dialog is opened so you can configure the settings for that server.
	+
	+	^Page^Description^
	+	\|[[vs8:vsconfig:features:eas:details\|Details]]\|Configure the settings for this server.\|
	+	\|[[vs8:vsconfig:features:eas:numbers\|Alert Numbers]]\|Configure which numbers will trigger an alert if someone dials them.\|
	+	\|[[vs8:vsconfig:features:eas:addrlist\|Address List]]\|Configure which email addresses will receive email alerts and/or which mailboxes will receive urgent voice message alerts.\|

Hospitality

Anonymous (anonymous@undisclosed.example.com) — 2023-01-07T17:45:18+00:00

2026/04/22 22:33	current
Line 1:	Line 1:
	+	~~NOTOC~~
	+	{{indexmenu_n>40}}
	+	====== Hospitality ======
	+	Hospitality features are provided to support the unique needs of the hospitality industry, such as simplified mailboxes for guest use and integration with a property management system (PMS). The 7.00 includes a service module that, when active, controls communication with the PMS over either an RS232 serial link or a TCP/IP network connection and also communicates via TCP/IP to client applications such as InnDesk and PMS Monitor.
	+
	+	The settings accessed through System Configuration allow you to configure the serial or TCP port used by the hospitality service, specify which communication protocol to use, and configure other hospitality-related settings.
	+
	+	{{:images:vs8:vsconfig:hosp-select.png\|}}
	+
	+	This dialog lists the key information for each configured server:
	+
	+	^Column^Description^
	+	\|//ID//\|Server ID, used when assigning a PMS link to a location.\|
	+	\|//Status//\|Indicates if the link is enabled or disabled.\|
	+	\|//Description//\|Configurable name or description; blank by default.\|
	+	\|//Protocol//\|Assigned communication protocol; must match protocol used by the PMS.\|
	+	\|//Link//\|Link configuration.\\ \\ For serial, it displays the COM port number.\\ For TCP/IP client, it displays the PMS IP address and the TCP port number.\\ For TCP/IP server, it displays the TCP port number.\|
	+
	+	==== Edit a Server ====
	+	To configure a server, select the server instance in the table and click Edit to open the editor for that server.
	+
	+	==== Add or Copy a Server ====
	+
	+	To add the next available server instance, click Add. Or, to create the next server instance based off an existing one, select the server to copy in the list and then click Copy. Either way, the configuration dialog will be opened to edit it. In the case of a copy, the editor will be populated with the setting values for the server instance copied from; otherwise, it will have default values instead.
	+
	+	At a minimum, you will need to change the assigned COM or TCP port and give it a unique name or description in the //Description// field on the General tab.
	+
	+	<WRAP round info 75%>
	+	//The maximum number of PMS instances that can be created is 99.//
	+	</WRAP>
	+
	+	==== Delete a Server ====
	+
	+	To remove the last server instance in the list, click Delete. The 7.00 requires the hospitality server ID numbers to be in order, starting from 1. Thus, you are only allowed to delete the last entry in the list. For example, if there are three server instances, you cannot delete server 2 without first deleting server 3.
	+
	+	<WRAP round important 75%>
	+	At least one server is required at all times, even if a PMS is not in use. Therefore, server instance 1 will always exist and cannot be deleted.
	+	</WRAP>
	+
	+	==== Import / Export ====
	+	Hospitality configurations can be exported for backup or for import on other systems.
	+
	+	=== Import ===
	+	Import can only be performed while the system is not running and you can either import a configuration as a new hospitality server or overwrite an existing one based on the number of hospitality servers allowed.
	+
	+	Once a new configuration has been imported, verify the connection type and any COM port or IP addresses.
	+
	+	=== Export ===
	+	Exports a file which can be used as a backup or for import onto systems with similar configuration.

Inventory Status Interface

Anonymous (anonymous@undisclosed.example.com) — 2023-01-07T17:45:18+00:00

2026/04/22 22:33	current
Line 1:	Line 1:
	+	~~NOTOC~~
	+	====== Inventory Status Interface ======
	+
	+	The Inventory Status Interface (ISI) is a telephony interface designed to allow users to report item and quantity information to one or more remote servers. Although the original conception was to provide a method for a hotel's housekeeping staff to report usage of items from the guest room minibar, the interface has been designed to allow for any type of inventory reporting a user may require.
	+
	+	This dialog is used to configure both the telephony interface and how to communicate with the remote server(s) or PMS.
	+
	+	{{:images:vs8:vsconfig:inventory.png?direct\|}}
	+
	+	===== User Interface Settings =====
	+
	+	These settings configure how the telephony user interface operates.
	+
	+	^Setting^Description^
	+	\|//Require user id//\|Check this box to prompt for a user ID at the start of the call.\\ \\ //If this option is disabled, the system will not ask for a password either.//\|
	+	\|//Require password//\|Check this box to require a valid password after prompting for the user ID.\\ \\ //If the //Require user id// setting is disabled, the system will never ask for a password, even if this setting is enabled.//\|
	+	\|//Block checked out postings//\|Check this box if you want the system to block the housekeeping staff from posting minibar charges in checked-out rooms.\|
	+	\|//Allow zero quantity//\|Defaults to force client to enter a value greater than 0. Checking this field allows them to enter a quantity of 0 or skip entry.\|
	+	\|//Use custom room list.//\|If checked the Administrator must add individual rooms to the Inventory Web Interface. Default is unchecked which uses the list of guest mailboxes.\|
	+	\|//Enable data entry for multiple rooms//\|Check this box if you want the telephony interface to allow data entry for more than one room in the same call.\\ \\ //Default is// ''disabled''.\|
	+	\|//Room number source//\|Use the selection box to select how the room number is determined.\\ <WRAP>
	+	* //Ask Caller// -- Always ask the caller for the room number.
	+	* //Use Calling Party// -- Use the calling party (caller ID) as received from the PBX. //If the calling party information was not provided, the system will ask the caller instead.//
	+	* //Use Called Party// -- Use the called party as received from the PBX. //If the called party information was not provided, the system will ask the caller instead.//
	+	</WRAP>\|
	+
	+	===== Global Settings =====
	+
	+	This section lists server-side settings that are global across all servers.
	+
	+	^Setting^Description^
	+	\|//Post Delay (seconds)//\|Set the amount time after a change is sent to the ISI before it is posted to all configured servers. Value is in seconds.\\ \\ Range is 10 to 999 seconds. Default is ''60'' seconds.\|
	+
	+	===== Per-Server Settings =====
	+
	+	Use the selection box to choose one of five servers to configure, then configure the remaining settings for the selected server.
	+
	+	^Setting^Description^
	+	\|//Enabled//\|Check this box to enable the selected server.\|
	+	\|//Protocol//\|Select the protocol to use for the selected server.\\ <WRAP>
	+	* //HTTP POST JAZZ// -- Perform an HTTP Post with the content being XML. This was originally called //DuVoice Version 1.00//. This is the default setting.
	+	* //HTTP POST JSON// -- Perform an HTTP Post with the content being JSON.
	+	* //HTTP POST FORM// -- Perform an HTTP Form Post.
	+	* //Comtrol// -- Choose this option if you are using a Comtrol device.
	+	* //Opera Minibar// -- Choose this option if you are sending the minibar data through the PMS link to an Opera PMS and you want to use the Minibar message type.
	+	* //Opera Direct Charge// -- Choose this option if you are sending the minibar data through the PMS link to an Opera PMS and you want to use the Direct Charge message type.
	+	</WRAP>\|
	+	\|//IP address or name//\|Enter a valid URL address or server name for the remote server. Examples: <nowiki>http://192.168.25.122/ivr/isi</nowiki> or <nowiki>https://192.168.25.122/ivr/isi</nowiki> \|
	+	\|//TCP/IP port//\|Enter the TCP address to use to connect with the remote server. Only used when connecting to Opera. \|
	+	\|//Username//\|Optional username in order to support basic security.\|
	+	\|//Password//\|Optional password in order to support basic security.\|
	+	\|//Retry interval//\|Enter the number of seconds to wait after failing to connect to the remote server before making another attempt.\\ \\ //The default value is// ''60'' seconds.\|
	+	\|//Maximum attempts//\|Enter the maximum number of times to attempt connecting to the remote server before logging a failure.\\ \\ //The default value is// ''30'' //attempts.//\|
	+
	+	<WRAP round info 75%>
	+	If the protocol is set to either //Comtrol//, //Opera Minibar// or //Opera Direct Charge//, all fields in the Server Settings box except //Enabled// and //Protocol// will be grayed-out and ignored.\\ \\ In the case of Comtrol, the data is routed through the Comtrol connector so all further configuration must be done on the [[vs7:manual:syscon:conn:comtrol\|Comtrol connector]] page.\\ \\ For the two Opera protocols, the data is routed through the hospitality server so that it gets sent to the Opera PMS over the PMS Link.
	+	</WRAP>

Room Status Interface

Anonymous (anonymous@undisclosed.example.com) — 2023-01-07T17:45:18+00:00

2026/04/22 22:33	current
Line 1:	Line 1:
	+	~~NOTOC~~
	+	====== Room Status Interface ======
	+
	+	The Room Status Interface (RSI) is a telephony interface designed to allow housekeeping personnel to report room status to one or more remote servers.
	+
	+	<WRAP round info 75%>
	+	The RSI service is entirely separate from the hospitality service; changes to room status using RSI will not be passed to the PMS via the hospitality server.
	+	</WRAP>
	+
	+	This dialog is used to configure the telephony interface as well as how the information is communicated to the remote server(s) or PMS.
	+
	+	{{:images:vs8:vsconfig:roomstatus.png?direct\|}}
	+
	+	===== User Interface Settings =====
	+
	+	These settings configure how the telephony user interface operates.
	+
	+	^Setting^Description^
	+	\|//Require user id//\|Check this box to prompt for a user ID at the start of the call. //If this option is disabled, the system will not ask for a password either.//\|
	+	\|//Use custom room list.//\|If checked the Administrator must add individual rooms to the Inventory Web Interface. Default is unchecked which uses the list of guest mailboxes.\|
	+	\|//Require password//\|Check this box to require a valid password after prompting for the user ID. //If the //Require user id// setting is disabled, the system will never ask for a password, even if this setting is enabled.//\|
	+	\|//Room number source//\|Use the selection box to select how the room number is determined.\\ <WRAP>
	+	* //Ask Caller// -- Always ask the caller for the room number.
	+	* //Use Calling Party// -- Use the calling party (caller ID) as received from the PBX. //If the calling party information was not provided, the system will ask the caller instead.//
	+	* //Use Called Party// -- Use the called party as received from the PBX. //If the called party information was not provided, the system will ask the caller instead.//
	+	</WRAP>\|
	+
	+	===== Global Settings =====
	+
	+	This section lists server-side settings that are global across all servers.
	+
	+	^Setting^Description^
	+	\|//Post Delay (seconds)//\|Set the amount time after a change is sent to the ISI before it is posted to all configured servers. Value is in seconds.\\ \\ Range is 10 to 999 seconds. Default is ''60'' seconds.\|
	+
	+	===== Per-Server Settings =====
	+
	+	Use the selection box to choose one of five servers to configure, then configure the remaining settings for the selected server.
	+
	+	^Setting^Description^
	+	\|//Enabled//\|Check the box to enable the selected server.\|
	+	\|//Protocol//\|Select the protocol to use for the selected server.\\ <WRAP>
	+	* //HTTP POST XML// -- Perform an HTTP Post with the content being XML. This was originally called //DuVoice Version 1.00//. This is the default setting.
	+	* //HTTP POST JSON// -- Perform an HTTP Post with the content being JSON.
	+	* //HTTP POST FORM// -- Perform an HTTP Form Post.
	+	* //Comtrol// -- Choose this option if you are using a Comtrol device.
	+	</WRAP>\|
	+	\|//Username//\|Optional username in order to support basic security.\|
	+	\|//Password//\|Optional password in order to support basic security.\|
	+	\|//IP address or name//\|Enter a valid URL address or server name for the remote server. Examples: <nowiki>http://192.168.25.122/ivr/rsi</nowiki> or <nowiki>https://192.168.25.122/ivr/rsi</nowiki> \|
	+	\|//TCP/IP port//\|Enter the TCP address to use to connect with the remote server. Only used when connecting to Opera. \|
	+	\|//Retry interval//\|Enter the number of seconds to wait after failing to connect to the remote server before making another attempt.\\ \\ //The default value// is ''60'' //seconds.//\|
	+	\|//Maximum attempts//\|Enter the maximum number of times to attempt connecting to the remote server before logging a failure.\\ \\ //The default value is// ''30'' //attempts.//\|
	+
	+	<WRAP round info 75%>
	+	If the protocol is set to //Comtrol//, all fields in the Server Settings box except //Enabled// and //Protocol// will be grayed-out and ignored.\\ \\ This is because, for Comtrol, the data is routed through the Comtrol connector so all further configuration must be done on the [[vs7:manual:syscon:conn:comtrol\|Comtrol connector]] page.
	+	</WRAP>

2026/04/22 22:33	current
Line 1:	Line 1:
	+	~~NOTOC~~
	+	====== Inventory Status Interface ======
	+
	+	The Inventory Status Interface (ISI) is a telephony interface designed to allow users to report item and quantity information to one or more remote servers. Although the original conception was to provide a method for a hotel's housekeeping staff to report usage of items from the guest room minibar, the interface has been designed to allow for any type of inventory reporting a user may require.
	+
	+	This dialog is used to configure both the telephony interface and how to communicate with the remote server(s) or PMS.
	+
	+	{{:images:vs8:vsconfig:inventory.png?direct\|}}
	+
	+	===== User Interface Settings =====
	+
	+	These settings configure how the telephony user interface operates.
	+
	+	^Setting^Description^
	+	\|//Require user id//\|Check this box to prompt for a user ID at the start of the call.\\ \\ //If this option is disabled, the system will not ask for a password either.//\|
	+	\|//Require password//\|Check this box to require a valid password after prompting for the user ID.\\ \\ //If the //Require user id// setting is disabled, the system will never ask for a password, even if this setting is enabled.//\|
	+	\|//Block checked out postings//\|Check this box if you want the system to block the housekeeping staff from posting minibar charges in checked-out rooms.\|
	+	\|//Allow zero quantity//\|Defaults to force client to enter a value greater than 0. Checking this field allows them to enter a quantity of 0 or skip entry.\|
	+	\|//Use custom room list.//\|If checked the Administrator must add individual rooms to the Inventory Web Interface. Default is unchecked which uses the list of guest mailboxes.\|
	+	\|//Enable data entry for multiple rooms//\|Check this box if you want the telephony interface to allow data entry for more than one room in the same call.\\ \\ //Default is// ''disabled''.\|
	+	\|//Room number source//\|Use the selection box to select how the room number is determined.\\ <WRAP>
	+	* //Ask Caller// -- Always ask the caller for the room number.
	+	* //Use Calling Party// -- Use the calling party (caller ID) as received from the PBX. //If the calling party information was not provided, the system will ask the caller instead.//
	+	* //Use Called Party// -- Use the called party as received from the PBX. //If the called party information was not provided, the system will ask the caller instead.//
	+	</WRAP>\|
	+
	+	===== Global Settings =====
	+
	+	This section lists server-side settings that are global across all servers.
	+
	+	^Setting^Description^
	+	\|//Post Delay (seconds)//\|Set the amount time after a change is sent to the ISI before it is posted to all configured servers. Value is in seconds.\\ \\ Range is 10 to 999 seconds. Default is ''60'' seconds.\|
	+
	+	===== Per-Server Settings =====
	+
	+	Use the selection box to choose one of five servers to configure, then configure the remaining settings for the selected server.
	+
	+	^Setting^Description^
	+	\|//Enabled//\|Check this box to enable the selected server.\|
	+	\|//Protocol//\|Select the protocol to use for the selected server.\\ <WRAP>
	+	* //HTTP POST JAZZ// -- Perform an HTTP Post with the content being XML. This was originally called //DuVoice Version 1.00//. This is the default setting.
	+	* //HTTP POST JSON// -- Perform an HTTP Post with the content being JSON.
	+	* //HTTP POST FORM// -- Perform an HTTP Form Post.
	+	* //Comtrol// -- Choose this option if you are using a Comtrol device.
	+	* //Opera Minibar// -- Choose this option if you are sending the minibar data through the PMS link to an Opera PMS and you want to use the Minibar message type.
	+	* //Opera Direct Charge// -- Choose this option if you are sending the minibar data through the PMS link to an Opera PMS and you want to use the Direct Charge message type.
	+	</WRAP>\|
	+	\|//IP address or name//\|Enter a valid URL address or server name for the remote server. Examples: <nowiki>http://192.168.25.122/ivr/isi</nowiki> or <nowiki>https://192.168.25.122/ivr/isi</nowiki> \|
	+	\|//TCP/IP port//\|Enter the TCP address to use to connect with the remote server. Only used when connecting to Opera. \|
	+	\|//Username//\|Optional username in order to support basic security.\|
	+	\|//Password//\|Optional password in order to support basic security.\|
	+	\|//Retry interval//\|Enter the number of seconds to wait after failing to connect to the remote server before making another attempt.\\ \\ //The default value is// ''60'' seconds.\|
	+	\|//Maximum attempts//\|Enter the maximum number of times to attempt connecting to the remote server before logging a failure.\\ \\ //The default value is// ''30'' //attempts.//\|
	+
	+	<WRAP round info 75%>
	+	If the protocol is set to either //Comtrol//, //Opera Minibar// or //Opera Direct Charge//, all fields in the Server Settings box except //Enabled// and //Protocol// will be grayed-out and ignored.\\ \\ In the case of Comtrol, the data is routed through the Comtrol connector so all further configuration must be done on the [[vs7:manual:syscon:conn:comtrol\|Comtrol connector]] page.\\ \\ For the two Opera protocols, the data is routed through the hospitality server so that it gets sent to the Opera PMS over the PMS Link.
	+	</WRAP>

2026/04/22 22:33	current
Line 1:	Line 1:
	+	~~NOTOC~~
	+	====== Room Status Interface ======
	+
	+	The Room Status Interface (RSI) is a telephony interface designed to allow housekeeping personnel to report room status to one or more remote servers.
	+
	+	<WRAP round info 75%>
	+	The RSI service is entirely separate from the hospitality service; changes to room status using RSI will not be passed to the PMS via the hospitality server.
	+	</WRAP>
	+
	+	This dialog is used to configure the telephony interface as well as how the information is communicated to the remote server(s) or PMS.
	+
	+	{{:images:vs8:vsconfig:roomstatus.png?direct\|}}
	+
	+	===== User Interface Settings =====
	+
	+	These settings configure how the telephony user interface operates.
	+
	+	^Setting^Description^
	+	\|//Require user id//\|Check this box to prompt for a user ID at the start of the call. //If this option is disabled, the system will not ask for a password either.//\|
	+	\|//Use custom room list.//\|If checked the Administrator must add individual rooms to the Inventory Web Interface. Default is unchecked which uses the list of guest mailboxes.\|
	+	\|//Require password//\|Check this box to require a valid password after prompting for the user ID. //If the //Require user id// setting is disabled, the system will never ask for a password, even if this setting is enabled.//\|
	+	\|//Room number source//\|Use the selection box to select how the room number is determined.\\ <WRAP>
	+	* //Ask Caller// -- Always ask the caller for the room number.
	+	* //Use Calling Party// -- Use the calling party (caller ID) as received from the PBX. //If the calling party information was not provided, the system will ask the caller instead.//
	+	* //Use Called Party// -- Use the called party as received from the PBX. //If the called party information was not provided, the system will ask the caller instead.//
	+	</WRAP>\|
	+
	+	===== Global Settings =====
	+
	+	This section lists server-side settings that are global across all servers.
	+
	+	^Setting^Description^
	+	\|//Post Delay (seconds)//\|Set the amount time after a change is sent to the ISI before it is posted to all configured servers. Value is in seconds.\\ \\ Range is 10 to 999 seconds. Default is ''60'' seconds.\|
	+
	+	===== Per-Server Settings =====
	+
	+	Use the selection box to choose one of five servers to configure, then configure the remaining settings for the selected server.
	+
	+	^Setting^Description^
	+	\|//Enabled//\|Check the box to enable the selected server.\|
	+	\|//Protocol//\|Select the protocol to use for the selected server.\\ <WRAP>
	+	* //HTTP POST XML// -- Perform an HTTP Post with the content being XML. This was originally called //DuVoice Version 1.00//. This is the default setting.
	+	* //HTTP POST JSON// -- Perform an HTTP Post with the content being JSON.
	+	* //HTTP POST FORM// -- Perform an HTTP Form Post.
	+	* //Comtrol// -- Choose this option if you are using a Comtrol device.
	+	</WRAP>\|
	+	\|//Username//\|Optional username in order to support basic security.\|
	+	\|//Password//\|Optional password in order to support basic security.\|
	+	\|//IP address or name//\|Enter a valid URL address or server name for the remote server. Examples: <nowiki>http://192.168.25.122/ivr/rsi</nowiki> or <nowiki>https://192.168.25.122/ivr/rsi</nowiki> \|
	+	\|//TCP/IP port//\|Enter the TCP address to use to connect with the remote server. Only used when connecting to Opera. \|
	+	\|//Retry interval//\|Enter the number of seconds to wait after failing to connect to the remote server before making another attempt.\\ \\ //The default value// is ''60'' //seconds.//\|
	+	\|//Maximum attempts//\|Enter the maximum number of times to attempt connecting to the remote server before logging a failure.\\ \\ //The default value is// ''30'' //attempts.//\|
	+
	+	<WRAP round info 75%>
	+	If the protocol is set to //Comtrol//, all fields in the Server Settings box except //Enabled// and //Protocol// will be grayed-out and ignored.\\ \\ This is because, for Comtrol, the data is routed through the Comtrol connector so all further configuration must be done on the [[vs7:manual:syscon:conn:comtrol\|Comtrol connector]] page.
	+	</WRAP>