AlphaCom 5.xx - 7.xx - Release Notes

Software in production: AMC 08.01<br\> Software released date: 2000-03-01<br\> Note: Additional features available in 08.20<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\>

AlphaCom 5.xx to 7.xx Release Notes

AMC 07.63 (1999-12-13)

Release: Official, available on request
NVRAM version 07.20

Functional changes

---

Load control can be disabled:<br\> Load control algorithm introduced in AMC 07.11 can be disabled. (We try to find out if the load control algorithm is a bit conservative, giving too low throughput.) This option must be activated from the TST console on the master, use the “nvram” command, set module_profile.st_profile [0].volume_level to an non-zero value.<br\> <br\> <br\> <br\>

AMC 07.62 (1999-11-30)

Release: Official, available on request
NVRAM version 07.20

Errors corrected

---

Load NVRAM from flash backup if NVRAM is corrupted, more improvements:<br\> Observation: AMC with bad battery may not restart after a power off. Problem was that after the NVRAM programming was loaded from the flash, a error -message was logged before the state-part of NVRAM was autoloaded. If the state-part was corrupted, this operation could give a processor reset. Corrected.<br\>

AMC realtime-clock driver tries to restart clock if stopped:<br\> AMC realtime clock may stop if the AMC battery is bad. The SW checks the status of the realtime clock and try to restart the clock if it as stopped.<br\> <br\> <br\> <br\>

AMC 07.61 (1999-08-12)

Release:  Official, for selected customers 
NVRAM version 07.20

Errors corrected

---

Wrong line number in line error reports:<br\> ER 1471: Observation in AMC 07.60: A line error is reported to a display station as port number 65536. ToneTest skip reports port no as 998. Corrected. <br\>

Callback on mail from remote exchange ends in private ringing:<br\> ER 1475. Observation in AMC 07.60. Corrected. <br\> <br\> <br\> <br\>

AMC 07.60 (1999-06-29)

Release:  Official, for selected customers 
NVRAM version 07.20

Errors corrected

---

Paging 44 does not work:<br\> ER 1455: Observation: Paging using 44 during conversation does not work in versions AMC 07.11 - 07.12. (This is due to a bug in the “optimize-for-time” compiler option.) Corrected. <br\>

Load NVRAM from flash backup if NVRAM is corrupted, improvements:<br\> If NVRAM data are loaded from flash at startup, a few checks on the NVRAM data are added to make sure that the exchange can complete the start up using these data. If the test fails, autoload is performed.<br\>

Priority mail events not reported:<br\> ER 1461, 1462. Observation in AMX X07.60 versions: the event "Priority mail in idle" is never reported off. The event Priority Mail is not reported at all. Corrected.<br\>

Open Duplex Conference mixer in board position 20 gives reset:<br\> ... at startup. ER 1468. Corrected.<br\>

Various adjustments to format of texts written to log-port:<br\> All reports does now print month before day. Adjustments to station-line-error report.<br\> <br\> <br\> <br\>

AMC X07.60 (1999-06-11)

Release:  Official, for selected customers 
NVRAM version 07.20

Functional Changes

---

SET_DIRNO_TEXT (119) data protocol message / action added:<br\> Makes it possible to change the text of a directory number from data-protocol or event handler. Format :

SET_DIRNO_TEXT( NET_OBJ_REF /*Directory number */, TEXT16                /* New text */ )

Example of use from event handler: $set_dirno_txt L8201 'Georg' The function was made for SEG for a Silent Alarm application.<br\>

Load NVRAM from flash backup if NVRAM is corrupted:<br\> If the magic number at the start of the NVRAM is incorrect, AMC will at start-up check the flash-backup. If the backup is valid and has the correct NVRAM-version, AMC will load the NVRAM from the flash backup instead of doing a autoload. <br\> It has been a few reports on that the NVRAM is autoloaded for no reason. This may be because of EMC-problems, bad battery or SW-errors, we don’t now yet. This feature should remove most of the problems if this happens.<br\> <br\> <br\> <br\>

AMC X07.60 (1999-06-10)

Release:  Official, for selected customers 
NVRAM version 07.20

Functional Changes

---

EXT_MAIL and Q_ELEM_ADDED dataprotocol messages adjusted:<br\> The outgoing EXT_MAIL(48) and Q_ELEM_ADDED(75) dataprotocol messages are adusted. The mail-reference parameter is now put in LOCAL_ENTITY format, not LOCAL_DIRNO. The change was requested by Cetec. <br\>

