Hostnames and IP addresses of online services for firewall configuration
April 2024
The following overview lists hostnames and IP addresses of the online services used by services such as UCConnect or ProCall Meetings.
This list can be used when special firewall settings with a positive list are needed so that UCServer or other clients can reach services on the internet.
Please note that IP addresses and DNS entries can change continuously.
Therefore, when creating positive lists in your network, you should work with wildcards.
It is best to create wildcard entries for *.ucconnect.de and *.meetings.procall.de and to allow all traffic to these hosts.
If you cannot work with the wildcard entries, note that you will need to update the rules in your firewall when entries change on this page. For this reason, the tables are date stamped.
The tables are provided with a date, which indicates the time of the last change.
The latest changes are also highlighted GREENin the tables and marked as "changed" in the column.
Default services
Status
Port number | Transport | Direction | Host | Purpose |
---|---|---|---|---|
443 | TLS | out | (*.)meetings.procall.de | ProCall Meetings services, such as the web front-end. |
20000-40000 | UDP | out | *.meetings.procall.de | Media to media server |
443 | UDP | out | *.meetings.procall.de | STUN requests to determine the public IP address of the client |
443 | UDP/TCP/TLS | out | *.meetings.procall.de | Media relay via TURN |
443 | TLS | out | *.ucconnect.de | Connection of the UCServer to UCConnect and login of the client browser via UCConnect at the UCServer The WebSocket protocol must be enabled. |
443/3478 | UDP/TCP | out | *.ucconnect.de | UCConnect services: STUN/TURN |
DNS entries and IP addresses for the wildcards
ProCall Meetings (*.meetings.procall.de)
Status
Role | DNS name | IP address | Ports/Log | changed |
---|---|---|---|---|
Web app | meetings.procall.de | 13.107.213.67 13.107.246.67 | 443/TCP | |
Load balancer | lb.meetings.procall.de | 135.125.218.1 | 443/TCP | |
Server components | ecs-1.meetings.procall.de | 51.89.117.254 | 443/TCP and 20000-40000/UDP | |
Server components | ecs-2.meetings.procall.de | 54.36.117.77 | 443/TCP and 20000-40000/UDP | |
Server components | ecs-3.meetings.procall.de | 54.37.77.136 | 443/TCP and 20000-40000/UDP | |
Server components | ecs-4.meetings.procall.de | 135.125.245.56 | 443/TCP and 20000-40000/UDP | |
Server components | ecs-5.meetings.procall.de | 51.89.5.126 | 443/TCP and 20000-40000/UDP | |
Server components | ecs-6.meetings.procall.de | 51.68.165.240 | 443/TCP and 20000-40000/UDP | |
Server components | ecs-7.meetings.procall.de | 51.89.4.156 | 443/TCP and 20000-40000/UDP | |
Server components | ecs-8.meetings.procall.de | 54.36.112.15 | 443/TCP and 20000-40000/UDP | |
Server components | ecs-10.meetings.procall.de | 51.89.117.180 | 443/TCP and 20000-40000/UDP | |
Server components | ecs-11.meetings.procall.de | 51.68.167.216 | 443/TCP and 20000-40000/UDP | |
Feedback server | logserver.meetings.procall.de | 51.210.184.110 | 443/TCP | |
STUN/TURN server | turn-1.meetings.procall.de | 54.36.117.196 | 443/UDP/TCP | |
STUN/TURN server | turn-2.meetings.procall.de | 135.125.244.210 | 443/UDP/TCP |
UCConnect (*.ucconnect.de)
Status
Role | URL DNS load balancer | IP address/hostname | Ports/Log | Changed | Comment |
---|---|---|---|---|---|
UCCore | uccontroller.ucconnect.de ucwebapi.ucconnect.de portal.ucconnect.de | uccore1
uccore2
uccore3
uccore4
| 443/TCP IP | Hosts the Controller, the Portal, the API, and the license server
| |
UCWeb | Not available | ucweb1
ucweb2
ucweb3
ucweb4
| 443/TCP IP | Hosts UCWeb
| |
UCPush | ucpush.ucconnect.de | ucpush1
ucpush2
ucpush3
| 443/TCP | Hosts UCPush
| |
UCTurn | Not available | ucturn3.ucconnect.de
ucturn4.ucconnect.de
| 3478/TCP/UDP 5349/TCP/UDP 80/TCP/UDP 443/TCP/UDP 49152-65535/TCP/UDP | Hosts a CoTurn Server
|
DNS records and IP addresses for Apple APNs and Google FCM
Apple APNs: https://support.apple.com/en-us/HT203609
Google FCM: https://firebase.google.com/docs/cloud-messaging/concept-options#messaging-ports-and-your-firewall
Optional: Microsoft Azure apps insights
See https://docs.microsoft.com/en-us/azure/azure-monitor/app/ip-addresses
Only required for ProCall meetings if you allow "Functional cookies": https://legal.estos.de/content/latest/datenschutz/datenschutzerklaerungen/datenschutzerklaerung-procall-meetings