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\>
AMC 08.28 (2003-03-28)
Release: Official, available on request NVRAM version 08.27.
Errors Corrected
ERR 1688: Answer Mail during off hook fails.<br\> ERR 1693: Stations in privacy is not reported up/down to the group call alocator.<br\> ERR 1694: Remote mail show 0 mails on proxy station.<br\> ERR 1696: HotLine feature activated when lifting handset in conference.<br\> ERR 1699: 9700 (93/1) causes reset when no pager defined.<br\> ERR 1701: Connection cleanup after software error timeout.<br\> ERR 1703: DualDisplay navigation key is not working in AlphaNet.<br\> ERR 1704: Parallel Handling of Call Request.<br\> ERR 1705: AMC-board, future battery problems.<br\> ERR 1706: RIO do not communicate with AMC.<br\> ERR 1707: EDO: Non printable ASCII 09 (TAB) is transmitted as multiple space characters.<br\> ERR 1708: M-key in MultiModul conversation causes reset.<br\> ERR 1711: Call Back mail not restored after reset.<br\> ERR 1712: AGA station; Event type 17; not restored immediately after reset.<br\>
ERR 1714: Hebrew directory not in Alphabetical order:<br\> Corrected. <br\>
ERR 1715: Simplex conf. to a not connected station is not cancelled:<br\> Corrected. Added conference disconnect code for "stations down"<br\>
Functional changes
Global flag: ignore_st_down_in_conv:<br\> If station is reported down while in conversation no reset of conversation occurs, Station is reported down after conversation reset.<br\>
Global flag: no_prog_during_grcall:<br\> Temporary disconnect all station from program while in groupcall.<br\>
New Station Bit Map Flags:<br\> Previous configured as DAK features in COS:
- Station flag bit 10 1 = FEAT_DAK_DISPLAY_DIRNO (DualDisplay)
- Station flag bit 11 1 = FEAT_AUTO_CANCEL
- Station flag bit 12 1 = FEAT_AUTO_DIR_NO_CONN
- Station flag bit 13 1 = FEAT_AUTO_INQUIRY
- Station flag bit 14 1 = Station has DAK display, can be used for CRM4 functionality in DualDisplay hardware
Load control default turned off:<br\> Let the system go on full speed.
Possible to use param1 for feature 52 and 85:<br\> This can be used to group event triggers by filtering on sub event type.<br\>
Key trigger event FEAT_DIGIT_EVENT(105):<br\> When activating this feature all succeeding digits are reported to the event handler and is trigged as EVENT_TRIGGER(25) with sub event equal to digit dialed 0-9. The event is ON as long as the station key is down and reported off when key is released (can be used for camera control ++).<br\> FEAT_DIGIT_EVENT with param1 = 0 display the digit hold down, with param1 different from 0 the display is not updated and can be updated by the event handler to indicate “left” “up”, “down” ++.<br\> <br\> <br\> <br\>
AMC 08.27 (2002-11-12)
Release: Official, available on request NVRAM version 08.27.
Errors Corrected
ER 1687: MPC data protocoll:<br\> Many carriage returns required on input command. The uart buffer is reset after restart<br\>
ER 1690 x827(611) RIO communication fails:<br\> Reversed to previous uart drivers.<br\> <br\> <br\> <br\>
AMC X08.27 (2002-06-11)
Release: Official, available on request NVRAM version 08.27.
Functional changes
AlphaNet Link Snatch:<br\> AlphaNet links is set to lowest priority during line test. Previously the audio test had normal priority. Now normal priority call will snatch AlphaNet links under test if no other links available.<br\>
Number of Voice Messages Increased to 80:<br\> It is now possible to use 80 stored voice messages. Thus change of NVRAM version.<br\>
Voice over IP functionality added. (Comuniq related):<br\> New DP command DUPLEX_DELAY used to set delay on duplex switching in 10 ms intervals. This message follows the AlphaNet audio path to the destination exchange where the duplex switching takes place.<br\>
Event Trigger Related To Conference:<br\> Conversation outgoing can be related to Conference directory numbers. It is now possible to use the event type 08-Conversation - Outgoing "When Related to” for conference directory numbers. The owner is the current speaker and %2.dir is the conference dir no. and %2.nam is the name of the conference. <br\><br\>
Errors Corrected
ER 1683: Dial_Digit command during simplex conference:<br\> $DD command is now working during conference and toggle feature etc. <br\>
Bug: HOTLINE call activated during conference:<br\> Hotline call activated without any testing on active hotline flag on station during conference while using handset. (DealerCom DAK Display update bug fix. Not relevant to current systems)<br\> <br\> <br\> <br\>
AMC X08.27 (2002-05-03)
Release: Official, available on request NVRAM version 08.26.
Functional changes
MPP optional parameters added:<br\> The MPP command has been extended with three new parameters, beep code, repetitions (number of transmissions) and priority. All three parameters are optional and may be substituted by the wild card (*) character. <br\> MPP <pager id> <sender> <"text"> <beep code> <repetitions> <priority><br\>
New Data Protocol message for set station COS membership $SSC / 0x0090:<br\> With this message a stations COS membership can be altered to any of the valid COS groups (1..16).<br\> $SCC L105 U8<br\>
New Data Protocol message for modify COS contents $MCC / 0x0091:<br\> Data Protocol messages for modify the contents (delete/add/toggle feature) in a COS group.<br\> $MCC U5 U100 U2<br\>
Possible to define ASLT as AlphaNet audio:<br\> ASLT lines can be programmed from AlphaPro to be used as AlphaNet audio links in the same way as AGA ports.<br\><br\>
Errors Corrected
Bug in $ST timer after reset:<br\> After reset all active event handler programmed timers was deleted.<br\>
ER 1685: Bug in Event Trigger Related To Global Group Call:<br\> The initiator of the global group call is now available on the initiating node %1. For global group call the %2.dir and %2.nam will contain the global group directory number and name. <br\> <br\> <br\> <br\>
AMC 08.26 (2002-02-19)
Release: Official, available on request NVRAM version 08.26.
Functional changes
Inquiry During Connection Changes:<br\> To inhibit inquiry during private ringing and other unwanted situations, the FEAT_INQUIRY is changed to be context sensitive. It is now only available when the inquiring station is in a “clean” connection. The change applies both to FEAT_INQUIRY and FEAT_AUTO_INQUIRY. (This functionality was meant to be available in 8.25 but an unfortunate compiling did mess it up on the released version)<br\>
AlphaPro Data Compression:<br\> Compression of data between AlphaPro and AlphaCom. A new version of the good old AlphaPro do an AMC version check and use compression if version is 8.26 or greater except for version 8.90 (Bank version). This means that both AlphaPro and AlphaCom are compatible in all version directions. It is possible to use a mix of new and old AlphaComs in an AlphaNet. The compressed frames will be tunnelled through old AlphaComs.<br\>
Changes FEAT_TRIG_EVENT and FEAT_TRIG_EV_SILENT:<br\> It is now possible to do a FEAT_TRIG_EVENT and FEAT_TRIG_EV_SILENT during conversation as an inquiry that will return to the conversation. The previous version would reset the conversation after FEAT_TRIG_EVENT.<br\>
Menu Navigation From DAK Keys:<br\> A new feature is implemented to send navigation directions to the menu system from DAK keys. (The navigation directions are the same system as used in nvram for programming directions of the station keyboard in menus: 7 => Left, 9 => Right, 2=> Go to previous level. etc)<br\>
FEAT_MENU_NAVIG, feature number: 97, Feature class: FCL MENU:<br\> The param1 value indicate navigation direction: param1 Description 0 Up to previous level in menu structure 1 Down to next level in menu structure 2 Go to previous (left) menu element on same level 3 Go to next (right) menu element on same level 4 Activate if possible, else navigate downwards 5 No action<br\>
Event Trigger Related To Group Call:<br\> Conversation outgoing can be related to group call directory numbers. It is now possible to use the event type 08-Conversation - Outgoing "When Related to” for group call directory numbers. The owner is the initiator of the group call, and %2.dir is the group call dir no. and %2.nam is the name of the group. The %2.phy is always 0. The initiator of the group call will only be available on the initiating node in a global group call. For global group call the %2.dir and %2.nam will contain the global group directory number and name. %1 for group call is the initiator. Because there is no known initiator for global group call the %1 is directed to station 1 (system station). <br\>
New Directory Table Sort Algorithm: New sort algorithm to avoid reset during huge table sorting. Restriction: If you have more than 255 stations beginning with the same display text character, stations with this particular letter will only be sorted on the first display text character.<br\>
Special Inquiry Feature for DAK Keys:<br\> Previous the DAK command “directory numbers during connection” used inquiry. The new solution is based on DAK using a new feature FEAT_AUTO_INQUIRY (feature no 102). The new feature is identical to the FEAT_INQUIRY. If DAK inquiry is wanted during conversation then include FEAT_AUTO_INQUIRY in COS (class of service). This makes it possible to stop inquiry from DAK and still have inquiry available during regular use (press 2 during connection). This feature applies only to the DAK command “directory number form idle”. “Directory number during connection” will have the same functionality as before.<br\>
DAK: Cancel Ongoing Conversation, Make New Connection:<br\> This is available by including FEAT_AUTO_CANCEL (feature no 103) in COS. This feature will reset any ongoing call the station is active in before handeling the DAK key. This feature applies only to the DAK command “directory number form idle”. “Directory number during connection” will have the same functionality as before. If both FEAT_AUTO_INQUIRY and FEAT_AUTO_CANCEL are added to COS, the auto cancel will be the winning feature.<br\>
Use Directory Number During Connection and Directory Number From Idle on Same DAK:<br\> This is available by including FEAT_AUTO_DIR_NO_CONN (feature no. 104) to COS. The feature find next event in DAK string if “directory number during connection” is received when station in idle. During connection the directory number from connection will run as before. It means that you have to program the DAK string with “directory number during connection” prior to “directory number from idle”. This command can be used for door opening during conversation. And thus you can use the same key for setting up conversation and opening the related door. DAK string “D 6 I 101” will dial up 101 if activated from idle and then open door if pressed during connection. Side effect: If several doors (D 6 I xxx), new DAK will open current door even if auto cancel is (104) enabled
New DAK E–command:<br\> The E-command will only work for FEAT_TRIG_EVENT and FEAT_TRIG_EV_SILENT. The E-command activates the event without using the inquiry/parking functionality. Thus it is possible to activate the event a number of times during connection (inquiry is restricted to one time). The action that is taken is the same, independent whether the station is in conversation or not, it just triggers the event. <br\>
Voice Messages Increased to 30:<br\> It is now possible to use 30 voice messages.<br\><br\>
DealerCom Functions
The full DealerCom functionality will be available in AMC version 9.00 but some of the features is available in 8.26. The only usable feature for today’s stations is:<br\>
Alpha Numeric Name Search System:<br\> A new search system like mobile phone address book. Use keys 1-9 to enter the (start of) the name. The “0” key is used as backspace to make it possible to correct the typed in text. To get out of the search menu the user must press the C key. When the user press select (“M” key) the first display line shows the name closest to the entered characters. By pressing “arrow up/down” the user can start stepping from the name displayed in first line like today’s name directory stepping after selecting character. The escape key (“2”) will bring the user back to the alphanumeric input for further editing of the search string. By pressing select in the user list there will be placed a call to the name shown in the display. Autoload AlphaNumSearch: Directory number 9537, Feature 21 param1 = 13. The characters related to each key can be edited in the MDF file.<br\><br\>
Errors Corrected
ER 1673: Event Trigger with parameter:<br\> If a station has physical number different from the user number, the Event Trigger with parameter (event type 25, feature 95) does not work for this station. In AlphaPro you specify the physical number as the event owner, but the event 25 seems to use the user number instead. Also if you use UDP group as owner it will not work as long as the user is different from the physical no.<br\> Fix: The event 25 is changed from using user id to use physical number.<br\> <br\> <br\> <br\>