RN Rev 07. Release Notes Release 1.2.1

Transcription

1 RN Rev 07 Release Notes Release 1.2.1

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 Overview Feedback Release numbering Details of this release Pre-requisites AastraLink Pro System Software IP Phone firmware Chapter 2 Release 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) Chapter 3 New Features and Fixes in Release Detailed Feature Descriptions and Usage Description Recovery Mode optimized d handset MAC address displays in Users List Restart of System enhanced Routing added to Meet-Me feature from IVR Configurable Echo Tail Length on FXO Tuning Page Permitted Abbreviated Dialing Entries Increased Caller ID Support for Hotline FXS Add detection for logging duplicate IP addresses Send to the Administrator if duplicate IP address is detected RN Release 1.2.1, Rev 07 iii

4 Integrated a caching DNS server/proxy Secondary Phones allow for remote connection to the local network Approved UPnP Routers in AastraLink Pro Hot fixes in release Description Chapter 4 Known Issues in Release Known Issues Chapter 5 Release Downgrade Procedures About this chapter Downgrade Procedure Description Downgrade Procedure (for software to 1.2) Downgrade Procedure (for software to 1.1 or 1.1p1) Chapter 6 Software Licensing and Copyright AastraLink Pro 160 Release Software Licensing iv RN Release 1.2.1, Rev 07

5 Chapter 1 Software Release Overview Introduction About this release AastraLink Pro 160 software release is a maintenance release delivering new features and hotfixes to the AastraLink software since the release of 1.2. 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 For more information about upgrading your AastraLink Pro 160, see Chapter 2, Release Upgrade Procedures in these Release Notes. Please provide any feedback regarding the content of this document via to RN Release 1.2.1, 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 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. 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.1, Rev 07

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.1, Rev

8 Details of this release IP Phone firmware This AastraLink Pro 160 software release incorporates IP phone firmware release 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 536M and 560M Expansion Modules, and 1.08 firmware of the Mobility Base Unit (MBU 400) and DECT 420d handsets. 1-4 RN Release 1.2.1, Rev 07

9 Chapter 2 Release Upgrade Procedures About this chapter This chapter provides important information and procedures for upgrading your AastraLink Pro 160 to Release IMPORTANT: Releases 1.1 and later are supported for upgrade to 1.2.1; if you are running a prior release of software, please upgrade to 1.1 first before attempting to upgrade to Release RN Release 1.2.1, Rev

10 Upgrade Procedure Upgrade Procedure Description Use the upgrade procedures in this section if: you currently have 1.2 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.1, Rev 07

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 software by navigating to the 'About' link at the top-right of the AastraLink Web UI. 6 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 Configurable Echo Tail Length on FXO Tuning Page on page 3-4 RN Release 1.2.1, 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 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.1, Rev 07

13 Upgrade Procedure Upgrade Procedure (for software version 1.1p1 or lower) Step Action 6 Confirm that your system is now running release 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.1, Rev

14

15 Chapter 3 New Features and Fixes in Release Introduction This chapter describes the new software features of the AastraLink Pro 160 running Software Release 1.2.1, and fixes for problems reported in release 1.2 software operation. Features and fixes listed here are incremental to release 1.2 and earlier. 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.1, Rev

16 Detailed Feature Descriptions and Usage Detailed Feature Descriptions and Usage Description This section summarizes the operation of each new feature in Release 1.2.1, with brief usage instructions or implementation notes as applicable. Feature ENH11610 ENH11612 ENH16477 ENH11715 ENH11859 ENH12197 ENH16470 ENH16577 ENH16582 ENH16584 ENH16776 Description Recovery Mode removed user intervention for previous bootup issues. 420d MAC address in the Users List displays the MBU and Handset number. Echo tail length on FXO Tuning page in the Web UI is now admin configurable. A graceful restart of the system now avoids memory exhaustion. Added routing to the Meet-Me feature from IVR for incoming FXO or SIP trunks. Increased the permitted Abbreviated Dialing entries on the AastraLink Pro. Added configurable caller ID field for the FXS hotlines on the Dial Plan page Add detection for logging duplicate IP addresses. the Administrator if duplicate IP address is detected. Integrate a caching DNS server/proxy. Secondary Phones allow for remote connection to the local network. 3-2 RN Release 1.2.1, Rev 07

