Proxy Servers for SIP and VoIP

No — and if you arrived looking for one, better to know in the first sentence. We don't provide PBX software, call routing, SIP registrars, or anything that participates in the SIP protocol itself; Asterisk, FreePBX, Kamailio, and OpenSIPS are that layer, and configuring them is their documentation's job. What we sell is the network underneath: a dedicated proxy address that your already-working phone system sends its traffic through, so your SIP provider sees one fixed IP instead of whatever your office connection happens to be that day. The confusion is baked into the terminology — VoIP engineering used the words “SIP proxy” for a server role decades before commercial proxy services existed — but the practical test is simple: if your question is “how do I route calls between extensions,” you need PBX software; if it's “how do I get my PBX a stable public address my carrier will whitelist,” you're on the right page. The two layers coexist happily: plenty of our telephony customers run Asterisk behind our addresses.

Both, and the split matters because a working call needs each at different moments. TCP-side: every address answers on HTTP, HTTPS, SOCKS4, and SOCKS5, so SIP signaling over TCP or TLS (ports 5060/5061) relays without any special plan — that part works even on our base products. UDP-side: SIP-over-UDP signaling and, critically, the RTP audio streams require the UDP add-on, which enables full SOCKS5 UDP ASSOCIATE on every IP in the plan — 50% of the base price, from $5/month, selected in the checkout configurator. The buying rule: if your phone system signals over TCP and you only need the fixed address for whitelisting, a base dedicated IP might technically suffice, but audio will still be UDP, so in practice every real telephony deployment should take the add-on — a silent call with perfect signaling is the exact failure mode of skipping it. One honest exclusion: the add-on covers datacenter, dedicated, and ISP plans, not rotating proxies — which would be the wrong product for persistent registrations anyway.

Yes — that's the single most common reason telephony customers buy here, and the whole product is shaped for it. Every dedicated address is static for the life of your plan: you give it to your SIP trunk provider once, they add it to their IP-authentication list, and the trunk works without registration passwords from then on. The failure this replaces is familiar to anyone running IP-auth trunks from an office: consumer and even business connections re-issue addresses after outages and router restarts, and each change means dead trunks until someone updates the whitelist — usually discovered when the morning's first call fails. A proxy address has no such life events. Two practical notes: give the provider the proxy IP (that's your traffic's source as they see it), and whitelist your office's current IP in our Dashboard so your equipment authenticates to the proxy the same passwordless way — up to 5 IPs at no charge, changeable when the office moves. If the provider's security review is strict about address origin, the ISP variant gives you the same permanence on a consumer-registered range.