What MyOperator IP addresses should I whitelist?

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.


📕Table of Contents

  1. Services & ports
  2. Prerequisites
  3. Watch the video walkthrough
  4. Get the current IP list
  5. Workflow
  6. Confirm it worked
  7. Edge cases & best practices
  8. Troubleshooting matrix
  9. Related Articles

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

[Back to top ⬆️]


2 — Prerequisites

• Firewall or cloud admin rights.

• Maintenance window if production voice is at risk.

• Latest IP list (next section).

[Back to top ⬆️]


Watch the video walkthrough


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

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

[Back to top ⬆️]


5 — Workflow

image.png

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

[Back to top ⬆️]


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 MO

PBX trace

Live call

Two-way audio, < 2s start

Call ID + packet capture

[Back to top ⬆️]


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.

[Back to top ⬆️]


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.

[Back to top ⬆️]


9 — Related Articles

• How do I monitor future MyOperator IP changes via API?

• Which SIP/RTP ports must be opened when using SRTP?

• How can I bulk-update AWS Security Groups when IPs change?

[Back to top ⬆️]


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