Hi Vadim, Thank you for your quick replies. (Previously, due to error, I sent reply to you. Now, I have resent with openbsc in cc)
I wasn't sure, if my firewall is blocking the port or not. Hence, I took a wire shark trace test.pcap. I ran sudo ufw allow 5701 and sudo ufw allow 5801 and then again took wire shark trace test2.pcap. Both traces are attached. From my inspection, the ports have still the same messages. I am also attaching the configuration of other components, as a reference. Thanks again for the help On Thu, 9 Apr 2020 at 13:52, Vadim Yanitskiy <[email protected]> wrote: > Hello Aalto, > > your configuration looks good to me. As far as I understand, you're > running both osmo-bts-trx and osmo-trx on the same machine. As can be > seen from your logs, TRXC commands from osmo-bts-trx are received by > osmo-trx: > > > <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0] command is > 'POWEROFF' > > however the response messages from osmo-trx do not reach osmo-bts-trx: > > > <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0] response is > 'RSP POWEROFF 0' > > <000b> trx_if.c:185 phy0.0: No satisfactory response from > transceiver(CMD POWEROFF) > > Maybe your firewall is blocking traffic (udp/5701 and udp/5801) > somehow? Could you please send us a *.pcap capture ('lo' interface)? > > With best regards, > Vadim Yanitskiy. >
osmo-sgsn.cfg
Description: Binary data
osmo-pcu.cfg
Description: Binary data
osmo-ggsn.cfg
Description: Binary data
test.pcap
Description: application/vnd.tcpdump.pcap
test2.pcap
Description: application/vnd.tcpdump.pcap
osmo-stp.cfg
Description: Binary data
osmo-msc.cfg
Description: Binary data
osmo-hlr.cfg
Description: Binary data
osmo-mgw-for-msc.cfg
Description: Binary data
