Questions about Althicom

VoIP means voice communication carried over IP networks rather than traditional analogue or ISDN lines.

In practical business terms, most modern cloud calling already uses this principle. The more useful questions today are usually how numbers are managed, where calls are routed, which applications users work in and how the voice environment connects to the rest of the business.

That depends on the environment.

Users may work from supported desk phones, computers, mobile devices or workplace applications such as Microsoft Teams. A reliable network connection and appropriately configured communication platform are more important than any single device type.

For a migration, we first check which existing devices and network components can remain in use.

Features depend on the selected platform and configuration, but common business functions include company numbers, users, queues, call routing, working-hour rules, forwarding, mobile and desktop access, reporting and integration with other business systems.

We do not treat a generic feature list as the solution. The environment is configured around the organisation's actual call flows and user requirements.

Voice quality depends on more than the calling application.

Bandwidth, latency, packet loss, local network configuration, internet connectivity, routing and the destination network can all affect the result.

A well-designed business environment therefore considers the network around the phone system as part of the implementation.

VoIP can be operated securely, but it is still connected infrastructure and needs proper administration.

Strong credentials, access control, platform updates, network design, user permissions and appropriate monitoring all matter. Security should be part of the architecture from the beginning rather than one setting added afterwards.

Reliability depends on the platform, internet connection, local network and the way routing and fallback are designed.

Cloud telephony can support serious business use, but critical environments should think about connectivity, alternative destinations and business-continuity requirements rather than assume the application alone guarantees availability.

Yes, where the relevant voice routes and destinations are supported.

International calling is part of modern voice infrastructure. For reseller and wholesale use cases, destination markets, traffic profile and routing become part of the technical and commercial design.

Yes, depending on the communication platform and configuration.

Many business calling environments allow users to work from supported mobile applications while keeping the company number and central routing behind the call.

In many cases, yes.

Number portability depends on the number type, country, ownership and current provider. We verify the options before migration rather than assuming every number can be moved in the same way.

Yes.

3CX is part of the Voice & Workplace portfolio and can be configured around users, business numbers, call routing, queues and integrations.

Yes.

Althicom can add business telephony to Microsoft Teams so employees work from a familiar environment while the telephony infrastructure is managed underneath.

Not necessarily.

In some architectures, Microsoft Teams can remain the employee-facing workspace while 3CX provides relevant telephony and routing capabilities underneath. The right setup depends on the organisation and its existing Microsoft environment.

Althicom supports local, national, international and other business-number requirements across available markets.

Availability, documentation and permitted use depend on the country and number type, so we verify the requirement for the specific market rather than publish an unverified global country count.

A DID is a telephone number that can deliver inbound calls directly into a PBX, communication platform or application.

DIDs are commonly used for local numbers, users, teams and reseller services where the number needs to be managed independently from one physical phone line.

A toll-free number allows the called organisation to carry the cost of the call rather than the caller, subject to the rules of the market where the number is provided.

Registration and availability can differ by country.

UIFN is an international freephone number concept designed for use across participating countries.

It is a specialised number type with its own requirements and should be evaluated against the markets and customer journey involved rather than treated as a standard local number.

Yes.

Business SMS can be used for authentication, reminders, notifications, customer service, operational updates and application-driven messaging.

Application-to-person messaging is communication generated by software rather than manually by another person.

Typical examples include verification codes, appointment reminders, delivery updates, alarms and service notifications.

Person-to-person messaging describes conversational traffic between people.

In a business environment it may require two-way routing, reply-capable senders and workflows that deliver inbound responses to the person or system responsible for handling them.

Two-way messaging can be supported where the sender setup and route are designed for inbound replies.

If replies are required, that needs to be part of the number and sender strategy from the beginning.

Yes.

Messaging can be connected directly to applications and workflows through available Althicom interfaces. This allows CRM, ERP, booking, logistics and software platforms to trigger communication themselves.

Yes, where the WhatsApp setup and approved use case support it.

The channels do not have to replace each other. SMS, WhatsApp and other messaging can be used according to the type of message, recipient and workflow.

The infrastructure can support permitted business messaging use cases, but the sender remains responsible for lawful marketing, consent, opt-out handling and applicable privacy and telecom rules.

Technical ability to send a message is not the same thing as permission to send it.

Yes.

Data connectivity can be used for routers, equipment, tablets, backup connectivity, mobile business applications and M2M or IoT deployments.

A data SIM is designed around mobile data rather than a normal consumer voice-and-data handset plan.

For business use, other requirements such as roaming, fixed IP, high data volumes, remote devices or long deployment lifecycles can be more important than the consumer bundle structure.

Fixed public IP options can be relevant where routing, VPN access, remote connectivity or whitelisting requires a stable public address.

Availability depends on the connectivity solution and implementation.

Carrier-grade NAT allows multiple users to share public IP addressing.

It works for many normal internet connections but may prevent direct inbound routing, which can be a problem for VPN, remote-access and infrastructure use cases.

If your application needs inbound reachability, this requirement should be identified before the connection is ordered.

Roaming options depend on the selected connectivity profile and networks.

For equipment that travels or spends long periods abroad, the expected markets and duration should be considered as part of the initial design.

Yes.

A mobile connection can provide another path when the primary fixed connection is unavailable, provided the router, addressing and business-continuity design support the intended failover behaviour.

Yes.

Resellers can use Althicom voice, numbers, messaging, connectivity and APIs underneath their own customer proposition.

Not necessarily.

The reseller model can keep the customer relationship and visible proposition with the reseller while Althicom provides infrastructure underneath.

SIP trunking connects a PBX or communication platform to external voice networks using SIP rather than traditional physical telephone lines.

It is particularly relevant for business PBXs, hosted voice platforms and wholesale voice environments.

Origination is the inbound side of voice infrastructure.

A customer calls a number and the call is delivered into the PBX, platform or application responsible for handling it.

Termination is the outbound side.

A call starts in your PBX, platform or application and is routed through the carrier layer to the destination network.

Yes.

Software companies and platforms can use voice, messaging, numbers and connectivity as infrastructure underneath their own interface and customer relationship.

Not always.

The appropriate operational model depends on the service. Where APIs or technical integrations are available, communication can be connected to your own platform and workflows instead of asking every user to work in another interface.

Use Report an Incident to create a support ticket so the issue can be tracked and followed up properly.

If the issue is urgent, call Althicom directly on +31 85 666 4 666.

Book a technical call of 30 or 45 minutes, depending on the specialist.

We use it to go through architecture, migration, implementation and technical requirements.

Standard direct-business implementations can be operational within 5 working days across Europe, and within one day when it is truly urgent, depending on number portability, integrations and migration requirements.

Carrier, reseller and API projects can involve different dependencies and are scoped separately.