Skip to content

Conversation

@vapi-tasker
Copy link
Contributor

@vapi-tasker vapi-tasker bot commented Jan 26, 2026

Description

  • Clarifies that the listed IP addresses (44.229.228.186/32, 44.238.177.138/32) are for SIP signaling only, not RTP media
  • Adds a new "RTP media" subsection explaining that RTP media traffic does not currently have a static set of IP addresses that can be whitelisted
  • Restructures the "Network requirements" section with clear subheadings for "SIP signaling" and "RTP media"

Before

The documentation stated:

"To allow SIP signaling and media between Vapi and your SIP provider, you must allowlist the following IP addresses"

This was misleading as it implied the IPs covered both signaling AND media.

After

The documentation now clearly separates:

  1. SIP signaling - static IPs that can be whitelisted
  2. RTP media - explicitly states no static IP list is currently available

Testing Steps

  • Run the app locally using fern docs dev or navigate to preview deployment
  • Ensure that the changed pages and code snippets work

Resolves VAP-11461

The documentation previously implied that the listed IP addresses
(44.229.228.186/32, 44.238.177.138/32) were for both SIP signaling
and RTP media traffic. This update clarifies that:

1. These IPs are for SIP signaling ONLY
2. RTP media traffic does not currently have a static set of IPs
   that can be whitelisted

This helps customers understand that they cannot whitelist specific
IPs for RTP media traffic at this time.

Resolves VAP-11461
@github-actions
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant