gbproxy: Use separate NS-VC for data / signalling on SGSN side

As we know, many production deployments have SGSN architectures with
clear control / user plane split.  In such situations, IP-SNS of the
SGSN informs us of two (classes of) IP endpoints:

    some that have control_weight > 0 and data_weight 0
    some that have control_weight 0 and data_weight > 0

Let's adjust the GBProxy_Tests.ttcn to use such a configuration for
each of the two simulated SGSNs.

Change-Id: If0e404bdf2c30a5e18748695608611be83f61109
Closes: OS#4953
This commit is contained in:
Harald Welte 2021-01-18 18:52:49 +01:00
parent e393c1f7c6
commit f3f2e25864
1 changed files with 26 additions and 0 deletions

View File

@ -73,6 +73,19 @@ modulepar {
}
},
nsvci := 101
}, {
provider := {
ip := {
address_family := AF_INET,
local_udp_port := 7770,
local_ip := "127.0.0.10",
remote_udp_port := 23000,
remote_ip := "127.0.0.1",
data_weight := 1,
signalling_weight := 0
}
},
nsvci := 201
}
}
@ -94,6 +107,19 @@ modulepar {
}
},
nsvci := 102
}, {
provider := {
ip := {
address_family := AF_INET,
local_udp_port := 8880,
local_ip := "127.0.0.11",
remote_udp_port := 23000,
remote_ip := "127.0.0.1",
data_weight := 1,
signalling_weight := 0
}
},
nsvci := 202
}
}
}