RN Rev 09. Release Notes Release 1.2.1p2

Transcription

1 RN Rev 09 Release Notes Release 1.2.1p2

2 Aastra Telecom will not accept liability for any damages and/or long distance charges, which result from unauthorized and/or unlawful use. While every effort has been made to ensure accuracy, Aastra Telecom will not be liable for technical or editorial errors or omissions contained within this documentation. The information contained in this documentation is subject to change without notice. Copyright 2009 Aastra Telecom. All Rights Reserved.

3 Contents Chapter 1 Software Release 1.2.1p2 Overview Feedback Release numbering Details of this release Pre-requisites AastraLink Pro System Software IP Phone firmware Chapter 2 Release 1.2.1p2 Upgrade Procedures About this chapter Upgrade Procedure Description Pre-Upgrade Steps (for all software versions) Upgrade Procedure (for software version 1.2 or higher) Upgrade Procedure (for software version 1.1p1 or lower) Manually Upgrading Your MBU 400 in Your AastraLink Pro Network Chapter 3 Features and Fixes in Release 1.2.1p2 New Features in Release 1.2.1p Descriptions More Timezones Supported on the AastraLink Pro Adding Timezones AastraLink Pro 160 and MBU 400 Release Issues Resolved in Release 1.2.1p Description RN Release 1.2.1p2, Rev 09 iii

4 Chapter 4 Known Issues in Release 1.2.1p2 Known Issues Documentation Issues Supported and Unsupported Codec Behavior on the AastraLink Gain Plan on AastraLink to Compensate for Telco PAD Chapter 5 Release 1.2.1p2 Downgrade Procedures About this chapter Downgrade Procedure Description Downgrade Procedure (from software 1.2.1p2 to or 1.2) Downgrade Procedure (from software 1.2.1p2 to 1.1 or 1.1p1) Chapter 6 Software Licensing and Copyright AastraLink Pro 160 Release 1.2.1p2 Software Licensing iv RN Release 1.2.1p2, Rev 09

5 Chapter 1 Software Release 1.2.1p2 Overview Introduction About this release AastraLink Pro 160 software release 1.2.1p2 is a patch release delivering new features and fixed issues to the AastraLink software since the release of 1.2.1p1. IMPORTANT: Always backup your system configuration via the AastraLink Web UI, prior to upgrading to a new release. Feedback You MUST have release 1.1 or later already installed on your AastraLink Pro 160 before installing Release 1.2.1p2. For more information about upgrading your AastraLink Pro 160, see Chapter 2, Release 1.2.1p2 Upgrade Procedures in these Release Notes. Please provide any feedback regarding the content of this document to RN Release 1.2.1p2, Rev

6 Introduction Release numbering AastraLink software releases are provided in two categories: Major releases are labeled with M.m release number, e.g. 1.0, 1.1 etc. Maintenance releases are labeled with M.m.n and add a maintenance number to the label, e.g Patch Releases are labeled with M.m.np# and add a patch number to the label, e.g p2. The "M" is the major release, defining the main feature set of the platform. The "m" is the minor release, defining the incremental feature set. The "n" is the maintenance release, defining the collection of post-release fixes. The "p" is the patch release, defining patch fixes to maintenance releases. The "#" is the number associated with the patch release. Standard and maintenance releases may have an associated build number, which is used internally by Aastra to track Beta versus General Availability releases. 1-2 RN Release 1.2.1p2, Rev 09

7 Details of this release Details of this release Pre-requisites This release is suitable for use with any AastraLink Pro system running 1.1 or later. Customers with AastraLink Pro systems using earlier software versions or pre-release alpha/beta code cannot directly upgrade, and should contact Aastra customer support for details of the appropriate installation procedure. AastraLink Pro System Software The AastraLink Pro system software resides on the externally accessible CompactFlash card. This is upgraded in-place by uploading a vnx.dra file via the Administrator s web interface. After updating the system software, the bootloader firmware residing on the internal boot flash will also be updated to the corresponding version. IMPORTANT: Updated boot firmware for the AastraLink Pro onboard flash is included in this patchkit. The boot firmware will be automatically installed after the CompactFlash upgrade has completed. The system is not considered fully upgraded until the Software and the bootloader firmware have both been upgraded to the same software version. Running with different CompactFlash and Onboard flash versions may result in service degradation and is not a supported configuration. Any customer contacting Aastra for support will be required to update the system boot firmware to the correct version prior to receiving assistance. RN Release 1.2.1p2, Rev