Support for duplex station in open-duplex conference:<br\> If a station has the “open duplex station” property flag set from AlphaPro, the station is allowed to enter a open-duplex conference without lifting the handset. <br\><br\>

Errors corrected

---

Reset related to groupcall camp-on queue on Gong:<br\> ER 1456: Observation: In multimodule systems having several non-overlapping groups covering more than 2 modules, the system resets in some situations. The frequency of resets is higher if the gongtone has long a duration (e.d door bell feature). Corrected.<br\> The problem occurs if one group call is active, and a second non-overlapping group call is in camp-on on the gong. If the first one is answered, and the waiting group has members in 3 modules or more, connection of audio will cause reset due to timeslot inconcistency.<br\> <br\> <br\> <br\>

AMC X07.60 (1999-06-04)

Release:  Official, for selected customers 
NVRAM version 07.20

Functional Changes

---

CONN_REQUEST dataprotocol message works with AlphaNet:<br\> The CONN_REQUEST (10) dataprotocol message can now be used to set up conversation between two stations in different exchanges in a AlphaNet. (Earlier versions of AMC supported only CONN_REQUEST-call between stations in the same exchange. <br\><br\>

Errors corrected

---

Exchange does not start if Intercard Cage data link is disabled:<br\> This error was introduced in AMC X 07.60, in conjunction with the flow control. The error is now corrected.<br\> <br\> <br\> <br\>

AMC X07.60 (1999-06-01)

Release:  Official, for selected customers.  MultiConference 
Main new feature: MultiConference
NVRAM version 07.20

Functional Changes

---

Faster exchange boot:<br\> Some optimizations of the runtime system, plus some adjustmenst to basic station handling has reduced time from reset until all stations in the master module is available to come 50 seconds. Slaves still are somewhat slower due to all serial communication that must take place.<br\>

General exchange speed and reliability improvements:<br\> Same modifications as AMC 07.11. Traffic capacity increase of some 40% for bank & finance high traffic systems.<br\>

MultiConference System:<br\> The Simplex Conference feature has been extended to allow a MultiConference, which allows one station to be member of (listen to) up to 8 Simplex Conferences at one time, and speak into one of them at a time.<br\> The MultiConference requires a MCS station to use all features. A MCS station is just a mechanical variant of the CRM4 station. The station has DAKs which allows operation like this: press, speak while holding, release to diconnect. The DAKs has LEDs indicating current channel allocation, and which channel has audio.<br\> As you can see below, most features can be set up using a standard station, so this functionality has a number of other applications also

AGA “board use” MultiConference Monitor:<br\> An AGA channel (two SBI channels) can be set up as MultiConference Monitor. This means that up to 6 Simplex Conferences are mixed, and the sum is available as a 0dB audio signal out of the AGA board. 8 monitors are available total, while 6 is easiest to wire in using a ASLT filter and conncetion board where the conferences are avaiable as ab-wires.<br\> For AGA boards in board positions 21 and 22 (multiprogram AGA positions), the MultiConference mix will be available in the corresponding programs also, allowing standard stations to listen to multiple conferences.<br\>

Features / dir.nos for MultiConference system:

7980 "MCSActivate"	feature=10 	id=0/1
7981 "MCSPriority"	feature=10  	id=2
7984 "MCSDeActAll"	feature=10  	id=3
7982 "MCS Select"	feature=11
7983 "MCSTalkBack"	feature=1

All these features are implemented as regular features with additional parameters. They can be dialed from a keypad for testing, but must be allocated to DAK keys to be useful for a customer.

• TalkBack: Parameters are <AGA board/channel/subchannel> <conference><br\>The configuration of the key controls AGA hardware. Pressing the key while listening to a MultiConference feeds the conference.
• Select: Parameter is <conference> <TalkBack DAK><br\>Reprograms the TalkBack key’s <conference> parameter.
• Activate: Parameter is <TalkBack DAK>, <TalkBack DAK>, <TalkBack DAK>,<br\>Pressing Activate enters a mode where TalkBack keys are toggled in and out of it’s pre-selected conference. When toggled in, audio is heard immediately. Terminate by pressing Activate once more.
• Priority: Parameter is <TalkBack DAK>.<br\>Switches OFF all conference monitoring, then forces ON the selected channel.
• De-activate all: Parameter: <none><br\>Variant of priority, i.e. switches off everything.

Events for Simplex Conference:<br\> New events:

• Simplex_Conference_Member: Occurs when a station joins or leaves a conference. Related_to = Conference.<br\>Sub-event 0 = ASLT member, sub-event 1 = AGA member.
• Simplex_Conference_Audio: Occurs when someone feeds the conference (but not driven by station M-key in this sw version).

Data protocol message: AUDIO_DETECTED ($VOX):<br\> Data message which signals to the conference that audio is present. Can be generated e.g from RCI connected to an Audio Detection Board, or a radio system’s squelch output. For use in action strings, use abbreviation $VOX.<br\>

OWN action command:<br\> Event Handler action command which can replace the %1 and %2 station references. Useful from RCI to look up a stations phys.no and name, or in Event Handler to reference a CRM4’s DAK keys.<br\>

%1.DAK action string parameter:<br\> This parameter looks up a DAK string in in a station’s DAK tables, and returns the key number. Intended for use together with the IND action which controls LEDs on CRM4 / MCS stations, so that LED indication goes automatically to the relevant DAK, and if DAK configuration is changed, indication will follow.<br\>

Simple Link Layer to AlphaCom data protocol:<br\> Readable ASCII formatted data protocol suited for debuging with a standard ASCII terminal. Full AlphaCom data protocol available.<br\> To simplify operator interface, symbolic names can be used for commands.<br\> Type $dial_digits L101 L102 to connect 101 to 102.<br\> Network layer is also available, so @2 $dial_digits L101 L102 means “send the command to node 2 and execute it there”.<br\>

Event Handler Actions are full data protocol:<br\> The symbolic form of the Simple Link layer is also possible to send from the Event Handler’s action strings. This means that RCIs and Events now can do virtually all exchange features, including controlling other exchanges in AlphaNet. Errors Corrected<br\>

Reset due to Hot-swap of AGA:<br\> ER 1358: If you take out an AGA board in pos. 20 or 21 for service while the exchange is running, the exchange will reset. Corrected. Probably introduced in 07.20 with the AGA Board Use functionality.<br\> <br\> <br\> <br\>

AMC 07.33 (1999-08-27)

Release:  Official, for selected customers (bugfix)
NVRAM version 07.20

Error Corrected

---

Stento Multidrop Linklayer - Slave mode: No retransmitts:<br\> Observation: The Stento Multildrop linklayer in slavemode (developed for the Taipei underground system): Frames are not retransmitted even if ACK is missing. Correction: OK.<br\> <br\> <br\> <br\>

AMC 07.32 (1999-03-25)

Release:  Official, for selected customers (bugfix)
NVRAM version 07.20

Functional Changes

---

Open duplex conference dataprotocol message added:<br\> If a external device includes a station into a open duplex conference (830x), the AlphaCom will now return a message when the handset is lifted and the station is connected to the conference-audio. The new message is:

OD_CONF_ENTERED 118 (0x0076)
NET_OBJ_REF   /* Station which enters conference /
NET_OBJ_REF   /* Which conference /

<br\>

Error Corrected

---

Data activation of Call request transfer to remote station fails:<br\> Observation: E.R. 1424: Dataprotocol message SET_REQ_TRANSF to a remote node+dirno does not work. No display update, and no transfer of mails. This works if the transfer is activated from the station. Correction: OK.<br\> <br\> <br\> <br\>

AMC 07.31 (1999-03-10)

Release:  Official, for selected customers (bugfix)
NVRAM version 07.20

Error Corrected

---

MPP with free text does not work:<br\> Observation: E.R. 1430: When sending a MPP free text message to radio pager from eventhandling/RCI, nothing happens. Correction: OK. The AlphaCom added a control character to the text in the ESPA message, which made the paging reject the message.<br\>

Tone test fails in slave module:<br\> Observation: E.R. 1406: The Station line Tone Test generated tones on stations in slaves, but reported all as faulty. Correction: OK<br\>

#SERVICE* work only one time after reset if not #TST ON*:<br\> Observation: #SERVICE* works only once if #TST ON* has not been used first. Correction: OK.<br\>

Optimised some CPU wasting:<br\> Observation: Exchange feels slow in high traffic. Correction: 11% of the AMC CPU capacity was used to scan the 6 APC-RCI’s and do some interrupt loadcontrol. This load has been reduced to 0.1%, freeing up CPU-capacity for other useful work. <br\><br\>

Known Bugs and/or Workarounds:<br\> Reset when Hot-plugging AGA board:<br\> Observation: Removing a AGA board when the exchange is operating may cause reset. This is especially a problem during commissioning, as the AGA releases resources according to NVRAM, which can have been changed by AlphaPro since the last exchange start-up.<br\>

Hotline DAK 8 activated always when going on-hook:<br\> Observation: Hotline will often be configured to start after 5 seconds, i.e. in many cases the hotline DAK 7 will NOT be activated. The hotline on-hook action DAK 8 will ALWAYS be activated though. As this is intended e.g. for CancelCallRequest, redundant messages should do no harm.<br\> <br\> <br\> <br\>

AMC 07.30 (1999-01-18)

Release:  Official, for selected customers.  New functions.
Includes AMC 07.08 and 07.09 corrections.
NVRAM version 07.20

Functional Changes

---

Feature added: Disconnect own station from ongoing groupcall:<br\> If you press C-key or dial 7884 on a station which is receiving a groupcall, the sound from the groupcall will disappear from this station. Limitations:

• The station will not be free to receive a new groupcall before the first groupcall is disconnected totally.
• EVENT/RCO control is not turned off before the groupcall is disconnected totally.

The disconnect-from-groupcall feature has feature-number 53. Feature 53 is not autoloaded into class of service 1. C-pres in Idle disconnects ongoing groupcall if feature 53 is included in the ClassOfService for this station. (C-pres in conversation just disconnects the conversation as before).<br\> Disconnect-from-groupcall is also available as a data protocol message (116).<br\>

Logging of line errors to remote exchange and/or external device:<br\> AlphaCom can be programmed with two addresses which will receive error report messages. If the receiver is an AlphaCom exchange, it will print the error report on the system log port. The format of the printout has been adjusted to fit a report on a single line. <br\> The error reports are sent using a new data protocol message with well defined parameters, STATUS_REPORT(114). External devices like a PC can use this message in a logging application. <br\> AMC 07.30 can only route reports regarding station line errors to remote devices. Support for routing reports for boards, audio lines etc will come in AMC 08.00. Current versions of AlphaPro can not program the forward addresses. Until AlphaPro 08.00 arrives, use the nvram-command on the TST-port.<br\> ex_profile.line_monitoring.report1_addr<br\> ex_profile.line_monitoring.report2_addr <br\>

LOG action - Print to system log from Event Handler / RCI:<br\> You can program something like LOG “Door B4 opens” as an action for a RCI or a system event. When this the condition is triggered, the text “Door B4 opens” is printed on the system log port, preceded by a timestamp. This feature can be used to set up simple call logging applications. <br\> The printout is rerouted in the same way as that line-error reports. The printout is sent via the new message LOG_STRING (117). <br\>

Insert name of event source in action (%1.NAM()):<br\> In the event handling the code %1.NAM() inserts the display text name of the “owner” of the event. %2.NAM() inserts the name of the “related-to” dir.no of the event. This is particularly useful with the LOG command described above, but can also be used for other purposes, like sending mail to pocket pagers or stations. <br\> The name inserted is 12 characters wide, right padded with space. %2.NAM() only works if %1 and %2 is in the same exchange. <br\>

MPC protocol input commands: >, <, - _:<br\> Support for the following MPC protocol input commands added:

> aaaa (M-pres)
< aaaa (M-release)
- aaaa (Offhook)
_ aaaa (Onhook).

MPC protocol is intended for legacy applications. New applications should use the AlphaCom protocol. <br\>

Check if M-key pressed when entering program conference:<br\> If the M-key is pressed when a station is included into a conference, the station starts feeding the conference. Requested for an evacuation application where conference-setup and M-key use is controlled by external equipment.<br\>

Telephones on ATL are not required to press M in groupcall:<br\> If a telephone connected to a ATL board starts a groupcall, the microphone is connected to the groupcall immediately after the gong tone. <br\> (Tip: It is also possible to program M-pres on * (DAK-1) and M-release on # (DAK-2). This will allow the telephone to set absence, call forwarding etc. without having to wait for timeout.) <br\>

Simple conversation setup from data protocol:<br\> A parameter has been added to the CONN_REQUEST (10) message, which can specify that AlphaCom shall not require acknowledge messages to set-up and disconnection. This makes it possible for a simple “fire and forget” application to set up conversations in AlphaCom. <br\>

Fast startup / reset of external device (RIO):<br\> If AMC 07.30 is used together with RIO 02.10 SW, the AlphaCom can detect a RIO reset and restore the RIO state within a few seconds. Earlier versions of AMC has to rely on a several minute timeout to detect reset of RIO. The AlphaCom can also detect a new RIO added to the bus within a few seconds.<br\> AMC now polls devices programmed in NVRAM all the time, also when AMC thinks the RIO is missing. This allows the RIO to inform AMC of its presence. (Requires ack-timeout to be set to 200ms or lower.)<br\>

TST port “rack” command display SW version of boards:<br\> Useful for debugging.<br\><br\>

Error Corrected

---

Improved errorhandling on ISO1745 linklayer (RIO communication):<br\> The ISO1745 linklayer (used for RIO communication) implementation is improved to handle noise on the databus in a better way. The probability of loosing messages is reduced. What has been done:

• Extra characters received due to noise are ignored.
• Retransmits message if a select sequence fails.
• Faster timeout on missing RIO activity (previously 10 seconds, now 1 second).

RIO 02.10 SW should be used to improve the RIO error-handling. <br\>

Global groupcall blocked by missing exchange:<br\> Observation: E.R. 1339: If an exchange that is member of a global group goes down, the global group call becomes busymarked after a couple of minutes. The group call becomes available again when the faulty exchange comes up again. Correction: OK<br\>

Reset when SendAll from AlphaPro:<br\> Observation: E.R. 1414: The Exchange resets during SendAll from AlphaPro, just after the directory numbers has been sent. This happens if many directory numbers has been reprogrammed, but all display texts still has the autoloaded value “Station nnn”. This condition caused the sorting of the namelist to take 22 seconds, which in turn caused the watchdog to trig exchange reset. Correction: OK (sorting algorithm slightly adjusted)<br\>

OpenDuplex conference via AlphaNet had closed microphone:<br\> Observation: E.R. 1410: Dial into an exchange via AlphaNet, and join a local conference by dialing 83xx. The conference sound is heard, but the microphone is not switched on. Correction: OK <br\>

Hot plug in of standby AMC board reset active AMC board:<br\> Observation: ER 1386. (Hot standby requires modifications to both AMC and APC HW) Correction: OK <br\>

AMC board in standby mode has confusing LED indication:<br\> Observation: AMC in standby mode blinks green like the active AMC, how do you know which is the active one? Correction: AMC in standby mode is steady green<br\>

AMC standby instability when used with the multidrop linklayer:<br\> Observation: Taipei railroad project: If the data link to the active AMC board failed, the system reset it self several times before it settled down with the AMC on the working datalink being master. Correction: OK<br\>

Leap year handling wrong:<br\> Observation: E.R. 1421: 29 days in February every year if you adjust clock sometime between 1 jan and 28 feb. Otherwise 28 days in February, even if is actually a leap year. A consequence is that wakeup (7883) does not work from evening feb 28 to morning mar 1. <br\> Correction: OK (After SW upgrade you have to set the AlphaCom clock once to set the leapyear counter right. Use AlphaPro or station (785) to set the clock.) <br\>

Partial remote number on DAK did not work towards TouchLine:<br\> Observation: Program a partial remote number plus digit to complete the remote number on a DAK. The remote exchange is a TouchLine. The connection in the remote exchange fails. Example: "4" is a partial remote number, "400" is the dir.no. of a station in the remote exchange. Programming "I4 P00" on a DAK does not work. Correction: OK (This is really a bug in TouchLine TAC, but AMC 07.30 goes around the problem)<br\>

Reset when global groupcall is overridden by priority:<br\> Observation: E.R. 1418: A global groupcall is started from a multimodule exchange. The groupcall is disconnected by a higher priority groupcall in the exchange of the initiator. This leads to exchange reset. Correction: OK <br\>

Reset when busy override of digit 0 pressed in conversation:<br\> Observation: E.R. 1420: Station A is in conversation with station B. Station A is pressing digit 0 (probably for mic-mute). Station C dials to A, gets busy and uses busy-override (MM or 58). The conversation is not set up, B is not disconnected. If station C presses C-key, subsequent conversations to or from A will fail. If station C presses digit 5 before pressing C-key, the exchange will reset after 10 seconds. Correction: OK <br\> <br\> <br\> <br\>