Microsoft Teams Direct Routing
Managed SBC-as-a-Service. The standard alternative to Microsoft Calling Plans for Bahamas users.
See Teams DR →A Bahamas SIP trunk with real +1 242 Bahamas DIDs, URCA-compliant allocation, Frankfurt + London ingress POPs, TLS:5061 with SRTP, every standard PBX integration. From $10.00/mo per DID plus per-minute usage, activation in 3-5 business days after KYC.
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 Bahamas SIP trunk is the same thing carrying +1 242 Bahamas DIDs allocated under URCA.
DIDHub provides the trunk authentication and SIP transport; URCA-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.
URCA doesn't require KYC for standard Bahamas number allocation. Activation is 3-5 business days.
What people typically use a Bahamas SIP trunk for:
The Bahamas' regulator URCA does not require KYC for standard NANP allocations. Activation 3-5 business days. NANP membership means dialing into Bahamian numbers from US/Canada works exactly like a domestic call.
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.
DIDHub supports the standard Bahamas number types over the SIP trunk:
| Code | Type | National dialing | International dialing | Mobile | From |
|---|---|---|---|---|---|
242 | Geographic | 242 XXXX XXXX | +1 242 242 XXXX XXXX | Yes | $10.00/mo + usage |
1-800 | Toll-free | 1-800 XXXX XXXX | +1 242 1-800 XXXX XXXX | Yes | $24.00/mo + usage |
For a deeper look at how number types differ globally, see DID number types explained.
The technical surface of the trunk is standardised; the Bahamas-specific choices are the POP, the codec list, and the failover topology.
For the codec deep-dive, see voice codecs explained.
Outbound from a Bahamas-allocated DID to Bahamas destinations is allowed within approved use cases. The per-minute economics:
| Destination | Per-minute | Billing increment | Notes |
|---|---|---|---|
| Bahamas landline (geographic) | €0.020/min | 1+1 second | Standard use cases |
| Bahamas mobile | €0.10/min | 1+1 second | Standard use cases |
| International from Bahamas DID | Per destination rate | 1+1 second | See global rates |
Create a DIDHub account, supply your business details and the intended use case for Bahamas numbers.
Allocation through our in-region carrier; typically 3-5 business days.
You pick the Bahamas number types you need and how many. Channel capacity allocated at the same time.
SIP URI (defaults to sip.didhub.io, terminating to Frankfurt), digest username/password or IP-ACL details, TLS cert verification fingerprint, and your assigned DIDs.
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.
Place a test call to one of your DIDs from a Bahamas mobile or landline; place a test outbound back. Confirm caller-ID resolves correctly, codec negotiates as expected, and audio quality is acceptable.
; /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-bahamas] type=auth auth_type=userpass username=YOUR_DIDHUB_USERNAME password=YOUR_DIDHUB_PASSWORD [didhub-bahamas] type=aor contact=sip:sip.didhub.io:5061;transport=tls qualify_frequency=30 [didhub-bahamas] type=endpoint transport=transport-tls context=from-didhub disallow=all allow=g711a,g722,opus outbound_auth=didhub-bahamas aors=didhub-bahamas dtmf_mode=rfc4733 media_encryption=sdes direct_media=no
# 3CX -> SIP Trunks -> Add SIP Trunk -> Generic SIP Trunk Trunk name: DIDHub Bahamas 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: +1 242 ... (one of your allocated DIDs) Codecs (priority): G.711a / G.722 / Opus
Every modern PBX, UC platform, and AI voice stack can authenticate against the trunk:
Managed SBC-as-a-Service. The standard alternative to Microsoft Calling Plans for Bahamas users.
See Teams DR →Standard pjsip trunk config (snippet below). FreePBX trunk module maps cleanly to DIDHub's IP-ACL or registration modes.
Asterisk → · FreePBX →Generic SIP trunk template with TLS:5061. Outbound caller ID per extension; per-DID inbound routing rules.
3CX guide →BYOC SIP trunk with Frankfurt ingress for tight latency. Bind specific Bahamas DIDs to specific agents.
AI voice integrations →Per-trunk DNID auto-correct, SRV-based POP failover (Frankfurt primary / London failover).
Kamailio →Per-extension digest registration; useful for distributed support teams routing Bahamas DIDs to remote agents.
Softphones →Live in 3-5 business days. Real Bahamas DIDs, no setup fee after KYC, no contract.
Four line items: per-DID monthly rental, per-minute inbound usage on every Bahamas DID (even landline geographic numbers carry an inbound MOU charge in Bahamas), channel capacity, and per-minute outbound. Setup is $0 once URCA paperwork is approved.
| Type | From | Notes |
|---|---|---|
| Geographic (Bahamas city codes) | $10.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 |
| 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 |
See section 5 above and the full global rate sheet.
Existing Bahamas number? Porting timeline is 3-5 weeks.
For the full porting playbook (US/UK/EU + the global gotchas), see number porting explained.
Frankfurt is the recommended primary; London is the standard failover. Both terminate to Bahamas via in-region carriers.
3-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 URCA/carrier side.
G.711a / G.722 / Opus as the negotiation list, in that order. G.711a is the regional default for Bahamas interop.
Yes, via Microsoft Teams Direct Routing through DIDHub's managed SBC. See Teams Direct Routing.
Yes, BYOC SIP trunk works with every major AI voice platform. Bind specific Bahamas DIDs to specific agents; outbound CLI must match an allocated DID.
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.
N/A (regional construct). Trust signals come instead through national regulator registration and operator-side caller-ID validation.
Yes. Typical Bahamas port timeline is 3-5 weeks. Required documents vary by number type; contact us for the specific checklist. See number porting explained for the global picture.
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.
Live in 3-5 business days. Real Bahamas DIDs, every standard PBX and AI-voice integration, no setup fee after KYC, no contract.