Microsoft Teams Direct Routing
Managed SBC-as-a-Service. The standard alternative to Microsoft Calling Plans for Mexico users.
See Teams DR →
Mexico · IFT
SIP Trunk in Mexico — Mexico City, Guadalajara or Monterrey Inbound + Outbound
A Mexico SIP trunk with real +52 Mexico DIDs, IFT-compliant allocation, São Paulo + Miami ingress POPs, TLS:5061 with SRTP, every standard PBX integration. From $5.00/mo per DID plus per-minute usage, activation in 2-5 business days after KYC.
Real Mexico DIDs allocated through licensed carriers
TLS + SRTP end-to-end
5–200 channel scale per trunk
1. What a SIP trunk in Mexico actually is
A SIP trunk is the IP delivery pipe between a carrier and your PBX, AI voice agent, or call-control platform; signaling over SIP, audio over RTP. A Mexico SIP trunk is the same thing carrying +52 Mexico DIDs allocated under IFT.
DIDHub provides the trunk authentication and SIP transport; IFT-compliant number allocation is coordinated through our in-region carrier partners. Your PBX or platform sees a standard SIP trunk; we handle the regulator-side paperwork.
2. Mexico regulation: IFT, KYC, compliance
IFT requires KYC documentation before any Mexico DID can be allocated. Activation typically takes 2-5 business days. DIDHub handles the document submission and regulator coordination on your behalf.
What people typically use a Mexico SIP trunk for:
- LATAM market entry, Mexico is the second-largest LATAM economy and a major B2B market.
- Mexico City CDMX presence, 55 numbers signal credibility to Mexican enterprise buyers.
- Cross-border NAFTA operations, Mexican numbers paired with US (+1) for North American coverage.
- Tourism and hospitality, Cancún 998 and Cabo 624 for travel-industry presence.
- Toll-free 800, free for Mexican callers, common for customer service.
Mexico's regulator IFT (Instituto Federal de Telecomunicaciones) requires KYC, Mexican RFC (taxpayer ID) for companies, or proof of identity for individuals, plus a Mexican address. Foreign companies typically register through a Mexican agent. DIDHub shows requirements clearly before purchase. Activation completes in 2-5 business days.
For the broader picture across countries, see our guide to international DID compliance & KYC bundles. For the SIP-trunk concept end-to-end, see the DID Number Provider guide.
3. Number types you can route over the trunk
DIDHub supports the standard Mexico number types over the SIP trunk:
| Code | Type | National dialing | International dialing | Mobile | From |
|---|---|---|---|---|---|
55, 33, 81 | Geographic (major metro) | 55 XXXX XXXX | +52 55 XXXX XXXX | Yes | $5.00/mo + usage |
222, 664, 998 … | Geographic (regional) | 222 XXXX XXXX | +52 222 XXXX XXXX | Yes | $5.00/mo + usage |
800 | Toll-free | 800 XXXX XXXX | +52 800 XXXX XXXX | Yes | $24.00/mo + usage |
For a deeper look at how number types differ globally, see DID number types explained.
4. How DIDHub's SIP trunk works in Mexico
The technical surface of the trunk is standardised; the Mexico-specific choices are the POP, the codec list, and the failover topology.
Ingress POPs
- São Paulo (primary), lowest in-region latency to Mexico endpoints.
- Miami (failover), secondary route used if the primary path degrades.
Transport & security
- TLS:5061 recommended for any production trunk; UDP allowed for legacy.
- SRTP for media via DTLS-SRTP or SDES.
- SIP authentication: digest registration (PBX behind NAT) or IP-ACL (static peering). See SIP authentication.
Codecs
- G.711 a-law (PCMA), the Latin American default.
- G.722, wideband HD voice on capable endpoints.
- Opus, for AI voice agents.
For the codec deep-dive, see voice codecs explained.
DTMF
- RFC 4733 (telephone-events over RTP) is the default. SIP INFO and in-band DTMF available for legacy interop on request.
Channel concurrency
- Trunks start at 5 concurrent channels and scale to 200 per trunk off the shelf. Larger requires a custom arrangement.
- Channels are independent of DID count; you can carry 200 numbers on a 10-channel trunk if your concurrent-call peak is 10. See multiple concurrent calls on one DID.
STIR/SHAKEN
- Not applicable. STIR/SHAKEN is US/Canada-only. Latin American trust signals come through national regulator registration and operator-side caller-ID validation.
5. Outbound calling from your Mexico trunk
Outbound from a Mexico-allocated DID to Mexico destinations is allowed within approved use cases. The per-minute economics:
| Destination | Per-minute | Billing increment | Notes |
|---|---|---|---|
| Mexico landline (geographic) | $0.08/min | 1+1 second | Standard use cases |
| Mexico mobile | $0.15/min | 1+1 second | Standard use cases |
| International from Mexico DID | Per destination rate | 1+1 second | See global rates |
Outbound caller-ID rules
- Your outbound CLI must match a DID you've allocated through the trunk. Setting an arbitrary caller ID is rejected at the SBC.
- Origin-based rating (OBR) applies on cross-border outbound, the regulated EEA tier may apply depending on the source carrier.
- For multi-region operators, see origin-based rating savings.
6. Setup in 6 steps
Sign up & submit details
Create a DIDHub account, supply your business details and the intended use case for Mexico numbers.
IFT compliance review
We coordinate with IFT and our in-region carrier; typical timeline 2-5 business days.
Allocate DIDs & channel capacity
You pick the Mexico number types you need and how many. Channel capacity allocated at the same time.
Receive trunk credentials
SIP URI (defaults to sip.didhub.io, terminating to São Paulo), digest username/password or IP-ACL details, TLS cert verification fingerprint, and your assigned DIDs.
Wire up your PBX or platform
Standard SIP trunk configuration on Asterisk, FreePBX, 3CX, Kamailio, OpenSIPS, or any modern stack. For Teams Direct Routing, Vapi, Retell, or other BYOC platforms, paste credentials into their BYOC config.
Test inbound + outbound
Place a test call to one of your DIDs from a Mexico mobile or landline; place a test outbound back. Confirm caller-ID resolves correctly, codec negotiates as expected, and audio quality is acceptable.
Asterisk pjsip example
; /etc/asterisk/pjsip.conf [transport-tls] type=transport protocol=tls bind=0.0.0.0:5061 cert_file=/etc/asterisk/keys/asterisk.crt priv_key_file=/etc/asterisk/keys/asterisk.key method=tlsv1_2 [didhub-mexico] type=auth auth_type=userpass username=YOUR_DIDHUB_USERNAME password=YOUR_DIDHUB_PASSWORD [didhub-mexico] type=aor contact=sip:sip.didhub.io:5061;transport=tls qualify_frequency=30 [didhub-mexico] type=endpoint transport=transport-tls context=from-didhub disallow=all allow=g711a,g722,opus outbound_auth=didhub-mexico aors=didhub-mexico dtmf_mode=rfc4733 media_encryption=sdes direct_media=no
3CX SIP trunk template snapshot
# 3CX -> SIP Trunks -> Add SIP Trunk -> Generic SIP Trunk Trunk name: DIDHub Mexico Registrar: sip.didhub.io Transport: TLS Port: 5061 Authentication: Register/Account based Auth ID: YOUR_DIDHUB_USERNAME Auth password: YOUR_DIDHUB_PASSWORD Outbound caller ID: +52 ... (one of your allocated DIDs) Codecs (priority): G.711a / G.722 / Opus
7. Integration patterns
Every modern PBX, UC platform, and AI voice stack can authenticate against the trunk:
Asterisk / FreePBX
Standard pjsip trunk config (snippet below). FreePBX trunk module maps cleanly to DIDHub's IP-ACL or registration modes.
Asterisk → · FreePBX →3CX
Generic SIP trunk template with TLS:5061. Outbound caller ID per extension; per-DID inbound routing rules.
3CX guide →AI voice agents (Vapi, Retell, ElevenLabs)
BYOC SIP trunk with São Paulo ingress for tight latency. Bind specific Mexico DIDs to specific agents.
AI voice integrations →Kamailio / OpenSIPS
Per-trunk DNID auto-correct, SRV-based POP failover (São Paulo primary / Miami failover).
Kamailio →Softphones (Zoiper, Bria, Linphone)
Per-extension digest registration; useful for distributed support teams routing Mexico DIDs to remote agents.
Softphones →Start your Mexico SIP trunk today
Live in 2-5 business days. Real Mexico DIDs, no setup fee after KYC, no contract.
8. Pricing
Four line items: per-DID monthly rental, per-minute inbound usage on every Mexico DID (even landline geographic numbers carry an inbound MOU charge in Mexico), channel capacity, and per-minute outbound. Setup is $0 once IFT paperwork is approved.
Per-DID monthly
| Type | From | Notes |
|---|---|---|
| Geographic (Mexico city codes) | $5.00/mo + usage | Inbound per-minute applies; standard use cases |
| Non-geographic / national | $36.00/mo + usage | Subject to regulator allocation |
| Toll-free | $24.00/mo + usage | Free for callers; you pay inbound per-minute |
Channel capacity
| Channels | Monthly | Suited for |
|---|---|---|
| 5 | Included with first DID | SMB / single office |
| 25 | $95/mo | Small contact centre, AI agent low concurrency |
| 50 | $180/mo | Mid-size contact centre, AI agent medium concurrency |
| 100 | $330/mo | Large contact centre, multi-tenant SaaS |
| 200 | $580/mo | Enterprise; larger by arrangement |
Per-minute outbound
See section 5 above and the full global rate sheet.
9. Porting an existing Mexico number
Existing Mexico number? Porting timeline is 3-6 weeks.
- Typical port time: 3-6 weeks
- Required documents: phone bill + LOA + ID + proof of address (IFT requirements)
- Cost: port-in fee per number; carrier-side fees may apply
For the full porting playbook (US/UK/EU + the global gotchas), see number porting explained.
10. FAQ
Which POP should I connect to for a Mexico SIP trunk?
São Paulo is the recommended primary; Miami is the standard failover. Both terminate to Mexico via in-region carriers.
How long does activation take for a Mexico SIP trunk?
2-5 business days after KYC documents are accepted (or instantly where KYC isn't required). Provisioning the SIP side itself is hours, not days; the variability is on the IFT/carrier side.
What codecs should I configure for a Mexico SIP trunk?
G.711a / G.722 / Opus as the negotiation list, in that order. G.711a is the regional default for Mexico interop.
Can I use my Mexico SIP trunk with Microsoft Teams?
Yes, via Microsoft Teams Direct Routing through DIDHub's managed SBC. See Teams Direct Routing.
Can I use my Mexico SIP trunk with AI voice agents (Vapi, Retell, ElevenLabs)?
Yes, BYOC SIP trunk works with every major AI voice platform. Bind specific Mexico DIDs to specific agents; outbound CLI must match an allocated DID.
How many concurrent calls can one Mexico DID handle?
The DID is an address; concurrent-call capacity is set by the channel count on the trunk. A 50-channel trunk with 1 DID can carry 50 concurrent calls to that one number; the same trunk with 200 DIDs can carry 50 concurrent calls across any combination of those numbers.
Does STIR/SHAKEN apply in Mexico?
N/A (regional construct). Trust signals come instead through national regulator registration and operator-side caller-ID validation.
Can I port my existing Mexico number to a DIDHub SIP trunk?
Yes. Typical Mexico port timeline is 3-6 weeks. Required documents vary by number type; contact us for the specific checklist. See number porting explained for the global picture.
What use cases get approved most easily?
Customer service inbound, opted-in callbacks, transactional 2FA, inbound AI voice agents, and Microsoft Teams Direct Routing for registered entities. Cold outbound, unsolicited SMS campaigns, and anonymous-relay setups are routinely rejected.
Start your Mexico SIP trunk today
Live in 2-5 business days. Real Mexico DIDs, every standard PBX and AI-voice integration, no setup fee after KYC, no contract.