17 Detailed Feature Descriptions and Usage Recovery Mode optimized ENH11610: Recovery Mode has been optimized to remove user intervention for previous bootup issues. The AastraLink now automatically attempts to recover the unit and checks the filesystem, only reverting to recovery mode if a severe filesystem error is encountered, or if recovery is manually entered by booting without a CompactFlash card inserted. 420d handset MAC address displays in Users List ENH11612: When an MBU 400 and 420d handsets are registered with the AastraLink, the "Mobility Base Unit" tab in the AastraLink Web UI now displays the MBU number and the 420d handset number in addition to the virtual MAC address of the handset, and the physical MAC address of the MBU 400. Restart of System enhanced ENH11715: The process of restarting asterisk has been enhanced to avoid memory exhaustion conditions. In the event that Asterisk runs out of memory, the Linux scheduler terminates and reloads Asterisk, avoiding prolonged service outage that would otherwise be the result. Routing added to Meet-Me feature from IVR ENH11859: The meet-me conference feature can now be reached from the IVR menu for incoming FXO and SIP trunk calls. Previously the meet-me feature was enabled for internal SIP extensions only. RN Release 1.2.1, Rev

18 Detailed Feature Descriptions and Usage Configurable Echo Tail Length on FXO Tuning Page ENH16477: Previously, on the FXO Tuning Page, you could only enable/disable the Echo Cancel parameter. In Release an option is provided to select a specific echo tail length in milliseconds. Valid echo tail lengths are 8ms, 16ms, 24ms, 32ms, 40ms, 48ms, 56ms, 64ms, 72ms, 80ms, 88ms, 96ms, 104ms, 112ms, 120ms, 128ms. The default and recommended echo cancellation tail is 48ms. Permitted Abbreviated Dialing Entries Increased ENH12197: The limit of abbreviated dialing entries has been expanded from a total of 10 to a total of 100. The prefix of 1 is automatically applied, so any number in the range of 100 to 199 is provisionable at the Web UI location Configuration->DialPlan->Abbreviations. 3-4 RN Release 1.2.1, Rev 07

19 Detailed Feature Descriptions and Usage Caller ID Support for Hotline FXS ENH16470: Caller ID support for the FXS hotlines has been added to Release An Administrator can now set a Caller ID for both Phone A and Phone B FXS hotlines. Provisioning a Caller ID allows incoming and outgoing FXS calls to display Caller IDs on the IP phones. You can set this feature using the "Phone A Caller ID" and/or "Phone B Caller ID" parameters at the Web UI location Configuration->DialPlan->Settings. FXS Hotline Caller ID Parameters RN Release 1.2.1, Rev

20 Detailed Feature Descriptions and Usage Add detection for logging duplicate IP addresses ENH16577: The AastraLink 160 will send a periodic ARP command every 30 seconds to detect if any other network device is configured with an IP address that clashes with the one in use by the AastraLink 160 software. If a clash is detected, a log is recorded for later system diagnosis. Send to the Administrator if duplicate IP address is detected ENH16582: In addition to the above logging, all administrators that have an address provisioned will be notified by AastraLink 160 of the IP collision. The will be sent once when the problem is initially detected, and will repeat every 10 minutes until the failure condition has been resolved. Integrated a caching DNS server/proxy ENH16584: A locally persistent DNS cache has been implemented on AastraLink 160 to ensure that system operation can continue in the event of DNS server becoming inaccessible on the network. DNS cached addresses will be verified every 15 minutes and expired after 1 week. 3-6 RN Release 1.2.1, Rev 07