8 Details of this release IP Phone firmware This AastraLink Pro 160 software release incorporates IP phone firmware release and up for the following phones: 9143i 9480i 9480i CT 6751i 6753i 6755i 6757i 6757i CT 6730i 6731i In addition, the AastraLink Pro 160 software supports the M670i and M675i Expansion Modules, and 1.30 firmware of the Mobility Base Unit (MBU 400) and DECT 420d handsets. 1-4 RN Release 1.2.1p2, Rev 09

9 Chapter 2 Release 1.2.1p2 Upgrade Procedures About this chapter This chapter provides important information and procedures for upgrading your AastraLink Pro 160 to Release 1.2.1p2. IMPORTANT: Releases 1.1 and later are supported for upgrade to 1.2.1p2; if you are running a prior release of software, please upgrade to 1.1 first before attempting to upgrade to Release 1.2.1p2. This chapter also includes a procedure to manually upgrade your MBU 400 and all associated handsets to release 1.30, if necessary. RN Release 1.2.1p2, Rev

10 Upgrade Procedure Upgrade Procedure Description Use the upgrade procedures in this section if: you currently have 1.2 or higher version loaded on your AastraLink Pro and want to upgrade to a higher release. ( Upgrade Procedure (for software version 1.2 or higher) on page 2-3) OR you currently have 1.1p1 or a lower version loaded on your Aastralink Pro and want to upgrade to a higher release. ( Upgrade Procedure (for software version 1.1p1 or lower) on page 2-4) Pre-Upgrade Steps (for all software versions) Pre-upgrade Steps (for all software versions) Step Action 1 Login to the AastraLink Web UI using your Administrator phone extension and password. 2 Navigate to the location Maintenance->Backup & Restore and click <Backup>. This downloads a copy of the current version database to the file backup.abf. Store this backup file safely on your PC. It may be required at a later time if you need to downgrade the AastraLink for any reason. 3 Using the 'About' link at the top-right of the page, note the software version currently installed. To upgrade from version 1.2 or higher, use the Upgrade Procedure (for software version 1.2 or higher) on page 2-3. To upgrade from version 1.1p1 or lower, use the Upgrade Procedure (for software version 1.1p1 or lower) on page RN Release 1.2.1p2, Rev 09

11 Upgrade Procedure Upgrade Procedure (for software version 1.2 or higher) Upgrade Procedure (for software version 1.2 or higher) Step Action 1 From the Administrator Web UI, navigate to the location Maintenance->Update->Manual Update. 2 In the Check for Updates Now field, click the Check link. The AastraLink searches for updates (latest software) on the Aastra Public Server. If an update to your software exists, a prompt displays asking you if you want to update your AastraLink. 3 Click <Yes> to update your AastraLink. or Click <No> to cancel the update. The software update process may take up to 15 minutes and MUST NOT be interrupted. While the software update is in progress, the AastraLink LED front panel shows alternating GREEN/ RED. IMPORTANT: NEVER power off or reset the AastraLink Pro while the LED shows alternating GREEN/RED as the system may become corrupt and not able to boot. 4 When the upgrade process has completed, the AastraLink Pro in the Ready state shows the LED slow flashing GREEN. Login to the AastraLink Web UI using your Administrator phone extension and password. 5 Confirm that your system is now running release 1.2.1p2 software by navigating to the 'About' link at the top-right of the AastraLink Web UI. 6 (For systems running 1.2 version) For systems using FXO lines only: After upgrading, you must confirm that the echo tail length is set to a suitable value. The recommended default value is 48ms. For more information about echo tail length, see the AastraLink Pro Administrator Guide. Note: You can run per-line FXO tuning if required. For more information, see the AastraLink Pro p1 Release Notes. RN Release 1.2.1p2, Rev

