 |
Aastra Phone Support
Description
Aastra Phone SupportRelease notes
Version 2.5.1 - Early deployment
- Bugfix: Update base stations firmware to 6.2 (M15272)
- Dependency:
- SOP Base Module 1.5.2+
- SOP API 2.27.5+ (Optional: If the access to the Corporate Directory via the micro-browser is used)
- Improvement: Register a ZEROCONF user when no config is specified. (M9338)
- Feature: Added Mitel OMM System 6.1 (M13633)
- Dependency:
- SOP Base Module 1.5.2+
- SOP API 2.27.5+ (Optional: If the access to the Corporate Directory via the micro-browser is used)
- Feature: Add new Aastra phone 6737i (M10280)
- Dependency:
- SOP Base Module 1.5.2+
- SOP API 2.27.5+ (Optional: If the access to the Corporate Directory via the micro-browser is used)
- Feature: Added Aastra OMM System 5.0 (M9281)
- Dependency:
- SOP Base Module 1.5.2+
- SOP API 2.27.5+ (Optional: If the access to the Corporate Directory via the micro-browser is used)
- Bugfix: Old configuration files were not deleted after an apply changes (M8764)
- Dependency:
- SOP Base Module 1.5.2+
- SOP API 2.27.5+ (Optional: If the access to the Corporate Directory via the micro-browser is used)
- Bugfix: All symbolic links were broken by the postsync task (M0)
- Bugfix: Speeddials were not added to virtualphone after pum login (M8652)
- Dependency:
- SOP Base Module 1.5.2+
- SOP API 2.27.5+ (Optional: If the access to the Corporate Directory via the micro-browser is used)
- Bugfix: Update Aastra firmware to 3.2.2.3109 (M7200)
- Dependency:
- SOP Base Module 1.5.2+
- SOP API 2.27.5+ (Optional: If the access to the Corporate Directory via the micro-browser is used)
- Improvement: Allow to detect phone type by SIP useragent in Phone libraries. (M5417)
- Improvement: Remove old profile configuration files when logging out with PUM. (M5417)
- Bugfix: PUM shell tools sometimes failed when database inconsistencies occurred. (M5417)
- Dependency:
- SOP Base Module 1.5.2+
- SOP API 2.27.5+ (Optional: If the access to the Corporate Directory via the micro-browser is used)
- Bugfix: phone was exiting corporate directory when using the corportate directory and the Idle URL together (M6087)
- Dependency:
- SOP Base Module 1.5.2+
- SOP API 2.27.5+ (Optional: If the access to the Corporate Directory via the micro-browser is used)
- Improvement: Get ConditionalIdle library to show queue status on the screen of the phone (M0004969)
- Dependency:
- SOP Base Module 1.4.4+
- SOP API 2.27.5+ (Optional: If the access to the Corporate Directory via the micro-browser is used)
- Improvement: Potential update impact level 2
: in the event this update contains a bug, it might have critical impact. Respect dependencies and retest your most important callflows and applicative integrations. Latest Aastra firmware (M5262)
- Dependency:
- SOP Base Module 1.4.0+
- SOP API 2.27.5+ (Optional: If the access to the Corporate Directory via the micro-browser is used)
- Improvement: Multilingual support for Dir.php (M0004835)
- Dependency:
- SOP Base Module 1.4.0+
- SOP API 2.27.5+ (Optional: If the access to the Corporate Directory via the micro-browser is used)
- Feature: Added support for RFP L35 (M0004943)
- Dependency:
- SOP Base Module 1.4.0+
- Feature: ConditionalIdle service added (M0004946)
- Dependency:
- SOP Base Module 1.4.0+
- Feature: Added support for 6739i phone (M0004465)
- Feature: New firmware v2.1 for Aastra SIP-DECT RFP L32 IP (M0003954)
- Feature: Implemented PUM for aastra (M3130)
- Bugfix: Includes Dir.php
- required for zeroconf
- default config allows to call zeroconf IVR
- Feature: Initial version
Module configuration interface
create_resource_form: .:/usr/share/escaux/glue/lib:/usr/share/escaux/glue/bin/gen_wiki_documentation/src/lib:/usr/share/escaux/glue/bin/gen_wiki_documentation/src/lib/
Module configuration parameters
- DSCP marking: Decimal DSCP value used for SIP and RTP. Enter comma separated list of 2 DSCP values for SIP and audio RTP in decimal.
Auto-provisioning
Please consult the Customer DHCP Server configuration guide for more information about the DHCP options necessary for autoprovisioning of this type of device.Active-Active support
The Aastra phones support the Escaux active-active configuration. In this mode the Aastra phone registers and uses the primary SOP for outgoing calls. If the primary SOP is down, the phone will register to the secondary SOP after a registration timeout in order to receive incoming calls and will use the secondary SOP for the outgoing calls. The registration timeout can be configured in the corresponding Aastra phone resource (see Registration refresh period parameter) This feature is supported only with resource version 1.02 or higher.Auto-answer support
In order to implement the intercom feature. A specific call flow must Set the variable __ALERT_INFO=info=alert-autoanswer before dialing the phone.SetRingTone action compatibility
It is now possible to control the ringtones from a call flow using the SetRingtone action. Please refer to the SetRingTone action documentation for more information. The following value for the ring tone are available:| Ring Tone | Description |
|---|---|
| 1 | Repetitive sequence of long ring and long silence |
| 2 | Repetitive sequence of short ringing, short silence, short ringing, long silence |
| 3 | Repetitive sequence of short ringing, short silence, medium ringing, long silence |
| 4 | Repetitive sequence of medium ringing, long ringing, short ringing, long silence |
| 5 | Single medium ringing |
SOS calls with the 632d handset
The Aastra 632d handset offers the possibility to play a distinctive ringtone when an SOS call is received. To implement this, 2 steps have to be taken:- The SOS number needs be configured in the resource
- The handset needs to receive a call from the SOS number. To change the caller ID number of a call, the SetCallerID action can be used in the callflow.
Copyright © Escaux SA