Test Integration

Once you have done the initial setup to create the voice ports, you may wish to test the system to verify it is integrating properly. However, if you have not yet programmed your switch, you should do that first.

Most switches require at least some programming steps to configure it to recognize that it is attached to a voice messaging system on specific extensions. This is particularly true for switches that offer inband integration. Switch programming varies by switch manufacturer and model and is therefore beyond the scope of this document.

DuVoice does offer integration notes for several popular switches. The latest versions of all integration notes are available at our support website at: #@supporturl@#. All integration notes are provided as PDF documents, viewable using Adobe Acrobat Reader or any other PDF viewer.

The final programming step before you can perform the initial integration testing is to start the service. Open Activity Monitor by selecting Start | All Programs | DuVoice | Activity Monitor (the exact path may vary depending on your version of Windows; this example is for Windows 7). A shortcut may also be present on the desktop or on the right-click context menu, or both.

To start the system, select Service | Start from the main menu. A stoplight icon at the far right of the status bar (lower right corner) will change from red to yellow to green. Once the icon changes to green, the system is running, although it may take a few moments longer for the Line entries to display Idle (as shown in the figure above).

Now that you have installed the hardware (and, if required, the software), have completed the basic configuration of the system, have programmed the switch and have started up the VMS service, you are ready to run through a few quick tests to verify that the VMS is integrating properly with the PBX.

For the following tests, assuming you have performed no configuration beyond that previously described, all ports should be assigned to the default tenant. For this tenant, the main greetings and auto attendant mailbox is 991, and the operator mailbox is 0.

Some of these tests require you to have at least one standard subscriber mailbox to use for testing. Since the operator mailbox, 0, is a standard mailbox, you may be able to test using it for most of the tests. However, once you have added the subscriber mailboxes for your dialing plan, you should probably run through a few of the voice mail tests below with one of those mailboxes as well.

• Verify system answers an outside trunk call with the main greetings.
• Verify the system can transfer to the operator.
• Verify the system can transfer to an extension (you will need to add a standard subscriber mailbox before doing this).

• Verify the system will forward to a mailbox on a ringing extension (external and internal).
• Verify the system will forward to a mailbox on a busy extension (external and internal).
• Verify that leaving a message will turn on the message light for a given extension.
• Verify that deleting or saving all new messages in the mailbox will turn off the message light.
• Verify that the system always asks for a password when retrieving messages (except when accessing a guest mailbox from the room's extension).

• Verify that a scheduled wakeup call rings the phone at the appointed time (or shortly thereafter) and that the prompts play as expected when you answer the call. This test requires that you will have created at least one guest mailbox.
  • To schedule a wakeup call over the phone using the admin interface, refer to the Schedule Wakeup Call (Admin) flowchart.
  • To schedule a wakeup call from the room phone directly, refer to the Schedule Wakeup Call (Guest) flowchart.
  • To schedule a wakeup call using InnDesk, refer to the InnDesk manual.
• If you have configured the guest class of service to notify the operator for failed wakeup calls, verify that a failed wakeup call does in fact trigger a notification to the operator.

  Note: A wakeup call is only considered to have failed after all call attempts have gone unanswered. The number of call attempts is defined in the Wakeup Call notification template (the default value is 4 attempts at one-minute intervals).