Best way for PBX Hosting with different IP for IPPbxes

[babak]

Hi
If carrier authentication and billing was just based on different PBX IP addresses and we just want to put Fusionpbx in middle to host pbx functionality ( contracts are between carrier and tenant owners and billing will be paid directly ) what is best way for doing this?
We need to define a sip profile for every tenant/IPPbx(they recognized and billed by their different IP Addresses by carrier) ?

Regards

 

[Adrian Fretwell]

This seems very wasteful of IP addresses, sure it could be done, but why not just use registration in your gateways. Registration will still keep the contracts between carrier and tenant.

 

[babak]

This seems very wasteful of IP addresses, sure it could be done, but why not just use registration in your gateways. Registration will still keep the contracts between carrier and tenant.

Hi @Adrian Fretwell
Provider billing and authentication is based on IP address and contracts are between carrier and end IP PBX owners in a big commercial complex( no choice of registration and there is a siptrunk VPN with private IP Addresses). I want to make a plan about how some of them can share their IP PBX Servers.
One way is using a LXC container for every IPPBX.
Another way is all IPPBX use one IP for connecting to Fusionpbx and in Fusionpbx we have Sip profiles for every IPPBX and connect to carrier with that profile and IP.
Every point is much appreciated.

Regards

 

[Adrian Fretwell]

OK, I see you are stuck with IP addresses. one option would be as you suggested to use one external SIP profile per customer. Obviously you will need to configure all of these IP addresses on your (~virtual) Network Interface Card. Avoid splitting addresses within the same subnet across NIC's, unless you want to get creative with routing tables.

Another solution worth considering would be to put a SIP proxy between the carrier and Fusion, that way you can use normal registration (and one external SIP profile) to the proxy and then have the proxy marshal the traffic between the IPs and the registered Fusion Gateways.