12 Upgrade Procedure Upgrade Procedure (for software version 1.1p1 or lower) Upgrade Procedure (for software version 1.1p1 or lower) Step Action 1 Using your PC s web browser, download the 1.2.1p2 software vnx.dra file from the following Aastra support Web site: This file is 60MB in size and may take several minutes to download to your PC. 2 From the Administrator Web UI, navigate to the location Maintenance->Update/Manual Update and browse to the vnx.dra file you just downloaded. Click <Upgrade> to transfer the file onto the AastraLink. 3 After uploading the new vnx.dra, the Web UI prompts you to confirm a reboot to begin updating. Select <Yes>. The software update process may take up to 15 minutes and MUST NOT be interrupted. While the software update is in progress, the AastraLink LED front panel shows alternating GREEN/ RED. IMPORTANT: NEVER power off or reset the AastraLink Pro while the LED shows alternating GREEN/RED as the system may become corrupt and not able to boot. 4 When the upgrade process has completed, the AastraLink Pro in the Ready state shows the LED slow flashing GREEN. Login to the AastraLink Web UI using your Administrator phone extension and password. 5 The system prompts you to run the FXO line tuning wizard. If your system has FXO lines connected, it is recommended to select <Yes> then click on the Auto Tuning button and follow the prompts. Otherwise click <No> to cancel this dialogue box. 2-4 RN Release 1.2.1p2, Rev 09

13 Upgrade Procedure Upgrade Procedure (for software version 1.1p1 or lower) Step Action 6 Confirm that your system is now running release 1.2.1p2 software by navigating to the 'About' link at the top-right of the AastraLink Web UI. 7 For systems using SIP trunks: Navigate to the location Configuration->VoIP->SIP trunks and delete the contents of the REALM field for any existing SIP trunks, and ensure the AUTH NAME and USERNAME fields are set correctly. Verify that all SIP trunks show Registered status at the location VoIP->SIP trunks Note: If you have more than one SIP trunk configured, ensure the SIP trunk mode is set to "Multiple" at the location Configuration->Dialplan, otherwise only the first SIP trunk will be usable. RN Release 1.2.1p2, Rev

14 Upgrade Procedure Manually Upgrading Your MBU 400 in Your AastraLink Pro Network If you have an MBU 400 with a release prior to 1.30 in your AastraLink network, after upgrading your AastaLink to release 1.2.1p2, the MBU is automatically updated to If the MBU does not update automatically, you can manually update the MBU in your network using the following procedure. Manual Upgrade Procedure for the MBU 400 Step Action 1 Follow the procedures for upgrading your AastraLink Pro to release 1.2.1p2 using the procedures defined previously. 2 After the AastraLink Pro upgrade is complete, on the 420d Handset, press the OK key (center circle black button). 3 Select Settings->System Settings->Firmware Update. 4 Select the 1.30 firmware. The MBU 400 and all associated 420d handsets are upgraded. The upgrade is complete when the 420d handset displays Upgraded to v RN Release 1.2.1p2, Rev 09

15 Chapter 3 Features and Fixes in Release 1.2.1p2 Introduction This chapter describes the new software features of the AastraLink Pro 160 running Software Release 1.2.1p2, and fixes for problems reported in release software operation. Features and fixes listed here are incremental to release Please refer to previous release notes for details of prior release feature sets. IMPORTANT NOTE REGARDING FXO TELEPHONE LINES The AastraLink Pro 160 FXO ports were designed for connection to direct-dial PSTN lines. The product may not operate correctly if connected to a line which does not provide direct-dial PSTN capability (for example, Centrex lines and PBX extensions, where a prefix digit must be dialed to obtain secondary PSTN dialtone.) RN Release 1.2.1p2, Rev