21 Detailed Feature Descriptions and Usage Secondary Phones allow for remote connection to the local network ENH16776: The AastraLink Pro now allows remote users using secondary phones to connect to its local network. The "Secondary Phone" parameter in the Web UI now allows an Administrator to select the options of "Disabled", "Local", or "Remote". Note: Secondary SIP extensions used from remote networks must be appropriately configured to ensure that they are using a valid routable IP address. If the secondary SIP device is behind a NAT device, this may require configuring it to use a STUN server to resolve the public IP, or enabling UPnP on the phone and NAT router to obtain the public address automatically. Please refer to the documentation for your SIP client device for additional information about its supported network topology. RN Release 1.2.1, Rev

22 Detailed Feature Descriptions and Usage Approved UPnP Routers in AastraLink Pro The following are approved UPnP routers for the AastraLink Pro release. SOHO Router Make/Model Revision Information Phone-Side (remote phone not co-located with AastraLink Pro) Server-Side (location where AastraLink Pro is installed) Netgear WGT624 Version 2 Supported Supported Firmware V4.2.11_1.0.1 D-Link DI 604 Firmware 3.51, 22 Supported Supported November 2004 D-Link DIR 625 Firmware Version 1.09 Supported Supported SMC 2404WBR Firmware Version Supported Supported Netgear WNR 3500 Version _6.0.22NA Supported Non-supported Linksys WRT54G Version 6 Firmware V Supported Non-supported 3-8 RN Release 1.2.1, Rev 07

23 Hot fixes in release Hot fixes in release Description This section summarizes the fixes in Release for issues found in Release 1.2 and earlier. Hotfix CLN11717 CLN11911 CLN12008 CLN12106 CLN12128 CLN16427 CLN16431 CLN16441 CLN16459 Description Add toggle for an Administrator to enable/disable availability of generic phone. Auto-updates sends the "new firmware downloaded" before downloading. Failure when adding a second 420d user on AastraLink. Incoming SLA call from FXO with no Caller ID shows as 9 on Phone UI. Deleting paging group extension also receives paging. Calls drop due to unprotected call progress tones. Modification of the 420d handset with AastraLink Web UI is not applied to MBU. Phone rings and line cuts off occasionally during a conversation. AastraLink Pro can't write MBU config file when 420d user name contains an apostrophe. CLN16557 Call-forward routing not working after 1.1p1 upgrade to 1.2. CLN16602 CLN16721 CLN16776 Setting password through Comedian Mail Can Make passwords Out of Synch. Phone does not display two ring group s voice messages properly. Softphone cannot connect to secondary extension due to NAT. RN Release 1.2.1, Rev

24 Hot fixes in release Hotfix DEF08208 DEF10257 DEF11347 DEF11665 DEF11707 DEF11804 DEF11821 DEF11827 DEF11866 DEF11881 DEF11884 DEF11901 DEF11917 DEF11927 DEF11934 DEF11960 DEF09560 DEF09767 DEF10027 DEF10539 DEF10662 DEF11175 DEF11192 DEF11446 DEF11447 DEF11452 DEF11530 DEF11541 DEF12026 DEF12037 DEF12038 DEF16405 DEF16407 DEF16409 DEF16417 DEF16438 DEF16482 DEF16483 DEF16485 DEF16504 DEF16505 DEF16543 DEF16552 DEF16558 DEF16674 Description Language translation errors Recording for "voic IVR" option 0,5 prompt to change password. Remote office: delay in updating remote phone IP address. AastraLink Pro FXO fails to receive CID with silent channel seizure signal dropout. Cannot play custom Auto-Attendant message after changing language. The default greeting message to customize a message is always in English. Dialplan/Settings is crowded and loads very slowly. SLA incoming call goes to Main Menu on overflow; should go to default route. AastraLink sending DNS requests for SLA stations. Translations: Unable to access mailbox options when you have a temp greeting. Scalability: DSP not detecting call progress tones reliably. AastraLink Pro: Spurious 5x DNS A query when a SIP trunk is added. Realm set at the SIP trunk is added as domain on authenticating user name RN Release 1.2.1, Rev 07

