Cellular Network Infrastructure » Core Network (CN) » osmo-gbproxy

Submitted in https://gerrit.osmocom.org/#/c/osmo-sgsn/+/9402

The ns-state command now replies with nsei, nsvci, local state, role, remote state of all NSVCs.
The gbproxy-state command replies with nsei, bvci, mcc, mnc, lac, rac, and state of each peer.

If there are no entries an error is returned.

daniel@adrastea:~/scm/osmo/osmo-python-tests/scripts(master) » ./osmo_ctrl.py -d 127.0.0.1 -p 4263 -g ns-state
Got message: b'GET_REPLY 23 gb-status 101,101,DEAD,BLOCKED,SGSN,DEAD,UNBLOCKED;'
daniel@adrastea:~/scm/osmo/osmo-python-tests/scripts(master) » ./osmo_ctrl.py -d 127.0.0.1 -p 4263 -g gbproxy-state
Got message: b'ERROR 23 No peers found'

The implementation of the commands changed:

The two commands are now named "nsvc-state" and "gbproxy-state"

The "nsvc-state" command replies with nsei, nsvci, local state, role, remote state of all NSVCs. The "gbproxy-state" command replies with nsei, bvci, mcc, mnc, lac, rac, and state of each peer. Entries are separated by a newline '\n' character. If there are no entries an empty list is returned. This behaviour is similar to that of the subscriber-list-active-v1 command in osmo-sgsn.

$ ./osmo_ctrl.py -d 127.0.0.1 -p 4263 -g nsvc-state Got message: b'GET_REPLY 23 nsvc-state 101,101,DEAD,BLOCKED,SGSN,DEAD,UNBLOCKED\n'
$ ./osmo_ctrl.py -d 127.0.0.1 -p 4263 -g gbproxy-state Got message: b'GET_REPLY 4871085901306801158 gbproxy-state '