Sample VLAN Configuration
The following formatted extract from show running-config ACLI output shows a sample tunnel configuration.
On the Subscriber-Aware Load Balancer ...
cluster-config
log-level NOTICE
source-rebalance-threshold 0
rebalance-skip-ahead 2000
...
service-port
address 192.168.180.1
port 5060
network-interface M00:100
service-port
address 192.168.180.1
port 5060
network-interface M00:102
On the SBC
sip-interface
realm-id Realm192p98
description
sip-port
address 192.168.248.52
port 5063
transport-protocol TCP
allow-anonymous registered
sip-port
address 192.168.248.52
port 5063
transport-protocol TCP
allow-anonymous registered
registration-caching enabled
secured-network enabled
tunnel-name T99
sip-interface
realm-id Realm192p99
description
sip-port
address 192.168.248.52
port 5063
transport-protocol TCP
allow-anonymous registered
sip-port
address 192.168.248.52
port 5063
transport-protocol TCP
allow-anonymous registered
registration-caching enabled
secured-network enabled
tunnel-name T100
As mentioned earlier, customers use unique IPs for each sip-interface and the same realm-id on the network-interface that us configured for your tunnel. This configuration is the same for each sip-interface. This means a single tunnel is sufficient when you are using unique IPs.
To achieve OLIP, however, you use different realm-ids across sip-interfaces, and configure tunnels on each corresponding network-interface. This means that OLIP on the access side requires multiple tunnels, as shown below.
network-interface
name M10
sub-port-id 348
ip-address 192.168.248.70
netmask 255.255.0.0
hip-address 192.168.248.70
icmp-address 192.168.248.70
tunnel-config
name T429
local-ip-address 192.168.248.70
remote-ip-address 102.168.248.40
application SIP
name M10
sub-port-id 349
ip-address 192.168.248.70
netmask 255.255.0.0
hip-address 192.168.248.70
icmp-address 192.168.248.70
tunnel-config
name T250
local-ip-address 192.168.248.70
remote-ip-address 102.168.248.40
application SIP