> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://myoperator.crisp.help/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# What MyOperator IP addresses should I whitelist?

## Quick answer

Always pull the live IP list from Admin Panel → Network Access → Allow-list IPs. Then create inbound rules for:

* TCP 443 (API & webhooks)
* UDP/TCP 5060-5063 or 5061/TLS (SIP)
* UDP 16384-32768 (RTP media)

Use the rule examples below for Linux iptables/ufw, Windows Firewall, AWS, Azure, and GCP.

---

## When should I use this guide?

Follow these steps if:

* your PBX/SBC sits behind a firewall,
* your server receives MyOperator webhooks, or
* You restrict inbound traffic in AWS/Azure/GCP.

---

## 1 — Services & ports (at a glance)

| Service | Direction | Protocol & Ports | Notes |
| --- | --- | --- | --- |
| API & Webhooks | MyOperator ➜ Your server | TCP 443 | In-call control & event POSTs |
| SIP signalling | MyOperator ➜ PBX | UDP/TCP 5060-5063 (5061 TLS) | Disable SIP-ALG |
| RTP media | MyOperator ➜ PBX | UDP 16384-32768 | Symmetric RTP recommended |

---

## 2 — Prerequisites

* Firewall or cloud admin rights.
* Maintenance window if production voice is at risk.
* Latest IP list (next section).

---

## 3 — Get the current IP list

1. Sign in → Admin Panel → Network Access → Allow-list IPs.
2. Copy all IPv4 and IPv6 addresses shown.
3. Export as shell variables for the examples below:

```
IP_API1=203.0.113.10 # replace with real
IP_SIP1=203.0.113.20
IP_RTP1=203.0.113.30
```

4. Repeat after any region change or status-page notice.

---

## 5 — Workflow

![](https://content.api.getguru.com/files/view/6e961a5c-6446-46e6-b1c3-d33c1b6ae460)

*Alt-text: “MyOperator sends API, SIP, and RTP traffic that passes through your firewall to PBX & servers.”*

---

## 6 — Confirm it worked

| Test | Expected result | Where to look |
| --- | --- | --- |
| Webhook test | HTTP 200 in ≤ 5 s | Admin Panel → Network Access → Send Test |
| SIP register | 200 OK / OPTIONS from MyOperator | PBX trace |
| Live call | Two-way audio, < 2s start | Call ID + packet capture |

---

## 7 — Edge cases & best practices

* Disable SIP ALG; it rewrites headers and breaks RTP.
* Preserve UDP 16384-32768; enable symmetric RTP.
* Allow all published IPs (HA).
* Duplicate rules for IPv6 if your network uses it.
* Review IP list quarterly or after status-page alerts.

---

## 8 — Troubleshooting matrix

| Symptom | Likely cause | Fix |
| --- | --- | --- |
| API time-outs | Wrong/old IPs | Refresh list; re-apply TCP 443 rules |
| One-way audio | RTP blocked | Open 16384-32768 UDP; symmetric RTP |
| Random call drops | Only one MO IP allowed | Add the entire published range |
| SIP register flaps | SIP ALG | Disable ALG; switch to TLS 5061 |
| IPv6 calls fail | No v6 rules | Mirror allow-list for IPv6 |

Escalate: Collect Call IDs, packet captures, and IP list → Help → Chat with Support.

---

Keywords: MyOperator IP whitelist, SIP RTP firewall, webhook allow-list, AWS security group MyOperator, network access