A VoIP gateway gives a hotel its own SIM-based voice trunks: local mobile numbers, no fixed-line contracts per room, and call records that flow into the billing system. The right deployment pairs a PBX for room logic with a gateway for external trunks, sized by peak concurrent external calls rather than room count.
This guide walks through the architecture, sizing method, and billing path that make SIM-based voice work in a hotel, so a buyer can spec the gateway correctly the first time instead of discovering integration gaps after opening day.
The Hotel Voice Architecture
A typical property runs four layers in sequence. The PBX handles room extensions, front-desk queues, wake-up calls, and dial plans. The VoIP gateway provides external trunks through SIMs. Call accounting software tracks guest call records, and the property management system (PMS) posts charges before check-out.
The gateway is the trunk layer: every external call—guest dialing out, incoming reservations, front-desk calls—travels through it. Internal calls between rooms stay inside the PBX and never touch the gateway, which is why port sizing should ignore room-to-room traffic entirely.
Reservations and front-desk calls shape the trunk design differently from guest calls. An incoming reservation lands on a number routed to the front-desk queue; a guest dialing out needs a route and a rate class; and a department number such as housekeeping rings its own extension. Each flow is a dial plan in the PBX plus a routing rule on the gateway, so define the flows before choosing ports.
Choosing the gateway model also means choosing the SIM fleet. Confirm the SIM-slot count, supported network generations, and codecs against the property's markets, because a property that hosts international guests may need roaming-friendly plans or per-country rate tables. The SK-VOIP series lists the port and SIM-slot configurations to compare.
The VoIP gateway product line covers the trunk side of this architecture, from small office units to higher-concurrency chassis.
Why SIM-Based Trunks Fit Hotels
SIM-based trunks solve problems hotels feel daily:
Local SIM numbers give the property a local presence in each market; there is no fixed-line contract per room and capacity scales with ports; call costs are visible per SIM, which simplifies billing reconciliation; and incoming calls to specific numbers can route directly to departments.
For properties in multiple cities, the same hardware family can carry each site's local numbers under one management model.
SIM-based trunks also remove the fixed-line dependency that many properties inherit. There is no ISDN or PSTN contract per room to renegotiate when the property changes hands, and adding capacity means adding a SIM and a port rather than ordering another line from the operator.
Cost visibility improves billing reconciliation because each SIM has its own call records and rates. The property can see which numbers generate revenue, which routes are expensive, and where to adjust the rate table, instead of waiting for a consolidated line bill at month end.
For business continuity, SIM trunks do not depend on one local operator contract the way a single PRI does. If a carrier degrades, calls can be re-routed across other SIMs in the pool, and a second gateway site can carry overflow; document the failover path in the same session as the main route.
For chains and management groups, the same hardware family standardizes operations across sites. One configuration template, one support channel, and one training set cover every property, which reduces the per-site engineering cost that kills multi-property voice projects.
Each property keeps its own rate table and its own local numbers, while the group retains one template for provisioning and support.
Capacity Sizing
Size by peak concurrent external calls, not room count:
| Property profile | Typical external-call concurrency | Starting tier |
|---|---|---|
| Small property, moderate traffic | 4–8 concurrent calls | 8 ports |
| Mid-size property with active front desk | 8–16 concurrent calls | 16 ports |
| Larger property with conference traffic | 16–32 concurrent calls | 32 ports |
Worked example: a 40-room property with a busy front desk peaks at 10 concurrent external calls; with headroom that points to 16 ports. Add margin for check-in and check-out hours, when guests call more.
Conference facilities and event weekends change the sizing picture. A ballroom day with 30 concurrent external calls needs a different chassis than a normal Tuesday, so use the measured peak from your PBX call detail records rather than a seasonal estimate, and add the same 1.5–2x headroom you would apply to SMS capacity planning.
Ports and SIM slots are not the same number. A gateway may carry more SIM slots than concurrent channels, because SIMs rotate and share channels; confirm both figures on the product page and size the SIM fleet for carrier variety, so a single operator outage does not take every call route down.
The PBX's call detail records are the most reliable input for this exercise: export the busiest week, count concurrent external calls in five-minute buckets, and take the peak. That number, plus headroom and carrier diversity, is the specification you hand to the supplier.
Billing and Integration
Guest call billing depends on the data path:
The gateway logs call records (CDRs) with duration, SIM used, and destination; call accounting software matches those records to rooms; and the PMS posts the charges before check-out.
Confirm the gateway's CDR export format matches your call accounting system before buying; format mismatches are the most common integration failure.
A useful CDR contains the call start time, duration, source extension or room, destination number, SIM or route used, and a status field. Confirm that every field your call accounting software expects is present, because missing fields usually mean silent billing gaps rather than a visible error.
Rate management is part of integration too. The property sets per-destination rates in the call accounting system, and the gateway's route selection decides which SIM carries each call; test international destinations with a small call set to confirm that rates and routes match before check-in traffic starts.
Commissioning should include a billing test, not just a connectivity test: make a guest-room call to a domestic and an international number, confirm the CDR arrives with the right room and duration, and post a test charge in the PMS before the first real guest uses the phone.
Telarvo Expert Views
Hotel deployments fail on integration, not hardware: the gateway works, but CDR format or front-desk routing was never tested before opening day. Define the call flow and the billing export in the quotation, then verify both with a pilot call set before check-in starts.
— Voice Solutions Engineer, Telarvo Store
Validation note: capacity tiers are planning guidance; size from the property's measured peak concurrency and confirm model-specific ports, SIM slots, and codecs.
Conclusion
Most properties already own a PBX and a PMS; the gateway is the missing trunk layer that connects them to mobile networks with local numbers. The sizing, routing, and billing decisions are all knowable before purchase, which is exactly why the integration plan should be written into the quotation.
Key Takeaways for B2B Buyers
Run a PBX for room logic and a gateway for trunks because they are complementary; size ports by peak concurrent external calls rather than room count; confirm the CDR export format against your call accounting software before buying; and add local SIM numbers per market for a local presence.
Questions to Ask Before Committing
Ask what your peak concurrent external call load is including check-in hours, which CDR formats the gateway exports and whether they match your billing stack, which SIM plans and local numbers apply in each operating city, and how training, commissioning, and support are documented in the quote.
Ask Telarvo Store for a VoIP gateway configuration review based on your property's call profile, and confirm the SK-VOIP model and CDR settings before quoting.
FAQs
Can guests call internationally through the gateway?
Yes, with appropriate routing rules and rates per destination. Configure dialing restrictions per room class if needed.
How many ports does a hotel need?
Match ports to peak concurrent external calls. A busy front desk and conference center drive the real peak, not room count.
Does the gateway replace the hotel PBX?
No. The PBX manages extensions and logic; the gateway is the trunk to mobile networks. They work together.
How is guest call billing handled?
Through CDR export to call accounting software, then to the PMS. Verify the export format before purchase.
Can the gateway handle room-to-room calls?
Room-to-room calls stay in the PBX and never consume gateway ports, so sizing covers external calls only.