====== Phone Control ======
7.00 provides support for setting call restrictions on guest room phones when integrating with certain PBX systems. The Phone Control dialog is used to configure the relevant options related to this feature, including whether a call accounting system is involved.
To configure the PBX link, refer to the [[vs7:manual:syscon:pbxlinks|PBX Links]] section instead.
{{:images:vs7:manual:hosp-phone.png?nolink|}}
===== Auto-set phone state on =====
Configure these automation settings to indicate whether the system should automatically change the call restriction status for guest rooms at check in and check out. Check the box provided to enable the feature, then use the associated drop-down list to select which user group restriction should be assigned in that case.
Selecting the ''--no change--'' option is effectively the same as removing the check from the check box. The contents of the drop-down list is determined by the contents of the //User group restrictions// table.
===== Call accounting =====
The 7.00 is able to integrate with a couple of different call accounting systems (CAS) in such a way that the CAS tells the 7.00 what the user group restriction should be for each guest room, and the 7.00 passes that information on to the PBX.
**When call accounting is enabled, the //Auto-set phone state on// options will be disabled and any manual changes to phone status (e.g., via InnDesk) will be overridden by the value set by the CAS.**
|< 85% 15% >|
^Setting^Description^
|//Type//|Select the call accounting package you are using from the list provided.\\ \\ //If your CAS package is not listed, contact your authorized DuVoice reseller for assistance.//\\ \\ If CAS integration is not in use, select ''--none--'' to disable this feature.|
|//Enabled//|Select the user group restriction value to be applied when the CAS indicates the phone should be enabled.\\ \\ Selecting ''--no change--'' will prevent the restriction value from ever being changed.|
|//Disabled//|Select the user group restriction value to be applied when the CAS indicates the phone should be disabled.\\ \\ Selecting ''--no change--'' will prevent the restriction value from ever being changed.|
===== User group restrictions =====
The user group restrictions table is used to map the supported PBX values to the supported PMS values, and also to provide the desired text to use whenever the system must display the phone status in a human-readable format. Each PBX system for which the 7.00 currently supports the phone control feature may use slightly different terminology, such as: //profile, class of service, group,// or //call restriction level//. For the most part, they mean essentially the same thing.
|< 85% 15% >|
^Column^Description^
|//Display Text//|Enter a descriptive word or short phrase for this restriction level or user group.|
|//PBX Value//|Enter the value sent to the PBX to assign this restriction level or user group to the specified extension. This value may be either a digit or a text string, depending on the PBX.\\ \\ //Since set restriction packets are never sent to the PMS, it is okay to have PBX values that do not match up to a PMS value. Such values can only be assigned via InnDesk or via the call accounting settings listed above.//|
|//PMS Value//|Enter the value sent by the PMS to assign this restriction level or user group to the specified extension.\\ \\ //If a PMS is being used and it can send messages to change the phone restriction level, and you are not using call accounting, always match each possible PMS value to a PBX value, even if you have to use the same PBX value for multiple PMS values.//\\ \\ If you have enabled the call accounting option, then you only need two PBX values, one that equates to enabled and one that equates to disabled. The PMS value column can be left blank because the PMS should be setting the phone state via the call accounting software and not directly to the 7.00.|
|//Active PMS//|Displays the PMS protocol currently assigned to this hospitality server instance. **Read-only.**|
===== Editing the User Group Restrictions Table =====
All editing options are accessible using the mouse.
|< 85% 15% >|
^Option^Description^
|//Edit a row//|To edit the //display text, PBX value// or //PMS value// for an existing row, left-click on the given field to edit it in-place.|
|//Add a row//|To add a row, right-click anywhere on the table and select //Add new row// from the context menu.\\ \\ This will add a new row to the table with the text ''NEW ENTRY'' in the //Display Text// field and the other two fields will be blank. You can then left-click on each field to edit them.|
|//Delete a row//|To delete a row, right-click on it and select //Delete selected row// from the context menu.|
|//Reset to defaults//|To reset the entire table to the default entries for the given PBX and PMS protocol combination (if known), right-click anywhere on the table and select //Reset to defaults// from the context menu.|
**Changes will only be saved when you click //OK// or //Apply//.**
The Avaya ACM, Nortel and Vodavi PBX systems require that the PBX values be configured in a specific way. Refer to the following two sections for more details.
==== Configuring the Avaya ACM profile string ====
In order for the system to correctly translate between PBX and PMS values when the Avaya ACM PBX is selected, it is necessary to configure the PBX Value strings exactly as the ACM protocol defines them. **The exact meaning of restriction levels 1, 2, 3, 6 and 7 depends on the configuration of the //Controlled Toll Restriction Replaces// setting on the PBX; you will need to ascertain how you ACM is programmed in order to match them up with the values sent by your PMS.**
The table below shows the possible call restriction levels and their descriptions as provided in the ACM interface specification:
|< 75% 10% >|
^ Level ^Meaning^
| //0// |No restriction|
| //1// |Outward / Toll restriction|
| //2// |Station-to-station / Toll restriction|
| //3// |Combination of 1 and 2|
| //4// |Total restriction|
| //5// |Termination restriction (DND) only|
| //6// |Combination of 1 and 5|
| //7// |Combination of 2 and 5|
==== Configuring the Nortel profile string ====
In order for the system to correctly translate between PBX and PMS values when the Nortel PBX is selected, it is necessary to configure the PBX profile strings exactly as the Nortel protocol defines them. The exact meaning of each setting is configurable on the PBX; you will need to ascertain how the Controlled COS, System COS, Enhanced Level 1 COS and Enhanced Level 2 COS are each programmed on your Nortel PBX in order to match them up with the values sent by your PMS.
The table below shows the possible profile strings and their descriptions as provided in the Nortel interface specification:
|< 75% 10% >|
^ Profile ^Meaning^
| //CO ON// |Controlled COS On|
| //E1 ON// |Enhanced Controlled COS Level 1 On|
| //E2 ON// |Enhanced Controlled COS Level 2 On|
| //CO OF// |Controlled COS Off - equates to System COS in the PBX.|
| //E1 OF// |Enhanced Controlled COS Level 1 Off - equates to System COS in the PBX.|
| //E2 OF// |Enhanced Controlled COS Level 2 Off - equates to System COS in the PBX.|
You may change the //Display Text// in the User Restrictions table to be anything you wish, but the //PBX Value// string must be one of the 8 possible choices listed in the table above. The //PMS Value// may vary depending on which PMS you are using and how it is configured.
**If you are using ACM protocol for the PMS, then the same restrictions apply to the //PMS Value// column as well.**
==== Configuring the Vodavi profile string ====
For Vodavi, the 7.00 must dial a series of DTMF codes over an analog voice connection to the Vodavi PBX. Typically, this dial string will be:
470,,,
where '''' is the extension number, '''' is the daytime class of service and '''' is the nighttime class of service. However, on some versions of the Vodavi, this suffix string may be different. Consequently, you need to configure the profile string to be everything that comes after the '','' portion of the example dial string. //Note that a pause (comma) is automatically added after the extension number, so you don't need to start the profile string with a comma.//
By default, the 7.00 is configured assuming the following possible class of service values on the Vodavi (some versions of Vodavi may vary; consult the documentation for your PBX to verify the available classes and what they mean):
|< 75% 10% >|
^ COS # ^Meaning^
| //1// |No restrictions|
| //2// |Table A governs|
| //3// |Table B governs|
| //4// |Table A and B govern|
| //5// |Restricts 0, 1, * and # dialed as the first digit, with a 7-digit maximum|
| //6// |Intercom only (no CO line access - will block 911 unless 911 Feature is active - consult your Vodavi documentation)|
| //7// |Restricts 0, 1, *, and # dialed as the first digit, with a 10-digit maximum|
The 7.00 defaults to assuming that the same COS will apply for both day and night, and will therefore use assign a profile string of ''1,1'' for restriction levels that equate to not restricted and will use ''6,6'' for restriction levels that equate to restricted. You can of course change the profile strings as needed.
**Since the actual dial string conventions may vary depending on the version of Vodavi installed, consult the documentation and/or configuration software for your Vodavi PBX to verify the classes of service available and how the dial string should be configured.**