VoLTE and Voice Plans for IoT Devices: An OEM's Guide

Voice is a mission-critical component for many IoT devices. Real-world deployments still depend on reliable, real-time communication between people and devices. From medical alert systems and security panels to connected wearables and access control systems, combined voice and data connectivity strategies enable life-saving technologies around the globe.

As cellular networks transition to fully IP-based architectures, VoLTE has emerged as the standard for delivering voice over modern LTE and 5G networks. For IoT OEMs, this shift is more is a fundamental change in how voice is provisioned, supported, and integrated into device design.

However, many SIMs and connectivity providers are unable to support the specialized plans required by deployments that utilize voice. This creates immediate limitations for voice-enabled devices. If a device depends on SMS for provisioning, onboarding can fail. If it requires a phone number for account registration or inbound communication, it may never function as intended.

For OEMs, this means voice support must be validated early. Connectivity decisions made during the design phase directly determine whether a device can support real-world voice functionality. In this article, we will explore how VoLTE functions, the importance of voice in the world of IoT innovation, and how Zipit Wireless’s global Tier-1 carrier relationships help IoT OEMs launch voice-enabled devices at scale.

What is VoLTE?

Voice over LTE (VoLTE) enables high-quality, real-time voice and data services on 4G and 5G networks. VoLTE replaces legacy 2G/3G voice in devices such as trackers, wearables, alarms, and connected vehicles. It’s a foundational step toward fully IP-based mobile networks and aligns with the broader transition to 5G.

VoLTE also offers faster call setup, better battery efficiency, and superior audio compared to older circuit-switched voice technologies. VoLTE is now the primary method for delivering voice services over modern cellular networks.

Historically, voice in cellular networks relied on circuit-switched infrastructure. Devices would reserve a dedicated channel for the duration of a call, separate from any data transmission. That model is now obsolete. As carriers transitioned to LTE, they eliminated circuit-switched voice entirely. Voice is now delivered as IP packets over the same network as data.

Devices can now support simultaneous voice and high-speed data transmissions, enabling use cases like a personal safety wearable placing an emergency call while transmitting GPS coordinates in real time. Call setup times are faster, which matters in scenarios where seconds make a difference.

But it also introduces new dependencies. Voice is tightly coupled with carrier infrastructure, quality of service policies, and IMS (IP Multimedia Subsystem) frameworks that govern how calls are established and maintained. VoLTE-enabled IoT devices require reliable connectivity strategies to transmit data and operate effectively.

Unlike legacy voice:

• VoLTE enables simultaneous voice and data transmission
• It offers improved call quality and faster call setup times
• It integrates into modern LTE and 5G network architectures

Some providers rely on workarounds, like over-the-top VoIP applications, that don’t deliver reliable, carrier-grade voice. Others may not support SMS or traditional telephony features at all, creating friction during device setup and operation.

For example:

• If a device requires SMS to configure an APN, what happens if the SIM doesn’t support SMS?
• If a wearable needs a 10-digit phone number for user registration, can the connectivity provider support that?

These are common deployment blockers, and many MVNOs and carriers are ill-equipped to help IoT OEMs manage the inherent complexities of voice-enabled IoT. Zipit Wireless’s dynamic connectivity strategies allow us to help IoT OEMs with voice application support their deployments and optimize efficiency, performance, and scalability.

How VoLTE delivers voice over LTE networks

VoLTE encodes voice as IP packets and transmits them over the LTE data channel. However, unlike regular data traffic, VoLTE gets carrier-managed Quality of Service (QoS) guarantees that prioritize voice packets over standard data.

This allows for simultaneous voice and data transmission. A personal safety device can place an emergency call while transmitting GPS coordinates at the same time. Call setup time also drops significantly (typically under 2 seconds versus 6–7 seconds for 3G). For a personal safety device or elevator phone, faster call setup and simultaneous data transmission are functional requirements.

Voice still matters in a data-first IoT world

The assumption that IoT is data-only overlooks entire product categories with active commercial markets and specific regulatory obligations. Voice in IoT is a human interface layer, an escalation mechanism, and often a compliance requirement.

