This page explains the operational requirements for using Acall applications.

💡 NOTE
This page intends for the following applications.
Acall Mobile / Acall Reception / Acall Meeting / Acall Gate / Acall Desktop

 

Supported OS

OS	Operation Guaranteed
iOS / iPadOS	Latest - one previous major version
Android	Latest major version
MacOS	Latest - one previous major version
Windows	Latest - one previous major version

⚠️ Note
Please refrain from upgrading to the latest version until we have confirmed that it works.
The latest version will be announced in the [List of Supported OS and Versions of the Application].

 

 

Supported App Version

To ensure that you always use the latest version of Acall Applications, only the latest versions are guaranteed to work.

Please see [List of Supported OS and Versions of the Application] for the current latest version.

If you are using an older version of the application when we receive an inquiry about a problem, we will inform you to upgrade the version of the application.

 

 

Supported Models

iPad / iPhone

The applications can be used on basically any iOS device, but we do not guarantee the operation on some devices.

 

Android Tablet

We have confirmed the operation with the latest Android OS available for Galaxy Tab A9+ devices.

The applications can be used on basically any Android OS device, but we do not guarantee the operation on some devices.

 

 

Network requirements

Ports

If network communication is restricted by a firewall or other means, please allow the following ports.

Port	TCP/UDP	Service/Protocol	Application	Direction
443	TCP	SSL/HTTPS	All	Outbound
8883	TCP/UDP	TLS	Gate module	Outbound
60022	TCP	SSH	Gate module	Outbound
2197 5223	TCP	APNs（※１）	Acall Reception Acall Meeting Acall Mobile(iOS) Signage	Outbound
5228 5229 5230	TCP	FCM（※２）	Acall Reception Acall Meeting Acall Mobile(Android) Acall Desktop	Outbound
5223	TCP	FaceTime（※３）	Acall Reception （FaceTime）	Outbound
3478 ~ 3497 16384 ~ 16387 16393 ~ 16402	UDP	FaceTime（※３）	Acall Reception （FaceTime）	Outbound

APNs（※１）
・Apple Push Notification Service
・Push notifications from Apple require direct network communication between Apple's servers and your iPad.
　If some server (proxy server) is intervened 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 intervened, allow the APNs port and communicate directly with the opened port.
　Reference（external）：If your Apple devices aren't getting Apple push notifications

FCM（※２）
・Firebase Cloud Messaging
　Reference（external）：FCM ports and your firewall

FaceTime（※３）
　Reference（external）：If you use FaceTime and iMessage behind a firewall

 

FQDN

It is not necessary to specify FQDN when allowing communication over a port. If you need to have some restriction with FQDN or IP address from a security point of view. Please specify the following FQDN or IP address to allow the port.

NOTE
・Since IP addresses are subject to change, please permit　FQDN for those listed as FQDN.
・IP address is fixed, so please permit IP addresses for those listed as IP address.
・We will notify in advance if FQDN/IP address is added or changed.

FQDN:Port

portal.workstyleos.com:443

api.workstyleos.com:443

api.acall.jp:443

admin.acall.jp:443

acall-production-images.s3-ap-northeast-1.amazonaws.com:443

sentry.io:443

portal.bff.workstyleos.com:443

mobile.bff.workstyleos.com:443

desktop.bff.workstyleos.com:443

acallapi.workstyleos.com:443

publicapi-prod-spotimg.s3-ap-northeast-1.amazonaws.com:443

publicapi-prod-floormap.s3-ap-northeast-1.amazonaws.com:443

publicapi-prod-floormap-image.s3-ap-northeast-1.amazonaws.com:443

publicapi-prod-portal-themeimg.s3.ap-northeast-1.amazonaws.com:443

publicapi-prod-temporary.s3.ap-northeast-1.amazonaws.com:443

publicapi-prod-excluded-password-import-users.s3.ap-northeast-1.amazonaws.com:443

a3216i7p86gxbi-ats.iot.ap-northeast-1.amazonaws.com:8883

13.231.20.218:60022

signage.bff.workstyleos.com:443

*.googleapis.com:443

browser-intake-ap1-datadoghq.com:443

 

 

Check lists for a stable Wi-Fi environment

All applications used on the iPad are in constant communication with the Acall server via the Internet.

Introduce some recommended environments to ensure a stable network environment.

 

LAN cable connection

LAN cable connection is not recommended for the following reasons.

• Not recommended by Apple Inc.
• FaceTime cannot be used.

If the following conditions are met, would recommend mobile data communication with a cellular model contract.

• The mobile network 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 situation with PING to make sure that the network status is stable.

 

Use of iPad cases

As for case covering iPad, Do not use any material (steel, aluminum, etc.) that may degrade the antenna performance of mobile communication, Wi-Fi, and Bluetooth.

NOTE
・Please refer to 4.6 of the following document.
　Accessory Design Guidelines for Apple Devices

 

Other Possible Communication Failures

To ensure a stable Wi-Fi environment, be sure to consider and check the following possible communication failures.

• 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

 

Check the network situation by Ping

Please confirm that the network communication situation of the installed iPad is suitable with the following method.

• Install an application such as PingPlotter that Ping can work continuously.
• Under the exact same conditions as actual operation situation (location, case, Wi-Fi, etc.), try Ping an external server that is connect the Internet for at least two days, and confirm that the communication situation 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 would recommend to check the network situation at least once every six months.