osmo-nitb/osmo-bts-trx: Logging traffic on A-bis interface
Hi all, I wanted to check if the bts - bsc communication works properly with my configuration. For example, if my osmo-nitb does send the system information messages to the bts. I tried the vty logging interface of osmo-bts and logged some messages, but they were not the messages I expected. I configured the groups rsl, oml, rll, rr and abis to "notice", all to "everything" and everything else to "error" and got following log output (lots of these and nothing else): ... <0006> scheduler.c:405 PH-RTS.ind: chan=CCCH chan_nr=0x90 link_id=0x00 fn=993588 ts=0 trx=0 <0006> scheduler.c:341 PH-DATA.req: chan_nr=0x90 link_id=0x00 fn=993588 ts=0 trx=0 ... PH-RTS.ind and PH-DATA.req seem to come from layer1 SAP, the osmo-trx and have probably nothing to do with the SI messages. Is traffic on abis generally not logged or is my log config faulty? I ended up configuring the gsmtap interface for osmo-bts and could so see the uplink/downlink in wireshark and could see that the SI information is properly sent. But gsmtap only works for the air interface. What is the best way for logging/sniffing the communication on the A-bis interface? With kind regards, Sebastian Stumpf
Sebastian, On Jul 1, 2016 4:06 PM, "Sebastian Stumpf" < sebastian.stumpf87@googlemail.com> wrote:
I ended up configuring the gsmtap interface for osmo-bts and could so see the uplink/downlink in wireshark and could see that the SI information is properly sent. But gsmtap only works for the air interface.
What is the best way for logging/sniffing the communication on the A-bis interface?
A-bis (OML/RSL) are using usual TCP socket. Wireshark should detect and decode messages sent over this socket automatically. Please excuse typos. Written with a touchscreen keyboard. -- Regards, Alexander Chemeris CEO Fairwaves, Inc. https://fairwaves.co
Indeed. There are even convenient wireshark display filters gsm_abis_rsl and gsm_abis_oml. On 07/01/2016 03:40 PM, Alexander Chemeris wrote:
Sebastian,
On Jul 1, 2016 4:06 PM, "Sebastian Stumpf" <sebastian.stumpf87@googlemail.com <mailto:sebastian.stumpf87@googlemail.com>> wrote:
I ended up configuring the gsmtap interface for osmo-bts and could so see the uplink/downlink in wireshark and could see that the SI information is properly sent. But gsmtap only works for the air interface.
What is the best way for logging/sniffing the communication on the A-bis interface?
A-bis (OML/RSL) are using usual TCP socket. Wireshark should detect and decode messages sent over this socket automatically.
Please excuse typos. Written with a touchscreen keyboard.
-- Regards, Alexander Chemeris CEO Fairwaves, Inc. https://fairwaves.co
-- Max Suraev <msuraev@sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte
participants (3)
-
Alexander Chemeris -
Max -
Sebastian Stumpf