AastraLink
Pro
160
RN-001030-02
Rev 04
Release Notes
Software Release 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 2008 Aastra Telecom. www.aastratelecom.com
All Rights Reserved.
Contents
Chapter 1
AastraLink Pro 160 Software Release 1.2 Overview
Feedback .................................................................................................................1-1
Release numbering ..................................................................................................1-2
Hotfix tracking ..........................................................................................................1-2
Patchkit description ..................................................................................................1-2
Details of this release .....................................................................................................1-3
Pre-requisites ...........................................................................................................1-3
AastraLink System Software ....................................................................................1-3
AastraLink Boot Firmware ........................................................................................1-4
IP Phone firmware ....................................................................................................1-5
New Features in Release 1.2 ...................................................................................1-6
Hotfixes in Release 1.2 ............................................................................................1-8
Previous Enhancements and Hotfixes Included in this Release ............................1-14
New Features in Release 1.1p1 .............................................................................1-14
Hotfixes in Release 1.1p1 ......................................................................................1-15
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 2
AastraLink Pro 160 New Features
Detailed Feature Descriptions and Usage ......................................................................2-2
Description ...............................................................................................................2-2
Multiple Paging Groups ............................................................................................2-2
Configuring a Paging Group ..............................................................................2-3
.
.
.
.
Using XML with the Paging Group Feature .......................................................2-4
.
Configurable Paging and Intercom Options .......................................................2-5
.
Meet-Me Conference Bridge Feature .......................................................................2-7
Host Capacity Limitations ..................................................................................2-8
.
.
Conference Bridge Dial-Plan Table ...................................................................2-8
.
Call Parking to Display the Parked Number on the Phone UI ..................................2-9
Web UI Click-to-Call Links Allow Editing ..................................................................2-9
Secondary Generic SIP and Softphone Support ....................................................2-10
Secondary Phones Can be Manually Enabled/Disabled on a Per-User Basis 2-10
.
.
.
.
RN-001030-02 Rev 04, Release 1.2
iii
Caller ID on FXS Ports ...........................................................................................2-11
Ability to Add FXS Extension to a Ring Group .......................................................2-12
Added Key System Shared Line Appearances (SLA) ............................................2-13
About Shared Line Appearances .....................................................................2-13
.
.
.
.
SLA and the AastraLink Pro ............................................................................2-13
.
SLA Key Mapping ............................................................................................2-14
.
SIP phone features for SLA lines ....................................................................2-15
.
Using AastraLink SLA from the SIP Phones ...................................................2-16
.
Configuring SLA on the AastraLink .................................................................2-17
.
SLA Membership .............................................................................................2-18
.
Configuration Changes ....................................................................................2-18
.
Automatic Tuning Wizard No Longer Requires a Phone Call ................................2-19
Call Transfer Directly to a User’s Voicemail ...........................................................2-21
Admin Disable of User Accounts ............................................................................2-21
Allow Incoming Call Routing Selection for Individual FXO Lines ...........................2-22
Voicemail Breakout on * to Login Prompt ...............................................................2-23
MBU 400 and 420d Handset Integration ................................................................2-23
MBU Configuration Download from the AastraLink .........................................2-25
.
.
.
.
.
.
.
Handset Registrations .....................................................................................2-26
.
SIP Trunking Single-Digit Prefix .............................................................................2-27
FXS Port Hotline Operation ....................................................................................2-29
Support for 6730i and 6731i IP Phones .................................................................2-30
Prompt Administrator if Updates are Required ......................................................2-30
Single Digit Routing Table for Auto-Attendant Main Menu .....................................2-31
Custom IVR Configuration ...............................................................................2-32
.
.
.
.
.
.
Onboard Flash Recovery Firmware Changes ........................................................2-32
.
Chapter 3
AastraLink Pro 160 Known Issues
Known Issues .................................................................................................................3-2
Documentation Issues ..............................................................................................3-2
Supported and Unsupported Codec Behavior on the AastraLink ......................3-3
.
.
.
Gain Plan on AastraLink to Compensate for Telco PAD ....................................3-3
.
Other Known Issues .................................................................................................3-5
.
Chapter 4
AastraLink Pro 160 Software Licensing and Copyright
AastraLink Pro 160 Release 1.2 Software Licensing .....................................................4-1
.
iv
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Introduction
Chapter 1
AastraLink Pro 160
Software Release 1.2 Overview
Introduction
About this release
AastraLink Pro 160 software release 1.2 is a feature release delivering new
functionality incremental to the previous 1.1 FCS release. It also contains a
complete roll-up of hotfixes from patchkits released since 1.1 FCS.
This release note includes information about new feature enhancements and
fixes in release 1.2, and also summarizes the hotfixes since 1.1 FCS.
IMPORTANT: Always backup your system configuration via the
Web UI, prior to upgrading to a new release.
Feedback
Please provide any feedback regarding the content of this document via email to
[email protected].
RN-001030-02 Rev 04, Release 1.2
1-1
AastraLink 160 Pro Software Release Note 1.2
Introduction
Release numbering
AastraLink software releases are provided in two categories:
•
Standard releases are labelled with M.m release number, e.g. 1.0, 1.1 etc.
•
Maintenance releases add a patchkit number to the label, e.g. 1.1p1.
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 "p" is the patchkit number, defining a collection of post-release hotfixes.
Standard and maintenance releases may have an associated build number, which
is used internally by Aastra to track Beta versus General Availability releases.
Hotfix tracking
Hotfixes are identified by ticket (CR) number of the problem being addressed.
Typically this is a number in the format DEF001234, or a customer ticket number
such as, INCD001234. However, other references may be used.
Hotfixes are generally not delivered individually to customers unless an
emergency binary is required to resolve a critical problem; the normal delivery
mechanism is via a patchkit. A patchkit is a collection of individual hotfixes, each
of which is intended to resolve a specific software defect or customer problem,
but which have been tested together as a complete set to ensure correct operation.
Patchkit description
Patchkits (maintenance releases) are issued between the normal major/minor
product release cycle, and generally contain limited new feature content; they are
primarily intended to improve the robustness or operability of the prior release.
Patchkits are cumulative, so the ’dra’ software archive for 1.2 contains the entire
original 1.1 software plus the updates for hotfixes resolved by interim patchkits.
1-2
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Details of this release
Details of this release
Pre-requisites
This release is suitable for use with any AastraLink system running 1.1 GA or
later, including 1.1p1.
Customers with AastraLink systems using earlier software versions or pre-release
alpha/beta code cannot directly upgrade, and should contact Aastra customer
support for details of the greenfield installation procedure.
AastraLink System Software
The AastraLink Pro system software resides on the externally accessible
CompactFlash card in the form of a Linux root filesystem. This is upgraded
in-place by uploading a vnx.dra file via the Administrator’s web interface.
After updating the system software, the firmware residing on the internal
boot flash must also be updated to the corresponding version. Updating
the boot firmware is covered in the next section.
IMPORTANT: Updated boot firmware for the AastraLink onboard flash
is included in this patchkit. The boot firmware upgrade must be initiated
manually after CompactFlash upgrade has completed.
The system is not considered fully upgraded until the Software and the
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-001030-02 Rev 04, Release 1.2
1-3
AastraLink 160 Pro Software Release Note 1.2
Details of this release
AastraLink Boot Firmware
After upgrading the CompactFlash to Release 1.2, the Administrator is prompted
at first login that a new boot firmware is required, per the following illustration.
UPGRADE OF THE SYSTEM BOOT FIRMWARE IS MANDATORY
Note: If the Administrator clicks NO, they will be logged out.
The firmware upgrade prompt is repeated at each subsequent login by the
Administrator, until the firmware update has been successfully
completed.
When the Administrator clicks YES, AastraLink reboots to install the new system
firmware. Phone service will not be available for approximately 5 minutes while
the upgrade takes place.
The boot firmware upgrade includes several automatic reboots; the firmware
upgrade is complete when the system LED shows flashing green.
DO NOT, under any circumstances, remove power, reset the AastraLink,
or otherwise disrupt the system while onboard flash reprogramming is in
progress, as indicated by an alternating red/green pattern on the system
LED. Interrupting this process WILL result in an unbootable system
requiring manual recovery.
1-4
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Details of this release
IP Phone firmware
This AastraLink Pro 160 software release incorporates IP phone firmware release
2.4.0 for the following phones:
9143i
55i
9480i
57i
9480i CT
57i CT
51i
6730i
53i
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.
Please refer to the IP Phone 2.4 release notes for details of phone features &
changes, and MBU-400 1.0 release notes for details of the MBU 400 features.
RN-001030-02 Rev 04, Release 1.2
1-5
AastraLink 160 Pro Software Release Note 1.2
Details of this release
New Features in Release 1.2
The following enhancements and new features are delivered by release 1.2.
Please refer to Chapter 2 of this release note for further information on
configuration and use.
Feature
Description
ENH05447
SIP phone MWI light up on enabling DND
ENH05448
SIP phone MWI light up on enabling call forward
ENH07235
mDns added to the download logs
ENH09445
Capability to revert to last db auto-backup copy in recovery WUI
ENH09915
IAX2 trunks integrated with UPnP port traversal
ENH10532
Allow unlisted numbers in the corporate directory (
ENH04810
Dynamic IP address reconfiguration (DHCP release / change)
ENH04864
Paging groups / zone paging
ENH05321
Paging groups list via XML from icom key
ENH05505
Meet-me conference bridge
ENH06001
Web UI Click-to-call links should allow editing out going numbers
ENH06041
Call parking to display the park slot on the TUI
ENH07099
Advanced SIP trunking - DNS SRV lookup
ENH07125
ENH10496
Generic SIP and Softphone support.
Secondary phones can be manually enable/disabled on a per-user basis.
ENH08300
Ability to add FXS extension to a ring group
ENH08998
Caller ID on FXS ports
ENH09001
Key system Shared Line Appearances (SLA)
ENH09002
Automatic Tuning Wizard, should not require making a phone cal, etc.
ENH09005
The ability to transfer a call directly to a users voice mailbox.
ENH09034
Ability for the admin to disable a user account
ENH09351
Allow incoming call routing selection for individual FXO lines
1-6
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Details of this release
Feature
Description
ENH10322
Dial 0 out from Voice Mail and * out to default Voice mail announcement
ENH10346
MBU400 Gateway + 420d Handset integration
ENH10347
SIP Trunking single-trunk/no-prefix Enhancement
ENH10537
Prompt administrator for FXO tuning on second login after upgrade
ENH10551
Prompt administrator for bootfs update on first login after upgrade
ENH10563
Add support for 6731i
ENH10596
Paging groups: PIN controlled access feature
ENH10651
Auto Attendant functionality: single digit main menu routing
ENH10782
Include MBU400 firmware in the upgrade dra file
ENH10904
Additional passthrough codec support for SIP trunk interop
ENH10912
Off-net SIP trunk without 'qualify' option
ENH10974
Add support for 6730i
ENH11162
Ability to configure phone access to SLA or locked to the pool line only
ENH11285
Method to force-release FXO call
ENH10946
Toggle for admin to enable/disable availability of generic phone feature
ENH11613
Boot sequence optimizations for recovery mode self-check
ENH11614
Add 420d virtual MAC address to MBU#/Handset# table on the admin Web UI
RN-001030-02 Rev 04, Release 1.2
1-7
AastraLink 160 Pro Software Release Note 1.2
Details of this release
Hotfixes in Release 1.2
The following hotfixes are newly delivered by Release 1.2.
Hotfix
Description
DEF07565
SIP DID does not remove whole set if multiple are selected for delete at once
DEF08958
French Language translation errors
DEF09513
Unable to access ring group vmail even though status line shows 1 New msg
DEF09881
In debug phone tab checking an extension and delete does not delete
DEF09891
Vnxdaemon never recovers from corrupt vnx.cfg file
DEF09914
Restore doesn’t set nameserver for static ip on reboot
DEF09952
Phone debug log status lost over upgrade
DEF09958
Add phone reboot confirmation prompt on admin Web UI
DEF09993
Show SIP/IAX prefix on the VOIP details edit screen
DEF10003
Voicemail notification shows wrong time
DEF10068
Ring group transfer to field is deleted when it is changed in AA
DEF10094
Recovery mode fails to format 4GB CF card
DEF10097
Asterisk SIP debug logging not working
DEF10205
VNX does not delete all asterisk db info when deleting a Ring Group.
DEF10326
Bad block test can go into a loop without notifying the user
DEF10340
Deleting a temporary greeting doesn't work when VVM menu is used
DEF10344
"Escape to extension" doesn't work for ** voicemail calls
DEF10359
After a config restore the host name reverts to aastralink
DEF10374
After setting net console in recovery mode support brought to white page
DEF10398
AastraLink doesn't get IP address from DHCP after recovery mode
DEF10435
Bad translation on the Web UI french
DEF10450
Unable to change from a DHCP acquired address to static IP address
DEF10457
Changing date in Web UI reverts to Wednesday 31th December 1969 at 19H
1-8
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Details of this release
Hotfix
Description
DEF10513
Asterisk reloads 5 times every time a phone boots up
DEF10533
Incoming calls to Ring Group when one user dnd 2 invites go to other grp mem
DEF10534
If all phones in a Ring Group are DND, the incoming calls drops instead of AA
DEF10548
Incoming ring group to auto-attendant does not play greeting
DEF10585
Visual voicemail options - group changes are incorrectly associated to user
DEF10586
e2fsck fails for CF cards >2GB
DEF10611
Unable to record a greeting for the operator through TUI
DEF10662
Auto-Attendant default greeting to customize message is always in english
DEF10670
Changing between static and dynamic IP addressing fails
DEF10708
E-mail alert Phone registration on "OFF" (Bad translation in french)
DEF10722
1.1p1 not writing kernel logs to file
DEF10899
AL PRO w/1.1.0b275 - Out bound calls through SIP trunk fail.
DEF06280
Unclean shutdown during upgrade causes filesystem corruption
DEF07065
Call park number is played to caller if callee releases during the announcement
DEF08202
ALP ignores IVR digits during custom greeting, but extensions route fine
DEF09705
More precise error message required for duplicate MAC address
DEF09732
Remote office: phone response with" cannot post data" when ALP XML push
DEF09767
Remote office: Delay in updating remote phone ip address
DEF09955
Add phone & Reboot, phone comes up showing Jan1
DEF09970
Broadsoft inbound SIP trunk calls doesn't work and gets a 403 error
DEF09979
Phones went no service and no WUI access upon ip changed via DHCP
DEF10057
AastraLink-Sylantro-SipTrunk: Inbound call to AL gets 403 forbidden
DEF10058
Linux should assert the FPLA reset line after doing sync for reboot
DEF10207
Aastralink-Different Username in REGISTER and INVITE header
DEF10257
Wrong displayed Identification for Unknown Name and Number in french
RN-001030-02 Rev 04, Release 1.2
1-9
AastraLink 160 Pro Software Release Note 1.2
Details of this release
Hotfix
Description
DEF10394
A seventh softkey appear for 53i
DEF10536
Large configs are not completely backed up or restored
DEF10725
Extension number in group-add page should be mandatory
DEF10920
Registration status not accurately shown on the Web UI for remote devices
DEF10945
AastraLink Pro w/ 1.1.1b275 has crashed twice in the last month.
DEF10995
Greenfield config in non-english system language does not work correctly
DEF11006
Eth0 sometimes going to zeroconf address when dhcp should be available
DEF11034
BosALP Trunks Not Restored Over Upgrade
DEF11043
DTMF not properly handled across SIP trunks
DEF11048
The 53i voicemail application has no exit item
DEF11051
After hitting Office Open/Close the TUI always displays "Office Open"
DEF11094
CfwdBsy: Ignore during active call is treated as unavailable, should be busy
DEF11132
Operator expansion module configured via user list shows speeddial not BLF
DEF11136
Disabling a language leaves phones orphaned to the old value
DEF11201
BosFXO outbound calls fail if preferred line is set
DEF11237
Custom Greeting Issues
DEF10873
VNX bulk-upload to the user list does not work for 420d handsets
DEF10990
Group member drop-down includes FXS for paging groups
DEF11150
Directed call pickup not working on operator phone
DEF11179
CID time displayed on FXS phone is not local time.
DEF11181
No ringback tone on sip phone for call to FXSA or FXSB phone.
DEF11240
The “Reboot Selected Entries” action does not reboot the selected MBUs
DEF11255
Hotline feature allows phone to be configured with Paging extension
DEF11278
XML paging key returns "Cannot display" if there are no paging groups defined
DEF11282
Pressing the right arrow from the XML paging list results in ""Invalid URI"
1-10
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Details of this release
Hotfix
Description
DEF11290
Dynamic Range is incorrectly set after running FXO auto tune in Enhanced
mode
DEF11291
Upgrade: admin is not prompted to reboot after uploading file vnx.dra
DEF11310
Directed Call Pickup fails on FXO -> SIP call, shouldn't display soft client
DEF11321
DECT-registered handsets receive calls sent to other handsets
DEF11323
SLA subscription period not set, default to 3600 (1hr)
DEF11327
Intermittent one-way voice path on remote office phone to FXO call
DEF11333
SLA phones are not ringing (no Invite sent)
DEF11341
Call records display inaccurate time
DEF11346
Unable to force-release a hung MSPD line using Web UI
DEF11353
Editing personal directory on TUI makes you type in entire number
DEF11357
Impossible to set the closed-hours auto attendant route to ring group
DEF11363
Overflow from ring grp should go to auto-attendant day/night not IVR main menu
DEF11364
Busy signal when an FXO call is placed to the VNX when AA set to a ring group
DEF11380
Impossible to re-enable a 420d handset user with AastraLink WUI
DEF11384
Custom IVR greeting is deleted after a config backup and restore
DEF11392
Beta push button functionality has changed from paging phone to calling it
DEF11401
Music On Hold does not work after Asterisk reload
DEF08464
CFWD All set to FXS no: caller gets unavailable msg
DEF09915
IAX2 call failed because of INVAL due to NAT rewrite
DEF10370
Recovery mode bad-block test should report CF errors in log
DEF10998
Slowdown in 1.2 - vnxdaemon function call speedups
DEF11194
FXO auto-tune config file is not persistent across upgrades
DEF11216
Delayed dial tone when SLA Line offhook is pressed
DEF11296
FXO configured as SLA is permanently seized if it there is no dial tone
DEF11297
CDR logs show blank fields when SLA line rings and not answered
RN-001030-02 Rev 04, Release 1.2
1-11
AastraLink 160 Pro Software Release Note 1.2
Details of this release
Hotfix
Description
DEF11324
Cannot add new group due to Web UI timeouts when >15 users
DEF11349
"No such table" intermittent errors on MBU user management
DEF11390
Memory leak on asterisk with 35 users causes crash after 3 weeks
DEF11391
Incoming SLA call should override existing state if not idle
DEF11429
DCP does not work when a call is placed to a ring group
DEF11451
Can save a 420d user configuration without handset choice
DEF11454
Periodic screen refreshes sent to the 420d handsets
DEF11461
Should not be able to configure SLA for 420d handsets
DEF11475
Aastralink Pro FXO greetings playing in english instead of french
DEF11502
Syslog for asterisk remote debugging not working
DEF11511
Impossible to delete contacts from ALP Web UI
DEF11517
Vnxdaemon coredump during IAX2 UPnP port-open on Linksys BEFSR41
DEF11521
Config server address on MBU is not updated if ALP IP address changes
DEF11523
Some Web UI page layouts overlap with system status footer
DEF11538
CDR archive function fails, limited to 2 days worth of records
DEF11542
Users list is displayed sorted by mac address, should be by extension
DEF11543
Vnxdaemon can't cope with Asterisk 1.4 restarting
DEF11555
"Operator" check box should not be displayed for 420d handsets
DEF11581
Saving dialplan page results in "Phone Registration" disabled
DEF11582
Phone is deleted when setting FMFM parallel to cell phone
DEF11583
For incoming SIP trunk call CFW FMFM to 8+external doesn't work
DEF11585
VNX user SIP DID number no longer displayed on Web UI
DEF11590
Ring group voicemail can not be played from IP phone TUI
DEF11599
Remote office phones are not updating their firmware
DEF09796
FXO tuning gain values are being rounded down
DEF11623
Web UI is blocked when upgrading
1-12
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Details of this release
Hotfix
Description
DEF11632
SLA incoming goes to main menu on overflow, should go to FXO default route
DEF11644
Asterisk sending DNS requests for SLA stations
DEF11653
Pre-dial number before hitting the SLA line key fails to send the DTMF correctly
DEF11678
Vnxdaemon scalability and memory usage optimizations
DEF11681
Unable to access mailbox options when you have a temp greeting
DEF11710
Additional French and Spanish translations
DEF11712
FXO auto-tune config file is not persistent across upgrades
DEF11713
Realm set at the SIP trunk is added as domain on username for authorization
DEF11716
Required kernel update, change to make it mandatory
DEF11723
SLA DND only applies to line 1 on phone, should apply to all line keys
DEF11731
Unable to dial extension from Auto Attendant if system is set to french
DEF11743
Intermittent display of a question mark instead of a phone icon for BLF
RN-001030-02 Rev 04, Release 1.2
1-13
AastraLink 160 Pro Software Release Note 1.2
Details of this release
Previous Enhancements and Hotfixes Included in this Release
The following hotfixes were delivered in a maintenance release since release 1.1
and have been integrated into the 1.2 release.
Please refer to the relevant maintenance release notes for further details.
New Features in Release 1.1p1
The following enhancements were previously delivered by patchkit release 1.1p1.
Feature
Description
ENH06536
An Administrator can now disable incoming Icom and related sub-features.
ENH07093
AastraLink inter-AastraLink networking over IAX: Toll bypass.
ENH08040
Administrator can now lock and modify softkey settings for each user.
ENH09015
Administrator can now configure mute on and off for Intercom calls.
ENH09017
Visual voicemail user interface navigation has been optimized.
ENH09302
Administrator can now run a manual fsck from recovery mode.
ENH09303
Administrator can now turn on netconsole from recovery mode.
ENH09305
Administrator can perform standalone (read only) badblock test of the CF card.
ENH09366
Softkey labels are now optional for non-LCD softkeys.
ENH09463
Can now view IPP firmware version of phone in the users list.
ENH09956
Phones can now be swapped without losing user configuration.
ENH10037
Administrator can now remove the paging option (opt-out) for user phones.
ENH10330
Voicemail to email notifications can now be encoded as a WAV file.
1-14
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Details of this release
Hotfixes in Release 1.1p1
The following hotfixes were previously delivered by patchkit release 1.1p1.
Hotfix
Description
DEF07439
When CompactFlash card reaches ~450M full, Web UI logins fail.
DEF08972
French Language translation correction.
DEF08976
French Language translation correction.
DEF08978
French Language translation correction.
DEF09458
Custom announcement files are not erased when doing a factory-default.
DEF09519
Recovery mode CF 'badblock' testing does not report physical errors.
DEF09529
Same ring group is shown twice in the auto-attendant drop-down list.
DEF09554
CID shows Unknown_number in name field for name absence reason code 0.
DEF09555
Changing language from Web UI does not work.
DEF09584
Web UI add user: Web UI should not allow to create users more than 4 digits
DEF09686
Self CID# is displayed instead of SIP trunking number.
DEF09706
System unresponsive when verbose and debug set to 3 & check SIP debug.
DEF09715
SIP DID number blank when added DID number in add phones.
DEF09751
An error occurred connecting to the Aastralink after editing/saving extension
DEF09770
An error occurred connecting to the Aastralink after remote phone reboot.
DEF09775
Only the first SIP trunking shows Registered; but all are registered.
DEF09796
FXO tuning override values are being rounded down to nearest 0.2 dB.
DEF09799
51i and 9143i: Vmail script terminates while accessing voicemail.
DEF09882
Preconfig, others call net_config incorrectly; net_config should handle bad args.
DEF09897
Title French Translation when Operator or Day/Night the softkey is press
DEF09898
French Prompt - Private number - displayed instead of "No confidentielles".
DEF09914
Restore does not set nameserver for static IP on reboot.
DEF09925
Run OBF badblock check in write mode to recover faulty CompactFlash card
RN-001030-02 Rev 04, Release 1.2
1-15
AastraLink 160 Pro Software Release Note 1.2
Details of this release
Hotfix
Description
DEF09938
French translation mistakes.
DEF09984
Bogus "-1" Extensions in the Corporate Directory.
DEF09999
E-mail address is not provisioned when adding a phone via the Web UI.
DEF10035
No warning tone for paging call.
DEF10043
Voice Mail escape to extension does not work for an incoming FXO call.
DEF10096
Barred numbers do not get applied for IAX calls.
DEF10140
SIP trunks timeout after 30 seconds.
DEF10175
Static IP is broken due to netconfig parser error
DEF10210
Reboot button needed on bad block test results.
DEF10220
Phone model prefixes the cancel button in softkey edit.
DEF10257
Wrong display for Unknown Name and Unknown Number in French.
DEF10260
When a default softkey permission is changed no indication of success.
DEF10324
Fall drops after 1 ring when a private number calls and the system is in French.
DEF10325
Call drops after 1 ring if call routed to call group and day/night activated.
DEF10340
Deleting a temporary greeting doesn't work when virtual voicemail menu is used.
DEF10342
Upgrade failed with vnxdaemon in coredump loop.
DEF10345
Web UI French Translation mistakes.
DEF10354
AastraLink auto-attendant not working correctly.
DEF10355
All phones reboot during upgrade, service outage.
DEF10376
Wrong message for operator in French.
DEF10381
Translation mistakes for forward calls on the phone (French).
DEF10450
Unable to change from a DHCP address to a static IP address (Web UI display).
DEF10670
Changing between static and dynamic IP addressing fails.
1-16
RN-001030-02 Rev 04, Release 1.2
Chapter 2
AastraLink Pro 160 New Features
Introduction
This chapter describes the enhancements to existing software operation, and new
software features of the AastraLink Pro 160 running Software Release 1.2.
Features listed here are incremental to the feature set of release 1.1 and earlier.
Only new 1.2 features are listed in this section. Please refer to previous release
notes for details of prior release feature sets.
RN-001030-02 Rev 04, Release 1.2
2-1
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Detailed Feature Descriptions and Usage
Description
This section summarizes the operation of each new feature, with brief usage
instructions or implementation notes as applicable.
Multiple Paging Groups
ENH04864: Previous releases of the AastraLink Pro 160 allowed you to provision
paging on a softkey for all users in a group. In release 1.2, you can now configure
multiple paging groups and use your keypad on the phone to dial a specific group.
A single phone can be a member of up to 4 paging groups only, plus a
system-wide ’all active phones’ group (660).
The following applies to the multiple paging group feature:
•
Supports up to 9 paging groups total per AastraLink.
•
Directory prefix 66 used for dial access to reach a paging group.
•
Dialing 660 reaches the system-wide ’all active phones’ paging group.
•
Phones currently in a call are no barge-in (system-wide option)
•
Intercom warning tone on/off for paging groups (system-wide option)
•
Icom key can be used as a Paging key (system-wide option).
•
Softkey can be used as a Paging key (per-user option)
•
The Phone UI displays a new Intercom/Paging screen if the phone has been
configured for a Paging Group.
Notes:
1. By default, incoming intercom calls are enabled for all IP phone models. If
required, an Administrator can enable outgoing intercom calls on all model
phones (except 51i).
2. The Icom hard key is applicable to the 480i and 480i CT only; all other
model phones (except 51i) can be configured with an Icom softkey.
3. Remote office phones cannot receive paging calls.
2-2
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Configuring a Paging Group
To facilitate the Paging Group feature, the Web UI now includes an option to
select a Paging Group to be configured at the location, Users->Groups.
Paging Group
Option
Paging Group
Members
(optional) The Password option allows you to establish a Personal ID Number
(PIN) that the user needs to enter before sending a Page.
Note: If the incoming "Barge-in" setting is disabled, or the incoming
"Auto-Answer" is disabled on the phone, the page does not go to the
speakerphone.
RN-001030-02 Rev 04, Release 1.2
2-3
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
The Paging Group you configure displays as shown in the following illustration.
Paging Group with
prefix of 66
Using XML with the Paging Group Feature
When the Paging Group feature is enabled on the AastraLink Pro, the
following displays to the phones that are members of the Paging Group:
•
Intercom - When selected, displays a screen that presents a text box that
allows you to enter the Paging Group number (for example, 661234). After
dialing the number, the phone initiates the intercom call to the Paging Group.
Note: Entering an invalid extension for an intercom call displays a brief error
before returning to the text entry screen.
2-4
•
Page All - When selected acts as a speeddial key and dials 660 to page all
configured Paging Groups.
•
A List of Configured Paging Groups - Allows you to select a specific
Paging Group for sending a page.
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Configurable Paging and Intercom Options
Release 1.2 includes the options of enabling/disabling specific Paging and
Intercom dial plan options via the Web UI. You can enable/disable the following
at the location Configuration->Dial Plan->Settings.
•
Allow Barge-In - enables or disables the paging and intercom to occur while
a phone is in the active call state
•
Play Warning Tone - enables or disables the warning tone to be heard before
a page or an intercom call on the phone.
•
Microphone Mute - enables or disable the speakerphone to mute when a
page or an intercom call is received by the phone.
•
Auto-Answer - enables or disables automatic answering of an intercom call
by the phone. If disabled, icom will be treated as a normal incoming call.
•
Paging Mode for Icom Key - enables or disables the Intercom key to act as a
Paging key, providing a list of paging groups instead of a number-entry field.
The values configured for the Dialplan page apply to all phones on the system;
there is no per-phone configuration of these options in Release 1.2
RN-001030-02 Rev 04, Release 1.2
2-5
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
.
Paging and Icom
Options
2-6
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Meet-Me Conference Bridge Feature
ENH05505: A feature has been added to the AastraLink Pro that enhances the
current 3-way conference available on the Aastra SIP phones. Release 1.2
provides AastraLink-hosted ad-hoc Meet-me Conference bridges for all users.
Conference bridges are created dynamically by the AastraLink when the feature is
accessed. If the moderator is the first to connect to the bridge, he/she is prompted
to choose a PIN; otherwise, the conference begins immediately with any users
waiting on hold (with music) joined to the conference.
A virtual conference bridge is associated to every SIP extension by adding an
accessor prefix 6 to the users phone number. For example, user 200’s meet-me
bridge is at 6200. (For more information about the conferencing dial plan, see the
“Conference Bridge Dial-Plan Table” on page 2-8).
A user calling into his/her home extension conference bridge becomes moderator
automatically. If calling from another extension (or externally) the user may
authenticate his/her voicemail credentials to become moderator. More than one
moderator login is permitted in a conference; if no moderator exists (i.e. all
moderators leave the conference) the conference is terminated.
When a moderator dials into a conference from a phone other than the his/her own
phone, the number 6102 must be dialed to allow password authentication of the
moderator. (For more information on dial plan numbers, see the “Conference
Bridge Dial-Plan Table” on page 2-8.)
The moderator can optionally configure a PIN on the conference bridge. If the
PIN is configured, users must enter this PIN before they can be joined into the
conference on the bridge.
Note: Any users currently in the hold queue prior to a moderator joining will
be added automatically. To differentiate between a PIN moderated and a
non-PIN moderated call, the moderator will NOT be prompted to create a PIN
for a conference if there are already users on hold waiting. Such a conference
shall be considered 'insecure'. The moderator can leave the conference, and
cause it to be terminated, before re-connecting and assigning a PIN.
RN-001030-02 Rev 04, Release 1.2
2-7
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Host Capacity Limitations
Meet-me conferencing capability is dependent on the available host CPU capacity.
AastraLink Release 1.2 supports a total of 12 simultaneous host-routed sessions.
One session is defined as a SIP trunk call, a remote office call, a conference call
participant, a voicemail call, or an auto-attendant call.
Calls directly between local SIP phones do not use a host session and are excluded
from the 12 session limit.
Conference Bridge Dial-Plan Table
The following table identifies the dial plan for dialing into the AastraLink Pro to
initiate the conferencing feature. Conferencing numbers are listed in bold.
DialPlan Numbers
6 Feature Access
0 Local Features
00 Paging
01 Relay
02...09 Unused
10 FXS A
11 FXS B
12 AutoFAX
20...99 Unused
1 Local CallP Features
00 IVR
01 Vmail
02 ConfMod
1 Unused
2* virtual extension
3* virtual extension
4* virtual extension
5...9 Unused
2 Meetme Extn
3 Meetme Extn
4 Meetme Extn
5 Call/Ring Groups
6 Paging/Intercom Groups
7 Call parking
8 Unused
9 Unused
2-8
Directory Numbers
6000
6001
Overhead paging
Activate Relay
6010
6011
6012
FAX/Phone A
FAX/Phone B
FAX A/B Auto selection
6100
6101
6102
Auto-attendant IVR
Voicemail
Conference Moderator
612xxx
613xxx
614xxx
Secondary SIP phones
Secondary SIP phones
Secondary SIP phones
62xxx
63xxx
64xxx
65xx
66xx
67xx
Meet-me owned by 2xxx
Meet-me owned by 3xxx
Meet-me owned by 4xxx
Ring Group xx
Paging Group xx
Parked Call xx
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Call Parking to Display the Parked Number on the Phone UI
ENH06041: In previous releases, after parking a call, an audible announcement
would be made stating the extension or number of the parked call.
In release 1.2, in addition to the audible announcement, the Phone UI now
displays the extension or number of the parked call on its screen for quick
reference.
Web UI Click-to-Call Links Allow Editing
ENH06001: When a call comes into a phone, the calling number is stored in the
Callers List. You can then click on the Callers List entry to automatically dial the
number to return a call.
Release 1.2 now allows you to edit the number before returning the call.
RN-001030-02 Rev 04, Release 1.2
2-9
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Secondary Generic SIP and Softphone Support
ENH07125: The AastraLink Pro now supports non-Aastra SIP terminals and
softclients. The generic account is not directly able to be dialed, but rings in
parallel with the main Aastra phone ti which it is associated.
Outgoing calls may be placed from the generic SIP device, and calls support
direct signalling therefore enhanced capabilities such as video softclients may be
used between each generic SIP device.
The account registration information is 61 + main extension (e.g. 61200) and the
password for registration is the users voicemail password/Web UI login.
Note that if any of the main phone account information is changed, the generic
account is disabled until the Aastra phone re-registers with Asterisk (this can be
instantaneous or require some time if the Aastra phone requires a reboot).
Secondary Phones Can be Manually Enabled/Disabled on a Per-User
Basis
ENH10496: By default all secondary generic SIP phones and softphones are
disabled after adding the phone to an AastraLink Pro network. An Administrator
can manually enable each phone on a per-user basis as required.
To enable/disable a secondary phone:
2-10
1.
After adding a secondary phone to you network, click Users.
2.
Click on a user’s extension.
3.
On the General tab, click in the "Secondary Enabled" field to place a
checkmark in the box and enable the secondary phone for the user, and click
SAVE.
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
4.
To disable the secondary phone, remove the checkmark, and click SAVE.
Secondary Enabled
field
The dialplan line prefix for the secondary phone displays as "61" at the
location Configuration->Dialplan->Settings as shown in the following
illustration.
Secondary Line
Prefix
Caller ID on FXS Ports
ENH08998: Support has been added for FXS Caller ID display for call set to
the FXS device. Calling name/extension and number (where known) display
according to the country-specific CLID capability set.
RN-001030-02 Rev 04, Release 1.2
2-11
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Ability to Add FXS Extension to a Ring Group
ENH08300: In Release 1.2, a User/Call Group is now called a Ring Group to
differentiate it from the newly added Paging Groups.
After adding a new Ring Group or editing an existing Ring Group, you can add
the applicable FXS extensions to the Ring Group. Note: FXS phones support only
ring groups, they cannot receive calls as part of a paging group.
Using the Web UI, you can now assign FXS extensions to Ring Groups at the
location Users->Groups.
The following illustration shows a list of FXS extensions,.
Ring Group
FXS extensions in
Ring Group
2-12
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Added Key System Shared Line Appearances (SLA)
ENH09001: In Release 1.2, the AastraLink Pro now provides Shared Line
Appearance (SLA) which allows the AastraLink to provide key system features in
addition to its existing Private Branch eXchange (PBX) functionality.
SLA and PBX can be used exclusively (i.e. all FXO lines as SLA, or all FXO lines
as PBX) or in a mixed mode. To differentiate between modes, the AastraLink user
interface refers to non-SLA lines as ’Pool’ lines, as they provide pooling of
incoming and outgoing lines for call processing purposes.
About Shared Line Appearances
A traditional key system has telephones with multiple buttons ("keys") and lights
that indicate which lines are in use. When you want to place a call, the user
presses a button to directly select the external FXO line connected to the
telephone company.
All Aastra SIP phone models support the AastraLink SLA feature except 420d
DECT handsets and 6751i SIP phones. The SLA supported phones use a visual
indication to show the line state (idle/ringing/in-use/hold). Indications are
provided via the LED on a line hard-key (L1, L2, etc.), LCD on a soft-key, or
LED on a programmable key.
The state of the line - busy, ringing or hold - is shown by the flashing state of the
LED or icon indicator, for hard-keys the color of the indicator also shows whether
the current phone (green) or another phone (red) is using the line.
SLA and the AastraLink Pro
In Release 1.2, SLA is configurable on a per FXO basis on the AastraLink Pro.
When no FXOs are configured as SLA, all 6 FXO ports perform the PBX dial
plan operation as outlined in Release 1.1 of the AastraLink Pro.
Any FXO ports not allocated for SLA use will be available for processing PBX
calls, and for Pool outgoing calls. A configurable timer allows SLA incoming
calls to overflow to PBX dial plan routing (auto-attendant, ring groups etc.), and
outgoing PBX calls will overflow to SLA lines if no FXO Pool line is available.
RN-001030-02 Rev 04, Release 1.2
2-13
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
SLA membership - i.e. whether a phone is to participate in the SLA key system, or
whether it is to be permitted access to PBX Pool lines only - can be configured
independently for each local and remote office phone.
SLA Key Mapping
FXO line to SIP phone key mapping for SLA varies by phone model.
The following table describes the mapping of the hard and soft line keys on the
SIP phone with the FXO ports on the rear of the AastraLink Pro.
SLA Supported
Phone Models
FXO 1
FXO 2
FXO 3
FXO 4
FXO 5
FXO 6
Mapping To AastraLink Pro
9480i / 9480iCT base
L1
L2
L3
L4
Softkey
L5
Softkey
L6
9143i
L1
L2
L3
Softkey
L4
-
-
6757i / 6757iCT base
L1
L2
L3
L4
Softkey
L5
Softkey
L6
As base
As base
As base
As base
As base
As base
6755i
L1
L2
L3
L4
Softkey
L5
Softkey
L6
6753i
L1
L2
L3
Softkey
L4
-
-
6751i
-
-
-
-
-
-
L1
L2
Softkey
L3
Softkey
L4
-
-
-
-
-
-
-
-
CT handset
6730i / 6731i
DECT 420d handset
For all phones, off-hook maps to "Pool line" which allows PBX dial plan calling.
The pool line feature sets the phone to L7 (9480i, 9480i CT, 6757i, 6757i CT,
6755i) or L5 (9143i, 6731i & 6753i) in the phone configuration when it is in the
idle state.
Note: SLA is not supported on Model Phones 6751i and 420d Handsets. These phones default to the line
pool operation only. If all FXO lines are configured for SLA, these phone models will not be able to receive
incoming FXO calls.
2-14
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
SIP phone features for SLA lines
When a User dials on an IP Phone, the phone assumes that the line on which the
user is dialing is a Pool line. If SLA is enabled on the phone, the phone changes its
behavior when the User dials out on a line. If SLA is enabled and specific features
on the phone are used (for example, redial, speeddial, transfer), the User must
specifically direct the feature to use the SLA line for the feature to work in that
mode.
The features affected by SLA include:
•
Redial list
•
Speed-dial softkey
•
3-way conference
•
Call transfer
Redial
To perform a Redial using a Pool line....
press <Redial> then press <Redial> again.
To perform a Redial using an SLA line L1.... press <Redial> then press <L1> key.
Speeddial
To perform a Speeddial using the Pool
line....
press the Speeddial key.
To perform a Speeddial using the SLA line
L1....
press <L1> and then press the Speeddial
key.
Note: Because Pool lines require prefix 9
for outside access, and SLA lines require
direct dialing, the same speeddial key
cannot be used in both modes.
3-Way Conference
Conferencing can be initiated for Pool or SLA incoming calls, but the target of the
conference (the third party being invited to join the call) can only be a Poll line or local
extension.
SLA lines cannot be the invitee of a 3-way conference call.
RN-001030-02 Rev 04, Release 1.2
2-15
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Call Transfer
The transfer (Xfer) key is a Pool line only feature, and does not operate for incoming SLA
calls.
SLA lines cannot be the target of a call transfer.
Using AastraLink SLA from the SIP Phones
If SLA is configured on an FXO port, the following occurs for all phones:
2-16
•
The line indicator flashes quickly when a call comes in, and the phone rings.
•
When the call is connected and answered, the line indicator lights up solid.
For hard-line keys (L1, L2, etc.) it will show green on the answering phone,
and red on all other phones.
•
When the call is placed on hold, the line indicator flashes slowly
For hard-line keys (L1, L2, etc.) it will show green on the holding phone, red
on all other phones.
•
Any phone can pickup a call from the held state.
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Configuring SLA on the AastraLink
You can configure an FXO port as SLA using the Web UI at the location,
Configuration->Dial Plan->FXO Lines. For each line, you can set the option
"SLA" to assign the FXO port as a shared line appearance.
RN-001030-02 Rev 04, Release 1.2
2-17
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
SLA Membership
By default, all existing SIP phones (and any new SIP phones added to the system)
use the shared line FXO configuration if it is enabled on the AastraLink.
Phones can be individually removed from the SLA feature by editing the phone in
the Administrator’s Web UI user list, and toggling the ’SLA Enabled’ option.
SLA toggle
Configuration Changes
If the AastraLink SLA configuration changes for any FXO, all phones will be
rebooted for the line key change to be applied. If membership is changed for a
single phone, that phone only reboots.
Note: If you enable the SLA feature on the AastraLink:
2-18
•
Phone Xfer is not supported for SLA lines.
•
Redial and Speed-dial default to using the Pool line.
•
When the Speaker key is pressed, or receiver goes off-hook, Pool line is
automatically selected.
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Automatic Tuning Wizard No Longer Requires a Phone Call
ENH09002: In previous releases, the Automatic Tuning Wizard required you to
place a call to adjust audio and audio gain on the FXO ports of the AastraLink.
In Release 1.2, the Automatic Tuning Wizard is now completely automated and
performs the adjustment without having to place a call.
FXO tuning is recommended for all systems at installation time, in order to tune
the AastraLink to match the telephone line, minimizing echo and maximizing the
audio quality.
Tuning is performed on the first available (connected/idle) line, and the resulting
values applied to all lines.
You can start the Automatic Tuning Wizard, if required, using the Web UI at the
location, Configuration->System->FXO Tuning.
Use the following procedure to start the Automatic Tuning Wizard:
1.
Click on Configuration->System->FXO Tuning.
The default values display on this screen.
2.
If adjustment of the Dynamic Range is required, select the required value for
your network before starting the Auto-Tune process.
RN-001030-02 Rev 04, Release 1.2
2-19
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
3.
Click the Auto Tune button. The Tuning Wizard automatically adjusts the
FXO line hybrid parameters for best balance with your telephone network
lines. This process may take up to 15 minutes to complete, but usually less.
Note: You can cancel the Automatic Tuning Wizard any time by clicking the
Abort button during the tuning process. The parameters remain unchanged if
you Abort the Automatic Tuning Wizard
4.
When the Automatic Tuning Wizard is complete, the following screen
displays.
Note: Auto-tuning should be repeated if any changes are made later to the
physical FXO line connections or tuning parameters.
2-20
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Call Transfer Directly to a User’s Voicemail
ENH09005: A feature has been added to the AastraLink that allows incoming
calls to go directly to a user’s voicemail if required, without the call ringing on the
phone. When a call is transferred to voicemail, the caller hears the "unavailable
message", and the callee hears no ring splash.
To transfer a call directly to voicemail, you enter the prefix of ** before the dialed
number from local extensions (for example, **4545). This routes the inbound call
to the voicemail prompt of the users mailbox rather than to the users phone.
Admin Disable of User Accounts
ENH09034: An Administrator can now disable user accounts from being
registered on the AastraLink Pro, but still retain the configuration for the phone in
the system. Disabled accounts cannot make or receive calls, and cannot log into
the Web UI. Also, the Corporate Directory lists only enabled accounts.
You can disable user accounts using the Web UI at the location, Users->User List.
After clicking on a user in the list, click on the General tab. The following screen
displays for you to enable or disable the user on the AastraLink.
Enable user by
placing a check mark
in the box
Disable user by
removing check mark
from the box
RN-001030-02 Rev 04, Release 1.2
2-21
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Allow Incoming Call Routing Selection for Individual FXO Lines
ENH09351: Release 1.2 now allows you to configure individual FXO lines for
which incoming calls are routed. In addition to Default (which will send calls via
the configured incoming call route on the auto-attendant page) and SLA, you can
configure a specific target extension, a Ring Group, the Auto-Attendant, FXS
phones, or the Operator.
Note that this feature also now allows you to provision FXO lines regardless of
the line state (i.e. even if there is no FXO line voltage) to enable for FXO
loopback door entry phone use.
You can configure the FXO lines using the Web UI at the location,
Configuration->Dial Plan->FXO Lines.
2-22
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Voicemail Breakout on * to Login Prompt
ENH10322: The AastraLink now allows a remote caller to retrieve their
voicemail messages by pressing the * key during the voicemail announcement.
This brings the caller directly to the voicemail login menu. The caller can then
enter their ID and password to access their mailbox and listen to messages.
Note: Pressing 0 (zero) during a user's voicemail announcement brings the
caller to the Operator extension, or if configured, the users Escape Extension
(provisioned at My Phone->Preferences->Voicemail).
MBU 400 and 420d Handset Integration
ENH10346: The AastraLink Pro now supports the Aastra Mobility Base Unit
400, and the Aastra 420d DECT Handset. You can register up to 8 handsets with
each MBU. The MBU supports up to 3 SIP calls simultaneously. Note that the
PSTN port of the MBU is not currently supported when MBU400 is configured by
AastraLink - outbound PSTN calls will be routed via the AastraLink FXO ports
Multiple MBU 400 units can be added, identified by MAC address, and then
registered to the AastraLink Pro. Each registered handset receives a SIP extension
on AastraLink, including Web UI login and voicemail.
RN-001030-02 Rev 04, Release 1.2
2-23
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
You can add MBU units to the AastraLink Pro using the Web UI at the location,
Configuration->VoIP->Mobility Base Units.
Once an MBU is registered, the administrator can provision extensions for
individual handsets by clicking the "Add Phones" button at the location,
Users->User List page and select the "Aastra420d" phone type.
If one or more MBU is registered, the "Mobility Base Unit" drop-down list will
show the available handsets (max 8 per MBU) to choose from.
Phone Type is
Aastra 420d
2-24
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
MBU Configuration Download from the AastraLink
The "User List" page indicates that an extension is an MBU handset by listing the
phone type as "Aastra420d". However, handsets will show as disconnected until
the handset has registered to the MBU, and the MBU has been provisioned to use
AastraLink as its configuration server.
You can set the MBU to receive configuration downloads from the AastraLink Pro
by setting the "Configuration Server Address" as the IP address of the
AastraLink, on the "Management Settings" page, and then rebooting the MBU
Refer to the MBU400 documentation for additional details.
RN-001030-02 Rev 04, Release 1.2
2-25
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Handset Registrations
After adding the MBU and Users in the AastraLink Web UI, provisioning the
MBU to use the AastraLink as its configuration server, and rebooting the MBU,
the MBU will enter service with 420d handsets registered and ready for use.
The MBU Web UI has been reduced to just the pages relevant for AastraLink; all
further user configuration is now performed via AastraLink Web UI (for example:
Call lists, voicemail, call forward, find-me follow-me, etc.)
For an MBU handset, the "My Phone" page looks the same as other phones
except there is no "SoftKeys" tab (similar to a user with a 51i IP Phone).
Note: The MBU handsets do not support XML, and therefore, cannot be used
as an operator extension.
Removing an MBU removes all extensions and handsets that were associated with
that MBU, and clears its configuration server association to the AastraLink.
2-26
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
SIP Trunking Single-Digit Prefix
ENH10347: The AastraLink Pro currently supports the dialing of a prefix + index
when multiple or single SIP trunks are setup. The user must dial 8+index+number
to dial out.
In Release 1.2, the AastraLink now supports single-digit prefixes on a single SIP
trunk. Now a user can dial 8+number when a single SIP trunk is configured, and
8+index+number when multiple SIP trunks are configured.
You can select whether to configure single or multiple SIP trunks by choosing
"Single" or "Multiple" for the SIP Trunk Mode parameter at the location,
Configuration->Dial Plan->Settings.
SIP Trunk Mode
RN-001030-02 Rev 04, Release 1.2
2-27
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Setting the SIP Trunk Mode to "Single" displays the following screen at
Configuration->VoIP->SIP Trunking.
Setting the SIP Trunk Mode to "Multiple" displays the following screen at
Configuration->VoIP->SIP Trunking.
2-28
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
FXS Port Hotline Operation
ENH10525: The FXS ports on the AastraLink Pro now support 'hotline'
operation, where going offhook automatically calls a preconfigured directory (or
call group) number.
You can configure the FXS port hotline feature using the Web UI at the location,
Configuration->Dial Plan->Settings.
Phone Hotlines
An Administrator can select (from a drop-down box) an extension or Ring Group
that is automatically dialed when a phone, attached to the specified FXS port,
goes off-hook. This feature is available on both FXS ports. The Administrator can
return the FXS port to its normal behavior by selecting the "None" option. This
sets the FXS port to only dial SIP extensions or Call Groups (the same as in
previous releases).
RN-001030-02 Rev 04, Release 1.2
2-29
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Support for 6730i and 6731i IP Phones
ENH10563: The AastraLink Pro now supports two new SIP phones: 6730i and
6731i. For more information about these phones, see the Aastra 6730i and 6731i
SIP Phone User Guides.
Prompt Administrator if Updates are Required
ENH10551: The AastraLink Pro now prompts the Administrator if there is a
firmware version mismatch between the on-board flash (OBF) and the compact
flash (CF).
The Admin can agree to update, in which case the AastraLink reboots and installs
the new boot code, or the Admin can reject the update.
The administrator may also be prompted to run FXO auto-tuning of their lines, if
this has not been performed since the last software update was installed.
If a prompt is rejected, AastraLink will prompts the Admin again at login after the
next reboot of the system.
2-30
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Single Digit Routing Table for Auto-Attendant Main Menu
ENH10651: The AastraLink Pro now allows you to press a single digit on your
phone’s keypad (0 through 9, *, or #) when navigating the Auto-Attendant Menu.
After the Administrator has recorded/uploaded a custom menu announcement,
you can configure a single digit key to match that announcement using the Web
UI at the location, Configuration->Auto-Attendant->Custom IVR.
RN-001030-02 Rev 04, Release 1.2
2-31
AastraLink 160 Pro Software Release Note 1.2
Detailed Feature Descriptions and Usage
Custom IVR Configuration
When custom IVR menu is enabled, you can configure any single-digit key on the
standard DTMF phone keypad to be used like a speeddial, to immediately perform
any of the following in the Auto-Attendant menu:
•
Dial by Name
•
Dial by Extension
•
Play another custom greeting
•
Ring admin configured number for that key
•
Go to Operator voicemail
•
Go to voicemail access
•
Replay the menu
•
Unused/Empty (plays the key number and runs invalid key handler)
From this screen, you can also select whether to disable "Dial-by-Name", dial by
First Name, or dial by Last Name.
Onboard Flash Recovery Firmware Changes
The onboard flash recovery mode has been enhanced with additional support
functionality. Two new pages were added to the recovery mode Web UI in 1.1p1:
•
Repair - allows the CompactFlash filesystem to run a File System Check and
optionally repair the filesystem using more thorough detailed checking than
the automatic boot-time method.
In release 1.2 this page now also allows the extraction of the current
AastraLink database from CompactFlash into .abf backup format.
•
2-32
Advanced - allows advanced debugging of an AastraLink system which is
failing to boot from its CompactFlash card. It is only intended to be used
under instruction of Aastra support personnel.
RN-001030-02 Rev 04, Release 1.2
Chapter 3
AastraLink Pro 160 Known Issues
Introduction
This section describes any new known issues in AastraLink Pro 160 release 1.2.
It includes a summary and work-around (where applicable) for each issue.
RN-001030-02 Rev 04, Release 1.2
3-1
AastraLink 160 Pro Software Release Note 1.2
Known Issues
Known Issues
This section describes the known issues in AastraLink Pro 160 release 1.2
Documentation Issues
The following table is a list of issues that will be documented in the AastraLink
1.2 Administrator Guide. Summaries of the changes are included below.
Issue
Description
DOC11065
Incoming SIP trunk call routing to voicemail.
For detailed information on this issue, see the section, “Supported and
Unsupported Codec Behavior on the AastraLink” on page 3-3.
DOC11067
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 3-3.
3-2
RN-001030-02 Rev 04, Release 1.2
AastraLink 160 Pro Software Release Note 1.2
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, voicemail, 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-001030-02 Rev 04, Release 1.2
3-3
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 premesis, 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.
AastraLink 160 Pro Software Release Note 1.2
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.
Other Known Issues
The following table is a list of other known issues in Release 1.2.
Issue
Description
DEF06482
Dynamically refreshing parked call list is invalid during early stage
DEF06756
Pressing a BLF softkey off hook during a conversation dials again
DEF07264
Long names cause numbers not to be displayed in TUI Call List
DEF07713
Activating the relay using the Relay key has no CDR
DEF08457
Calls can only be transferred once, drops on multiple xfer (A->B->C)
DEF09708
2 entries in the "Call List" on leaving voicemail
DEF09786
When CFWD All is set, Call list doesn't show the forwarded status
DEF09808
FXO call list and CRD log shows "Answered" status when canceled
DEF09994
Blind transferring one ring group to another results in all lines ringing
DEF10018
Transferring call from one ring group to another results in no overflow
DEF10789
WebUI restore fails if backup file is >80MB, requires manual restore
DEF11027
Setting highest index softkey drives operator keys off page.
DEF11342
expansion module on 57i has wrong label on top - "List 1, Lis"
DEF11407
1-digit custom IVR should permit a recording for each language
DEF11445
Backup/restore with static route results in VNX sending DHCP discovery
DEF11513
Calls from 420d handset to Voicemail are seen as calls to "Unknown"
DEF11546
Asterisk 1.4 doesn't do full SRV lookup for SIP trunks, only does A lookup
DEF11617
mDNS responder does not reply after asterisk restart, requires reboot
DEF11645
SLA line switching with no calls should release previous line
DEF11658
Short dialtone stutter heard when you select SLA line
DEF11674
Voicemail count is incorrect for systems upgrade from 1.1 GA
RN-001030-02 Rev 04, Release 1.2
3-5
Chapter 4
AastraLink Pro 160
Software Licensing and Copyright
AastraLink Pro 160 Release 1.2 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 Software Licensing
41-001204-02 REV 00
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-001030-02 Rev 04, Release 1.2
4-1
AastraLink 160 Pro Software Release Note 1.2
AastraLink Pro 160 Release 1.2 Software Licensing
Licensing
Document
About Screen
4-2
RN-001030-02 Rev 04, Release 1.2
AastraLink Pro 160
Software Release 1.2
Published in the USA
RN-001030-02 Rev 04
Software Release Note
November 2008