Project

General

Profile

Feature #4917

reporting of alarms/errors known to the icE1usb

Added by laforge about 1 month ago. Updated about 1 month ago.

Status:
In Progress
Priority:
Normal
Assignee:
Target version:
-
Start date:
12/18/2020
Due date:
% Done:

20%

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

History

#1 Updated by laforge about 1 month 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

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)