16 New Features in Release 1.2.1p2 New Features in Release 1.2.1p2 Descriptions This section provides the new features in AastraLink Pro 160 Release 1.2.1p2. Each feature also specifies whether the feature applies to an Administrator, Service Administrator, User, or all of the above. Feature More Timezones Supported on the AastraLink Pro (Administrator and User) AastraLink Pro 160 and MBU 400 Release 1.30 Description The AastraLink Pro now supports more timezones, allowing for installation in even more countries throughout the world. When these timezones are enabled, a User can select the applicable timezone on their phone or via the AastraLink Web UI. The AastraLink Pro 160 Release 1.2.1p2 supports the MBU 400 firmware Release (Administrator) 3-2 RN Release 1.2.1p2, Rev 09

17 New Features in Release 1.2.1p2 More Timezones Supported on the AastraLink Pro The AastraLink Pro 160 now supports a wide variety of timezones, which allows you to install the AastraLink Pro in locations all over the world. The Administrator phone on the AastraLink network must be configured with the applicable timezone before the AastraLink Pro can provide them to other phones on the network. Note: The IP Phones acquire the timezones upon synchronization with the AastralLink at boot time. They use the current value of the system clock from the AastraLink, offset from UTC (i.e., minutes east or west from GMT). When the local time on the AastraLink changes for Daylight Savings Time (DST), the IP Phones are not aware of the change until the next reboot. Therefore, after each DST transition (twice per year), the IP Phones must be rebooted manually to re-sync the timezone offset from the AastraLink. The following procedures describe how to enable the timezones in the AastraLink Pro network. RN Release 1.2.1p2, Rev

18 New Features in Release 1.2.1p2 Adding Timezones Use the following procedures to add timezones to the AastraLink Pro network.. AastraLink Pro 160 Administrator IP Phone UI Step Action Configure the Administrator phone with timezones. 1 After the AasraLink Pro 160 has booted fully (status light should be blinking green) plug the Administrator phone into the same network as the AastraLink, and supply power to the phone. When the phone boots up, the Administrator is presented with different configuration options on the Phone UI (User Interface) as indicated in the next several steps. 2 System Language 1. English 2. Francais 3. Espanol Choose the applicable system language and press <SELECT>. 3 Country 1. United States 2. Canada 3. Mexico 4. Other Choose "Other" and press <SELECT>. 4 Timezone From the list of timezones, choose the applicable timezone and press <SELECT>. For a list of timezones, refer to your AastraLink Pro 160 User Guide or AastraLink Pro 160 Administrator Guide. 5 Date & Time 1. Automatic 2. Manual Choose "Automatic" and press <SELECT>. 3-4 RN Release 1.2.1p2, Rev 09

19 New Features in Release 1.2.1p2 AastraLink Pro 160 Administrator IP Phone UI Step Action 6 Optional Settings 1. Edit Options 2. Use Default Choose "Use Default" and press <SELECT>. This option uses a three digit extension plan. If a four digit extension plan is desired then choose "Edit Options". 7 In the "First Name" field, enter the Administrator s first name using the phone s keypad. 8 In the "Last Name" field, enter the Administrator s last name using the phone s keypad. 9 In the " Address" field, enter the Administrator s address using the phone s keypad. Use the # key to scroll to sign. 10 In the "Password" field, enter the password. This is used in combination with the Administrator s extension to log into the AastraLink Pro Web UI. The Administrator phone reboots, and registers with the AastraLink Pro. RN Release 1.2.1p2, Rev

20 New Features in Release 1.2.1p2 AastraLink Pro 160 Web UI Step Action Set the timezones on the AastraLink Pro. 1 Login to Aastralink Pro Web UI as Administrator (i.e. username 200 or extension name of your administrator and default password 22222). 2 Navigate to the Configuration -> System -> Regional Settings page. 3 In the Location field, select "Other". 4 In the Timezone field, select the applicable timezone for your location. For a list of timezones, refer to your AastraLink Pro 160 User Guide or AastraLink Pro 160 Administrator Guide. 5 Click <SAVE> to save your settings. 3-6 RN Release 1.2.1p2, Rev 09

