Connected themoment you buy
Every route comes with its interconnect: a SIP trunk with digest credentials or IP authorisation, issued with the purchase and ready for your softswitch or SBC.
In short
A bilateral interconnect usually means an agreement, an IP exchange and a round of test calls before the first minute flows.
Here the interconnect comes with the route. Buy it, and your trunk is provisioned with SIP credentials or your IPs authorised, ready for your softswitch or SBC to send traffic in minutes.
What you can do
- 01
SIP trunking
Outbound trunks, isolated per purchase.
- 02
IP and credential auth
Authorise source IPs or use SIP digest username and password.
- 03
Number provisioning
Buy DIDs and point them where your calls should land.
- 04
Codecs
G.711 a-law and u-law, and G.729.
- 05
Route checks
A route a buyer reports is re-tested automatically once the seller marks it fixed.
Getting connected
From purchase to first call in four steps
The settings below are the whole job. They sit on one page of your dashboard, and one copy button hands them to whoever runs your switch.
Let us recognise your switch
Whitelist your switch's public IP, as a single address or a whole range. Prefer credentials? Skip it and answer our SIP digest challenge with the username and password issued for each purchase.
Connect a route
Connecting a route on the marketplace issues its interconnect on the spot: a credential pair for that purchase, shown on its connection card and sent to you by email.
Point your trunk at your Switch IP
Create one trunk to your Switch IP on port 5060, over UDP or TCP, offering G.711a, G.711u or G.729. It is the only address you send calls to, whatever you buy.
Open your firewall, then test
Allow our media servers for SIP and RTP, run a test call from the dashboard, and read a plain-language result before real traffic flows.
One connection card
Everything your switch needs, on one card
Every purchase has a connection card with the address to send calls to, the port, the transport, the codecs and the credentials issued for that route, with the password hidden until you reveal it. Above it sits your Switch IP, the single address your whole account sends to. Handing over to an engineer? Copy settings puts the address, transport, codecs, digest realm and firewall rules into one plain-text block.
- Credentials are unique to each purchase and encrypted at rest.
- Rotate a purchase's credentials in one click. The new password is shown once and replaces the old pair.
- With a Switch plan, claim a dedicated Switch IP of your own at no extra charge, and nobody else sends to that address.
- Pause or cancel a purchase and its registration and live calls are dropped at once.
Send calls to
198.51.100.77:5060
This is your single address on the exchange. Point your switch or PBX at it, and we recognise your calls by it.
- SIP port
- 5060
- Transport
- UDP or TCP
- Codecs
- G.711a · G.711u · G.729
- Auth
- IP or digest
United Kingdom Mobile
Premium · Full CLI · $0.0124/min
SIP connection
- SIP user
- usr_7f3a91c2e4b8d605
- SIP password
- ••••••••••••••••
- Digest realm
- 198.51.100.77
- Algorithm
- MD5, no qop
Or skip the credentials: 203.0.113.0/28 is whitelisted on this account.
Authentication, your way
IP authentication or digest, whichever your switch speaks
Most carrier switches authenticate by address, so that is the default: whitelist an IP or a CIDR range and your calls are recognised the moment they arrive, with no registration and nothing to configure on the trunk. If your platform prefers digest, every purchase carries its own username and password, challenged with one fixed realm and MD5. Your trunk keeps presenting its own caller ID in the From header, because the credential only decides which account the call belongs to.
- Whitelist changes reach the edge in about 30 seconds.
- An address authenticates for one PacketExchange account only, so there is never any doubt whose call it is.
- One entry covers a single SBC or a whole range of gateways.
How we recognise your calls
IP authentication
Recommended. No registration: calls are recognised by the address they come from.
Username and password
Answer our SIP digest challenge with the credentials issued for each purchase.
Whitelisted addresses
3 entries
203.0.113.10
Core SBC
203.0.113.11
Standby SBC
198.51.100.0/28
Media gateway range
A single IP or a whole range both work. An address can be whitelisted on one PacketExchange account only.
Prove the path
Test the connection before the traffic does
From the dashboard you can check SIP reachability or place a real test call through the route you bought, to a number and caller ID you choose. The result comes back as a step-by-step trace and a verdict in plain English, and when something fails it names the SIP response, the hangup cause and the fix. The seller's address is withheld from every result you see, so the evidence is complete without exposing anyone's network.
- A failed call names its cause, such as a SIP 403 or a timeout, instead of a bare error.
- Test calls are rate-limited per purchase, which keeps them a diagnostic tool.
- Still failing after the seller says it is fixed? A route report re-tests their endpoint automatically.
- Route
- United Kingdom Mobile
- Test number
- +44 7700 900123
- Caller ID
- +44 7700 900456
Call connected end-to-end
The route answered a real call placed from our media addresses.
SIP response
200Call length
14sTest took
19sTrace
Route endpoint: the seller endpoint
Send SIP INVITE: from our media addresses to the seller endpoint
Endpoint response: SIP 200
Call result: answered and completed (14s)
The seller’s address is withheld from buyer test results.
Interconnect features
Built for the engineer who has to make it work
Standard SIP and SMPP, with the details a carrier network actually needs already handled.
Credentials per purchase
Every route you buy gets its own SIP username and password, encrypted at rest, shown on its connection card and rotatable at any time.
IP authentication with ranges
Whitelist a single address or a CIDR subnet. Calls are recognised by source IP first, with digest credentials as the fallback.
One address for everything
A single Switch IP and port carries every route you hold. With a Switch plan, claim a dedicated address at no extra charge, and it is yours alone.
Standard SIP, standard codecs
SIP on port 5060 over UDP or TCP, with G.711a, G.711u and G.729. The softswitch or SBC you run today connects as it is.
SMS over SMPP
Bind over TCP as a transceiver, transmitter or receiver with the system ID and password from your purchase. Send-time receipts (accepted or failed) can be posted to your callback URL.
Calls capped by your balance
As a call is set up over your trunk, its maximum length is worked out from your balance and the route rate, so a trunk cannot run up a debt.
Pause, resume or cancel
Pause a purchase and its registration and live calls drop; resume when you are ready. Cancelling tears the connection down for good.
Settings in one block
Copy settings produces a plain-text hand-off with your Switch IP, transport, codecs, digest details and every firewall rule, ready to paste into a ticket.
Why connect here
One interconnect, every route you buy
The expensive part of wholesale voice is rarely the rate. It is the time between agreeing a deal and carrying the first call. This takes it out.
Live minutes after you buy
No interconnect agreement and no IP exchange by email. Connect a route and its credentials exist immediately, and whitelist changes reach the edge in about 30 seconds.
New destinations, same trunk
Your trunk already reaches every route you buy. Connect another route and the next call to that destination uses it, with no change on your switch.
Isolated by design
Credentials are issued per purchase, so rotating or cancelling one never touches the others. Sellers never see your switch and you never see theirs: calls reach them from our media servers.
A trunk that cannot overspend
Traffic is prepaid, each call is capped at what your balance covers, and it is billed at hangup with a platform fee that never exceeds $0.001 per call.
Before and after
Interconnecting, without the project plan
- Paperwork
- The usual way: An interconnect agreement with every supplier
- On PacketExchangeThe interconnect comes with the route you connect
- Authorising your switch
- The usual way: IP addresses swapped by email, then configured on both sides
- On PacketExchangeWhitelist your IP once in the dashboard; it reaches the edge in about 30 seconds
- Credentials
- The usual way: Shared logins agreed by email and changed by ticket
- On PacketExchangeA credential pair per purchase, rotated from the dashboard in one click
- Adding a destination
- The usual way: A new supplier, a new trunk and a new round of testing
- On PacketExchangeConnect another route, and the trunk you already have carries it
- Testing
- The usual way: Test calls arranged with the supplier's operations team
- On PacketExchangeReachability checks and real test calls you run yourself, with any failure explained
- Handing over
- The usual way: Settings scattered across emails and attachments
- On PacketExchangeOne copyable block: address, transport, codecs, authentication and firewall rules
- Switching off
- The usual way: Asking the supplier to disable your account
- On PacketExchangePause or cancel a purchase, and its registration and live calls drop at once
| The usual way | On PacketExchange | |
|---|---|---|
| Paperwork | An interconnect agreement with every supplier | The interconnect comes with the route you connect |
| Authorising your switch | IP addresses swapped by email, then configured on both sides | Whitelist your IP once in the dashboard; it reaches the edge in about 30 seconds |
| Credentials | Shared logins agreed by email and changed by ticket | A credential pair per purchase, rotated from the dashboard in one click |
| Adding a destination | A new supplier, a new trunk and a new round of testing | Connect another route, and the trunk you already have carries it |
| Testing | Test calls arranged with the supplier's operations team | Reachability checks and real test calls you run yourself, with any failure explained |
| Handing over | Settings scattered across emails and attachments | One copyable block: address, transport, codecs, authentication and firewall rules |
| Switching off | Asking the supplier to disable your account | Pause or cancel a purchase, and its registration and live calls drop at once |
Built for
Who runs traffic on it
Live in minutes
Send your first call minutes after you buy.
Isolated credentials
Each purchase gets its own credentials, kept separate from the rest.
Works with your switch
Standard SIP, so the softswitch or SBC you run today connects as it is.
Pricing
The interconnect is free; you pay for traffic
- port, setup or monthly trunk fee
- $0
- platform fee on trunk traffic
- 0.5%
- fee cap per call
- $0.001
There is no port fee, no setup fee and no monthly charge for a trunk. Connecting a route issues its interconnect at no cost.
Traffic over your own trunk is billed per call at the route rate plus a 0.5% platform fee, capped at $0.001 per call, straight from your prepaid balance.
What you pay for
Trunk and credentials
Included with every purchase, for as long as the purchase is active.
Dedicated Switch IP
Included with a Switch plan, at no extra charge.
Platform fee on trunk traffic
0.5% of the carrier rate, never more than $0.001 per call.
Prepaid balance
Top up from $5 by card or crypto, or from $100 by bank wire.
Calls that never connect are not billed.
Questions engineers ask
Interconnecting, answered
The questions buyers ask before they start. Anything not covered here is in the help centre, or ask the team directly.
Does my switch have to register?
No. With IP authentication your calls are recognised by the address they arrive from, with no registration at all. Platforms that prefer digest can answer our challenge on each call with the credentials issued for the purchase.
Which transports and codecs are supported?
SIP on port 5060 over UDP or TCP, with G.711a, G.711u and G.729 on your trunk. Each marketplace listing also shows the codecs its route supports.
Can one trunk carry several routes?
Yes. Every route you buy is reachable over the same trunk, and for each call the exchange uses the route you hold that covers the number most specifically. To fail calls over between several routes automatically, send them through Smart Routing or run your own route plan on the Switch.
What does the seller see of my network?
Nothing that identifies you. Calls reach the seller from our media servers, which they authorise on their side, and your addresses and credentials are never passed on. It works the other way too: the seller's endpoint is never shown to you.
What should my firewall allow?
Every media server address listed in your dashboard, for SIP on port 5060 over UDP and TCP, and for RTP audio across the stated port range. Allow all of them: a partial list makes calls fail intermittently.
Why is every call being refused with a 403?
Usually one of three things: a zero balance, a number outside the prefixes of the routes you hold, or a purchase that is still under review.
My IP is already registered to another account. What now?
An address can authenticate for one PacketExchange account only. If the address is yours, contact support and it will be moved across.
Do SMS routes connect the same way?
SMS routes connect over SMPP instead: bind over TCP with the system ID and password from your purchase. SMPP binds always use credentials, so there is no IP whitelist for SMS.