One server or several connected servers
Two architectures are possible, and are chosen with Klytic based on the number of sites, their size and their autonomy.
- One server for all sites. All sites connect to the same server dedicated to your organization: a single configuration, a common numbering plan, a single point of administration.
- Several servers associated with sites and connected to each other. Each server serves one site or a group of sites. The servers are linked, which allows free and secure internal calls between sites, and confines any outage to the sites served by the server concerned.
The selection criteria are explained in VoIP, SIP, IP PBX and UCaaS: which architecture.
What you get
- A phone organization shared by all sites, on one dedicated server or on several connected servers. A single point of contact: Klytic.
- Direct numbers for each employee, whatever their site, and reception numbers per branch or a single number.
- Ring groups and call queues to reach the right department or the right site.
- An auto attendant that routes the caller: “press 1 for the … branch”.
- Transfers between sites without going back through the public network.
- Apps for computer, mobile and browser, for mobile or remote employees, attached to their site.
What you prepare with Klytic
Setting up a multi-site phone system starts with a description of your organization. Klytic turns it into a configuration. Prepare the following, site by site.
- The numbering plan. The list of existing numbers to port, the direct numbers to assign, and any common reception number. Also indicate whether you want short internal extension numbers.
- Hours and announcements. Each site’s opening hours, local public holidays, and the message played outside business hours.
- Reception. A central reception that distributes calls to the sites, or a local reception per branch. Both can coexist.
- Groups and queues. Who answers which number, in what order, and what happens when nobody picks up.
- What happens when a site goes down. If a branch’s Internet link fails, where to forward its calls: an on-call mobile, another branch, or an announcement.
- Line types. For each employee, the right line: Basic Line, Advanced Line, Business Line or Manager Line. All four can be combined on the same phone system.
- Phones. Which employees use a desk phone, rented or existing, and which use only the app. No physical phone is required.
Detailed configuration, such as distribution rules or announcements, is carried out by Klytic based on these elements. Later changes are requested through support.
How each site connects
The desk phones and apps at each site connect to the phone system over the Internet. There is no phone system to install at each branch when the server is hosted in the Klytic cloud. If your phone system is installed on your own servers, the sites connect to it in the same way.
Communications between phones or apps and the phone system are encrypted with SRTP and TLS. A call to an external number remains encrypted as far as the Klytic platform; beyond that, its protection depends on the carriers it passes through.
Call quality also depends on each site’s network. During setup, Klytic tells you what needs to be checked with your network provider. This page is not an installation guide: connection details are handled case by case.
Your numbers and your carrier
Your existing numbers can be kept, whatever the site, through number porting. You can also create new ones.
Two options are available for connecting to the public telephone network:
- Keep your current carrier. Your subscription and your numbers stay with them, and Klytic connects your lines to the phone system, subject to compatibility.
- Also entrust your lines to Klytic, with its landline and mobile calling plans. The phone system, the lines and the mobiles are then with the same provider.
If your branches currently use different carriers, let us know: porting is planned site by site.
When a site loses its connection
Since the phone system is central, a link failure at one branch affects only that branch. The other sites keep working. Calls intended for the cut-off branch follow the forwarding rules set during preparation, and employees with the app remain reachable on their direct number from their mobile.
If the phone system itself is unavailable, all sites are affected. The server is backed up every day by Klytic backups, with a recovery time objective of less than 4 hours. The possible fallbacks are detailed in Keeping telephony running during an outage.
Adding a site later
A new site joins the same phone system. Prepare the same elements for it: numbers, hours, reception, lines and phones. Send them to support, who will add the site to your configuration. Lines can be added as your needs grow.
Frequently asked questions
One phone system or one per site: which should we choose?
The criteria are explained in VoIP, SIP, IP PBX and UCaaS: which architecture.
What happens if the phone system is unavailable?
In the cloud, Klytic Tel relies on a leading cloud hosting provider, with an enterprise-grade availability commitment of 99.99% (excluding planned maintenance announced in advance) and failover between several hosting sites in the event of an outage: resilience to outages is very high. Klytic can also deploy the solution with another cloud provider of your choice. See Keeping telephony running during an outage.
Can we record calls at just one site?
Recording is decided line by line or queue by queue. See Who can listen to recordings in Klytic Tel.
Are calls from one site to another charged?
No. Internal calls between your sites go through your Klytic Tel servers, encrypted, without using a carrier’s network: they are free and secure, whether with a single server or with several connected servers. Rates for outside calls are on the Pricing page.