25 Hot fixes in release Hotfix DEF11598 DEF11609 DEF11640 DEF11648 DEF11651 DEF11658 DEF11662 DEF11696 DEF11720 DEF11726 DEF11762 DEF11836 DEF11847 DEF11850 DEF11855 DEF11857 DEF11872 DEF11877 DEF11880 DEF11883 Description Remote office phones are not updating their firmware. Voic notification does not display the right time. Intermittent display of a question mark instead of a phone icon for BLF. SLA DND only applies to line 1 on phone. You cannot dial number before hitting the SLA line. Short stutter heard when you select SLA line. Caller list should use the same outgoing route as the incoming call. The * or 0 not recognized on voice mail via ** or Ring Group No Answer. Editing softkeys from the user list creates keys with blank labels. Unable to dial extension from Auto-Attendant if in French. The "escape to extension" was not working correctly. Web UI shows DND set to "off" & phone status line shows DND set to "on". Prompts too long during initial.php when French is selected. notification not received on leaving voic to Ring Group. Not possible to reach FXS B 6011 from IVR for incoming FXO or SIP trunk. Two softkeys created for "Park List" but only one can be changed back to empty. Enabling remote office "HTTP Port Range" = 0 and UPnP crashes AastraLink. Phones with SLA disabled still receive provisioning data. If Ring Group configured to go to Auto-Attendant the call is sent to what Auto-Attendant is configured. After clicking <Save> on the auto-tune page, a reboot results in tuning pop up. DEF11888 SLA enabled field is set even though SLA isn't supported on 6751i. DEF11891 Unable to call a page group from a phone connected to an FXS port. RN Release 1.2.1, Rev

26 Hot fixes in release Hotfix DEF11918 Description The "call forward all" extension was missing from the TUI upon re-entry. DEF11951 SIP Trunk working but Web UI reports "unregistered" + CLI = unmonitored. DEF11953 DEF11978 DEF11985 DEF11987 DEF12006 DEF12051 DEF12066 DEF12071 DEF12077 DEF12090 DEF12127 DEF12131 DEF12148 DEF12175 DEF12181 DEF12191 DEF12193 DEF12231 DEF16437 DEF16460 DEF16463 Saving in FXO tuning wizard resets echo_tail to 8 ms. No sent when one of the Administrator users had a blank field. Paging softkey changes to Intercom after reboot of AastraLink. Status line doesn't show DND activated. After upgrade - hotline does not call hotline Ring Group. Web UI SIP trunk always responds as decline to SIP trunking invite. Inbound PSTN not working correctly in some scenarios. Incorrect warning message when SLA station is enabled or disabled. Unable to modify a 420d user with AastraLink Web UI. AastraLink Pro no service when internet is down. Wrong displayed identification for private call in Spanish. Unable to add any user with "Add Phones" button. Phone with SLA disabled on a system with SLA enabled shows SIP offline. Log rotates when removing AastraLink logs. Line disconnects during normal calls. Call cut off after 1.2 version upgrade. Calls drop when in a conference call or when far end is busy. Setting "locked" softkeys globally has not affect. The 24 hrs Time format will not save on Web-UI. AastraLink Pro 1.2 no service - Web GUI access - call processing stopped. AastraLink pro 1.2 System crashes [asterisk, no logs - dhcp] RN Release 1.2.1, Rev 07

