Miscellaneous Projects » Ericsson RBS 6xxx

For some strange reason current wireshark seems to be completely unable to decode the OM2000, I don't have the time right now to start investigating that, sorry. Without a proper decode it's hard to know what's happening here.

Despite having the gsm_abis_oml dialect set to "Ericsson OM2000", I get only "data" as decode:

Weird, decode works for me.

What I see is the TF Configuration Request and TF Configuration Request Ack, but then nothing from the TF after that.
So to me, that indicates either an E1 clock out of range, or the internal OCXO is still warming up.

I just rebuilt wireshark master (33e63d19e5496c151bad69f65cdbc7cba2b4c211), and it does still exhibit the problem.

I also see the problem with the oldes build I have currently installed: v3.3.0rc0-1701-g4bea0e7c2ebf which I built on July 25th.

doh!

for some strange reason I had gsm_abis_om2000 in the ~/.wireshark/disabled_protos list. No idea how that happened...

Adding RUS and DUG logs retrieved from OMT after power on and 1 attempt to run osmo-bsc.

Adding a PCAP after we get a TF Configuration Result.

would it be that the DUG does not like one of our SI5 messages?

Ok Thanks, I should clarify there is still no RF transmission from the unit and no channels listed as active in osmo-bsc.

Things do not advance after this last SACCH FILLing error.

Closing as: of little value apart from some documentation of first experiences with the RBS units.

Mostly it was due to E1 clock out of range, E1 clock was from a PCI card, using the iceE1 or a GPS unit fixed waiting forever at TF Configuration Request Ack