How many IP Office (without SCN) can be work behind one SBC (SIP Trunking and Remote Worker)

[LJDirk]

Hi,

It should be deployed to multiple IPOffices (VMware environment) for individual customers.
The "SIP Trunks" and the "Remote Woker" are to be secured via a Session Border Controller.
Question: Do I need a separate SBC for each IP Office instance or can I secure several IPOs with an SBC?

The maximum connections of the SBC (2,500 trunks & 1.800 RW) were left aside. The Avaya "SBC Offer Definition 7.1) are not clear enough about this.

What are the caveats, if several IPOs could be run over one SBC?
IP Routing?
Security?
...?


Obviously it is of eminent relevance, that I this, what you celeprate, not optimally effective assume, since the integrate of you in the communicative system as code related terms with me no explosive associations in mental-empirical reproduction process of the mind.

 

[derfloh]

No problem. Don't know of a maximum number. With many customers and potential heavy load I would consider using a HA pair.

Just link one public IP for each customer to the B1 interface - separated by VLANs if needed and if possible - and one internal IP for each customer on A1 interface. Again separated by VLANs if needed.

Next create Server configuration for each IPO and create Endpoint Flow for each IPO to link the B1 address together with the A1 address of each specific customer.

If you want to have less B1 IPs you can create URI groups for each customer's SIP domain like *@customer<x>sipdomain.net and use it as another option in each customer's Endpoint Flow.

The URI group thing will probably not work for the DMZ relay rules to forward the needed ports to the correct 1XP server and probably not to separate the SIP trunks if the two customers use the same SIP provider.

I would go the multiple B1 IP way.