General

Profile

neels

Issues

Projects

Activity

06/18/2019

10:23 PM OsmoMSC Bug #2880 (Resolved): OsmoMSC never releases MO call if MNCC doesn't respond to SETUP
TC_mo_setup_and_nothing passes.
I hope that means the issue is resolved.
10:04 PM OsmoMSC Bug #2880: OsmoMSC never releases MO call if MNCC doesn't respond to SETUP
(I have since then become familiar with MNCC setups and can indeed investigate this one. Once I get to it.)
09:55 PM OsmoMSC Bug #2921 (Rejected): Second of two subsequent runs of TC_lu_by_tmsi_noauth_unknown failed
killing this issue since it is about outdated code.
09:18 PM OsmoMSC Bug #3735 (Stalled): call arriving during another call has no voice
09:18 PM OsmoMSC Bug #3735: call arriving during another call has no voice
this was resolved, but should be re-tested with new osmo-msc...
(Ideally with a ttcn3 test, but we don't verify the ...
09:16 PM OsmoMSC Bug #3996 (Resolved): memory leaks in osmo-msc after neels/ho merge
09:11 PM OsmoMSC Bug #4007 (Feedback): msc crashes with sigsegv on "sh subscriber msisdn xxxxx" via vty
@roh can you test again with current master? Code has changed since you reported the bug. Looking at the current code...

06/12/2019

02:17 AM OsmoBSC Support #4058 (New): verify that re-using ARFCN+BSIC pairs across separate BSS works
A remote BSS may re-use an ARFCN+BSIC pair that is also used in the local BSS.
Verify in a test that an inter-BSC ha...
02:13 AM OsmoBSC Support #4057 (New): verify that re-using ARFCN+BSIC pairs within a BSS works
Any ARFCN+BSIC pair may be used any number of times in a BSS.
If a given cell reports good RXLEV for a specific ARFC...
02:05 AM OsmoBSC Support #4056 (New): verify that legacy handover configuration still works after introduction of inter-BSC HO support
The legacy handover configuration is that all ARFCNs used by any BTS are indicated as neighbor ARFCNs for all cells.
...

Also available in: Atom

Add picture from clipboard (Maximum size: 48.8 MB)