All configuration is performed from the Avaya IP Office Manager application. This application can be installed on the DuVoice system without interfering with the DuVoice operation. This is highly reccommended for easy configuration checks by DuVoice technical support.

• Name display change.
• User rights changes (COS).
• Message Waiting (MWI) set/clear.
• Emergency Alert Notification (EAS).
• DND via Call Forward All.

• DuVoice 8.0 or above.
• IP Office version 12 and above.
• CTI Pro if using:
  Emergency Alert Notification. (required on every IP Office system that will be monitored)
  TAPI, which is only used Station Monitor and for Analog integration. Typically not used for SIP based systems.
• Lan connection.
• IP Office manager software should be installed on the DuVoice system for easier programming and troubleshooting.
• One license of 3rd Party IP Endpoints for every line of DuVoice.
• Voice Compression Module. Example: VCM64/ATM4.

Ports which should be unblocked for incoming network traffic between Avaya IPO and DuVoice Application.

When configuring an IP Office Server solution you must manage users, extensions and groups discussed here on the server and not under Solution. If you have additional IP500's connected to the solution it is suggested to manage them via that specific Server rather than under Solution.

IP500 and Server Editions are configured the same with the exception of voicemail support and optional changes for forwarding.

These changes must be made by logging into the security configuration of the PBX using Avaya IP Office Manager located under File | Advanced | Security Settings….

Login using the security account.

Default username and passwords:
User Name: security
Password: securitypwd

These settings allow the DuVoice to change names and other settings. For Emergency Alert (EAS) DevLink is required. TAPI is required if using Station Monitor.

The IP Office name change interface requires a valid certificate on the IP Office. If this certificate is expired then name changes and CTI interfaces will fail. Typically there is no need to manage this section but it's noted here to verify proper configuration.

Note: DuVoice does not support TLS.

A SIP extension must be created for each line of DuVoice.

A User must be created for each extension created.

Remove all line appearances expect for Button 1.

Create a huntgroup for the DuVoice lines.

This feature should not be enabled.

It is suggested to create a group for the operators and set the overflow to be directed towards that group.

This feature should be disabled for this group.

This feature should be disabled for this group.

This feature should be disabled for this group.

Only IP500 supports voicemail groups. If the location is using the DuVoice as the primary voicemail set the voicemail type to Group Voicemail in the IPOffice System>Voicemail Tab, otherwise this setting can be anything. If Group Voicemail is not to be used for IP500, follow the instructions to configure forwarding short codes or in conjunction with Embedded or Voicemail Pro. If using IPO Server Edition, Group Voicemail is not an option and the forwarding short codes will need to be used for DuVoice voicemail.

If you are configuring shortcodes on a IPO Server Edition, all shortcodes should be configured at the Solution level.

When using IP Office Server Edition with multiple IP Offices at a single location this shortcode is required.

Used to set MWI for a station.

Used to clear MWI for a station.

This code is used when a guest room requests do not disturb (DND) on. This is only required when DuVoice is not the Group voicemail for the system because setting DND for a user does not use the forward settings.

This code is used when a guest room requests do not disturb (DND) off. This is only required when DuVoice is not the Group voicemail for the system because setting DND for a user does not use the forward settings.

DuVoice typically assigns the operator mailbox extension “0”. This will be dialed for transfers to the operator, Failed wakeup alerts, and possible 911 Emergency alerts. IP Office does not have a 0 extension by default therefore it's required to configure a shortcode that will direct calls to 0 or the appropriate extension/group. Typical installations this is the reception desk.

For hospitality systems at least two User Rights groups must be created. By default the DuVoice uses the names RESTRICTED for rooms which are checked out and UNRESTRICTED for those which are checked in. Group names are case-sensitive so care should be taken when creating them.

For staff and guest phones using the DuVoice as their voicemail follow these steps.

SNMP method is prefered over CTI Pro method, as it's generally more stable and less resource intensive.

For SNMP alerts the IP Office must be configured to send system events to the DuVoice system.

System Events are configured from the System settings.

Add an SNMP Trap

SNMP Emergency alerts only work if a number dialed is specified as Dial Emergency in the ARS. In the configuration example below a route for 911 has been configured as well as 811 which we've configured to dial an extension number rather than emergency. Having a number like 811 allows the site to verify emergency alerts are working without calling the authorities. You will need to add 811 to the list of numbers to monitor.

The IP Office must have a CTI Pro License. To check this, open the IP Office configuration application and look for CTI Link Pro under the License tab, as shown below.

The setup wizard only asks for the basic configuration settings and additional configuration must be performed in System Configuration.

