No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FAQ How to configure a lot of mapgroups on SE2x00

Publication Date:  2012-08-09 Views:  75 Downloads:  0
Issue Description
Very popular question during SBC implementation: For the functions of SIP, H323 proxy for trunk groups traffic - we have to use separate IP addresses as a server IP addresses on SBC for different map groups. Only using IP address of Server IP - SBC can recognize which TG this call belong to. But one physical interface provide only 32 sub IP addresses, so meet limitation: support only 32 trunk groups, but very often it's nessesary to configure much more. How to solve this limitation.


Alarm Information
None.

Handling Process
The way of resolution - using interface loopback.

1. need make network plan for two IP networks - for client (if needed) and server addresses of SBC, for example, create networks 10.200.40.0/24 - for client addresses and 10.200.50.0/24 - for server addresses.
2. Add new interfaces by commands: 
interface LoopBack302
description client_ZZZ
ip address 10.200.40.5 255.255.255.255
interface LoopBack802
description server_ZZZ
ip address 10.200.50.5 255.255.255.255
we can add many such interfaces, no limit - hundred or thousands, depended on total SBC abilities.
3. Need configure IP routing to such networks. Next hop addresses - should be corresponding physical port on SBC.
for example:
Physical port configuration.
#Physical port to NGN network, trunk port, including Signalling and Media VLANs
interface GigabitEthernet1/0/0
description Signalling to MSK port g1/0/4
#
interface GigabitEthernet1/0/0.511
vlan-type dot1q 511
description Signalling to MSK port g1/0/4
ip address 10.200.20.22 255.255.255.224
vrrp vrid 1 virtual-ip 10.200.20.12
#
interface GigabitEthernet1/0/0.521
vlan-type dot1q 521
description Media to MSK port g1/0/4
ip address 10.200.30.26 255.255.255.192
vrrp vrid 2 virtual-ip 10.200.30.25
qos apply policy ip-precedence-5 outbound
#
#Physical port to external network
interface GigabitEthernet2/0/0
description Media to MSK port g1/0/4
#
interface GigabitEthernet2/0/0.522
vlan-type dot1q 522
description --VPN_Customer--
ip address 10.200.100.5 255.255.255.248
vrrp vrid 3 virtual-ip 10.200.100.4
for such example, IP routing in the network should be the following:
From signalling network:
route to network 10.200.40.0/24, next hop address 10.200.20.12
From media network:
route to 10.200.40.0/24, next hop address 10.200.30.35
From external network:
route to 10.200.100.0/24, next hop address 10.200.100.4
Then create mapgroup, use Loopback interfaces as client and server addresses, according to example:
sbc mapgroup intercom-ip 1021
description TG_inbound
clientaddr  10.200.50.5
serveraddr  10.200.40.5
softxaddr  10.200.20.10
media-clientaddr  10.200.50.5
media-serveraddr  10.200.40.5
enable
sbc mapgroup intercom-ip 1022
description TG_outbound
clientaddr  10.200.40.5
serveraddr  10.200.50.5
softxaddr  81.23.162.149
media-clientaddr  10.200.40.5
media-serveraddr  10.200.50.5
enable
Quick checking correctness of the IP routing:
From IFMI board of SoftX3000 we shoul ping address 10.200.40.5
From HRB of UMG and other gateways, located on site we should be able to ping 10.200.40.5
Remote client will connect to address 10.200.50.5, it also should be able to ping it.
Such configuration allow to avoid limitation with IP addresses.
Root Cause
None.


Suggestions
this solution works well, so you can use this experience in case of meet same problem conditions.

END