Skip to content

Wholesale SIP trunking for switches and IP-PBXs

Connect your softswitch, platform or IP-PBX to international voice over SIP, with capacity sized to the sessions you actually run.

SIP call setup through OroCarrierYour switch sends an INVITE to OroCarrier, which selects a route and forwards it to the destination network. Ringing and answer responses return the same way, then media flows end to end.Your switchSBC / softswitchOroCarrierroute selectionDestinationterminating networkINVITEINVITE100 Trying180 Ringing180 Ringing200 OK200 OKACKACKRTP media, end to end
Simplified SIP call setup across an OroCarrier interconnection. The route to the destination is chosen per call.

What a SIP trunk is

A SIP trunk is a logical voice connection between two IP networks. Instead of physical phone lines, calls are set up as SIP sessions: one side sends an INVITE, the other negotiates media, and the audio flows as RTP packets. Capacity is defined by how many sessions can run at once, not by how many copper pairs are installed.

For a business this replaces legacy lines into a PBX. For a carrier or VoIP provider it is the standard way to interconnect with another network for termination and origination.

IP-PBX integration

Most modern PBX platforms, including Asterisk and FreeSWITCH based systems, 3CX and other SIP-compliant PBXs, connect to a SIP trunk using either IP authentication or registration. During onboarding we confirm the method your platform supports, the number formats it sends and the codecs it prefers, then test inbound and outbound calls before going live.

Wholesale and business use

The same underlying technology serves two different buyers, and we configure it differently for each.

Wholesale trunks

Switch-to-switch interconnection for carriers and VoIP providers. IP-based authentication, higher session capacity, rate-deck billing and CDR exchange.

Business trunks

Connectivity for a single organisation's PBX or contact centre platform, combining outbound calling with inbound numbers on one trunk.

Interconnection options

Public internet SIP interconnection is standard. Other interconnection models can be discussed where traffic volume and both networks justify them.

Session-based capacity

SIP trunk capacity is expressed as concurrent sessions and calls per second. We size both to your real traffic profile rather than a fixed package, and adjust them as your volumes change.

Technical profile for a SIP trunk

These are the parameters recorded for each trunk and tested before activation.

  • Authentication: IP allowlisting or SIP registration
  • Transport: UDP, TCP or TLS, with SRTP where supported
  • Codecs: agreed list and order, typically G.711 a-law, G.711 u-law and G.729
  • DTMF: RFC 2833 / RFC 4733 telephone-events or SIP INFO
  • Session limits: concurrent calls and calls per second
  • Number normalisation: E.164 or national format, with prefix handling
  • Inbound routing to one or more destination endpoints

Who it is for

VoIP and hosted PBX providers
Upstream SIP connectivity for outbound and inbound calls across your customer base.
Carriers
Switch-to-switch SIP interconnection for exchanging wholesale traffic.
Businesses with an IP-PBX
Replace legacy lines and add international numbers on one trunk.
Contact centre platforms
Session capacity sized to agent counts and campaign peaks.

Frequently asked questions

Do you support SIP registration or only IP authentication?

Both methods are available. Wholesale interconnections normally use IP authentication. Registration suits PBXs on dynamic addresses.

How many concurrent calls can a trunk carry?

Capacity is agreed per trunk based on your traffic profile and can be adjusted as volumes grow.

Can one trunk handle both inbound and outbound calls?

Yes. A single trunk can carry outbound termination and inbound origination for your numbers.

Related services

Tell us where your traffic needs to go.

We reply with what we can route, how, and on what terms.

What to send us

  • Destinations and expected minutes
  • Route class: CLI or non-CLI
  • Your switch and signalling details
Talk to our team