Robust voice functionality and voice data transmission are increasingly necessary for successful IoT use cases. Devices like medical alert systems, elevator phones, alarm panels, and smart intercoms rely on real-time, person-to-person communication. Others, like asset trackers or connected wearables, depend on SMS and voice functionality for provisioning, user interaction, or escalation events.

Many IoT use cases require true voice capability

Several device types depend on real voice calls, real phone numbers, and real SMS to function:

• Emergency communication devices: Personal safety devices, lone worker monitors, and fall detection wearables require VoLTE to place a voice call while simultaneously transmitting location data. E911 compliance is mandatory for U.S.-deployed devices in this category.
• Medical alert systems: PERS (Personal Emergency Response Systems) require a real 10-digit phone number to register with monitoring platforms and receive inbound calls from response centers. Many also require SMS for device configuration.
• Elevator phones and alarm panels: These POTS replacement devices historically used analog phone lines and are now migrating to cellular. They combine low-frequency, high-reliability voice with background data telemetry.
• Smart intercoms and access control: Access control intercoms require VoLTE to place a voice call from an entry point to a resident's phone number. This is a real call to a real number, not a VoIP session.
• Fleet and field communication devices: Industrial field communication systems use VoLTE to enable voice communication between field workers and central control rooms over the same LTE connection used for telematics data.

Voice functions as a safety and escalation layer

In many IoT deployments, voice isn't the primary communication channel for routine operations. Instead, it's the escalation layer when automated data-driven responses aren't enough.

A personal safety device transmits location data continuously via data. But when a fall is detected, it escalates to a voice call so a human can assess the situation. An alarm panel sends a data alert, but the monitoring center calls back to verify before dispatching emergency services. Voice is the human interface that activates when automated systems reach their limits, and the data transmission relies on nuanced, individualized connectivity strategies.

Devices require a 10-digit phone number or true SMS

Many IoT devices require a real MSISDN (10-digit phone number) and true SMS capability not only for voice calls, but for device configuration and service registration as well.

A GPS tracker that uses SMS to configure its APN settings cannot establish a data connection at all if the SIM lacks SMS capability. The device is dead on arrival. A kids' wearable that requires SMS verification to register with a companion app cannot complete onboarding.

Standard IoT data SIMs do not provision MSISDNs or support true person-to-person SMS by default. This is a hard failure, not a degraded-performance scenario. You'll want to confirm SMS and MSISDN support with your connectivity provider before finalizing hardware.

Learn more: Can You Future-Proof Your IoT Strategy? A Roadmap for Long-Term Success

VoLTE vs. VoIP for IoT devices

For OEMs who have identified that their device requires voice, the next question is architecture. Here's how VoLTE and VoIP compare across the dimensions that matter for IoT deployment decisions:

VoLTE, VoIP, and IMS explained

Generic VoIP runs over any data connection without carrier involvement, without QoS guarantees, and without emergency services routing. VoLTE, on the other hand, is carrier-managed. It operates within the carrier's IMS (IP Multimedia Subsystem) infrastructure and carries guaranteed latency under 150ms along with E911/E112 emergency call routing.

IMS is the 3GPP-defined signaling framework that manages VoLTE session setup, authentication, and routing. IMS profiles are carrier-specific, meaning device behavior can vary across networks. For mission-critical IoT applications, VoIP is not a substitute for VoLTE.

QoS guarantees and why they matter for mission-critical devices

VoLTE traffic is assigned a dedicated bearer with guaranteed latency under 150ms and packet loss thresholds that maintain call intelligibility even under network load. For a personal safety device placing an emergency call. A dropped or unintelligible call in an emergency scenario is a device failure with potential liability consequences. Generic VoIP over a shared data bearer cannot provide the same guarantees.

When VoIP is a viable alternative

