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 and is suggested 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 5.31 or above.
• IP Office version 8 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.

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.

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.

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.

Only IP500 supports voicemail groups. If the location is using the DuVoice as the primary voicemail set the voicemail type to Group Voicemail, otherwise this setting can be anything. If Group Voicemail is not to be used for IP500, follow the instructions to configure forwarding short codes to use DuVoice voicemail 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.

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.

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

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.

Add the RestrictPhone notification template to each guest mailbox.

By default the DuVoice assigns the operator mailbox extension “0”. This will be dialed for transfers to the operator, Failed wakeup alerts, and possible 911 Emergency alerts. Avaya IP Office does not have a 0 extension by default. It is required to configure a shortcode that will direct calls to 0 to the appropriate extension or huntgroup. This will normally be the reception desk. The following example sends 0 to group 501.

This code is used when a maid enter a room pickes up the guest phone and dials a desired shortcode rather than the duvoice default of maids manually dialing duvoice and entering the 61N maid code. This is a optional features and you can use any available shortcode the customer needs/wants. In the following example, the DuVoice huntgroup is 7777 (This should be changed to match the huntgroup you have configured for DuVoice), and the shortcode used on the IPOffice is *61

For hospitality systems at least two User Rights groups must be created.

create the desired number of user rights templates for guests in various states. By default the DuVoice uses the names RESTRICTED for rooms which are checked out and UNRESTRICTED for those which are checked in.

These names are case-sensitive.

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

If your system was purchased as a kit please follow Installation and Setup from the manual.

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. The password is optional.

For more information see SIP Configuration in manual.

If this site is using Emergency Alerts (EAS) a configuration must be created for each PBX on location. This configuration can be found under the features tab on System Configuration.

For more information see the Manual under Emergency Alert.

These settings allow you to temporarily block alerts from the same extension for a specified number of seconds after an emergency number is dialed.

For example, if extension 1101 dials 911, an alert will be sent. If they hang up and then redial 911 again 10 seconds later and then again 5 minutes after that, that would normally generate a second and then a third alert. However, if this setting is set to 30 seconds, the second alert would be blocked while the third would be sent (since it occurred more than 30 seconds after the first alert).

Issues with using SNMP alerts:

• Only calls configured by the PBX as emergency will alert.
• Alerts may be delayed as much as one minute due to SNMP.

Set the SNMP Trap service in the Windows Services to Automatic and start the service.

Enable SNMP in System Events.

If the location is using the Forward ON/OFF shortcodes for DND then each guest mailbox must have the RestrictPhone notification added to the list of notifications.

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.

1. Login to IP Office Administration.
2. Go to the System settings.
3. Click on Voicemail tab
4. 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.
5. 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.