This page explains the operating requirements for using ACALL applications.
ACALL applications include ACALL RECEPTION, ACALL MEETING, ACALL GATE, ACALL mobile, and ACALL WORK.
For supported OS, please refer to the "List of Supported OS and Versions of the Application."
OS with matching major versions
You can use the software, but we do not guarantee performance.
If a problem occurs, we will investigate and fix it.
OS with an older major version
In some cases, you may use the software, but we do not guarantee the performance.
If a problem occurs, we may ask you to upgrade your OS.
Unsupported latest version
Please refrain from upgrading to the latest version that is not yet supported, as we have not confirmed the operation of the application, and it may cause serious problems.
We will announce the support for new versions in the "List of Supported OS and Versions of the Application" and the news section on the service website.
Supported Versions of Apps
For the latest version of each application, please refer to the "List of Supported OS and Versions of Applications."
ACALL Applications guarantees that only the latest version of the application will work.
If a problem occurs with an older version, we will inform you to upgrade the application.
You can use the software if it is compatible with your OS, but we may not guarantee performance on some models.
If communication is restricted by a firewall or other means, please open the following ports.
3478 ~ 3497
16384 ~ 16387
16393 ~ 16402
・Apple Push Notification Service
・Push notifications from Apple require direct communication between Apple's servers and your iPad.
If some server (proxy server) is involved in the connection from the network where the iPad is installed to the Internet, it will not deliver the push notification.
If a proxy server is involved, open the APNS port and communicate directly with the opened port.
Reference（external）：If your Apple devices aren't getting Apple push notifications
・Firebase Cloud Messaging
Reference（external）：FCM ports and your firewall
Reference（externaml）：If you use FaceTime and iMessage behind a firewall
If you are restricting communication through a firewall, etc., please allow the following FQDNs.
- IP addresses are variable, so permission by IP address is not available.
Permission by FQDN is required.
- We will notify you in advance if the FQDN is to be added or changed.
|api.acall.jp:443 & api.acall.jp:80|
|admin.acall.jp:443 & admin.acall.jp:80|
Items to check for a stable Wi-Fi environment
All applications used on the iPad are in constant communication with the WorkstyleOS server via the Internet.
The following is a list of recommended environments to ensure a stable network environment.
About wired LAN connection
Wired LAN connection is not recommended for the following reasons.
- Not recommended by Apple Inc.
- FaceTime cannot be used.
If the following conditions are met, we recommend mobile data communication with a cellular model contract.
- The mobile network signal condition is good at the installation site.
- You are not using a printer or robot (no communication on the local network)
In any connection methods, be sure to check the network status by pinging to make sure that the network status is stable.
Use of iPad cases
Do not use any material (steel, aluminum, etc.) that may degrade the antenna performance of mobile communication, Wi-Fi, and Bluetooth for the case covering iPad.
・Please refer to 4.6 of the following document.
Accessory Design Guidelines for Apple Devices
Other Possible Failures
To ensure a stable Wi-Fi environment, be sure to consider and check the following possible obstacles.
- Signal attenuation caused by obstacles such as partitions
- Signal interference from microwave ovens, Bluetooth devices, etc.
- Crowding in similar signal bands
- Temporary signal outage due to DFS regulations
Checking the network status by pinging
Please confirm that the network communication status of the installed iPad is suitable using the following method.
- Install an application such as PingPlotter that can perform continuous pinging.
- Under the same conditions as in actual operation (location, case, surrounding Wi-Fi, etc.), continuously ping an external server via the Internet for at least two days, and confirm that the communication status is good.
The response time should be 100 ms or less at all times.
Since the network environment constantly changes due to the increase and decrease of users, surrounding signal conditions, etc., we recommend checking the network status at least once every six months.