Network Infrastructure & Firewall Whitelisting

This page lists the public Siperb endpoints — IP addresses, hostnames and ports — that you may need to allow through a firewall so your PBX, SIP trunk or Siperb client can reach Siperb and audio works in both directions. If your calls register but have no audio, or registration never completes, a firewall or carrier that is silently dropping our traffic is the most common cause.

There are two groups of endpoints, and they are whitelisted differently:

  • SBC / trunk endpoints — for connecting a PBX or SIP trunk. These have static IP addresses, so you whitelist them by IP.
  • Client / web platform endpoints — for the Siperb web, desktop and mobile apps. These sit behind AWS load balancers with changing IP addresses, so you whitelist them by hostname, not IP.

SBC / trunk endpoints (whitelist by IP)

Each Session Border Controller (SBC) handles SIP signalling and RTP media for trunk and PBX connections. Whitelist all the SBC IP addresses listed below. These are stable, dedicated IPs that do not change — and in the rare event one ever needs to, you will be notified well in advance.

HostnamePublic IPRegionRoleStatus
eu-west-1-sbc-1.siperb.com52.50.165.204eu-west-1 (Ireland)Trunk-facingLive
eu-west-1-sbc-2.siperb.com63.33.254.52eu-west-1 (Ireland)Trunk-facingLive
us-east-1-sbc-4.siperb.com3.228.202.78us-east-1 (N. Virginia)Trunk-facingLive

Note: You never need to allow any internal Siperb addresses — only the public IPs listed above. RTP media uses the same public IP as signalling on each SBC.

Ports & protocols — SBC / trunk

ServiceProtocolPortDirectionNotes
SIP signallingUDP + TCP5060Bidirectional (to/from SBC IP)Default trunk signalling
SIP over TLSTCP / TLS5061BidirectionalRecommended where a SIP ALG mangles 5060 (e.g. FortiGate). The certificate SAN is the SBC hostname, so connect by hostname, not IP.
RTP media (rtpengine)UDP30000–40000BidirectionalAudio. Shares the same public IP as signalling.

Note: While signalling is often proxied through the SBC (Proxy Mode), the SBC does not have to carry the media or perform transcoding. If your endpoint supports DTLS-SRTP natively, media can flow directly without the SBC relaying or transcoding it — in which case the RTP range above is not used for that call.

Client / web platform endpoints (whitelist by hostname)

If you restrict outbound traffic for the devices running the Siperb web, desktop or mobile apps, allow HTTPS/WSS (TCP 443) to the hostnames below. These front-ends sit behind AWS load balancers, so their IP addresses change — allow them by hostname/domain rather than by IP.

HostnameServiceProtocolPortDirection
www.siperb.comWeb app / portalHTTPS443Outbound from client
api.siperb.comAPIHTTPS443Outbound from client
ws-eu-west-1.siperb.comSIP over WebSocket — wss://ws-eu-west-1.siperb.com/ws (registration & calls)WSS / TLS443Outbound from client

Note: For WebRTC NAT traversal, Siperb clients use Google’s public STUN/TURN by default — no extra firewall rules are needed for most networks. You can also configure your own dedicated or alternative TURN server.

Firewall whitelisting — worked example

To allow a PBX or SIP trunk to reach Siperb, create firewall rules that permit traffic both outbound to and inbound from each SBC public IP on:

  • UDP + TCP 5060 — SIP signalling
  • TCP 5061 — SIP over TLS (connect by hostname)
  • UDP 30000–40000 — RTP audio (bidirectional, same IP as signalling)

Important: If your REGISTER sits unanswered — stuck on “Request Sent”, or timing out with REGISTER_TIMEOUT — the usual cause is a firewall or carrier (ITSP) that is silently dropping packets from Siperb’s SBC source IP. Ask your ITSP to confirm our SBC IPs are allowed as a source, not just as a destination.

Regions & latency

Siperb’s SBCs are hosted on AWS. Current regions are eu-west-1 (Ireland) and us-east-1 (N. Virginia). Choosing an anchor nearer to your PBX reduces media latency (one-way delay). Note that distance adds latency but does not by itself cause packet loss — closer is not “less loss”.

IP changes & failover

The SBC IP addresses listed above are static and committed — they are not expected to change. If we ever need to change or add an SBC IP, we will notify affected customers well in advance so you can update your firewall before any cut-over.

Still having trouble?

If you have whitelisted the IPs and ports above and calls still fail, see Connections for registration and trunk setup, or contact Siperb Support with your SBC hostname and a SIP trace.