Looking for advice on multi-tenancy

[Alphabetic]

Hi all

we have a site that will start subletting offices.

we need a solution to provision handsets to cloud 3CX instances.

Can anyone recommend a best solution for this that also minimises the need for us to visit site for set up.

ideally, we want client to be able to plug the phones in themselves and they provision.

 

[VasilisV_3CX]

Hi @kieferschild,

Can you tell me about the network setup, will each customer have their own network or be sharing a network?

 

[Alphabetic]

Hi @kieferschild,

Can you tell me about the network setup, will each customer have their own network or be sharing a network?

1 physical network with VLANs

 

[VasilisV_3CX]

Hi @kieferschild,

Only DHCP Option 66 will autoconfig the devices the way you require, but this hinges on having the custom option 66 working on each VLAN, as each customer will have their own unique FQDN.

 

[Alphabetic]

Hi @kieferschild,

Only DHCP Option 66 will autoconfig the devices the way you require, but this hinges on having the custom option 66 working on each VLAN, as each customer will have their own unique FQDN.

Yes, this should be fine. My main concern is in relation to the SBC. What would be the best way to do this?

We're looking maybe 30+ tenants over the next few years.

 

[VasilisV_3CX]

Hi @kieferschild,

Well given that the situation isn't ideal by our standards, you could try to 'abuse' a mechanism. First try to get it working without this but if you can't here's what you could try.

1. First set the phones to STUN in the Management Console to inform the RPS server of the FQDN.
2. Then reconfigure the extension's Phone Provisioning tab for SBC with the correct SBC IP.
3. The Phone will still request the RPS and you input the credentials, but instead the config file it will pull, will be for the SBC

Remember that the RPS request will stays in the system for 2 weeks.

 

[Alphabetic]

Hi @kieferschild,

Well given that the situation isn't ideal by our standards, you could try to 'abuse' a mechanism. First try to get it working without this but if you can't here's what you could try.

1. First set the phones to STUN in the Management Console to inform the RPS server of the FQDN.
2. Then reconfigure the extension's Phone Provisioning tab for SBC with the correct SBC IP.
3. The Phone will still request the RPS and you input the credentials, but instead the config file it will pull, will be for the SBC

Remember that the RPS request will stays in the system for 2 weeks.

Im questioning more the SBC side of it.

What have other customers done in regards to this?

What I want to avoid is having 30+ Pis.

Is there a solution that has little hardware but can be used as SBCs for networks?

Im thinking about VMs using VLAN tagging.

 

[VasilisV_3CX]

Im thinking about VMs using VLAN tagging.

In that case this is the solution I'd go with.