Herbert and a participant look at the screen showing the people joining the meeting remotely.
Back to the service overview Communications & providers

Communications in detail.
Plan telephony and meetings.

Assess call routing, existing systems, FreePBX, provider-hosted services and Teams. Test number porting, fallback routes and meeting rooms in practice.

From the incoming call to the right person

How should a call reach your business?

Opening hours, cover arrangements and working locations determine the routes. DAXS records numbers and contracts, configures distribution and tests the agreed cases.

Call distribution with reachability checks, endpoint selection, fallback route and functional testing.
An agreed fallback route makes reachability something you can plan. Connections, devices, time rules and platform functions are tested specifically.
  1. 01Number and provider

    Which connections, numbers and contract terms are in place? Agree requirements and connection options with the provider.

  2. 02Time rules and call groups

    Route calls to the right people during and outside agreed hours. Define cover, busy handling and forwarding.

  3. 03Office, home and mobile

    Choose a telephone, softphone or suitable platform for each working location. Test incoming and outgoing calls on the endpoints needed.

  4. 04Fallback route

    For a defined failure, test call forwarding, a mobile connection or an alternative device. The route must bypass the actual failure.

When can each model make sense?

The platform follows the call workflow.

Specific functions, contracts and devices are checked before making a commitment.
ModelPossible useControl, dependencies and support
Existing telephone systemWhere the required functions, support and devices remain suitable.Retain the existing setup and integrations; plan maintenance, replacement and a later transition.
FreePBX / privately operated platformWhere direct control and customised call routing are required.Organise the platform, updates, backups and ownership. A provider and secure access are still required.
Provider-hosted telephonyWhere telephony as a managed service fits the workflow.Check the contract, product functions, devices and reliance on internet connectivity. Coordinate changes and forwarding with the provider.
Microsoft TeamsWhere Teams is used for collaboration and the telephony requirements fit.Check licensing, provider connectivity, mobile use and required functions in advance. Coordinate support with the Microsoft environment.
Endpoints, workflow integration, ongoing costs and a later transition belong in every comparison. Existing technology is assessed on its merits.
Stay reachable during an outage

Which connection must the fallback route bypass?

Internet connection or provider fails

A second connection or mobile link can bypass a connection failure. A provider outage may instead require forwarding arranged outside that service. Check the contract and technical options in advance.

Site power or network fails

Local telephones and the telephone system can fail together. Mobile availability, external forwarding or an alternative platform are prepared as required. A backup internet connection alone does not solve a power outage.

Telephone system fails

An available connection or working line does not guarantee call distribution. Back up configuration, check recovery and test the planned alternative route. The test must demonstrate that people can actually be reached.

For internet, mobile services, telephony and site connectivity, the Magenta Business page explains typical uses and how the provider and DAXS work together. The right connection is selected around your requirements.

Remote participants are part of the meeting too

A meeting room works as one system.

Local participants face the screen, the camera frames the room appropriately and everyone can be heard. DAXS plans the room, platform and IT connection and tests usability in an external test call.

  1. 01Start simply

    Match the screen, sign-in and controls to the meeting workflow actually used. Starting a session should take as few clear steps as possible.

  2. 02Hear and be seen

    Plan seating, lighting, microphones and cameras so that local and remote participants can take part. Room size and acoustics determine the choice.

  3. 03Test externally

    Someone outside the room checks the picture, speech clarity and participation. Screen sharing and the intended devices are tested in the same session.

Logitech and other manufacturers offer possible equipment options. The room, its use and acceptance tests determine the setup.

Keep your numbers and workflows

Porting and implementation need coordination.

The current setup, provider and target platform are coordinated before the change. Number porting, the test window and fallback route belong in the same plan.

  1. 01Assess

    Record numbers, contracts, devices, locations and contacts; identify functions to retain.

  2. 02Coordinate

    Plan provider coordination, the porting date, test window and user communication. Discuss limitations and possible interruptions.

  3. 03Test and hand over

    Test incoming and outgoing calls, call groups, cover arrangements and mobile use. Document settings and responsibilities.

A possible project

Plan reachability in the office, at home and on the move.

A call should reach the right person. If that person is busy or away, a clear fallback route is needed. DAXS agrees call groups, devices and time rules with you and checks what the existing or planned telephony platform actually supports.

Describe call routes in advance

Numbers, main contacts, opening or availability hours and cover arrangements are recorded. A standalone system, hosted service and existing connections are assessed for suitability. Rules must fit organisational workflows and remain understandable to staff.

Test the right situations

A test covers incoming and outgoing calls, transfer, absence and the agreed fallback route. Office, home and mobile use are each considered. Connection quality and behaviour during an incident depend on the connection and platform and are tested specifically.

View planning and acceptance points
  • Record existing numbers, connections and devices.
  • Agree call groups, availability hours and cover arrangements.
  • Check required call functions and platform limitations.
  • Assess networking, power supply and reliance on internet connectivity.
  • Test normal use, absence and the agreed incident route.
  • Acceptance: hand over call routes, contacts and concise user instructions.

Example review framework. Scope and suitable evidence are agreed for your environment.

BEFORE YOU DECIDE

Questions about telephony and meetings.

Can existing phone numbers be kept?
This is checked with the provider, the contract terms and the planned connection. A porting process is agreed before the change takes place.
Does telephony have to move to the cloud?
No. Existing phone systems, self-hosted platforms and cloud telephony are assessed against requirements, operations and cost.
When is FreePBX suitable?
When functional requirements, direct control and an operable environment fit together. Updates, backup and responsibilities are part of the decision.
Can Teams replace a conventional telephone?
Where requirements fit, Teams can serve as a telephony platform. Licensing, provider connectivity, endpoints and required functions are checked in advance.
What happens if the internet connection fails?
The impact depends on the platform, provider and connection. Additional circuits, mobile fallback and call forwarding are planned and tested according to your needs.
What makes a meeting room work well?
Clear sound, suitable framing, simple controls and a stable connection. Device selection and testing depend on the room and meeting platform.
THE NEXT PRACTICAL STEP

Review your call routing or meeting room.

Describe who needs to be reachable and when, or what currently disrupts meetings. We will agree on an initial scope for planning and testing.

Simply explained

This page explains telephony platforms, number porting and fallback routes, as well as the requirements for a usable meeting room.