This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Neels Hofmeyr nhofmeyr at sysmocom.deSorry to see no response here for a whole week. Have you resolved the issue? On Mon, Oct 22, 2018 at 04:37:27PM +0200, Lars Prehn wrote: > Using the VTY interface I can see that only HNBGW and MSC annouced their > code points towards STP. : > > as-rkm-1 AS_ACTIVE 1 0.23.5 > > as-rkm-2 AS_ACTIVE 2 0.23.1 So, you need to get osmo-sgsn to connect to osmo-stp. My osmo-sgsn.cfg looks like this: ---- sgsn gtp local-ip 192.168.2.3 ggsn 0 remote-ip 192.168.2.4 ggsn 0 gtp-version 1 auth-policy remote gsup remote-ip 127.0.0.1 ns encapsulation udp local-ip 192.168.2.3 encapsulation udp local-port 23000 encapsulation framerelay-gre enabled 0 ---- i.e. the SS7 config is implicit / default. When I vty 'enable; show running-config', this implicit cs7 cfg is shown as ---- cs7 instance 1 point-code 0.23.4 asp asp-clnt-OsmoSGSN 2905 0 m3ua remote-ip 127.0.0.1 as as-clnt-OsmoSGSN m3ua asp asp-clnt-OsmoSGSN routing-key 1 0.23.4 ---- Not sure if this helps, but I can't see any mistake in your config. Is your SGSN running on a different machine / network segment and cannot reach the STP at 127.0.0.1? Then change the remote-ip as shown in the cs7 instace cfg... ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20181029/97eb56bd/attachment.bin>