The below decision tree will walk you through the possible paths a call can take when there are issues or outages, and some of the redundant technology in place to avoid problems.
Are you making an inbound call our an outbound call?
The number 123-456-7890 is calling into your number 098-765-4321 that you have with SIPTrunk.com
The behavior depends on if there are any issues with bvoip at the time, which is rare.
In the event that bvoip is fully operational, calls will flow into the bvoip system as normal.
The behavior depends on how your system is configured, and whether or not you have High Availability licensing with a failover server that sits at the ready.
A failover on your primary server will route all calls to the high availability failover server after a brief delay, as it takes some time for the failover server to take over.
SIPTrunk.com allows you to configure either a PSTN Backup or Vmail to Email under every DID in the portal.
The Vmail to Email option must be filled in with an email, and during an outage all messages left get sent as attachments to the configured email. You cannot change the greeting for the voicemail prompt unfortunately.
The PSTN Backup option is filled in with a valid phone number (start with the 1 country code), and during an outage calls are forwarded to that number.
The behavior depends on what component is having an outage
An outage on either proxy gateway should have little to no impact on your system, as your system should be configured to utilized gw1.siptrunk.com as the primary, and gw2.siptrunk.com as the alternate proxy.
If you are ever seeing issues in this case, you can try removing the failing proxy from your configuration and replace it with the other one, however that should not be necessary.
In the event of a full system outage, calls will route through their Hypernetwork partner, as long as your number is not in one of the few areas of the United States that does not support the Hypernetwork. You can confirm if all your numbers are supported by reaching out to support@siptrunk.com.
After a brief outage of the number as it ports to their Hypernetwork partner carrier, calls will flow into the bvoip system as normal.
Once the outage at SIPTrunk.com is restored, your numbers will silently port back as if nothing happened.
In the very unlikely occurrence bvoip also has an outage at the same time as SIPTrunk.com, the behavior depends on whether you have a High Availability licensing with bvoip or not.
A failover on your primary server will route all calls to the high availability failover server after a brief delay, as it takes some time for the failover server to take over.
In this case calls will fail, however reaching this point is rare as it requires a full server outage with both bvoip and SIPTrunk.com to occur at once.
You make a call from your number 098-765-4321 that you have with SIPTrunk.com
The behavior depends on if there are any issues with bvoip at the time, which is rare.
In the event that bvoip is fully operational, calls will flow out of the bvoip system as normal.
The behavior depends on how your system is configured, and whether or not you have High Availability licensing with a failover server that sits at the ready.
A failover on your primary server will route all users to the high availability failover server after a brief delay, as it takes some time for the failover server to take over.
In this case calls will fail, as you would not be able to reach the server to make calls.
The behavior depends on what component is having an outage
An outage on either proxy gateway should have little to no impact on your system, as your system should be configured to utilized gw1.siptrunk.com as the primary, and gw2.siptrunk.com as the alternate proxy.
If you are seeing issues ever in this case, you can try removing the failing proxy from your configuration and replace it with the other one, however that should not be necessary.
The behavior now depends on whether you've configured a backup trunk provider.
Setting up a backup trunk provider is not required, and generally not recommended in most scenarios due to cost, but if you need to ensure calls can be made out no matter what then this is the best bet.
In the event that your backup provider is operational and configured as Route 2 in any outbound rules, calls will flow out of the bvoip system as normal.
You may need to adjust the outbound caller ID to differ on the additional routes, depending on if your backup provider supports using numbers they don't hold in caller ID.
In this case calls will fail, as there is no functioning trunk connection to send calls out of.