Microsoft Teams Direct Routing
Managed SBC-as-a-Service. The standard alternative to Microsoft Calling Plans for Japan users.
See Teams DR →
Japan · MIC
SIP Trunk in Japan — Tokyo, Osaka or Kyoto Inbound + Outbound
A Japan SIP trunk with real +81 Japan DIDs, MIC-compliant allocation, Tokyo + Singapore ingress POPs, TLS:5061 with SRTP, every standard PBX integration. From $4.00/mo per DID plus per-minute usage, activation in 1-5 business days after KYC.
Real Japan DIDs allocated through licensed carriers
TLS + SRTP end-to-end
5–200 channel scale per trunk
1. What a SIP trunk in Japan 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 Japan SIP trunk is the same thing carrying +81 Japan DIDs allocated under MIC.
DIDHub provides the trunk authentication and SIP transport; MIC-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. Japan regulation: MIC, KYC, compliance
MIC requires KYC documentation before any Japan DID can be allocated. Activation typically takes 1-5 business days. DIDHub handles the document submission and regulator coordination on your behalf.
What people typically use a Japan SIP trunk for:
- APAC market entry, Tokyo 03 numbers signal trust to Japanese B2B.
- Lightweight 050 VoIP, easier KYC, common for SaaS targeting Japan.
- Toll-free 0120, free for Japanese callers, standard for customer service.
- Navi-Dial 0570, national rate for service hotlines.
Japan's regulator MIC requires KYC, proof of identity and a Japanese address (residential, business, or registered agent). Geographic numbers have stricter requirements; the 050 IP-phone range is easier and faster to activate. DIDHub shows the documents required clearly before purchase.
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 Japan number types over the SIP trunk:
| Code | Type | National dialing | International dialing | Mobile | From |
|---|---|---|---|---|---|
03, 06, 075, 092 … | Geographic | 03 XXXX XXXX | +81 3 XXXX XXXX | Yes | $4.00/mo + usage |
050 | IP phone (VoIP) | 050 XXXX XXXX | +81 50 XXXX XXXX | Yes | $3.00/mo + usage |
0570 | Navi-Dial (national) | 0570 XXXX XXXX | +81 570 XXXX XXXX | Yes | $10.00/mo + usage |
0120 | Toll-free | 0120 XXXX XXXX | +81 120 XXXX XXXX | Yes | $20.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 Japan
The technical surface of the trunk is standardised; the Japan-specific choices are the POP, the codec list, and the failover topology.
Ingress POPs
- Tokyo (primary), lowest in-region latency to Japan endpoints.
- Singapore (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 APAC default.
- G.722, wideband HD voice on capable endpoints.
- Opus, for AI voice agents and IP-native softphones.
- G.729, available on request.
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 a US/Canada construct that doesn't exist in APAC. Trust signals come through national regulator registration and operator-side caller-ID validation.
5. Outbound calling from your Japan trunk
Outbound from a Japan-allocated DID to Japan destinations is allowed within approved use cases. The per-minute economics:
| Destination | Per-minute | Billing increment | Notes |
|---|---|---|---|
| Japan landline (geographic) | $0.05/min | 1+1 second | Standard use cases |
| Japan mobile | $0.10/min | 1+1 second | Standard use cases |
| International from Japan 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 Japan numbers.
MIC compliance review
We coordinate with MIC and our in-region carrier; typical timeline 1-5 business days.
Allocate DIDs & channel capacity
You pick the Japan 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 Tokyo), 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 Japan 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-japan] type=auth auth_type=userpass username=YOUR_DIDHUB_USERNAME password=YOUR_DIDHUB_PASSWORD [didhub-japan] type=aor contact=sip:sip.didhub.io:5061;transport=tls qualify_frequency=30 [didhub-japan] type=endpoint transport=transport-tls context=from-didhub disallow=all allow=g711a,g722,opus outbound_auth=didhub-japan aors=didhub-japan 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 Japan 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: +81 ... (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 Tokyo ingress for tight latency. Bind specific Japan DIDs to specific agents.
AI voice integrations →Kamailio / OpenSIPS
Per-trunk DNID auto-correct, SRV-based POP failover (Tokyo primary / Singapore failover).
Kamailio →Softphones (Zoiper, Bria, Linphone)
Per-extension digest registration; useful for distributed support teams routing Japan DIDs to remote agents.
Softphones →Start your Japan SIP trunk today
Live in 1-5 business days. Real Japan DIDs, no setup fee after KYC, no contract.
8. Pricing
Four line items: per-DID monthly rental, per-minute inbound usage on every Japan DID (even landline geographic numbers carry an inbound MOU charge in Japan), channel capacity, and per-minute outbound. Setup is $0 once MIC paperwork is approved.
Per-DID monthly
| Type | From | Notes |
|---|---|---|
| Geographic (Japan city codes) | $4.00/mo + usage | Inbound per-minute applies; standard use cases |
| Non-geographic / national | $30.00/mo + usage | Subject to regulator allocation |
| Toll-free | $20.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 Japan number
Existing Japan number? Porting timeline is 2-6 weeks.
- Typical port time: 2-6 weeks
- Required documents: phone bill + LOA + ID + proof of address (MIC 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 Japan SIP trunk?
Tokyo is the recommended primary; Singapore is the standard failover. Both terminate to Japan via in-region carriers.
How long does activation take for a Japan SIP trunk?
1-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 MIC/carrier side.
What codecs should I configure for a Japan SIP trunk?
G.711a / G.722 / Opus as the negotiation list, in that order. G.711a is the regional default for Japan interop.
Can I use my Japan SIP trunk with Microsoft Teams?
Yes, via Microsoft Teams Direct Routing through DIDHub's managed SBC. See Teams Direct Routing.
Can I use my Japan SIP trunk with AI voice agents (Vapi, Retell, ElevenLabs)?
Yes, BYOC SIP trunk works with every major AI voice platform. Bind specific Japan DIDs to specific agents; outbound CLI must match an allocated DID.
How many concurrent calls can one Japan 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 Japan?
N/A (regional construct). Trust signals come instead through national regulator registration and operator-side caller-ID validation.
Can I port my existing Japan number to a DIDHub SIP trunk?
Yes. Typical Japan port timeline is 2-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 Japan SIP trunk today
Live in 1-5 business days. Real Japan DIDs, every standard PBX and AI-voice integration, no setup fee after KYC, no contract.