Support

Anonymous (anonymous@undisclosed.example.com) — 2023-03-27T17:57:54+00:00

2026/05/03 11:44		current
Line 1:		Line 1:
		+	{{page>:download:home&noheader}}

Guest Room Telephones

Anonymous (anonymous@undisclosed.example.com) — 2024-12-20T17:05:08+00:00

2026/05/03 11:44	current
Line 1:	Line 1:
	+	======= Guest Room Telephones =======
	+
	+
	+
	+
	+
	+
	+	===== MWI SIP Notify =====
	+	==== Configuration ====
	+	All these methods require the Message Waiting notification to be configured as SIP or SIP+PMS.
	+
	+	=== Notifications ===
	+	From Mailbox Administration->Templates->Notifications.
	+
	+	{{:images:howto:sip:mwisip.png\|}}
	+
	+	Set both the MWI On and MWI Off template to use SIP or SIP + PMS if you prefer.
	+
	+	===== Direct To Phone =====
	+	Often if the PBX doesn't supply forwarding of message waiting to a phone or is blocked because it has it's own voicemail the DuVoice can send a SIP notify directly to the phone or gateway.
	+
	+	Care should be taken to ensure the PBX never sends a SIP Notify to the extension otherwise the light may not be in the correct state.
	+
	+	==== Requirements ====
	+	* Phone is configured for a static IP address. This can done on the phone or within the DHCP server which is preferred.
	+	* Phone must support anonymous SIP notify.
	+	* DuVoice must be able to send network packets directly to the phone. Ensure their are no proxy servers or network settings which could prevent this.
	+	* DuVoice must be licensed for SIP.
	+
	+	==== Mailbox ====
	+	Edit a mailbox, choose Address List, and configure one or more of the MWI addresses for the SIP address you wish to send the notification.
	+
	+	{{:images:howto:sip:mwiipaddress.png\|}}
	+
	+	===== SIP to Analog Gateways =====
	+	When using a SIP gateway to connect analog phones, many support the ability to address an extension directly allowing the DuVoice system to send a SIP notify to the gateway.
	+
	+	Some Gateways only use use the gateway IP address for each port while others like the Grandstream GXW4224V2 use the IP address and a port number for each jack. In the case of the Grandstream
	+
	+	==== Issues ====
	+	* The Gateway must support the type of MWI light the analog phone uses and must be set accordingly. Grandstream GXW4224V2 and Adtran 924e supports both FSK and NEON.
	+
	+	==== Grandstream GXW4224V2 ====
	+
	+	For this Gateway or the 48 port gateway port numbers are requred after the IP address. Therefore the MWI address would be phone extension (or DID) number followed by the gateways IP address and the jacks FXS port number. The Grandstream doesn't seem to use the extension number but it should match that of the mailbox and it needs to be a valid SIP address otherwise the DV2000 will reject it. GXW4224V2 port numbers start at 5060 for jack 1, and 5062 for jack 2, 5064 for jack 3 etc. Be sure the gateway port is set to 5060.
	+
	+	In this example the address is for extension 3101 on FXS jack 2.
	+	Example 3101@192.168.100.243:5062 The 3101 will be a 10 digit DID on a hosted system
	+
	+	NOTE: Under Profile-SIP Settings-Security Accept Incoming SIP from Proxy Only must be set to NO
	+
	+	==== Adtran 924e ====
	+	Only the extension @ gateway IP address is required
	+	Example
	+	3101@192.168.100.243
	+
	+	==== Audiocodes MP-124 ====
	+
	+	Enable MWI:
	+	Configuration->VoIP->GW and IP to IP->DTMF and Supplementary ->Supplementary Services
	+	Message Waiting Indication (MWI) Parameters
	+	Enable MWI "ENABLE"
	+
	+	Only the extension @ gateway IP address is required
	+	Example
	+	3101@192.168.100.243
	+	Note: This extension or phone number must be the number in Configuration->VoIP->HuntGroup>Endpoint Phone Number for the channel
	+
	+	===== SIP Telephones used in Guestrooms =====
	+	In most hosted SIP PBX applications with DuVoice DV2000 the built in When using a SIP telephones in the guest room, the telephone musy support recieving a SIP notify for the message light from the DuVoice DV2000 IP address which is NOT the same IP address as the hosted PBX. The may also be refered to as an "Anonymous" SIP notify. Various manufacturers deal with this in a few different ways. Some allow and IP address to be entered for the message waiting server, some may have a securty checkbox that allows SIP messages from an IP address other than the registered PBX and some have the abilty to subscribe to a different IP just for message waiting lights. (See Subscribe below).
	+
	+	NOTE: Some telephones support sending the IP address to the DV2000 so static IPs are not required: [[https://support.duvoice.com/vs8/vsconfig/system/service/ipphonecfg]]
	+
	+	==== vTech ====
	+	Most vTech phones have these feature available under Phone Configuration->Advanced SIP settings. In this example the DuVoice is located at IP address 192.168.200.100. In this example the port number cannot be specified. If the device allows this it should match that of the DuVoice system under SIP Configuration.
	+
	+	==== Polycom ====
	+	Polycom phones allow third party SIP notify but the SIP Port defined in the SIP section of the phone web admin.
	+	Polycom Edge E100 Example: 12818452518@192.168.11.42:5135 (where The Polycom Edge E100 local sip port is set in the Polycom web admin under SIP settings as 5135)
	+
	+	==== Yealink ====
	+	Yealink phones allow third party SIP notify.
	+
	+
	+	{{:images:howto:sip:vtechmwiserver.png\|}}
	+
	+	===== MWI Subscription =====
	+	If a phone doesn't support anonymous SIP notify, but supports subscription. The DuVoice system can handle SIP subscriptions for a maximum of 250 extensions. This limit is due to the SIP stack and not a configuration setting which can be changed.
	+
	+	<WRAP center round important 100%>
	+	This feature is only supported on DuVoice 7.01 and above.
	+	</WRAP>
	+
	+	==== Requirements ====
	+	* Phone support custom 3rd party address for Message Waiting subscription.
	+	* Phone extension must match mailbox number or have the ability to specify the account.
	+	* DuVoice must be able to send network packets directly to the gateway.
	+	* DuVoice must be licensed for SIP.
	+
	+	==== Mailbox ====
	+	No special configuration must be performed in the mailbox.
	+
	+	<WRAP center round tip 60%>
	+	Leave the MWI addresses as the extension which is the default setting. Using a SIP address will cause subscriptions to fail.
	+	</WRAP>
	+
	+
	+
	+
	+
	+
	+
	+	===== IPPHONECFG Tool =====
	+	This optional server will listen for events posted by SIP telephones and/or perform a ARP query to automatically configure an MWI address for a mailbox.
	+
	+	===== Requirements =====
	+	* DV2000 8.0.46 or above.
	+
	+	===== Features =====
	+	* Telephones can be configured for DHCP.
	+	* Phones can configure themselves.
	+	* Multiple phones per-mailbox.
	+	* Individual phone overrides.
	+	* Change will retain original extension number.
	+	* Change will retain original port number.
	+	* ARP query to match MAC address to mailbox or MWI address.
	+
	+	===== Telephones =====
	+	==== ARP ====
	+	* Any and all IP phones on the same subnet as the DV2000.
	+
	+	==== HTTP ====
	+	* Poly / Polycom
	+	* Yealink
	+	* Bittel
	+	* vTech
	+
	+	===== Operation =====
	+	Because many SIP PBXs do not support message waiting (MWI) from 3rd parties the DV2000 can be configured to send the phone a SIP Notify packet to set/clear the MWI light. However this requires each phone to have a fixed IP address and be manually configured within Manager.
	+
	+	In order to automatically configure telephones this server can listen for changes from the telephone as well as perform an ARP request to match MAC addresses to mailboxes.
	+
	+	==== ARP ====
	+	Creates a list of all possible IP addresses on all network adapters in the system. Then it queries each one asking for the devices MAC address. If the device responds with a MAC address, we search the mailbox list for it and configure the MWI address if we find one.
	+
	+	If we cannot find the MAC address assigned to a mailbox then we search all MWI addresses description for a matching MAC address. If we find a match then we configure that exact MWI address. Using this method allows them to assign a MAC address per MWI address for when multiple telephones exist in a room.
	+
	+	==== HTTP ====
	+	Using this method allows telephones to use DHCP and automatically configure the MWI address on the DV2000 based. However if telephones are configured to use a random SIP port this server cannot be used because none of the telephones support sending their port number.
	+
	+	The server will automatically check if there is an existing extension and port number as part of the address and not change these. This allows the administrator to pre-configure all mailboxes and only the IP address will be modified.
	+
	+	==== Assignment ====
	+	Here are some examples of how the MWI address is modified by the server when determine the extension is 3101 and the phones IP address is 192.168.100.67.
	+
	+	Examples
	+	^ Extension ^ IP Address ^ Existing MWI ^ Becomes ^
	+	\|3101\| 192.168.100.67 \| Empty \| 3101@192.168.100.67 \|
	+	\|3101\| 192.168.100.67 \| 3101 \| 3101@192.168.100.67 \|
	+	\|3101\| 192.168.100.67 \| 3101@192.168.100.55 \| 3101@192.168.100.67 \|
	+	\|3101\| 192.168.100.67 \| 12055551212 \| 12055551212@192.168.100.67 \|
	+	\|3101\| 192.168.100.67 \| 3101:5070 \| 3101@192.168.100.67:5070 \|
	+	\|3101\| 192.168.100.67 \| 3101@192.168.100.55:5070 \| 3101@192.168.100.67:5070 \|
	+	\|3101\| 192.168.100.67 \| 12055551212@192.168.100.55:5070 \| 12055551212@192.168.100.67:5070 \|
	+
	+	====== Server Setup ======
	+	This server is always disabled by default and must be manually configured. This server is never added to the list of servers on updates or upgrades and can be added manually.
	+
	+	- Edit the server by double clicking on the it.
	+	- Edit the port number. This is typically always set to the default.
	+	- Add any optional arguments.
	+
	+	===== Arguments =====
	+	All fields are optional.
	+
	+	^ Argument ^ Description ^
	+	\| -i \| IP addresses of the system to bind on. Default is any IP address of the computer.\|
	+	\| -p \| Port number to listen for events on. Default is //9090//. To disable the HTTP interface and only use ARP set value to 0.\|
	+	\| -mwi \| MWI address to modify. Can be anything in the range 0-30. Default is 0. \|
	+	\| -anycall \| By default the system will not automatically configure the MWI unless the called or calling party is the DV2000. This setting tells it to accept changes whenever a call is made or received. This only works for Polycom phones and when the Incoming or Outgoing Call event is checked. \|
	+	\| -port \|This will add the port number to the SIP address.\|
	+	\| -arp \| Number of minutes to perform query. Minimum value supported is 10 minutes.\|
	+
	+	Example
	+	-i 192.168.100.10 -p 9090 -mwi 2 -anycall -port 5070
	+
	+	<WRAP center round tip 100%>
	+	Note when using a firewall you will need to add an exception for the port.
	+	</WRAP>
	+
	+	====== Polycom ======
	+	These events are configured via the phones administration interface.
	+
	+	===== Events =====
	+	The DV2000 supports most of the events. While these packets to the DV2000 are very small and will not prevent a phone from taking or receiving calls a typical configuration would be to only check //Line Registration//. Using the outgoing or incoming call events the phones MAC address will automatically be configured. This does require that the telephone extension match either the mailbox or extension number.
	+
	+	^ Type ^ Description ^
	+	\|Line Registration\|Whenever the phone registers with a PBX, an event is sent.\|
	+	\|Incoming Call\|Any outgoing call, the phone will post an event.\|
	+	\|Outgoing Call\|Any outgoing call, the phone will post an event.\|
	+	\|Onhook\|Anytime phone goes onhook, the phone will post an event.\|
	+	\|Offhook\|Anytime phone goes offhook, the phone will post an event.\|
	+
	+	==== Line Registration/Onhook/Offhook ====
	+	Using one of these events requires the telephones MAC address must be configured in the mailbox using Manager located under //Advanced//. The server will then find the first mailbox with the MAC address contained in the event and change that mailbox.
	+
	+	==== Incoming/Outgoing ====
	+	When using //Incoming// or //Outgoing// call, the DV2000 will attempt to match the called or calling number with either the mailbox number or the extension of the mailbox.
	+
	+	{{:images:vs8:vsconfig:polyconfig-phone.png\|?direct}}
	+
	+	Set //Notification URL// to the IP/DNS name of the DV2000 followed by the port and "/polycom".
	+
	+	Example:
	+	http://192.168.1.1:9090/ipcfg/polycom
	+
	+	===== Overrides =====
	+	The server will accept three additional parameters in the URL allowing individual telephones to control their own settings.
	+
	+	==== Mailbox ====
	+	Add ///<mailbox>// to the URL. The following will force the server to update mailbox 3101 regardless of the extension number it detects from the event.
	+
	+	Example:
	+	http://192.168.1.1:9090/ipcfg/polycom/3101
	+
	+	==== MWI Address ====
	+	To force an MWI address add ///<mailbox>/<number>// to the URL. You must specify the mailbox number for this option. In this example it will update the MWI address 4 in mailbox 3101.
	+
	+	Example:
	+	http://192.168.1.1:9090/ipcfg/polycom/3101/4
	+
	+	==== Port ====
	+	To force the address to have a custom port number add ///<mailbox>/<number>/<port>// to the URL. This will force the port number to always be set.
	+
	+	Example:
	+	http://192.168.1.1:9090/ipcfg/polycom/3101/4/5070
	+
	+	====== Other ======
	+	These phones perform a HTTP GET request for a specific action and all require the same URL parameters.
	+
	+	=== Required ===
	+	^Parameter^ Description ^
	+	\|ip\|IP address of the phone. Phone will automatically set this when set to //$ip//.\|
	+	\|mac\|MAC address of the phone. Phone will automatically set this when set to //$mac//.\|
	+	\|ext\|Extension number of the phone. Set this to either the extension or mailbox you want changed for this phone.\|
	+
	+	=== Optional ===
	+	\|port\|Port number to add to MWI address. Only needed when phone is not configured to use port 5060.\|
	+	\|mwi\|MWI address to use in the range 0-30. Default is 0.\|
	+
	+	===== Yealink =====
	+	Set the URL for Registered under //Features \| Action URL// on the telephones configuration screen. This can be changed at anytime without rebooting the phone.
	+
	+	=== Variables ===
	+	^ $ip \| The current ip address of the phone. \|
	+	^ $mac \| MAC address of the telephone. \|
	+
	+	Example
	+	http://192.168.1.1:9090/ipcfg/yealink?ext=3105&ip=$ip&mac=$mac
	+
	+	{{:images:vs8:vsconfig:yealink-phone.png\|?direct}}
	+
	+	===== Bittel =====
	+	Set the URL for Registered under //Phone \| Action URL// on the telephones configuration screen. The phone must be rebooted in order for the change to take affect.
	+
	+	=== Variables ===
	+	^ $ip \| The current ip address of the phone. \|
	+	^ $mac \| MAC address of the telephone. \|
	+
	+	Example
	+	http://192.168.1.1:9090/ipcfg/bittel?ext=3105&ip=$ip&mac=$mac
	+
	+	{{:images:vs8:vsconfig:bittel-phone.png\|?direct}}
	+
	+	===== vTech =====
	+	Under //Setup \| Action URL Settings// set the Setup finished field to the URL. This action is called following the telephone booting.
	+
	+	=== Variables ===
	+	^ $phone_ip \| The current ip address of the phone (the L2TP ip address if the phone is connected via L2TP and $local_ip otherwise) \|
	+	^ $mac \| MAC address of the telephone. \|
	+
	+	Example
	+	http://192.168.1.1:9090/ipcfg/vtech?ext=3105&ip=$phone_ip&mac=$mac
	+
	+	{{:images:vs8:vsconfig:vtech-phone.png\|?direct}}
	+
	+	====== Tips ======
	+	===== Quick Setup =====
	+	For the quickest setup configure telephones to send //Incoming Call// event. Then call the phone from the DV2000 using either a Message Delivery, Transfer or wakeup call. Performing these actions on a guest room which is occupied however isn't suggested.
	+
	+	===== Multiple Phones =====
	+	For those situations where there are multiple phones in a room the //Notification URL// can be modified on the additional phones to update a common mailbox using the additional ///<mailbox>// shown above.
	+
	+	===== Maid Status =====
	+	Another option is to set the even type to //Outgoing// and then each time a maid or anybody calls the DV2000 it will automatically be configured.

Homepage

Anonymous (anonymous@undisclosed.example.com) — 2025-05-30T15:25:12+00:00

2026/05/03 11:44	current
Line 1:	Line 1:
	+	~~NOTOC~~
	+	~~Title: Homepage~~
	+	<jumbotron color="#3F50B4">
	+	====== DuVoice Support ======
	+	DuVoice provides any hosted, on premise IP or legacy PBX a connection to the property management system, wake up calls and guest messaging all managed through a friendly web console for the staff. Unified messaging is available for staff or business customers.
	+
	+	<btn type="primary">[[vs8:home\|DV2000 v8]]</btn>
	+	<btn type="warning">[[sales:home\|Sales]]</btn>
	+	<btn type="info">[[integration:home\|PBX Integrations]]</btn>
	+	==== Product Demonstration ====
	+	Fully featured online demo of the DuVoice hospitality interfaces, including InnDesk, Inventory, Room status, and Tenant Care.\\
	+	<btn type="primary">[[https://demo.duvoice.com/user/login\|Demo]]</btn>
	+
	+	</jumbotron>
	+
	+	<grid>
	+	<col sm="6">
	+	<panel type="primary" title="Contact Us">
	+	== Sales ==
	+	^ Telephone \| 800-888-1057 \|
	+	^ Email \| sales@duvoice.com \|
	+
	+	== Office ==
	+	^ Monday - Friday \| 7am - 4pm PST \|
	+	^ Office \| 425-889-9790 \|
	+	^ Fax \| 425-889-8799 \|
	+	</panel>
	+	</col>
	+
	+	<col sm="6">
	+	<panel type="primary" title="Support">
	+	== US ==
	+	^ Telephone \| 425-250-2393 \|
	+	^ Email \| support@duvoice.com \|
	+
	+	== International ==
	+	[[http://www.duvoice.com/international-contacts/\|Click here]]
	+	</panel>
	+	</col>
	+	</grid>

Anonymous (anonymous@undisclosed.example.com) — 2024-01-11T17:49:22+00:00

2023/08/02 21:14		current
Line 9:		Line 9:
	* [[vs7:manual:home\|DV2000 v7 Manual]]		* [[vs7:manual:home\|DV2000 v7 Manual]]
	* [[help:home\|End User Help]]		* [[help:home\|End User Help]]
-	* [[howto:home\|HowTo]]	+	* [[howto:home\|HowTo / Troubleshooting]]
	* [[qa:home\|Q & A]]		* [[qa:home\|Q & A]]
-	* [[note:home\|Technical Notes]]
	* Resources		* Resources
	* [[sales:home\|Sales]]		* [[sales:home\|Sales]]

Phone MWI Integration

Anonymous (anonymous@undisclosed.example.com) — 2025-01-31T01:37:40+00:00

2026/05/03 11:44	current
Line 1:	Line 1:
	+	====== Phone MWI Integration ======
	+
	+	===== Preface =====
	+
	+	====== SIP Telephones ======
	+
	+
	+	==== vTech ====
	+	^ Interface ^ Documentation ^
	+	\| vTech \| <btn type="success" icon="fa fa-link" size="xs">[[phonemwi:vtech\| View]]</btn>\|
	+
	+	==== Polycom ====
	+	^ Interface ^ Documentation ^
	+	\| Polycom \| <btn type="success" icon="fa fa-link" size="xs">[[phonemwi:polycom\| View]]</btn>\|
	+
	+	==== Yealink ====
	+	^ Interface ^ Documentation ^
	+	\| Yealink \| <btn type="success" icon="fa fa-link" size="xs">[[phonemwi:yealink\| View]]</btn>\|
	+
	+	==== Bittel ====
	+	^ Interface ^ Documentation ^
	+	\| Bittel \| <btn type="success" icon="fa fa-link" size="xs">[[phonemwi:bittel\| View]]</btn>\|
	+
	+
	+	====== SIP Analog Gateways ======
	+
	+	==== Grandstream ====
	+	^ Interface ^ Documentation ^
	+	\| Grandstream GXW4224V2 \| <btn type="success" icon="fa fa-link" size="xs">[[phonemwi:grandstream:gxw4224v2:home\| View]]</btn>\|
	+
	+	==== Adtran ====
	+	^ Interface ^ Documentation ^
	+	\| Adtran 924e \| <btn type="success" icon="fa fa-link" size="xs">[[phonemwi:adtran:924e:home\| View]]</btn>\|
	+
	+	==== Audiocodes ====
	+	^ Interface ^ Documentation ^
	+	\| Audiocodes MP-124 \| <btn type="success" icon="fa fa-link" size="xs">[[phonemwi:audiocodes:mp124:home\| View]]</btn>\|
	+

DV2000 PMS Links

Anonymous (anonymous@undisclosed.example.com) — 2023-01-07T17:44:38+00:00

2026/05/03 11:44	current
Line 1:	Line 1:
	+	====== DV2000 PMS Links ======

Contact