Skip to content
Althicom
Call us: +31 85 666 4 666

Keep devices connected without treating them like phones

Connected devices have different requirements from employees with smartphones.

They may stay online for years, travel between networks, sit behind routers or require remote access.

Build the connectivity around the device and application.

Free and non-binding. You talk to someone technical, not a sales script.

Some M2M environments need to be reachable from outside.

Use a fixed public IP where routing, monitoring, remote management or VPN connectivity requires a stable address.

The IP model should be chosen according to the actual access requirement rather than added only after remote connectivity fails.

Fixed public IP
CGNAT

Standard mobile data may sit behind carrier-grade NAT.

For devices that only initiate outbound traffic, that may be perfectly acceptable.

For direct inbound access, it may make the application impossible to operate as designed.

The requirement therefore needs to be identified before deployment.

A fleet of connected devices should be treated as infrastructure rather than as hundreds of unrelated mobile subscriptions.

Structure the connectivity around the application, deployment and operational lifecycle.

That can include how SIMs are assigned, how devices are grouped, which markets they operate in and which services require special routing or addressing.

Fleet-oriented management

Remote sites and routers

M2M connectivity is not limited to tiny sensors.

Routers at remote sites, kiosks, terminals and unattended locations can use the same mobile infrastructure when the connection needs to run without a local employee managing it.

Alerts and messaging

Some connected applications also need SMS or another messaging channel.

A device or monitoring platform may need to notify people when a threshold is reached, a process changes or an alarm is triggered.

Because Althicom provides messaging as well as connectivity, those layers can be designed together where useful.

The silhouette of a man on the phone against a blue sky
A woman holding a laptop writes notes on a whiteboard

Voice or number requirements

A connected application may occasionally need voice or a telephone identity as part of a broader service.

Rather than treat that requirement as a separate supplier decision, it can be considered alongside the data layer when the use case calls for it.

For integrators and platforms

M2M and IoT solutions are often sold by a software company, hardware provider or systems integrator rather than directly by a telecom provider.

A smiling woman with a headset working at a laptop

Related services