Lyra Media Ranges & Firewalls
Lyra voice media traffic will come from a different IP range
What's changing
As part of the migration to the Lyra platform, voice media (RTP) traffic will no longer originate from the same IP address as the 2talk Plus SIP proxy. Media will instead come from a dedicated range of IP addresses.
If your firewall or access control list only allows traffic from the 2talk Plus SIP proxy IP, media traffic will be blocked once your account has migrated.
Who this affects
This change is expected to only affect SIP peering connections configured with strict media firewall rules.
Registrations should not be an issue, unless a customer's firewall only allows the SIP proxy IP.
2talk are not able to test this. We recommend checking your firewall configuration ahead of migration.
What you need to do
Update your firewall or access control lists to permit the new media IP range and ports, alongside your existing SIP proxy rules. This is only needed if you restrict RTP/media traffic to specific source IPs, such as the current SIP proxy address. If you don't restrict media by source IP, no changes should be necessary.
RTP/media range
|
Setting |
Value |
|---|---|
|
Source IP range |
27.111.14.0/24 |
|
Source Ports |
UDP 20000 to 50000 |
SIP transport and ports
|
Transport |
Port |
|---|---|
|
UDP |
5060 or 50600 |
|
TCP |
5060 or 50600 |
|
TLS (encrypted) |
5061 |