This page explains the operational requirements for the Acall Portal.

This applies to the following apps: 
Acall Mobile / Acall Reception / Acall Meeting / Acall Gate / Acall Desktop

Supported OS

Please refrain from updating to the latest version until we have completed our compatibility testing. 
For the current list of supported OS versions, please refer to Supported OS & app version list.

Supported Application Version

Supported Devices

Network Requirements

💡 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.

Allow by Port

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

FCM (*2)
- Firebase Cloud Messaging（Google Push Notification Service）
Reference (external):FCM ports and your firewall

FaceTime (*3)
Reference (external):If you use FaceTime and iMessage behind a firewall

💡 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.

Checklist for Ensuring a Stable Wi-Fi Environment

All applications used on the iPad communicate continuously with Acall servers over the Internet.

The following are the recommended environment and settings for ensuring a stable network connection.

Wired LAN Connections

Wired LAN connections are not recommended for the following reasons:

• Not recommended by Apple
• FaceTime cannot be used

If the following conditions apply, we recommend using mobile data communication via a cellular model contract:

• The installation location has good mobile network signal coverage
• No use of sticker printers or robots (i.e., no communication over the local network is required)

Regardless of the connection method used, be sure to perform a “network status check using PING” to confirm that the network environment is stable.

iPad Cases

Note
Please refer to section 4.6 of the following document:
Accessory Design Guidelines for Apple Devices

Other Potential Causes of Issues

To ensure stable Wi-Fi usage, be sure to consider and verify the following potential sources of interference:

• Signal attenuation caused by obstacles such as partitions
• Radio interference from devices such as microwave ovens and Bluetooth devices
• Signal congestion due to crowded/overlapping frequency bands
• Temporary signal interruption due to the impact of DFS regulations.

Checking network status using ping.

Please make sure to verify that the installed iPad has a stable network connection by following the steps below.

• Install an application capable of continuously running ping tests.
• Under the exact same conditions as actual operation (including location, case, surrounding Wi-Fi environment, etc.), continuously perform ping tests for at least two days to an external server over the internet, and confirm that the network connection remains stable.
• The response time should consistently remain below 100 ms.

Because network conditions constantly change due to factors such as the number of users and surrounding radio wave conditions, it is recommended that this network verification process be conducted at least once every six months.