VoIP can work for non-safety-critical communication applications where call quality degradation is acceptable. It's also viable for devices that operate exclusively on Wi-Fi with stable broadband, and for applications where the device communicates with a known endpoint rather than routing to arbitrary phone numbers. VoIP eliminates carrier certification requirements and can be faster to deploy for non-critical applications. However, it cannot substitute for VoLTE in any scenario requiring E911 compliance, a real phone number, or guaranteed call quality under variable network conditions.

Technical requirements for voice-enabled IoT devices

Adding voice to an IoT device requires deliberate decisions at the hardware, firmware, and carrier level. Decisions made incorrectly early in development are expensive to reverse.

LTE-M and module selection for VoLTE support

LTE-M (Cat-M1) is the preferred network technology for voice-capable IoT devices in North America. It natively supports VoLTE, offers moderate power consumption, and maintains strong U.S. coverage. NB-IoT, by contrast, does not support voice and is not a viable choice for voice-enabled devices.

Not all LTE modules include VoLTE firmware or have completed carrier-specific certification. You'll want to verify module certification against the target carrier's approved device list before committing to a hardware design. Discovering a module isn't certified after design lock requires a hardware re-spin.

IMS integration and firmware readiness

IMS registration requires explicit firmware development. The device firmware handles IMS session setup, authentication, and re-registration, and it requires configuration with carrier-specific IMS profiles.

Because IMS profiles vary by carrier, a device certified on one carrier's network may behave differently on another. OEMs who treat VoLTE as a software feature to be enabled via a configuration flag will discover that IMS integration is a firmware development workstream that requires separate scoping and resources.

Carrier certification requirements for VoLTE devices

Carrier certification is the most commonly underestimated requirement in voice-enabled IoT development. Each Tier-1 carrier (Verizon, AT&T, T-Mobile) maintains separate certification labs, separate testing requirements, and separate approval timelines.

• Certification costs: Per-device SKU certification can range from $10,000–$50,000 per carrier. Multi-carrier certification across all three U.S. Tier-1 carriers can reach $30,000–$150,000 per SKU.
• Timeline impact: Certification typically adds 6–12 months to deployment timelines compared to 2–3 months for data-only devices.
• Per-carrier testing: A device that passes AT&T certification is not automatically approved on Verizon or T-Mobile. Testing repeats for each carrier.

Zipit Wireless bypasses this per-carrier fragmentation through our existing global Tier-1 carrier relationships.

Voice plans vs. data plans for IoT deployments

Standard IoT SIMs are often configured for data-only connectivity. They are not always assigned a 10-digit MSISDN, they may not support person-to-person voice calls, and they do not always support true SMS. This is a provisioning decision made by the MVNO or carrier.

OEMs who select a data-only IoT SIM and assume voice can be enabled later will discover that enabling voice requires a different SIM type, a different provisioning profile, and often a different connectivity provider entirely.

Learn more: IoT Data Plans: A Complete Roadmap from Deployment to Monetization for Cellular Devices

How IoT voice plans differ from consumer mobile plans

Consumer voice plans are structured around minute bundles or unlimited calling. These are models built for predictable, high-frequency human voice usage. IoT voice usage is fundamentally different: event-driven, low-frequency, and often safety-critical.

A personal safety device may place one call per year. An alarm panel may place one call per alarm event. Consumer minute-bundle plans are poorly matched to IoT usage patterns. OEMs either over-provision (paying for minutes that are never used) or face per-minute overage charges when usage spikes.

Combined voice and data plans for IoT devices

Rather than managing separate voice and data plans across different billing systems, OEMs working with IoT-focused MVNOs can configure integrated plans that bundle voice capability alongside data within a single plan structure.

Combined plans simplify billing, eliminate reconciliation overhead, and provide a single operational view of connectivity costs per device. For devices like elevator phones or alarm panels that use both capabilities (data for telemetry, voice for emergency communication) a combined plan is the correct architecture for managing total connectivity cost.

Partnering with a connectivity provider that understands the logical nuances of differing IoT deployments and applications is crucial for building a flexible and scalable connectivity strategy. Zipit Wireless not only understands the depth of complexity each IoT deployment presents, we can actively help OEMs support their voice and data transmission needs with specialized plans.

