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.

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

• DuVoice 8.0 or above.
• IP Office version 12 and above.
  • Known working on:
    • 12.0
    • 12.1
    • 12.2
    • 12.3
• LAN connection.
• IP Office manager software is required to be installed on the DuVoice server:
  • Allows for easier programming and troubleshooting.
  • Required for hospitality integration.
    • See DLL section under hospitality integration below.
• 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 be disabled.

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.

Create a new shortcode to create a process for housekeeping to punch in codes with.

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.

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.

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.

For IPO v12.0+, hospitality integration requires DLL fix.

The HowTo article on this DLL fix, can be found here.

Ensure an Avaya technician has installed IP Office Manager Suite application onto the DuVoice server.

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.

Refer to the EAS HowTo page here.