From the DuVoice server, run System Configuration from the DuVoice folder under startup.

For each IP Office at a location a separate profile is required in order to perform name changes.

When using multiple IP Office's at a site, you must create a new profile for each of PBX. Then configure all the guest mailboxes located on a specific PBX within it's own profile. This is due to the Avaya User Configuration API not currently supporting changing names and class of service across a solution.

Enable each line to register. If you chose to require the DuVoice lines to login enter a user account and password for each line. The IP Office defaults to the extension number as the account.

Add the RestrictPhone notification template to each guest mailbox.

SNMP method is prefered over CTI Pro method, as it's generally more stable and less resource intensive.

Windows must be configured to receive SNMP traps using the SNMP Trap service. Without this setting no alerts will be detected.

From the services control panel find SNMP Trap.

1. Set Startup type to Automatic.
2. Start service.

From Features | Emergency Alert, click Add

1. Choose Avaya IP Office SNMP for PBX.
2. Enter a description of this PBX to help with reporting.
3. If you will be alerting via SNMP from multiple IP Office systems, enter the IP address of for this system in PBX DNS Name or IP.
4. Add any addresses to alert using the Address List tab.
5. Once all configured, click OK.

Note: If you are alerting via SNMP from multiple IP Office systems. Create a server configuration for each one. This will prevent duplicate alerts when the IP Office uses small community networking.

From Features | Emergency Alert, click Add

1. Choose Avaya IP Office DevLink for PBX.
2. Enter a description of this PBX to help with reporting.
3. Add any addresses to alert using the Address List tab.
4. Enter the IP address of the PBX in PBX DNS Name or IP field.
5. Once all configured, click OK.

Change TLS to 1.0 (from 1.2). Note: If your organization prevents changing the TLS level to 1.0 for security reasons, it can be added manually. Avaya distributes the required DLL files need for TLS 1.2 along with Avaya IP Office Manager. Refer to 'For IP Office v12.1' section below for more details regarding this procedure.

1. Shutdown the DV2000.
2. Optionally backup the DLL files listed below (from the DuVoice folder) in case the ones from you IP Office Manager do not work.
3. Copy all DLL files from the Avaya IP Office Manager installation folder to the DV2000 installation folder.
   These files are located in C:\Program Files (x86)\Avaya\IP Office Admin Suite\Manager and should be copied to C:\Program Files (x86)\DuVoice DV2000.
   These files are:
   • LegacySettings.dll
   • SecurityManager.dll
   • UpgdWiz.dll
   • WhoIs2.dll
   • WindowsControlLibrary.dll
   • ValidationVisability.dll
   • CoreServices.dll
4. Optionally, create a seperate backup the DLL files listed above in case you need to readd them after performing a DuVoice patch update.
5. Start the DV2000.
6. Test using either IPOViewer or performing a name change.

If the IP Office displays the following dialog choose Retain. This is because the DuVoice system has made changes to the PBX since the last time Manager has been run.

This is a problem with the Avaya TAPI driver which is used to enable/disable DND for a user. This is typically not a problem, however when using forwarding on users rather than configuring the DuVoice system as the voicemail it can occur.

Disable support for DND in the profile.

On upgrades and by default the IP Office is configured so that the message button sends user to visual voicemail rather than the voicemail system defined.

Note: The message button cannot be used on Server Edition because it does not support voicemail of type group. If using a non-server edition the steps below can be used to resolve it.

• Login to IP Office Administration.
• Go to the System settings.
• Click on Voicemail tab
• Uncheck Messages Button Goes to Visual Voice. You may need to set the voicemail type to something besides Group Voicemail if it's disabled long enough to uncheck the box.
• Save changes and merge the configuration.

The IP office monitor application is really nice, however it has one major flaw in that it will not time/date stamp the entries.

You can change this behavior by checking the following two fields on the System tab.

Prefix YYYY-MM-DD hh:mm:ss:mss Date/Time Periodic Prints

This is typically caused because the extension is configured for voicemail and the DuVoice is not the primary voicemail. Typically the IP Office is configured to use it's own voicemail and when the DuVoice sends a code to turn the light on it will do it, but then immediately turn it off because the IP Office's internal message queue for the extension says it has no messages.

The fix in this case is to disable voicemail for the extension. If this is done you must confirm that the extension is using forwarding in order for the DuVoice to act as it's voicemail mailbox. If the extension is to use the IP Office for it's voicemail you must delete the mailbox which corresponds with this extension in the DuVoice or disable voicemail in mailbox's class of service.

Typically this is due to the fact the system does not have Voice Compression Module.

The recommended no answer time is 25 seconds.