ttcn3-bscnat: Prepare cfgs for VTY & Osmux support

* Adding "osmux on" for each BSC will be required to enable Osmux later
on, but still it doesn't change behavior now because Osmux must be
enabled globally too (will be done through VTY).

* Set up correct bind and remote IP addr to have VTY working later on.

* Use extended timestamp to have subsecond accuracy to match with pcap
easily.

Change-Id: I794a17bdeaff9ab9316d7a6acb1e58dfd815b645
This commit is contained in:
Pau Espin 2019-05-22 20:16:19 +02:00
parent 77bf937cac
commit 808801a9fa
3 changed files with 6 additions and 0 deletions

View File

@ -6,6 +6,7 @@
*.JUnitLogger.testsuite_name := "BSCNAT_Tests"
[TESTPORT_PARAMETERS]
*.BSCNATVTY.CTRL_HOSTNAME := "172.18.15.20"
[MODULE_PARAMETERS]
mp_bsc_port := 49999;

View File

@ -5,15 +5,18 @@ nat
description bsc
max-endpoints 32
paging forbidden 0
osmux on
bsc 1
token BSC1
location_area_code 2
description bsc
max-endpoints 32
paging forbidden 0
osmux on
bsc 2
token BSC2
location_area_code 3
description bsc
max-endpoints 32
paging forbidden 0
osmux on

View File

@ -7,10 +7,12 @@ log file /data/osmo-bsc_nat.log
logging color 0
logging print category 1
logging timestamp 1
logging print extended-timestamp 1
logging level force-all debug
!
line vty
no login
bind 0.0.0.0
!
mgcp
bind ip 172.18.15.20