21 New Features in Release 1.2.1p2 AastraLink Pro 160 and MBU 400 Release 1.30 The AastraLink Pro 160, Release 1.2.1p2 now supports MBU 400 Release 1.30 firmware. When enabled on the AastraLink Pro 160, all timezones configured on the AastraLink Pro can also be used with the MBU 400 system. Note: The MBU acquires the timezones upon synchronization with the AastralLink at boot time. It uses the current value of the system clock from the AastraLink, offset from UTC (i.e., minutes east or west from GMT). When the local time on the AastraLink changes for Daylight Savings Time (DST), the MBU is not aware of the change until the next reboot. Therefore, after each DST transition (twice per year), the MBU must be rebooted manually to re-sync the timezone offset from the AastraLink. RN Release 1.2.1p2, Rev

22 Issues Resolved in Release 1.2.1p2 Issues Resolved in Release 1.2.1p2 Description This section summarizes the fixes in Release 1.2.1p2 for issues found in Release and earlier. Issue CLN18113 DEF17815 DEF17885 DEF18107 DEF18193 Description Previously, when a User created a BLF list for an expansion module connected to their own phone, all extensions including the the User s extension were populated. A User was also permitted to create a BLF softkey for their own phone. Now, the AastraLin k Pro does not allow the User to include their own extension when configuring a BLF List or when creating a BLF softkey. In some cases, Users cannot hear the other party on their extension, the FXO lines appear as "in-use" and no one is on the phone. This issue was caused by the local Telco not disengaging the FXO lines, and thus the FXO lines would freeze. This has now been corrected. In some cases, the extension 200/operator was in an idle state and rang when an incoming call was recieved, but no audio was heard, even though audio was being transmitted from extension 200/operator. Also, the BLF LEDs were lit up on all phones indicating that extension 200/operator was in use. This issue was caused by the local Telco not disengaging the FXO lines, and thus the FXO lines would freeze. This issue has been corrected. A stuttered tone (change in tone) was heard when making an outgoing FXO call. When the FXO was configured for SLA, only one tone was heard. If in non-sla mode, two tones were heard. This issue has been corrected for outgoing FXO calls. Tones are no longer heard during SLA and non-sla calls. In the AastraLink Web UI, at the location Configuration->System->Set Date/Time, the time was being displayed in UTC format instead of the local time for the applicable timezone. This has been corrected and the "Time" field now shows the correct local time for the configured timezone. 3-8 RN Release 1.2.1p2, Rev 09

