AlphaCom 8.xx - Release Notes
From Zenitel Wiki
<br\> Software in production: AMC 09.01<br\> Software released date: 2003-05-06<br\> Note: Additional features available in 08.27<br\> Note 1: We sometimes do bugfixes in older versions while working with a new version. You can’t read the list version by version, and always assume that a correction is included in the next. Be aware of high release numbers, e.g. 06.05 vs. 07.01. Check version dates, and also comments for each version. <br\> Note 2: For each software version the NVRAM version is listed. If the NVRAM version is different, the AMC board must be coldstarted, and then you must do a SendAll from AlphaPro to restore the configuration.<br\><br\>
Contents
AlphaCom 8.xx Release Notes
AMC 08.29 (2003-11-13)
Release: Official, available on request NVRAM version 08.27.
Functional changes
Open Duplex Call mode option to $CALL Data Protocol message:<br\> Call mode options, parameter 3 in $CALL Data Protocol message: New option: 128 / 0x80 (CSF_OPEN_DUPLEX): Force call to be in Open Duplex mode<br\>
Key trigger event FEAT_DIGIT_EVENT(105): Added start event:<br\> Improvement of feature introduced in version 08.28: Report EventTrigger (15) when the FEAT_DIGIT_EVENT feature is activated. (%1 = station, %2 = Feature Directory number. %CHG = ON). Corresponding OFF-event when the feature is disconnected.<br\>
Conversation in “PNCI” mode: Digits reported as events:<br\> Conversation with a station of type PNCI (Conversation with external system); New: Digits keys are reported to Event Handler as EventTrigger w/UserParam (25) with sub event equal to digit dialed 0-9. (%1 is calling station, %2 is PNCI.) The event is reported ON when the key is pressed, and OFF when it is released. (Many applications: Integration with cameras, recorders, PABX.) <br\><br\>
Errors Corrected
ERR 1719: Mail in Idle: Mismatch between Current Mail and display text:<br\> Corrected. The station display was not updated.<br\>
ERR 1723: Global Conference do not work with AE1:<br\> Corrected. Illegal sub channels were used for AE1.<br\>
ERR 1738: AlphaNet call setup fails when all scanners are busy:<br\> Description: When all scanners are busy the activation of an AlphaNet call will reset two active conversations, but still not start the AlphaNet call.<br\> Changes made:
- 1. The priority of the AlphaNet setup is now based on the priority of the initiating station. Previously it always used Alarm priority.
- 2. The snatch of scanner routine is fixed to only snatch from one communication (if the communication has allocated 2 scanners.)
- 3. The initiating and transit node(s) in an AlphaNet call will no longer require scanners, hence the bug fix in point 1 and 2 is no longer valid for err 1738 but will reduce call resets when snatching scanners by alarm priority call setup. <br\>
ERR 1745: Exchange reset when dialing too many digit during camp on for an AlphaNet line:<br\> The reset occures when the AlphaNet reseourse becomes available again. If the sum of the number of digits dialed to reach the camp on queue and the digits dialed in the queue reach 9 the reset occured.<br\>
ERR 1746: Exchange reset during faulty conversation setup sequence:<br\> Software error timers are used to control that a function sequence is performed within a limited time, or else the feature is canceled. In a high traffic system resources can be heavy loaded and thus activate the reset. A conversation cleanup could in some rare situations end in an exchange reset.<br\> <br\> <br\> <br\>