Microsoft Teams Direct Routing
Managed SBC-as-a-Service. The standard alternative to Microsoft Calling Plans for Kyrgyzstan users.
See Teams DR →A Kyrgyzstan SIP trunk with real +996 Kyrgyzstan DIDs, SCITC-compliant allocation, Dubai + Singapore ingress POPs, TLS:5061 with SRTP, every standard PBX integration. From $12.00/mo per DID plus per-minute usage, activation in 10-20 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 Kyrgyzstan SIP trunk is the same thing carrying +996 Kyrgyzstan DIDs allocated under SCITC.
DIDHub provides the trunk authentication and SIP transport; SCITC-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.
SCITC requires KYC documentation before any Kyrgyzstan DID can be allocated. Activation typically takes 10-20 business days. DIDHub handles the document submission and regulator coordination on your behalf.
What people typically use a Kyrgyzstan SIP trunk for:
Kyrgyzstan's regulator SCITC requires KYC for foreign customers. Activation 10-20 business days. SMS support is limited.
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 Kyrgyzstan number types over the SIP trunk:
| Code | Type | National dialing | International dialing | Mobile | From |
|---|---|---|---|---|---|
312, 3222 | Geographic | 312 XXXX XXXX | +996 312 XXXX XXXX | Yes | $12.00/mo + usage |
Toll-free | Toll-free | Toll-free XXXX XXXX | +996 Toll-free XXXX XXXX | Yes | $36.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 Kyrgyzstan-specific choices are the POP, the codec list, and the failover topology.
For the codec deep-dive, see voice codecs explained.
Outbound from a Kyrgyzstan-allocated DID to Kyrgyzstan destinations is allowed within approved use cases. The per-minute economics:
| Destination | Per-minute | Billing increment | Notes |
|---|---|---|---|
| Kyrgyzstan landline (geographic) | $0.10/min | 1+1 second | Standard use cases |
| Kyrgyzstan mobile | $0.20/min | 1+1 second | Standard use cases |
| International from Kyrgyzstan DID | Per destination rate | 1+1 second | See global rates |
Create a DIDHub account, supply your business details and the intended use case for Kyrgyzstan numbers.
We coordinate with SCITC and our in-region carrier; typical timeline 10-20 business days.
You pick the Kyrgyzstan number types you need and how many. Channel capacity allocated at the same time.
SIP URI (defaults to sip.didhub.io, terminating to Dubai), 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 Kyrgyzstan 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-kyrgyzstan] type=auth auth_type=userpass username=YOUR_DIDHUB_USERNAME password=YOUR_DIDHUB_PASSWORD [didhub-kyrgyzstan] type=aor contact=sip:sip.didhub.io:5061;transport=tls qualify_frequency=30 [didhub-kyrgyzstan] type=endpoint transport=transport-tls context=from-didhub disallow=all allow=g711a,g722,opus outbound_auth=didhub-kyrgyzstan aors=didhub-kyrgyzstan dtmf_mode=rfc4733 media_encryption=sdes direct_media=no
# 3CX -> SIP Trunks -> Add SIP Trunk -> Generic SIP Trunk Trunk name: DIDHub Kyrgyzstan 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: +996 ... (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 Kyrgyzstan 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 Dubai ingress for tight latency. Bind specific Kyrgyzstan DIDs to specific agents.
AI voice integrations →Per-trunk DNID auto-correct, SRV-based POP failover (Dubai primary / Singapore failover).
Kamailio →Per-extension digest registration; useful for distributed support teams routing Kyrgyzstan DIDs to remote agents.
Softphones →Live in 10-20 business days. Real Kyrgyzstan DIDs, no setup fee after KYC, no contract.
Four line items: per-DID monthly rental, per-minute inbound usage on every Kyrgyzstan DID (even landline geographic numbers carry an inbound MOU charge in Kyrgyzstan), channel capacity, and per-minute outbound. Setup is $0 once SCITC paperwork is approved.
| Type | From | Notes |
|---|---|---|
| Geographic (Kyrgyzstan city codes) | $12.00/mo + usage | Inbound per-minute applies; standard use cases |
| Non-geographic / national | $50.00/mo + usage | Subject to regulator allocation |
| Toll-free | $36.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 Kyrgyzstan number? Porting timeline is Limited.
For the full porting playbook (US/UK/EU + the global gotchas), see number porting explained.
Dubai is the recommended primary; Singapore is the standard failover. Both terminate to Kyrgyzstan via in-region carriers.
10-20 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 SCITC/carrier side.
G.711a / G.722 / Opus as the negotiation list, in that order. G.711a is the regional default for Kyrgyzstan 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 Kyrgyzstan 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 Kyrgyzstan port timeline is Limited. 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 10-20 business days. Real Kyrgyzstan DIDs, every standard PBX and AI-voice integration, no setup fee after KYC, no contract.