Getting Started · 2 min read

Inbound DIDs — do we offer them?

Where inbound numbers fit (and don't) in the non-cli.site product, with alternatives.

Short answer

non-cli.site is outbound termination only. We do not sell inbound DIDs.

Why

Inbound numbers come with regulatory overhead — local presence, address verification, number portability — that conflicts with our no-KYC, instant-activation model. We focus on the outbound side and do it well.

What to do instead

  • Use a retail DID provider (Twilio, Telnyx, DIDWW) for inbound and forward to your softswitch.
  • Configure your PBX to use the retail provider for inbound and non-cli.site for outbound. This is the standard architecture for cost optimization — pay retail for inbound where it's a small bill, save on outbound where the volume is.

Routing example

; Inbound from retail DID provider → local extension
[from-twilio]
exten => _X.,1,Dial(PJSIP/100)

; Outbound via non-cli.site
[from-internal]
exten => _X.,1,Dial(PJSIP/${EXTEN}@noncli-trunk)

Related in Getting Started

Still stuck?

Open a ticket