Configuration

The Martec System Interface (MSI) is configured using the System Configuration application.

To access its configuration dialog, select Features | Martec from the main menu.

Note: If the Martec option is grayed out, this means the feature has not been licensed and is not available for use on your system. If you have purchased this add-on feature, please contact DuVoice Technical Support to discuss how to get the feature enabled on your system. If you have not purchased this feature, please contact DuVoice Sales to discuss whether this feature will work for your application and, if so, how to purchase it.

General settings

The Martec configuration settings are divided between three property pages. The first page, General, is shown below.

The MSI server performs a maintenance routine once each day, clearing out any activity log entries older than 30 days (these statements are used in generating reports). The maintenance time setting determines what time each day this maintenance routine is performed. Use the time selector to change the hour, minute, and/or the AM/PM setting.

Click OK to save your changes and close the dialog; Apply to save changes but leave the dialog open; or Cancel to close the dialog without saving anything.

Outdial settings

The Outdial page, shown below, allows you to change settings that affect how the system handles the actual calls it makes to the extensions it was told to call.

Call progress

The DV2000/DV4 will always use call progress when outdialing for the MSI, in order to detect whether a call is answered, is not answered (RNA), is busy, or if the line does not have dial tone (e.g., if the voice line is not connected to the PBX).

The Ring count setting determines approximately how many rings it should accept before deciding that the call is not answered. Internally, this actually translates to an amount of time, which is approximately 6 seconds per ring (based on the Bellcore standard: 2 seconds on, 4 seconds off). So, for the value of 3 shown in the figure above, the system would wait about 18 seconds before deciding the call is RNA.

Retries

There are two settings that control retries if the initial call attempt is not answered:

Setting

Description

Max retries

Set the number of times the system should try again to complete the call after it has failed the first attempt. A value of 0 means that only the initial call attempt will be made; there will be no retries.

Once the maximum number of retries is reached, the call will be canceled and logged as having failed.

The default value is 3 retries.

Retry delay

Set the length of time, in seconds, to wait between the end of one call attempt and the start of the next.

This is the minimum delay; the actual delay may vary depending on the number of voice lines are available and how many calls need to be made.

The valid range is from 1 to 999 seconds. The default setting is 15 seconds.

Message

There are three settings that control what message is played to the called party:

Setting	Description
Single room	Enter the prompt ID number to play when an alert is sent to a single room only. You can only use numeric digits and do not need to enter the file extension (.wav is assumed). If you wish to use a different prompt ID for whatever reason, you can change it here. However, note that if you enter a prompt ID with either more or less than 4 digits, you will not be able to use the administrator telephony interface to re-record the prompt, although it will play for the called party just fine. The default prompt is 2080.
Multiple room	Enter the prompt ID number to play when an alert is sent to multiple rooms. You can only use numeric digits and do not need to enter the file extension (.wav is assumed). If you wish to use a different prompt ID for whatever reason, you can change it here. However, note that if you enter a prompt ID with either more or less than 4 digits, you will not be able to use the administrator telephony interface to re-record the prompt, although it will play for the called party just fine. The default prompt is 2076.
Repeat message x times	Enter the number of times to repeat the message. The system will automatically add a brief pause between each repetition. The valid range is from 0 to 9 repetitions. The default value of 0 means the message will only play once.

Professionally Recording Custom Prompts

If you wish to have either message professionally recorded, make sure it is recorded using the DV2000/DV4's standard recording format: 8000 Hz, 8-bit mu-Law PCM WAVE.

Name the file using whichever prompt ID you have configured it to be, and use the .WAV extension (for example, the default multiple-room prompt would be named 2076.WAV). Then place it in the appropriate language folder (e.g., for US English, place the prompt in C:\DuVoice\LANGUAGE\101).

Serial settings

The Serial tab, shown below, allows you to select which COM port(s) are used to connect the MSI with the Martec safety management system (SMS), and what baud rate and other transmission settings are used.

Ports

The MSI is only requires a single serial connection with the SMS in order to work; however, it can support a second serial connection for redundancy. Both ports can be active at the same time, but if the MSI receives data on both ports at the same time, it assumes that it is receiving identical data and will discard whichever data packet arrived second.

If a redundant port is not required (or is not supported by your SMS), you can set the second COM port to a value of None, as shown in the figure above.

Protocol

The protocol setting determines how the MSI interprets any packets or control characters it receives over the serial connection from the SMS. Currently, only the SMS protocol from Martec is supported, so this option is fixed and cannot be changed. The same protocol will be used for both COM ports.

COM settings

The COM settings control the actual data flow over the COM port(s); if both ports are used, they must be configured identically. The Baud rate determines the speed of data transmission. Select the value from the drop-down list that matches the value used by your SMS. Likewise, the Data bits, Stop bits and Parity settings should also match those used by the SMS.