Release Notes for Avaya Distributed Office Release 1.1.1

Release Notes Issue 1.0, October 3, 2007

Installation and Upgrade Notes  If you connect any IP phone (9600-, 4600- or 1600-series IP Telephone) to the Power over Ethernet (PoE) ports of the Distributed Office platform before the entire system has been configured and initialized, then the phone will obtain an IP address in the default range of 192.168.0.10 through 192.168.0.130; you must reset the phone manually (with a power cycle) to force it obtain a new IP address from the specified range of addresses.

Initial Installation using Assistants

 If you are creating a new profile and modeling the Administrative Users Accounts page, you must permit access to the Access Security Gateway (ASG) tab or else it will be disabled after completing the Setup Assistant. Note that in all default profiles, the user is permitted access to the ASG tab in assistance mode.

 The Setup Assistant may time out after a long session followed by a brief period of inactivity. To resume the Assistant, log in and then point your browser to https://x.y.z.w/lba/index.php?runMode=interactive&taskID=2, where x.y.z.w is the IP address of the device.

 In assistance mode, do not use the “SNMPv1 Enable, SNMPv3 Enable” value in the SNMP Agent Status field on the Data Services Status screen.

Supported Platforms/Configurations  For this release, the Avaya Distributed Office i120 platform supports the use of two MM720 (ISDN BRI) Media Modules. Distributed Office Local Manager does not limit the number of MM720 modules a user can configure. Do not configure more than two such modules, as this makes the system fail and enter recovery mode.

 Distributed Office Local Manager is not supported under Microsoft Windows Vista using Internet Explorer 7 or later.

Known Issues and Workarounds  If a conference call is originated across two PSTN trunks using line appearances on a 1600- series telephone, and additional 1600-series phones join the call (before or after the conference has been established), then using the Exclude button on the original 1600-series phone will drop only one of the additional 1600-series callers on the other line appearances.

 The dial plan extension length can be changed using the Install from Scratch Assistant, which is loaded after erasing the system’s configuration (e.g. an NVRAM init). You cannot change the dial plan extension length by erasing ONLY the Telephony Configuration and rebooting the system, since in this case the Install from Scratch assistant does not load.  In very rare cases, Distributed Office Local Manager may not respond. If this occurs, wait two to three minutes and try again.

 If you place a call on hold and then unhold the call on Cisco 7905/7912 phones, the call will drop. Avoiding using "hold" on these phones. This only occurs on Cisco 7905/7912 phones.

 If you delete a large number of “zombie” mailboxes in Distributed Office Local Manager and the deletion operation fails, then a long message is displayed in the Distributed Office Local Manager status bar. This can cause duplication of the status bar background on the screen.

 You cannot change the call-appearance button number while it is referenced by bridge- appearance on another station. You need to remove the bridge-appearance, change the call- appearance button and then change the bridge-appearance to refer to the new call- appearance button.

 The Automated Attendant "Name" and "Outgoing Email" fields are colored yellow in Microsoft Internet Explorer 6.0.2800. The functionality of the page is not affected.

 In Distributed Office Local Manager on the pages that have the capability to upload and save automated prompts, you cannot upload a second prompt file after uploading and saving a prompt. In order to upload a different prompt, reload the web interface page by pressing the corresponding link in the navigation pane, navigating to the relevant tab, and reselecting the 'Get' button. This applies to the Automated Attendants' Temporary Schedule, Day Menu, Night Menu and Sub Menus pages in Distributed Office Local Manager.

 When adding a Bridged Appearance Button to a station using the Buttons tab on the Distributed Office Local Manager Users page, always select the “Bridge to” extension by using the drop-down list.

 CPN confusion (or even inadvertent call rejection) may occur in the following administrative scenario. Your system has one or more ISDN public trunk groups (BRI or PRI type), and has been installed or upgraded (using certain profiles) and/or subsequently modified (using the Dial Plan screen under Telephony in Distributed Office Local Manager) to change a value for the “Call Type” field on any “First Digit” row from “dac” or “Unused” to “ext”, and you have any entries on the ISDN Numbering Public Unknown screen that match the following: 1. “ISDN Trunk Group” field value is “all” 2. “Digits to Prefix to Form Calling Party Number (CPN)” field is blank 3. “Total CPN Length” field value is the same as your Dial Plan extension “Length”. If your Distributed Office system administration matches this scenario, calls to the public network sent over your ISDN trunks may use the extension number of the CPN, thereby confusing the called party, or even be rejected by the central office as being from invalid numbers, in certain rare cases. To fix this, you must manually remove (or correct such that a proper public number is sent for) the matching entries on the ISDN Numbering Public Unknown screen under Public Networking in the Telephony area of DOLM. Adding an entry for each first digit of an extension should be a standard administrative operation.

 Avaya recommends avoiding asymmetrical media encryption settings between Distributed Office locations.  Adding trusted root certificates in Distributed Office Release 1.1 or 1.1.1 is not supported.

 Third-party certificate authorities are not supported in this release of Distributed Office.

 Distributed Office Release 1.1 and 1.1.1 only support the CCITT u-Law 8.000 kHz, 8-bit, Mono format for Music-on-hold files.

 Calls from another branch that are parked at a branch endpoint will be dropped after 40 seconds if Music-on-hold has not been enabled. Parked calls from within the same branch, whether calls made from a local endpoint or outside PSTN calls, do not drop in 40 seconds.

