Difference between revisions of "RMD - Release Notes"
From Zenitel Wiki
| Line 1: | Line 1: | ||
=RMD Release 01.10 (2010-06-03)= | =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 RM "health" status. | ||
| Line 6: | Line 7: | ||
==RMD Functional Changes / Enhancements== | ==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 | + | 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. |
Revision as of 08:00, 7 June 2010
Contents
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 RM "health" status.
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.