Looking to get full media server IP list for whitelisting inside an SBC. Seems we get a few different AWS IPs being used for call media in the 200 OK response e.g. 34.219.112.196 35.165.205.132 etc.

Looking into it

Yeah, it is because we have load balancer in place due to why we can't even provide the exact IP address which you can whitelist it atm.

But wouldn't those LBs* have at the very least ranges they use?

According to the documentation, the only officially supported IPs for SIP signaling and media with Vapi are: - 44.229.228.186/32 - 44.238.177.138/32 These are the IPs you should whitelist for SIP traffic. There is no broader AWS IP range or full media server IP list provided in the documentation, and due to load balancers, a static list of all possible media server IPs is not available. Could you clarify if you specifically need to whitelist for SIP signaling/media only, or are you looking for a broader AWS IP range for all possible media servers? Source: - [Vapi SIP Trunking Documentation Network Requirements](https://docs.vapi.ai/advanced/sip/sip-trunk#network-requirements)

From some testing it seems like these IPs are mainly used: 34.219.112.196 35.165.205.132 35.92.126.90 Vastly different ranges which is...interesting, would recommend allocating a range to your LB where possible, or make the addresses queryable via DNS or something along those lines

Currently, the only officially supported IPs for SIP signaling and media with Vapi are: -

44.229.228.186/32

-

44.238.177.138/32

There is no broader AWS IP range or dynamic list available for whitelisting, and the documentation does not address additional media server IPs observed in practice. For now, it's recommended to whitelist only these two IPs as per the official guidance. [Source: Vapi SIP Trunking Documentation Network Requirements](https://docs.vapi.ai/advanced/sip/sip-trunk#network-requirements) Source: - [Vapi SIP Trunking Documentation Network Requirements](https://docs.vapi.ai/advanced/sip/sip-trunk#network-requirements)

Yeah, we are in-talk about it cause multiple customers asked for it. But, right now we haven't allocated a IP range to it.

@Ben Asking VAPI to provide you with a static list of IP addresses for media services is redundant, as VAPI needs to scale up and down as required - meaning that their media addresses will always by dynamic and change during the day (maybe even during a single call). The correct approach in your case would be to install a media gateway in a DMZ network, and make sure to "trombone" all your media traffic through it.

To whitelist Vapi SIP signaling and media, use only the officially supported IPs:

plaintext
44.229.228.186/32
44.238.177.138/32

No broader static range or DNS-based solution is available at this time. Please monitor the [official documentation](https://docs.vapi.ai/advanced/sip/sip-trunk#network-requirements) for updates. Source: - [Vapi SIP Trunking Documentation Network Requirements](https://docs.vapi.ai/advanced/sip/sip-trunk#network-requirements)

@Sahil Can someone PLEASE ease the @Vapi Support Bot in some manner - it keeps on repeating the same answers in the same questions, causing tickets to appear as "updated" or "answered" when infact, there is no new relevant information in it.

At this time, **Vapi only officially supports whitelisting the following IPs for SIP signaling and media**:

plaintext
44.229.228.186/32
44.238.177.138/32

There is no broader AWS range or DNS-based solution available for media server IPs. Please monitor the [official documentation](https://docs.vapi.ai/advanced/sip/sip-trunk#network-requirements) for any future updates or changes to this policy. Source: - [Vapi SIP Trunking Documentation Network Requirements](https://docs.vapi.ai/advanced/sip/sip-trunk#network-requirements)

Will pass the feedback to duckie team.