Best Practices

Configuring and Customizing  Set only one type of language (US-English, Spanish, etc.) in each slot, and do not to update language packs across slots (for example, downloading a Spanish language pack to a previously US-English slot).

 When the primary language in monolingual mode is the language in slot 2, you can record a personal greeting but not delete it, so you cannot return to the default system greeting. However, you can re-record your greeting

 If you change the time zone, the date may not be updated automatically. Check the updated time and date and configure them manually if necessary.

 If you administer a SIP station and enter an extension number that is already in use by another station, you will not get an error. However the SIP station will not function and will not receive dial tone on call appearances. Do not administer multiple stations with the same extension.

 When duplicating a user whose station is assigned with an analog port, the analog port is displayed as an unassigned (and selectable) port even though it is already assigned to the user being duplicated. Selecting this port for the new user will fail. Select a different analog port when duplicating such a user.

 In order to change a Trunk group for an existing ICHT entry, delete the ICHT entry and re- add it with new trunk group.

 When a specific port number has been selected to be the mirror port, do not select it also for use in port redundancy.

 Before replacing the media module with a different type of media module in an i120, completely clear the configuration on the slot and check the Physical Configuration page to verify that the slot is empty.

 When a non-default option is chosen for the country code using Distributed Office Local Manager, the customized tones are not deleted automatically. This may cause system resource issues, depending on the option chosen. Delete the customized tones before you change the default country code.  If you attempt to configure an auto-attendant announcement with a name but no actual prompt file, Distributed Office Local Manager will use a "dummy" prompt file. This dummy prompt will be played later via auto-attendant menus. Delete the announcement or download a new announcement file.

 In Release 1.1 or 1.1.1 of Distributed Office application enablement, CTI support for the Avaya 3410 Wireless Telephone is NOT available. This limitation is an addendum to those listed in the "Limitations" section in Chapter 2 of Installation, Configuration, and Troubleshooting Guide for Avaya Distributed Office application enablement.

Operating Features  After changing the SIP domain, you need to reset the device in order to work with the new domain

 You can only use pre-defined time zones.

 Delete multiple announcements one-by-one in Distributed Office Local Manager, rather than selecting multiple announcements and clicking Delete.

 The login authentication times out after approximately 40 seconds, and technicians cannot access the Distributed Office using the “connect2” tool. If this happens: o Make sure the primary DNS server is accessible. If not, remove DNS configuration o Increase timeouts in 'connect2'

 It is not recommended to use the FTP server of Microsoft Internet Information Server (IIS) version 5.0, which comes as part of the Windows 2000 operating system, for backing-up or restoring a Distributed Office configuration. Problems were encountered using the IIS FTP server in the "Win2000 Server" edition, build 5.00.2195, Service Pack 4.

 Do not remove a coverage path until you have verified that no users have this path assigned, as no warning is given that the deleted path is in use.

 WU FTP is not supported as an FTP (file transfer protocol) server (for backup/restore, upload/download, etc.) Use other FTP servers from the supported servers list.

 Do not create paging groups in Distributed Office of more than 20 members for an i120 and not more than 6 members for an i40.

 If you are performing an NVRAM init, then assign a different IP address for the Distributed Office platform after the NVRAM init than the statically assigned IP address configured in the IP phones before the init. After finishing the full device configuration, you may add back the IP address that was statically assigned and configured in the IP phones.

 Do not remove the mailbox named “KEY”, which appears in some constructs on the Mailbox Usage Report page.