Revert "hnbgw: osmo-hnbgw.cfg: Update file to make it similar to the one in docker-playground"
This reverts commit e9c6c7b97ee5b870212c54a08064acbde5670d5d which
breaks all of the test cases reliably. I'm surprised how it got
submitted in the first place, as it can never have worked. It uses
127.0.0.1:2905 on both the STP and the HNBGW side.
Change-Id: Ia7d9a743e0359ce7220c42597ded670967d562a9
diff --git a/hnbgw/osmo-hnbgw.cfg b/hnbgw/osmo-hnbgw.cfg
index 2ed6905..8a9774b 100644
--- a/hnbgw/osmo-hnbgw.cfg
+++ b/hnbgw/osmo-hnbgw.cfg
@@ -2,26 +2,18 @@
! OsmoHNBGW (1.1.0) configuration saved from vty
!!
!
-log gsmtap 127.0.0.1
- logging level set-all debug
- logging filter all 1
-!
log stderr
logging filter all 1
- logging color 0
- logging print category-hex 0
+ logging color 1
+ logging print category-hex 1
logging print category 1
- logging print level 1
logging print thread-id 0
logging print extended-timestamp 1
- logging print file basename last
+ logging print file 1
logging level set-all debug
!
line vty
no login
- bind 0.0.0.0
-ctrl
- bind 0.0.0.0
!
stats interval 0
@@ -35,42 +27,30 @@
enable
cs7 instance 0
- asp asp-clnt-msc-0 2905 2905 m3ua
- local-ip 127.0.0.1
- remote-ip 127.0.0.2
- role asp
- sctp-role client
point-code 0.23.5
+
sccp-address msc-naught
- routing-indicator PC
point-code 0.23.4
sccp-address msc-one
- routing-indicator PC
point-code 0.0.2
sccp-address msc-two
- routing-indicator PC
point-code 0.0.3
sccp-address msc-three
- routing-indicator PC
point-code 0.0.4
sccp-address sgsn-naught
- routing-indicator PC
point-code 0.23.1
sccp-address sgsn-one
- routing-indicator PC
point-code 0.1.2
sccp-address sgsn-two
- routing-indicator PC
point-code 0.1.3
sccp-address sgsn-three
- routing-indicator PC
point-code 0.1.4
hnbgw
@@ -79,9 +59,6 @@
local-ip 127.0.0.1
local-port 29169
hnbap-allow-tmsi 1
- mgw 0
- mgw local-ip 127.0.0.1
- mgw remote-ip 127.0.0.1
# don't spam RANAP RESET messages for up to eight CN links across all tests
timer hnbgw T4 60
# reduce default X31 from 15 seconds