27 Hot fixes in release Hotfix DEF16491 DEF16494 DEF16520 DEF16521 DEF16539 DEF16546 DEF16547 DEF16555 DEF16571 DEF16578 DEF16583 DEF16620 DEF16630 DEF16665 DEF16742 DEF16770 DEF16830 DEF16832 Description Hotline does not show Caller ID if it contains a space. AastraLink Pro w/ random no service [asterisk]. AastraLink Pro w/ 1.2 the FXO has 8 second delay before dialing. AastraLink Pro: Delay of DTMF dialing without dial tone is too long. AastraLink Pro locked up. Unable to make outgoing calls. AastraLink Pro: No DTMF signal sent to FXO line in connected state from FXSA/B phone. AastraLink Pro: No DTMF is sent to FXO line if no dial tone is provided. Date format incorrectly displayed by Regional Settings page. Paging is omitted from the list of Softkey Permissions. System reverted from static IP to zeroconf when network failed. HTTPD does not restart causing vnxdaemon to hang if IP address changes. AastraLink Pro: Hotline CID is not recorded in User Call List. Aastralink Pro Auto-Assistant GET closed greeting when schedule was open. AastraLink Pro: one of multiple FQDN trunk became unregistered after in service for a period of time. DTMF tones do not traverse in/out Remote Phones through FXO lines. IP Phone reboot during system upgrade can lead to Operator status messages. Auto-Attendant reporting false schedule state on operator Phone UI. Double status messages displayed on remote phones. RN Release 1.2.1, Rev

28

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

30 Known Issues Known Issues The following table is a list of any significant known issues in Release that may require additional action to be taken by the customer. Issue Functional Issues DEF11839 DEF16443 DEF16477 DEF16479 DEF16527 DEF16642 DEF16745 DEF16749 DEF16779 DEF16871 DEF16880 DEF16883 Display Issues DEF11847 DEF16419 DEF16544 DEF16581 DEF16641 Description Some phones didn't reboot and change to SLA station (SUBSCRIBE not sent) Inbound call drops voic XML interface. CLID does not function correctly if gain levels are modified. Faulty FXO line is used to make outgoing call instead of using free FXO line System lost default language setting during upgrade. A "clicking" sound is heard when transitioning a call from an IP phone to FXO. Location is Mexico. FXO does not release line for 500/500 ms busy tone. FXO4 does not respond to ringing after extreme FXO/FXS call scenario. DSP freezes in extreme FXO/FXS call scenarios. New phone Registration request was denied on attempting to register. Parallel FMFM: First number doesn't ring if 2nd is a Ring group number. Unable to save softkey to the phone. Prompts may be too long when French is selected Missing translations in Service Admin screens Day and month short labels are not translated in Date Format choice. Operator flag disappears and "This number is not available" after reboot Missing translations when you print an insert. 4-2 RN Release 1.2.1, Rev 07

31 Chapter 5 Release Downgrade Procedures About this chapter This chapter provides important information and procedures for downgrading your AastraLink Pro 160 from release IMPORTANT: Downgrading from to 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.1, Rev

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

33 Downgrade Procedure Downgrade Procedure (for software to 1.2) Use the following procedure to downgrade the AastraLink Pro 160 from Release to Release 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 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.1, 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 upgrade, 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.1, Rev 07

35 Downgrade Procedure Downgrade Procedure (for software to 1.1 or 1.1p1) Use the following procedure to downgrade the AastraLink Pro 160 from Release 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 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 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. 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.1, 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 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 update). Click <Restore> to upload the backup.abf from your PC to the AastraLink. 5-6 RN Release 1.2.1, Rev 07

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 upgrade, including the use of static IP addressing if it was previously enabled. 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.1, Rev

38

39 Chapter 6 Software Licensing and Copyright AastraLink Pro 160 Release Software Licensing For AastraLink Pro160 software licensing and copyright information, please refer to the following document: Document Document Number AastraLink Pro 160 Release 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 Licensing. The document is downloaded to your web browser as an Adobe Acrobat PDF file. (See an example of the About Screen on the next page). RN Release 1.2.1, Rev

40 AastraLink Pro 160 Release Software Licensing Licensing Document About Screen 6-2 RN Release 1.2.1, Rev 07

41

42 AastraLink Pro 160 Software Release Published in the USA RN Rev 07 Software Release Note February 2009