Global deployment challenges for voice-enabled IoT

Voice adds a dimension of complexity to global deployments that goes beyond standard data connectivity challenges.

Carrier and regional VoLTE support variability

VoLTE support is not uniform across carriers or regions. While Tier-1 U.S. carriers have completed VoLTE rollouts, international carrier VoLTE deployment varies significantly by country and carrier.

In some markets, VoLTE is available only on specific frequency bands or only for devices on the home network, not for roaming devices. OEMs deploying voice-enabled IoT globally cannot assume that a device certified for VoLTE on a U.S. carrier will function correctly on a partner network in another region. This can require access to native connectivity strategies. Without a partnership that can offer global Tier-1 connectivity options, OEMs are forced to negotiate these contracts, adding an enormous burden of work that stretches beyond their team’s core competencies.

Voice roaming limitations

VoLTE roaming requires IMS interoperability between the home network and the visited network. This is a more complex technical dependency than data roaming, which operates at the IP layer.

For global IoT deployments, relying on roaming for voice connectivity introduces a failure rate that is unacceptable for safety-critical applications. The solution is native connectivity—SIMs provisioned on local carrier networks in each target market, not roaming profiles dependent on inter-carrier IMS agreements.

Tip: Multi-network SIM strategies, where the SIM can connect to multiple carrier networks in each market, provide the redundancy that voice-enabled IoT requires. For safety-critical applications, native connectivity in each deployment region is the correct architecture; roaming should not be the primary strategy.

Learn more: The IoT Playbook for Carrier & Connectivity Strategies Maximizing Global Reach & Uptime

What to look for in a VoLTE-capable IoT connectivity partner

The complexity covered above translates into specific evaluation criteria when selecting a connectivity provider.

True VoLTE access vs. data-only MVNO offerings

The most important question to ask a prospective connectivity provider isn't "do you support VoLTE?" but "do you have direct VoLTE access from Tier-1 carriers?"

Many MVNOs offer data-only IoT SIMs and cannot provision a 10-digit MSISDN, enable true voice calls, or support true SMS. Some MVNOs market connectivity as "LTE" without disclosing that voice capability is not included. You'll want to confirm explicitly before signing a contract that the MVNO can provision SIMs with a real MSISDN, support person-to-person voice calls, and enable true SMS.

Tier-1 carrier relationships and what they enable

An MVNO's ability to deliver VoLTE is directly dependent on its carrier agreements. MVNOs without direct Tier-1 carrier relationships cannot access the IMS infrastructure required for VoLTE, they can only offer data connectivity.

Zipit's direct relationships with all three major North American carriers enable the provisioning of VoLTE-capable SIMs and support for carrier-certified device deployments with the QoS guarantees that VoLTE requires.

Unified voice and data billing for IoT fleets

Managing voice and data billing across separate systems creates operational overhead that scales poorly with fleet size. At 10,000 devices, reconciling voice usage from one carrier portal with data usage from another and mapping both to device-level billing becomes a significant burden.

Zipit's connectivity management platform and billing solutions provide a single operational view of both voice and data services across deployed device fleets, with per-device visibility into combined usage and cost. For OEMs monetizing connectivity through subscription services, unified billing is the infrastructure that makes subscription billing to end customers accurate and scalable.

Partner with Zipit Wireless and maximize your VoLTE-enabled device’s performance and growth

Voice is not a legacy feature in IoT. It's an evolving requirement that introduces complexity across device design, connectivity strategy, and billing. Working with a connectivity partner that understands VoLTE requirements from the start and can deliver true VoLTE access, combined voice and data plans, and unified management simplifies what would otherwise be a fragmented, multi-vendor challenge.

To explore how Zipit can support your voice-enabled IoT deployment, contact us.

You may also like:

• Bring Your Own Cellular Connectivity: How Reliable Connections Strengthen Security and Support for IoT Devices
• The Advantages of Cellular Connectivity for Stationary IoT Devices
• Expanding IoT Connectivity Worldwide: Taking North American Deployments Global