Snon-cli.site
Sign inGet a trunk
← Knowledge base
Integration · 2 min read

Dialing format — when to use E.164, plus, or 00

Why some destinations fail with a leading + and how to normalize numbers before sending to the trunk.

The rule

non-cli.site trunks accept E.164 without the +. So a UK mobile is 447712345678, not +447712345678 and not 00447712345678.

Why it matters

  • Calls sent with a leading + get rejected as 484 Address Incomplete on some upstreams.
  • Calls with 00 international prefix get double-prefixed and routed to nowhere.
  • Calls without a country code may match a US prefix and be billed accordingly. Bad surprise.

Normalization in Asterisk

exten => _+X.,1,Goto(outbound,${EXTEN:1},1)
exten => _00X.,1,Goto(outbound,${EXTEN:2},1)
exten => _X.,1,Dial(PJSIP/${EXTEN}@noncli-trunk,60)

Test before bulk

Always call one number manually before kicking off a dialer campaign. A misconfigured prefix at 30 CPS burns balance fast.

Related in Integration

How to integrate a SIP trunk with Asterisk
Working pjsip.conf and extensions.conf for non-cli.site trunks, with non-CLI and CLI examples.
How to integrate a SIP trunk with FreeSWITCH
Gateway XML and dialplan for non-cli.site termination with optional CLI override.
Supported codecs, ports, and IP authentication
Network requirements for connecting to sip.non-cli.site and which codecs we negotiate.

Still stuck?

Open a ticket