User Interface (With High Availability Mode)
- OSS/BSS Answers
- App Model - Organization Management
- App Model - Communication Apps Answers
- License Model - Organization Management
License Model - CPaaS Solution Answers
Phone System - Admin Guide Phone System - End-user Guide Mobile App Desktop App Web Phone Auto Attendant - Admin Guide Developer Hub - Admin Guide Microsoft Teams Operator Connect - Admin Guide Microsoft Teams Direct Routing - Admin Guide Contact Center - Supervisor Guide Contact Center - Agent Guide Omni-Channel SIP Trunk CPaaS - SIP Trunk CPaaS Fax Contact Dashboard Campaign File Explorer
- Integrations Answers
- Updated Regulations
- Ideas Portal
Table of Contents
To use the High Availability function, users must purchase a High Availability add-on.
User Behaviour Flow
After purchasing a High Availability add-on, users will have a Secondary Sip Account along with the Primary Sip Account to support 2 systems at the same time when using Load Balancing or Auto Fail-over mode.
The High Availability default mode is Only Primary when the customer first purchased a High Availability add-on.
Secondary SIP Account
For the Secondary Sip Account, users can customize:
IP Address List
Load Balancing Mode
- Distribute and balance the traffic of incoming calls following the round-robin mode of both Sip Account
- DO NOT CARE about status of the Sip Account, for instance, if the Primary Sip Account failed, our system will NOT retry
- Share the same concurrent calls flag based on the Primary Sip Account, for instance:
- Primary Sip Account has 30 concurrent calls
- Secondary Sip Account will share 30 concurrent calls with Primary Sip Account
- Primary Sip Account concurrent calls value + Secondary Sip Account concurrent calls value = 30 concurrent calls in total
- Share the same Caller ID for outbound direction based on the Primary Sip Account settings
Check Status of SIP Account:
- Before initiating a failover, the system should first check the status of the Primary Sip Account. If the Primary Sip Account is down or unreachable, the system should proceed with the failover process.
Concurrent Calls Logic:
- When failover is triggered, the system should share the same concurrent calls flag based on the Primary Sip Account. For example, if the Primary Sip Account has 30 concurrent calls, the Secondary Sip Account will share 30 concurrent calls with the Primary Sip Account.
- The sum of concurrent calls for both SIP accounts should not exceed the total number of concurrent calls allowed.
We design the Fail-over logic based on sip response code from far-end of the customer side (Inbound Direction) including Wrong credential, Network/Firewall issues at client side, etc.
If the PBX has set up an authentication mechanism on their end that requires them to authenticate with our system for the call to proceed, then the PBX may respond with a 401 or 407 or 408 or 404 code to prompt the authentication process. If Customer System 1 is unable to authenticate, then it may trigger the Fail-over process to route the call to the Secondary Sip Account to Customer System 2.