AVAYA and SIP TRUNK +SBC Network topology

[abtt]

Hello,
I need to set up a SIP trunk. It will be behind a dedicated MPLS VPN. The provider has its own SBC ( on his side)
We want to put our own internal SBC (virtual machine). The ISP router would be connected to our core network.

We want 2 SIP trunks (active / standby). So one SBC server per trunk link

The provider asks me to provide 2 IPs, one for the main router, one for the backup router.

We already have an sbc in place, but it is only used for remote workers (via the main internet link). It is behind a cisco ASA firewall.

the future SIP trunk will have its own sbc and it will work with dedicated MPLs VPN.
But I watched how it was done.
There are 2 networks A1 and B1, internal and external.
I imagine doing the same on the future SBC.

The configuration of the current SBC is like this:

A1- Internal GW : 10.39.90.254 / 24 IP : 10.3.9.90.60
B1- externel GW : 192.168.90.250/24 IP : 192.168.90.60


On the core switch 10.39.90.254 is the Switch Virtual Interface of the VLAN 90
and 192.168.90.254, same for the VLAN 91

Ip office server is in the VLAN 90 ( 10.39.90.90)

IP routing is activate on the core switch, so all the VLAN can communicate each other.

For the trunk SBC should I put A1 in the same sub interface as the IP Office server?
And B1 on the VLAN 91.

Like this for example :

A1- Internal GW : 10.39.90.254 / 24 IP : 10.3.9.90.65
B1- externel GW : 192.168.90.250/24 IP : 192.168.90.65 (GW here is the ASA interface)

Or should I create 2 new VLANs on the core network ( To limit the broadcast domain)?

VLAN 92 and 93 for example?

Like this :

VLAN 92
ip address 10.39.92.254 255.255.255.0

VLAN 93
ip address 192.168.92.254 255.255.255.0

A1- Internal GW : 10.39.92.254 / 24 IP : 10.3.9.92.60
B1- externel GW : 192.168.93.254/24 IP : 192.168.93.60

And give my SIP TRUNK provider 2 IP for the LAN part of their router :

192.168.92.100 /24
192.168.92.120 /24

 

[derfloh]

At the end the easiest is to create new interfaces/VLANs on both sides of the SBC. You can also use as second IP on the A1 interface and create a B2 ör B1.93 sub interface.

I would avoid to use the current interfaces.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[abtt]

Thank you derfloh

and another question, we will have 2 SIP trunk links (fiber) one active and one back up.
Only one SBC server can handle this or do we need one SBC per link?

 

[derfloh]

Can be done with one. But if you want to have resiliency the SBC will be the single point of failure then.

You can have two single SBCs or a SBC HA cluster. It is configured like a single SBC but you will have two servers. One is active and the other is passive but will take over all calls (even ongoing calls) from the primary in milliseconds if it fails.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN