Summary

  • PBX Hosting presents a substantial Mexican communications service: SIP trunks, virtual numbers, cloud PBX, call-centre diallers, SMS, web hosting, VPS and dedicated servers. Its public terms say the service is backed by INBTEL, which holds a Mexican commercial telecommunications concession.
  • Network evidence connects the two names without making them interchangeable. AS265586 is registered and routed as INBTEL, while the IPv4 block 200.58.252.0/22 is publicly labelled PBX HOSTING SA DE CV and originated by that AS.
  • The most important controls are operational, not promotional. Call routing, concurrent-call capacity, recordings, CDR retention, backups, customer identity checks, provisioning and support all have explicit boundaries in the published service terms.
  • A buyer should therefore verify the contracting party, service location, route and carrier design, recovery obligations, incident communications and escalation coverage for the exact product being bought. A concession, an IP block and a 99.99% headline are useful evidence, but they do not answer those questions by themselves.

A cloud phone system becomes infrastructure at the moment the office stops keeping a working alternative. Incoming sales calls, collections, customer support and emergency escalation then depend on a chain that starts with the user's internet access, passes through software and hosted compute, and reaches the public telephone network through carrier interconnection. The apparent simplicity of a browser-controlled extension hides that chain. For a procurement team, the central question is not whether PBX Hosting can place a call. It is whether the whole chain can be identified, tested and held accountable when calls fail.

PBX Hosting's public footprint gives that investigation more substance than a generic hosted-PBX label would suggest. Its site markets SIP trunks, virtual Mexican numbers, toll-free numbers, a cloud switchboard, call-centre packages, predictive dialling, bulk SMS, web hosting, VPS and dedicated servers. The home page claims more than 500 million minutes a month, over 5,000 satisfied customers, more than ten years of experience and 99.99% effective availability. Those figures are company claims, not independently measured results, but they establish the scale and reliability story that the provider asks customers to buy.

The service identity needs to be read in layers. PBX Hosting's terms describe it as a company backed by INBTEL S.A. de C.V., which has a single commercial-use concession before Mexico's telecommunications regulator. An industry directory describes PBX Hosting as a subsidiary and brand of INBTEL Comunicaciones, while the company's LinkedIn page uses the wording "PBX Hosting by INBTEL" and says it operates under a federal telecommunications concession. The exact legal and commercial roles should therefore be confirmed in the order form and invoice rather than inferred from the brand alone.

The regulatory record supports the INBTEL side of that account. In August 2019, the Instituto Federal de Telecomunicaciones approved a single commercial-use concession for INBTEL. A December 2024 decision then addressed interconnection conditions between INBTEL and several fixed-network operators for 2025. Earlier public decisions also dealt with interconnection between INBTEL and mobile or fixed carriers. This is stronger evidence than a logo or an assertion of direct access to the telephone network: it places INBTEL inside the regulated interconnection process.

It does not, by itself, define which entity contracts each PBX Hosting product or guarantee the performance of a customer's calls.

Public number-resource evidence adds a second operating layer. BGP.tools identifies AS265586 as INBTEL S.A. de C.V., active under LACNIC, with a visible mix of IPv4 and IPv6 origins and multiple upstreams. In the same routing view, 200.58.252.0/22 is described as PBX HOSTING SA DE CV and covered by a valid route-origin authorisation. Hurricane Electric's BGP view also shows a LACNIC route object for that block with AS265586 as the origin, while a route entry in another registry describes INBTEL. Reverse-DNS names across the block use the pbxhosting.com.mx domain.

That combination matters because it is a concrete connection between the customer-facing name and an operating network. The evidence supports a narrower conclusion than "PBX Hosting owns a complete independent network": a block bearing the PBX Hosting name is routed through INBTEL's autonomous system. BGP.tools observed six upstreams when reviewed, including Arelion, Flo Networks, Telecom Italia Sparkle, DIGY Networks, Hurricane Electric and Alestra, as well as a much larger peer set. Route observations change, and a list of upstreams does not prove how a specific voice service is engineered.

It does provide a testable surface for asking about path diversity, failover, DDoS response, route monitoring and planned maintenance.

The product pages show where that network becomes a customer workflow. The free SIP-trunk offer includes unlimited trunks, statistics, a web panel and technical support. PBX Hosting explains that the trunk bridges a customer's PBX to VoIP and the public switched telephone network. Its cloud-PBX service moves the switchboard into a hosted environment, with remote access, centralised web management, extension configuration, call handling and maintenance performed by the provider. The practical trade is clear: the customer avoids on-premises PBX hardware but transfers more control over configuration and availability to a remote service.

The call-centre offer increases that dependency. PBXDialer is marketed for inbound and outbound work, with predictive dialling, campaign scheduling, mixed sessions, prerecorded messages, browser-based agent access, automatic call recording and live operational monitoring. Public plans range by simultaneous calls and agent capacity. The PBX Dialer 30 plan, for example, advertises support for 30 simultaneous calls and up to 30 agents; larger tiers advertise 60 or 150. The service terms separately specify concurrent-call limits for PBX and VICIdial packages. These are capacity boundaries, not minor pricing details.

A collections team that needs 80 active conversations cannot safely treat an 80-agent login count as equivalent to 80 concurrent calls.

Automation changes the supervision work rather than removing it. Predictive dialling can reduce idle time, but someone still has to tune campaigns, control abandoned-call risk, maintain contact data, review recordings, watch agent states and reconcile call-detail records with billing. PBX Hosting's terms say customers should back up recordings and CDRs they need. For the free SIP-trunk service, the company disclaims responsibility for CDRs older than one month, and it asks customers to monitor the disk space used for switchboard recordings. The records also use the Central time zone at UTC-06:00.

These details affect investigations, customer disputes and compliance reviews; retention and time-zone handling belong in the operating design, not in post-incident discovery.

The broader hosting offer adds another set of responsibilities. PBX Hosting advertises shared web hosting, VPS and dedicated servers. The VPS page lists configurable compute tiers with SSD storage, monthly transfer allowances and technical support, while the dedicated plans list larger resources. The terms say shared-hosting customers must schedule their own periodic backups and state that PBX Hosting is not responsible for accidental information loss. They also prohibit using shared hosting as a backup repository and impose storage, database, transfer and resource-use limits.

A plan called "hosting" is therefore not a managed recovery service. A customer must design an off-service backup, test restoration and know which party owns the result.

Locality requires the same precision. The brand is Mexican, the regulator evidence is Mexican, the public phone-number offer spans more than 300 Mexican area codes, and the network resources are registered in the region. The website also advertises contact numbers in Argentina, Peru, Colombia and Miami, and its terms discuss virtual numbers in Mexico, the United States, Canada and other countries. None of those facts locates a particular PBX instance, recording, CDR, backup, management panel or support system.

For data-sovereignty purposes, a Mexican number is a routing and commercial attribute, not proof that every copy of the associated data remains in Mexico.

The published terms are especially useful because they expose the service's control points. New customers must provide registration information, identification, address and tax documents, and return a signed contract within 30 days. PBX Hosting reserves suspension rights when those requirements are not met or when it detects prohibited or abusive use. SIP trunks must use an assigned caller ID from the provider's environment, and US-bound calls require an assigned CID. These controls can reduce abuse, but they also create dependencies on administrative review.

Procurement teams should ask who can suspend service, what evidence triggers a restriction, how an appeal works and which contacts can act outside normal business hours.

Provisioning is not entirely automatic either. The terms say the clock starts after payment has been identified and the administrative contact form has been delivered. They state indicative business-hour activation windows of six to 12 hours for virtual numbers, 12 to 24 hours for PBX switchboards, and 24 to 72 hours for dedicated servers and VPNs. That makes local administrative labour part of the product. A customer's go-live plan must account for payment reconciliation, identity checks, configuration, number assignment and hand-off, not merely the instant creation associated with a self-service cloud console.

Support coverage is similarly specific. The website lists technical-support hours of 8am to 9pm Monday to Friday and 9am to 6pm Saturday, while sales and administrative hours are shorter. It provides telephone, WhatsApp and email contacts. The refund language says a qualifying claim requires a ticket that has gone more than 24 hours without a response under the stated SLA, and it distinguishes a response from a solution. That is a meaningful contractual clue: a first reply is not the same as restoration.

Buyers with overnight operations should establish the after-hours incident route, engineering escalation authority, response and restoration targets, status-update cadence and service-credit mechanism in writing.

Availability claims need the same distinction. The home and company pages display 99.99%, while the general terms contain a section headed 99.9% availability and acknowledge planned or unplanned interruptions. The difference is material: 99.99% and 99.9% imply very different annual downtime allowances before exclusions. The public material reviewed does not supply an independently measured status history or a complete calculation method. A contract should therefore specify which percentage applies to which service, the measurement point, excluded maintenance, start and end of an incident, credit entitlement and whether carrier failures count.

For a buyer, the diligence plan can be concrete. First, reconcile the legal names: identify the contracting and invoicing entity, the concession holder, the entity responsible for personal data, and the party that owns or controls assigned numbers and IP resources. Second, map the technical chain for the purchased product: customer access link, DNS, authentication, PBX application, media path, SIP interconnection, recording store, CDR system, management console and upstream networks.

Third, test failure, not just activation: sever one internet path, exhaust concurrent-call capacity, restore a recording, export CDRs, rotate administrator credentials, open an after-hours ticket and port or reroute a number.

The same exercise should settle exit risk. Customers should know how quickly numbers can be ported, how configurations and recordings are exported, whether a final CDR set is available, what happens to prepaid balance, when deleted services are physically removed, and whether cancellation itself causes immediate deletion. PBX Hosting's terms require written cancellation by the account holder and describe administrative and physical removal. A business whose phone operation is embedded in a provider's dialler, numbers and records needs a tested exit sequence before a dispute or outage forces one.

PBX Hosting is therefore more than a name attached to a generic cloud offer. The public record shows hosted communications products, a regulated INBTEL relationship, interconnection activity, visible number resources and explicit operating rules. The strongest evidence is not the size claim on the home page; it is the way the concession, route origin, product limits and contractual responsibilities can be connected and tested.

That evidence still stops short of assurance. It does not establish measured availability, workload location, restoration success, after-hours engineering performance or the exact liability chain for every product. The defensible conclusion is narrower: PBX Hosting presents a credible operating surface for further procurement work, and its own public terms tell buyers where that work must concentrate. The name becomes assurance only when the legal roles, routes, records, recovery controls and human escalation path all survive a realistic test.