Networking

The following is a document detailing the requirements and recommendations for the site’s network hosting a DuVoice server.

This document is intended as an overview to suffice for a generic understanding of how to get the DuVoice network integration to the other services required for DuVoice functionality rather than reviewing all steps for full integration, because there are specifics that are unique for each site that will need to be addressed accordingly.

Since most of the time, these networks are separated.

• DuVoice provided hardware ships with two network interfaces.
  • Connection for telephony network.
  • Connection for hospitality network.

However, in some cases, both telephony and hospitality networks can be shared on a single interface.

• The DuVoice server will need to have each interface set with a static IP address.
  • This will need to be done by the on-site implementation team.

Since Windows doesn’t perform optimally with two default gateways, one of these networks should have direct access to their respective resources.

• DuVoice technicians require remote access to the DuVoice server.
  • The recommended method is TeamViewer.
    • TeamViewer requires internet access. (Network ports listed on this page below).

• Restricting access to TeamViewer is not recommended.
  • In this case, the site’s implementation team must provide an alternative.
  • The prefered method in this case is a simple link a DuVoice technician can use.
    • DuVoice technicians will not register for any remote access alternatives.
      • Any alternatives that require an account must be set up by the on-site implementation team.

If on-site staff would like to the InnDesk WebUI interface, their system that they would like to use to access InnDesk will need network access to the DuVoice server to establish an HTTP connection.

• The telephony NIC must have ONLY one IPv4 address assigned.
• There are can only be one default gateway configured within Windows.
• Any network changes require a full OS reboot.

The Dialogic HMP telephony drivers require that the network interface on the DuVoice server that registers to the phone system is the same network interface that also send the SIP Notify to the phones/gateways for turning the MWI on/off.

If using an on premise PBX, the telephony network the DuVoice server is connected to will require direct access to the PBX.

If using a hosted PBX solution, the telephony network the DuVoice server is connected to will require internet access in order to access the PBX.

The telephony network the DuVoice server is connected to will require network access to the phones/gateways to send SIP Notify packets to update MWI on/off.

The hospitality network the DuVoice server is connected to will require network access to the PMS interface server.

• UDP: 5060-5061

Note: This is a recommended port value, but will ultimately be determined by the PBX vendor on a case-by-case basis.

• UDP: 49152-49408

This link is used by the DuVoice server to send guest caller-id updates from the DuVoice server to the phone system.

Note: No recommended defaults, but we will need a port open for this connection.

This port will ultimately be determined by the PBX model on a case-by-case basis.

Most of the time, it uses TCP rather than UDP.

• TCP: 1719, 1720, 5060, 12002, 12003, 12004, 20000, and 20001.

• TCP: 5000

Note: This is a recommended port value, but will ultimately be determined by the PMS vendor on a case-by-case basis.

• TCP/UDP: 5938, 443, 80