Question & Answers

Starting with DV2000 v8, we now support up to 30 addresses.

Whether using the analog or SIP integration, DuVoice is available as a turnkey solution that included PC and, in the case of the analog solution, analog voice boards. For SIP applications, DuVoice is also available as a software only solution that you can install on a PC or Server on the same network as the PBX.

For SIP systems, yes. For analog and digital systems, no. Analog and digital boards are now manufactured by a company other than Dialogic and their software is incompatible with the DV2000. We always document on the requirements page which versions we support and provide links to the latest on each versions download page.

Check that you have not enabled .WAV files to be blocked under Mcfree Access Protection Properties. The system uses .WAV files for all it’s prompts and messages.

The system will purge any expired messages every hour. Deleted messages are stored for 24 hours.

No. For best results the mailbox number should match the extension of the room. Each room has an additional field for room number which allows alpha-numeric text. InnDesk uses the room number field exclusively for all interactions.

No. We currently only support blind transfers. However when we attempt to transfer if the PBX responds that the extension cannot be found or is busy we will cancel the transfer and redirect to voicemail.

RFC 2833/4733 and Inband. The DV2000 does not support DTMF via SIP INFO packets. It is not recommended to use inband DTMF especially when using analog gateways as it can cause DTMF issues.
Note: Inband mode cannot be used when using low bit-rate (LBR) coders.

Switch to RFC 2833 DTMF support on the device. If this is not available see this workaround here.

No. This should not be enabled on your router and will cause the DV2000 to fail on registration. This is due to the fact the router is changing the Contact field used to identify the DV2000 and the Dialogic driver doesn't support this.

This is a known issue with the Mitel. In each and every case it has been resolved by the telephone tech performing some action on the Mitel. All of them refuse to tell us what they did and what the issue was.

The DV2000 is not responsible for re-registration and this is performed by the Dialogic Driver. This can only be diagnosed by viewing the Dialogic logs. See here.

No, but we strongly suggest you run one. See our guide on how to configure the Windows firewall here.

No, and it's suggested you logout of Windows each time maintenance has been completed.

No. The DV2000 uses no file shares or domain level interfaces. It also does not require any printer access.

None of the DuVoice product requires certificates of any kind, including all of the web interfaces. While a customer may generated their own self signed certificates for https support these must be generated and configured by the customer. We do support TLS when accessing 3rd party interfaces like email servers and PBX Link interfaces.

The DV2000 may use 3rd party libraries produced by NEC or Avaya to access those manufactures PBX's and we update those libraries as often as we can, however many have not been updated to support newer versions of TLS.

What about TLS 1.0
As stated all certificates are the responsibility of the customer, any scan finding TLS 1.0 most likely found the user generated certificates for either the WebUI interface or a 3rd party application installed on the DV2000 system.

Yes, on the history page it shows what features were added and what problems were resolved.

With very few exceptions you should be able to update your system without contacting DuVoice.

DuVoice typically changes the major version number when major significant changes have been made. Typically these changes require a greater level of support and therefor changing the key number helps prevent unexpected changes or failures.

DuVoice can connect with either one analog extension per voice mail port or one SIP endpoint per voice mail port. DuVoice uses the DevLink provided by CTI Pro for call processing information and to update PBX programming based on PMS commands.

IP Office uses an IP Interface to call accounting. Most of the older call accounting solutions use a serial interface to the PBX. In most cases, it is more practical to replace the existing call account solution with a newer one.

Yes, most PBX’s are compatible with nearly all analog guest room phones in use. This includes the Avaya IP Office.

Avaya requires that call waiting be enabled on SIP stations in order to support transfers.

Yes it typically is performed via shortcodes but can also be done via TAPI but that requires a CTI-Pro (Avaya part #171988) to be turned enabled on each remote location.

Guest Name: The DuVoice system will push the guest name to the display if a guest calls the front desk.

911: The DuVoice system also monitors all guest rooms for a 911 call. The IP phone(s) will display which room called 911 and the phone will beep.

This is because of a known issue within the IPOffice that exists when a analog device (voice mail port) on an analog extension port answers on the leading edge of a ring before the IP Office has time to create the audio path.

To accommodate it, open System Configuration, then open the integration file the ports are assigned to. On the General tab of the integration file, open Off Hook by clicking on it. Add Sleep 1sec (1000ms) from the PBX code drop-down list before the Off Hook phrase. Choose to Save it in the integration file, then in the System Configuration window, under Tools, choose to Upload Voice Board Parameters.

This setting prevents the voice mail system from answering before the IP Office has created the audio path from the outside caller.

No. The DuVoice can handle all the voice mail requirements for the staff and guests.

One analog extension per voice mail port and CTI PRO (Avaya P/N 171988).

Beginning in version 4.01.008 DuVoice no longer supports call bar for room control on the Avaya IP Office. Therefore when performing an upgrade room control will be disabled until the the system is configured for user rights restrictions.

User Rights act as templates for users, locking selected user settings to the template value. These changes can include shortcode configuration, call restrictions and button programming. Using user rights also allows for better integration with the property management system.

Replicating the outgoing call bar using user rights is quite simple.

  Create a user rights group called BAR and one called UNBAR.
  Under the group BAR, check the Enable outgoing call bar and choose Apply User Rights Value.
  Under the group UNBAR, un-check the Enable outgoing call bar and choose Apply User Rights Value.
  Save these settings on the IP Office.
  In System Configuration | Features | Hospitality, under Phone Control enter the groups BAR and UNBAR under the PBX Value for the corresponding PMS Value.

Avaya IP Office versions 5, 6, and 7 have a problem with SIP extensions registering on Sundays.

Typically at midnight on Sunday or Sunday midnight GMT, the system will start returning an invalid Date field which will cause the SIP extension to fail registration. This problem resolves itself 24 hours later on Monday. Changing the date or time has no effect on the problem.

Avaya is aware of this problem and has resolved it in version 8 of IP Office.

DuVoice SIP based systems may only be installed in a virtual environment running VMWare or HyperV.