23 Issues Resolved in Release 1.2.1p2 Issue DEF18219 DEF18231 Description In the AastraLink Pro Web UI, at the location Configuration->System->Regional Settings, if you set the "Time Format" field as 24 hours, the "Time" field on the Configuration->System->Set Date/Time page still displayed in 12 hour format. The Time format now displays correctly. In the AastraLink Pro Web UI, at the location Configuration->System->Regional Settings, if you set the "Date Format" field to a specific format and then click SAVE, the new format did not display correctly on this page. (However, the new format DID display correctly in the Call List. This issue is now corrected and the data format now displays as expected after a SAVE on the Configuration->System->Regional Settings page. RN Release 1.2.1p2, Rev

24

25 Chapter 4 Known Issues in Release 1.2.1p2 Introduction This section describes any known issues in AastraLink Pro 160 Release 1.2.1p2 at the time release, with a description for each issue. RN Release 1.2.1p2, Rev

26 Known Issues Known Issues Documentation Issues The following table is a list of issues that are documented in the next revision of the AastraLink 1.2 Administrator Guide. Summaries of the changes are included below. Issue DOC11065 DOC11067 Description Incoming SIP trunk call routing to voic . For detailed information on this issue, see the section, Supported and Unsupported Codec Behavior on the AastraLink on page 4-3. Setting gain plan on AastraLinks to compensate for Telco PAD. For detailed information on this issue, see the section, Gain Plan on AastraLink to Compensate for Telco PAD on page RN Release 1.2.1p2, Rev 09

27 Known Issues Supported and Unsupported Codec Behavior on the AastraLink DOC11065: Release 1.2 permits audio codecs to be used other than those which are supported by default on the AastraLink - for example, G.729, G.722 wideband. The G.729 and G.722 codecs pass through the AastraLink between endpoints which support them - for example Generic SIP clients and SIP trunks - and are enabled for termination at the Aastra IP phone. Video codecs are also passed through from SIP trunk to Generic SIP endpoints, based on their Session Description Protocol (SDP) capability set. However, calls using codecs not supported on the AastraLink cannot use local resources - for example, voic , auto-attendant, FXO/FXS ports, and overhead paging. In addition, music-on-hold does not operate and the call may be dropped or become silent. Gain Plan on AastraLink to Compensate for Telco PAD DOC11067: Release 1.2 incorporates a new FXO auto-tuning capability that allows the administrator to ensure that the FXO ports are configured for optimal audio quality. This is implemented by adjusting the FXO line hybrid to correctly balance the analogue loop based on distance to the Central Office (CO). However, correct FXO operation also requires that the telephone company (Telco) has correctly provisioned the line to meet the local regulatory requirements. In USA/Canada, nominal specification for an FXO line is 35mA loop current providing 6dB signal power loss into 600 Ohm load at the customer premises. If the incoming signal level is too great, the FXO interface hybrid can become saturated. This will not prevent correct balancing of the hybrid during FXO auto-tuning but may result in audio distortions such as: Clipping: Refers to audio distortion caused by over-driven incoming signal, and can be caused by too high a power level received at the FXO, or by normal power level terminated by an incorrect impedance balance of the tip and ring. Sibilance: where the local AastraLink user hears back a portion of high energy syllables of their own speech due to over-driving of outgoing signal. RN Release 1.2.1p2, Rev

28 Known Issues Telco line adjustments High signal levels may be adjusted by having the Telco change the PAD settings at the CO to place attenuation on the FXO lines to reduce the power level, or lower the line current. Low signal levels require additional gain on the incoming FXO line - this requires that any existing PAD on the line be removed at the CO or the possible addition of loading coils at every 6000 foot interval to maintain line impedance (long lines have high capacitance; loading coils are inductive and re-balance the impedance, lowering line losses and thereby increasing signal power level). AastraLink adjustments for Line Gain The correct way to measure and adjust line gain is to make a test call from the FXO line to the 1000Hz milliwatt test tone at the CO, and use a line signal power meter to detect 0dB across the loop. However, as described above, this usually requires a service technician to measure the FXO line at the customer premises, and arrange with a second technician to make the appropriate adjustments at the CO. As an alternative, incorrect FXO signal levels can be partially compensated for on the AastraLink as follows: High power problems 1. For Sibilance, change the dynamic range setting on the FXO Tuning page from its default setting to Full or Enhanced. 2. For near-end echo, try adjusting the RTP to Line power in steps of -3dB (default is -3dB, so use -6dB or more attenuation - increasing the RTP to line power increases the near end echo effect, attenuating it reduces echo.) 3. For far-end echo, change the Line to RTP power in steps of -3dB and make test calls - for example -3dB or -6dB. Note that increasing the Line to RTP power may also affects the FXO ability to receive CallerID signals. Note: Attenuation decreases signal to noise ratio, so although lowering RTP to Line power improves near-end echo, it may adversely affect audio quality. 4-4 RN Release 1.2.1p2, Rev 09

29 Known Issues Low power problems 1. Set the RTP to Line power in steps of +3dB (default is -3dB, so try 0dB first) until the far-end caller reports acceptable signal level. 2. If necessary, set the Line to RTP power in steps of 3dB until the local AastraLink level is acceptable. RN Release 1.2.1p2, Rev

30

31 Chapter 5 Release 1.2.1p2 Downgrade Procedures About this chapter This chapter provides important information and procedures for downgrading your AastraLink Pro 160 from release 1.2.1p2. IMPORTANT: Downgrading from 1.2.1p2 to or 1.2 is directly supported with an additional reboot; Downgrading to 1.1 or 1.1p1 requires manual factory-default & restore. RN Release 1.2.1p2, Rev

32 Downgrade Procedure Downgrade Procedure Description Use the downgrade procedures in this section if: you currently have 1.2.1p2 loaded on your AastraLink Pro and want to downgrade to or 1.2. ( Downgrade Procedure (from software 1.2.1p2 to or 1.2) on page 5-3) OR you currently have 1.2.1p2 loaded on your Aastralink Pro and want to downgrade to 1.1 or 1.1p1. ( Downgrade Procedure (from software 1.2.1p2 to 1.1 or 1.1p1) on page 5-5) 5-2 RN Release 1.2.1p2, Rev 09

33 Downgrade Procedure Downgrade Procedure (from software 1.2.1p2 to or 1.2) Use the following procedure to downgrade the AastraLink Pro 160 from Release 1.2.1p2 to Release or 1.2. This procedure is required to avoid corrupting the AastraLink system configuration database. AastraLink Pro 160 Downgrade Procedure Step Action 1 Using your PC, download the or 1.2 software release vnx.dra file from the following location: 2 Login to the AastraLink Web UI using your Administrator phone extension and password. Navigate to the location Maintenance/Update->Manual Update and browse to the vnx.dra you just downloaded. Click <Upgrade> to transfer the vnx.dra file onto the AastraLink. After loading the new vnx.dra, the AastraLink prompts you to reboot. Click <Yes>. The software downgrade process may take up to 15 minutes and MUST NOT be interrupted. While the software downgrade is in progress, the AastraLink LED shows alternating GREEN/RED. When the downgrade process is complete, the AastraLink LED flashes slow GREEN which indicates the AastraLink Pro is in the Ready state. RN Release 1.2.1p2, Rev

34 Downgrade Procedure AastraLink Pro 160 Downgrade Procedure Step Action 3 Login to the AastraLink Web UI using your original Administrator phone extension and password. The AastraLink prompts you to update the onboard firmware to match the current CF software Select <Yes>. Allow the onboard firmware update to complete. This takes approximately 5 minutes, during which the AastraLink LED flashes RED/GREEN. When firmware update is complete, the AastraLink reboots, and the LED shows fast flashing GREEN which indicates the AastraLink software initialization is in progress. After the reboot, the AastraLink pro LED shows slow flashing GREEN which indicates the AastraLink Pro is in the Ready state. The AastraLink is as it was prior to the 1.2.1p2 downgrade, including the use of static IP addressing if it was previously enabled. 4 Note: The IP phones in the AastraLink network will still be running the 2.4 firmware. You may need to reboot the phones for them to work properly with the earlier AastraLink software release. In the AastraLink Web UI, navigate to the location Users->User List. Select the phones in this list that you want to reboot and click <Reboot Phones>. This ensures the downgrade of the IP Phone firmware for use with the earlier AastraLink Release. 5-4 RN Release 1.2.1p2, Rev 09

35 Downgrade Procedure Downgrade Procedure (from software 1.2.1p2 to 1.1 or 1.1p1) Use the following procedure to downgrade the AastraLink Pro 160 from Release 1.2.1p2 to Release 1.1 or 1.1p1. This procedure is required to avoid corrupting the AastraLink system configuration database. IMPORTANT: As described in step 2 of the procedure below, an additional manual reboot may be required to complete the downgrade from Release 1.2.1p2 to 1.2 before service resumes. AastraLink Pro 160 Downgrade Procedure Step Action 1 Using your PC, download the 1.1 or 1.1p1 software release vnx.dra file. 2 Login to the AastraLink Web UI using your Administrator phone extension and password. Navigate to the location Maintenance/Update->Manual Update and browse to the vnx.dra you just downloaded. Click <Upgrade> to transfer the vnx.dra file onto the AastraLink. After loading the new vnx.dra, the AastraLink prompts you to reboot. Click <Yes>. The software downgrade process may take up to 15 minutes and MUST NOT be interrupted. While the software downgrade is in progress, the AastraLink LED shows alternating GREEN/RED. When the downgrade process is complete, the AastraLink LED flashes slow GREEN which indicates the AastraLink Pro is in the Ready state. Note: If the LED is still flashing RED/GREEN after 15 minutes, an additional manual reboot may be required. Remove the power cable, then reinsert the power cable, and wait an additional 15 minutes for the software to re-initialize. RN Release 1.2.1p2, Rev

36 Downgrade Procedure AastraLink Pro 160 Downgrade Procedure Step Action 3 On the rear of the AastraLink, locate the RESET switch behind a small hole in the metal frame next to the power connector. PRESS AND HOLD the reset switch gently using a paperclip, KEEP IT PRESSED until the AastraLink LED lights an AMBER color, then RELEASE the switch. Note: For more information about using the RESET switch to reset the factory defaults on the AastraLink, see the AastraLink Pro 160 Administrator Guide, Chapter 7, the section, "Restoring AastraLink Factory Default Settings". 4 When the factory-default is complete, the AastraLink LED shows slow flashing GREEN ON/OFF. This indicates the AastraLink erased the 1.2.1p2 database and is now in a factory-default state. The AastraLink is ready for the original database to be restored from your backup.abf file on your PC. 5 From your PC, access the AastraLink Web UI and login using the following account: Extension: admin Password: Note: At this time, the AastraLink is using either DHCP or it will use fallback to a ZeroConf IP address. If your AastraLink previously used Static IP addressing, see the AastraLink Pro 160 Administrator Guide, Chapter 6, the section, "How does network addressing work? for more information. 6 Select a session language and click <Save>. Navigate to the location Maintenance->Backup & Restore. In the "Restore System" field, click <Browse> and go to the location of the backup.abf file on your PC (you created the backup.abf file before installing the 1.2.1p2 update). Click <Restore> to upload the backup.abf from your PC to the AastraLink. 5-6 RN Release 1.2.1p2, Rev 09

37 Downgrade Procedure AastraLink Pro 160 Downgrade Procedure Step Action 7 The AastraLink prompts you to confirm the Restore and Reboot. Click <Yes>. Depending on the amount of voic on your system, the restore process may take 15 minutes or more to complete, during which the AastraLink LED flashes RED/GREEN. When the restore is complete, the AastraLink reboots and the LED shows fast flashing GREEN which indicates the AastraLink software initialization in progress. When the reboot is complete, the AastraLink LED shows slow flashing GREEN which indicates the AastraLink is in the Ready state. 8 Login to the AastraLink Web UI using your original Administrator phone extension and password. The AastraLink prompts you to update the onboard firmware to match the current CF software Select <Yes>. Allow the onboard firmware update to complete. This takes approximately 5 minutes, during which the AastraLink LED flashes RED/GREEN. When firmware update is complete, the AastraLink reboots, and the LED shows fast flashing GREEN which indicates the AastraLink software initialization is in progress. When the reboot is complete, the AastraLink LED shows slow flashing GREEN which indicates the AastraLink is in the Ready state. The AastraLink is as it was prior to the 1.2.1p2 upgrade, including the use of static IP addressing if it was previously enabled. Any changes made in the 1.2.1p2 software are lost. 9 Note: The IP phones in the AastraLink network will still be running the 2.4 firmware. You may need to reboot the phones for them to work properly with the earlier AastraLink software release. In the AastraLink Web UI, navigate to the location Users->User List. Select the phones in this list that you want to reboot and click <Reboot Phones>. This ensures the downgrade of the IP Phone firmware for use with the earlier AastraLink Release. RN Release 1.2.1p2, Rev

38

39 Chapter 6 Software Licensing and Copyright AastraLink Pro 160 Release 1.2.1p2 Software Licensing For AastraLink Pro160 software licensing and copyright information, please refer to the following document: Document Document Number AastraLink Pro 160 Release 1.2.1p2 Software Licensing REV 01 You can view this document by logging in to the AastraLink Pro 160 Web UI as the Administrator, and select About located at the top of the page, then click on Download PDF. The document is downloaded to your web browser as an Adobe Acrobat PDF file. Licensing Document About Screen RN Release 1.2.1p2, Rev

40

41 AastraLink Pro 160 Software Release 1.2.1p2 Published in the USA RN Rev 09 Software Release Note August 2009