RMD - Release Notes
From Zenitel Wiki
Contents
RMD Release 01.19 (2010-12-17)
This release was made to fix the problems experienced with the mail forwarding when Call Request was activated and a transfer was made to another Call Request Group/Station, bug reported from Stentofon Australia. RMD version 1.17 to 1.18 was internal test releases and was never a general release.
RMD Errors Corrected
RMD now handles mail forwarding between Call Request Groups.
RMD Functional Changes / Enhancements
RMD now uses the DPMT_SET_CALL_REQ_MODE to respond to a mail forwarding/call transfer in the Call Request Group. This is used both for mail forwarding and to terminate/cancel/delete the Call Request mail. If the on/off parameter is OFF then RMD will start a timer (500 ms). If this timer times out then this is regarded as Call Request terminate/cancel/delete and the RM station will be switched off else if the ON parameter enters before timeout then this will be regarded as a Call Request mail transfer to a new Call Request Group.
RMD Release 01.16 (2010-06-29)
This release was made to fix the problems experienced at the Basurto Hospital in Bilbao, Spain. RMD version 1.12 to 1.15 was internal test releases for Basurto Hospital and was never a general release.
RMD Errors Corrected
RMD Functional Changes / Enhancements
Increased number of initial fsm_ind's from 6 to 20. The function that should dynamically allocate more fsm_ind's seemed to fail (unknown reason, malloc() in global C lib compiled with different compiler than rmd (timesys) ?). Anyway, the increase in fsm_ind's seemed to fix the problems experienced in Basurto Hospital. Also changed reason status in AUDIO_LINK_NOT_AVAILABLE param #1 from value 2 (faulty) to value 1 (busy) and AlphaCom calls to busy RM stations will now camp on busy and not be abrupt disconnected.
RMD Release 01.11 (2010-06-08)
RMD Errors Corrected
Corrected A station node in Event Report
RMD Functional Changes / Enhancements
RMD Release 01.10 (2010-06-03)
This was a release for the Spanish Hospital project Basurto in Bilbao, but have general impact and interest for all RMD projects that might be realized in the future. The following issues has been addressed:
- Detection of the RM system "health" status and pre-emptive handling according to this.
RMD Errors Corrected
RMD Functional Changes / Enhancements
RMD now detects if the RM systems replies with status U(nobtainable) a certain number of times within a certain time period. If two or more status U are received within a pre-determined time period the RMD will regard this as if the ETP process in the RM is no longer operational and the RMD will end transmitting the Heartbeat message to the RM. This will force the RM system to clear all ETP releated data and disconnect all ETP related calls. Similarly the RMD process in the AlphaCom will disconnect all RM related calls. The RM & RMD processes will normally be operational within 10-15 seconds.
RMD Release 01.04 (2010-05-21)
This is the first official release of the Ring-Master Daemon, all previous releases was X releases.
RMD Errors Corrected
The ETP link heartbeat seemed to fail regularly. Rewritten the SW controlling the ETP link status in the RMD.