Which IP addresses should I allow when using Communication APIs and SIP Trunking?
What IP addresses do I need to add to my firewall if I'm using Vonage Communication APIs and SIP Trunking?
- Communication APIs
- SIP Trunking
- IP Addresses
- Firewall Settings
If your platform restricts the inbound traffic it can receive using IP address ranges (typically via firewalls), you'll need to add the following IP addresses to your allow lists, depending on the API products you use. These IP ranges are used for receiving HTTP Callbacks (WebHooks), WebSocket Connections, SIP, and RTP/Media.
Vonage's API platform traffic will come from any of the IP addresses included in the referenced subnets.
Any function (HTTP Callbacks, WebHooks, WebSocket connections, SIP, and RTP/Media) could use IP addresses included in the following IP ranges. Please allow these ranges to enable seamless communication with Vonage APIs.
SIP IP Addresses
It is highly recommended that the above-mentioned “Primary Subnets” are allowed for SIP, to avoid you needing to make configuration changes in the future. If your SIP trunking platform cannot be configured to allow subnets, the following specific IP addresses should be allowed:
The following port ranges apply to the various types of traffic which you will exchange with Vonage APIs:
Type of Traffic
HTTP Callbacks (WebHooks)
As configured by customer (usually TCP ports 80 or 443)
As configured by customer (usually TCP port 443)
UDP on port 5060
UDP ports 10000 - 50000
Article is closed for comments.