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.
| Hostname | Public IP | Region | Role | Status |
|---|---|---|---|---|
| eu-west-1-sbc-1.siperb.com | 52.50.165.204 | eu-west-1 (Ireland) | Trunk-facing | Live |
| eu-west-1-sbc-2.siperb.com | 63.33.254.52 | eu-west-1 (Ireland) | Trunk-facing | Live |
| us-east-1-sbc-4.siperb.com | 3.228.202.78 | us-east-1 (N. Virginia) | Trunk-facing | Live |
Ports & protocols — SBC / trunk
| Service | Protocol | Port | Direction | Notes |
|---|---|---|---|---|
| SIP signalling | UDP + TCP | 5060 | Bidirectional (to/from SBC IP) | Default trunk signalling |
| SIP over TLS | TCP / TLS | 5061 | Bidirectional | Recommended 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) | UDP | 30000–40000 | Bidirectional | Audio. Shares the same public IP as signalling. |
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.
| Hostname | Service | Protocol | Port | Direction |
|---|---|---|---|---|
| www.siperb.com | Web app / portal | HTTPS | 443 | Outbound from client |
| api.siperb.com | API | HTTPS | 443 | Outbound from client |
| ws-eu-west-1.siperb.com | SIP over WebSocket — wss://ws-eu-west-1.siperb.com/ws (registration & calls) | WSS / TLS | 443 | Outbound from client |
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)
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.
