General

Profile

laforge

  • Registered on: 02/07/2016
  • Last connection: 11/03/2017

Issues

Projects

Activity

11/20/2017

08:04 PM OsmoSTP Bug #2668 (Resolved): osmo-stp: endless loop in osmo_timer_del()
It seems that https://gerrit.osmocom.org/4939 solves the problem. More testing required to be sure.
07:13 PM OsmoMSC Bug #2669 (New): osm-msc doesn't clean up BSC state
If a BSC has ever sent a BSSMAP RESET to OsmoMSC we acknowledge this with a RESET-ACK. But then it appears we keep i...
07:09 PM OsmoSTP Bug #2668 (Resolved): osmo-stp: endless loop in osmo_timer_del()
When using current osmo-stp master, I quite frequently get it into a state where it consumes 100% CPU and infinite lo...
07:08 PM OsmoMSC Bug #2667 (New): osm-msc reports "invalid or out-of-range index"
When starting osmo-msc on Debian unstable with no sms.db file, I get:...
07:07 PM OsmoMSC Bug #2666 (New): osmo-msc crashes when receiving SCCP with RI=GT from A
On the A interface, we use SCCP with PC/SSN only. However, if a SCCP message with RI (Routing Indicator) = GT (Globa...
04:40 PM Cellular Infrastructure Bug #2664 (Closed): document our default point codes in the wiki
See [[Point_Codes]]
04:40 PM Cellular Infrastructure Wiki edit: Point_Codes (#1)
04:23 PM OsmoSGSN Bug #2665 (New): OsmoSGSN doesn't listen on reasonable default point code
OsmoMSC already has compile-time default point codes, so let's make sure we also have one for the SGSN. 0.23.4 looks...
04:22 PM Cellular Infrastructure Bug #2664 (Closed): document our default point codes in the wiki
the default point codes like 0.23.1-N are not documented anywhere. Let's do this like with port numbers.
04:21 PM OsmoHNBGW Bug #2663 (New): osmo-hnbgw missing reasonable default configuration for sigtran
unlike e.g. osmo-bsc, osmo-hnbgw doesn't have a reasonable "sane" default configuration. The config includes "127.0....

Also available in: Atom