Night Button Codes

The DV2000/DV4 does support the use of inband night button codes, but only at a global (rather than per-template) level. These codes are stored in a configuration file named integration.ini which is located in the VMSYSTEM folder. Assuming a default installation, it would be located in:

The figure below shows the default version of this configuration file. To add one of these special inband mask codes, open this file using Notepad and add the string after the '=' sign on the appropriate line (with no space). There can be only one inband code string per line. You can use all the same mask values described in the Inband Mask Codes table.

[Inband Masks]

This section defines the extra inband mask codes. If the system cannot match an inband code string to any of those defined in the assigned PBX integration template, it will look at these strings next.

Mask	Description
NightButtonOn	Specifies the inband code that tells the system to switch to Night mode.
NightButtonOff	Specifies the inband code that tells the system to switch to Day mode.
NoActionHangup1..9	Specifies any inband codes that the system should immediately throw out and disconnect. Up to nine codes are supported. Used for codes the PBX can send that do not actually represent a real call (e.g., the PBX may send a code when it is rebooted).

[Night Button]

The Template setting specifies the scheduled event template that is used by the auto attendant mailbox for the main location to specify the Day mode settings (greeting, SDA menu, COS, etc.). For the Default Location, the auto attendant mailbox is 991 and the default scheduled event template is Day Schedule.

On receipt of the NightButtonOn code, this template will be disabled. On receipt of the NightButtonOff code, this template will be enabled.

Note: Since only one scheduled event template can be specified, to use the night button feature for multiple locations requires that the auto attendant mailbox for each location use the same scheduled event template.

Processing Inband Codes

When the system is trying to match an inband DTMF string against the inband mask codes to determine the call type, it always compares them in a specific order.

First, it will try to match the string against one of the mask codes defined in the PBX integration, moving through the different code types in the following order: RNA, busy, immediate record, subscriber login and always forward. For each type, it will process the list of codes from the top down before moving on to the next code type.

If, after processing all the mask codes defined in the PBX integration template, it still has not found a match, the system will process the mask codes defined in the integration.ini file, starting with NightButtonOn, then NightButtonOff, and then each of the nine NoActionHangup codes. If it still cannot find a matching mask code, it will direct the call to the auto attendant mailbox for the location assigned to the voice line the call came in on.

Once a match is found, the system will parse the inband string according to the matching mask code to determine the call type and, if relevant, the called extension and the calling extension.