Contents
This page explains the operational requirements for the Acall Portal.
Supported OS
Acall Portal supports the following OS.
- WindowsOS
- MacOS
Supported Browser
Acall Portal supports the following web browsers.
Recommended Browser
- Google Chrome latest version (Recommended Browser)
Supported Browser
- Microsoft Edge (Chromium/Mac) latest version
- Safari latest version
NOTE Supported browsers guarantee functional operation; however, issues such as minor display inconsistencies may not be addressed if they do not affect functionality.
Please consider using a recommended browser.
NOTE
Browser notifications will be sent from Acall Portal, so we recommend allowing notification settings.
Network Requirements
All communications are outbound only. No inbound firewall ports need to be opened.
💡 Note - This page lists only the network communications required by the Acall apps themselves. - Please separately allow any communications required for the device and/or other software installed on the device (e.g., MDM), such as internet connectivity checks, vendor account authentication, and OS updates, according to the device manufacturer’s requirements. - If these communications are not allowed, they may affect the operation of the Acall apps.
For configuring allow rules on firewalls and similar systems, please refer to either “Allow by Port” or “Allow by FQDN,” depending on your security policy. (You do not need to implement both.)
Allow by Port
If communications are restricted by firewalls or similar systems, please open the following ports.
| Protocol | Port | Service | Application | Note |
| TCP | 443 | HTTPS | All | |
| TCP | 443 | WSS | Acall Meeting (v2.0.12 or later) | Firewall / If you control traffic at the protocol level on your proxy, you must also allow WebSocket communications (Upgrade: websocket). |
| TCP / UDP | 8883 | TLS | Gate module | |
| TCP | 60022 | SSH | Gate module | |
| TCP | 2197 / 5223 | APNs (*1) | Acall Reception / Acall Gate / Acall Meeting (iOS, v2.0.11 or earlier) / Acall Mobile (iOS) / Signage | |
| TCP | 5228 / 5229 / 5230 | FCM (*2) | Acall Reception / Acall Gate / Acall Meeting (iOS, v2.0.11 or earlier) / Acall Mobile / Acall Desktop | |
| TCP | 5223 | FaceTime (*3) | Acall Reception (FaceTime) | |
| UDP | 3478〜3497 / 16384〜16387 / 16393〜16402 | FaceTime (*3) | Acall Reception (FaceTime) |
APNs (*1) - APNs (Apple Push Notification service) - For Apple push notifications, the iPad must be able to communicate directly with Apple’s servers. If a proxy server (or any other intermediary server) is used when connecting from the iPad’s network to the internet, push notifications may not be delivered. If a proxy is in place, please open the APNs ports and configure the network so that traffic over those opened ports bypasses the proxy and connects directly. Reference (external): If your Apple devices aren't getting Apple push notifications
FaceTime (*3) Reference (external):If you use FaceTime and iMessage behind a firewall
Allow by FQDN
Specifying an FQDN is not required when opening ports; however, if your security policy requires restrictions based on FQDNs or IP addresses, please allow the ports by specifying the following FQDNs or IP addresses.
💡 NOTE - For entries listed as FQDNs, the IP addresses are subject to change; therefore, please configure access permissions using the FQDNs. - For entries listed as IP addresses, the addresses are fixed; therefore, please configure access permissions using the IP addresses. = Any additions or changes to the FQDNs or IP addresses will be announced in advance.
| FQDN / IP | Protocol | Port | Service | Note |
| portal.workstyleos.com | TCP | 443 | HTTPS | |
| api.workstyleos.com | TCP | 443 | HTTPS | |
| api.acall.jp | TCP | 443 | HTTPS | |
| admin.acall.jp | TCP | 443 | HTTPS | |
| acall-production-images.s3-ap-northeast-1.amazonaws.com | TCP | 443 | HTTPS | |
| sentry.io | TCP | 443 | HTTPS | |
| portal.bff.workstyleos.com | TCP | 443 | HTTPS | |
| mobile.bff.workstyleos.com | TCP | 443 | HTTPS | |
| desktop.bff.workstyleos.com | TCP | 443 | HTTPS | |
| acallapi.workstyleos.com | TCP | 443 | HTTPS | |
| publicapi-prod-spotimg.s3-ap-northeast-1.amazonaws.com | TCP | 443 | HTTPS | |
| publicapi-prod-floormap.s3-ap-northeast-1.amazonaws.com | TCP | 443 | HTTPS | |
| publicapi-prod-floormap-image.s3-ap-northeast-1.amazonaws.com | TCP | 443 | HTTPS | |
| publicapi-prod-portal-themeimg.s3.ap-northeast-1.amazonaws.com | TCP | 443 | HTTPS | |
| publicapi-prod-temporary.s3.ap-northeast-1.amazonaws.com | TCP | 443 | HTTPS | |
| publicapi-prod-excluded-password-import-users.s3.ap-northeast-1.amazonaws.com | TCP | 443 | HTTPS | |
| publicapi-prod-import-spots.s3.ap-northeast-1.amazonaws.com | TCP | 443 | HTTPS | |
| publicapi-prod-export-workspace-reservations.s3.ap-northeast-1.amazonaws.com | TCP | 443 | HTTPS | |
| a3216i7p86gxbi-ats.iot.ap-northeast-1.amazonaws.com | TCP・UDP | 8883 | TLS | |
| 13.231.20.218 | TCP | 60022 | SSH | |
| signage.bff.workstyleos.com | TCP | 443 | HTTPS | |
| *.googleapis.com | TCP | 443 | HTTPS | |
| browser-intake-ap1-datadoghq.com | TCP | 443 | HTTPS | |
| *.appsync-realtime-api.ap-northeast-1.amazonaws.com | TCP | 443 | HTTPS and WSS | Required for Acall Meeting (v2.0.12 or later). If protocol-level control is enforced by a firewall or proxy, communication using WebSocket (Upgrade: websocket) must also be allowed. |
Comments
0 comments
Article is closed for comments.