Actions
Feature #4917
closedreporting of alarms/errors known to the icE1usb
Start date:
12/18/2020
Due date:
% Done:
70%
Spec Reference:
Description
Now that the device firmware is exposing error situations / counters via a dedicated interrupt endpoint, we should make use of this in osmo-e1d.
See https://gerrit.osmocom.org/c/osmo-e1d/+/21782 and https://gerrit.osmocom.org/c/osmo-e1d/+/21783 for a start.
We should also consider if and how to report such errors to the clients (libosmo-e1d users).
Furthermore, there is also important knowledge to be gained from parsing the TS0, such as- does the remote end indicate alarm via A bit
- does the remote end report CRC errors via E bits
Checklist
- receive and report device-reported errors in VTY+LOG
- pass error informatio n to clients/users
- process TS0 to learn about reported remote errors
Updated by laforge over 3 years ago
- Checklist item process TS0 to learn about reported remote errors set to Done
https://gerrit.osmocom.org/c/osmo-e1d/+/21808 adds reporting of E and A bits to VTY and log
Updated by laforge about 2 years ago
- Checklist item receive and report device-reported errors in VTY+LOG set to Done
Updated by tnt 1 day ago
- Checklist item pass error informatio n to clients/users set to Done
- Status changed from Stalled to Resolved
Sometime ago jolly passed on the LOF through event, now we also send LOS and AIS.
https://gerrit.osmocom.org/c/osmo-e1d/+/36689
https://gerrit.osmocom.org/c/osmo-e1d/+/36690
Actions
