@JaredBusch Hi Jared, I am using Fusion PBX, So you're thinking there is a possibility to limit them calling few phone number?

Hi Friends, One of my customer dealing with the patient at their treatment facilities have to request for some sort of outbound call with limit access for the patient, here is the scenario and not sure if there is a possibility to create in Fusion or any other system you can recommend.

They have patients at their facilities and want to provide them some option in order to use one phone line at their office to make calls to their friends or family who they authorize.

Let's say each patient have designated pin code to add when they’re going to make calls, that pin code only allow them to make call certain number we have put to the fusion or system as their family or authorized contact person, of course, each patient has their own code to call and different numbers.

Really appreciate if have any recommendation.

Any recommendation for SIP trunk provider?

Hi Scott and Mark,

I have couple customer looking for about 800 VoIP extension in California, I need some recommendation good infrastructure setup, I really appreciate for your suggestion and recommendation.

Q1. Hosting Provider recommendation
1 .AWS
2. vultr
3. Digital ocean
4- Dedicated server( colocation)
Note: of course everyone agreed to pay less as long as have minimum downtime for better call quality

Q2.Fusion Server infrastructure option

1.Separate database Server
server 1 - Fusion application
Seever 2 - postscript database

NOTE: Of course I should have a good bandwidth between two server

2. Load Balancer option
   Load Balancer point to Server 1- App1 and Server 2- App 2 and these two app server point to a Database server(postscript database)

Note: The load balancer is a single point of failure; if it goes down, your whole service can go down. A high availability (HA) setup is an infrastructure without a single point of failure. To learn how to implement an HA setup, you can read this section of How To Use Floating IPs.

3. Master-Slave Database Replication

Note: The application accessing the database must have a mechanism to determine which database nodes it should send an update and read requests to Updates to slaves are asynchronous, so there is a chance that their contents could be out of date If the master fails, no updates can be performed on the database until the issue is corrected and does not have built-in failover in case of failure of a master node

4. load balance the caching servers, in addition to the application servers, and use database replication in a single environment.
   

Note:This environment still has two single points of failure (load balancer and master database server), but it provides the all of the other reliability and performance benefits that were described in each section above.

5. IF you recommned any other setup to start for two new customer and of cource i can scale it later.

Q3. Do i need to setup kamailio or opensips and what is the advantage to have it now?

Thank you so much in advance for you help and support.