Supported Devices & System Requirements

TigerConnect works on both iOS and Android smartphones and tablets as well as popular web browsers. Compatible devices include iPhone, iPad, iPod Touch, and various Android devices. Below you will find a list of devices, web browsers and operating systems that are compatible with the TigerConnect application as well as the minimum system requirements for each.

The Desktop App is nearly identical to the Web Console in function, but provides additional features like notifications, icon badges, etc., and is more secure given there is no need to use a web browser. Additionally, for those users that wish to have priority messaging with TigerConnect, using the Desktop App allows for uncluttered access to TigerConnect in a standalone app.

Desktop App for Windows

Windows 7 (32/64-bit)

Windows 8/8.1 (32/64-bit)

Windows 10 (32/64-bit)

MSI (Server Installation – 32-bit only)

Supported Installs – Windows 7, 8, 8.1, 10

NOTE: Microsoft .NET Framework 4.5.2 or newer is required to install and use the Desktop App on Windows.

Desktop App for Mac

OS X 10.8 (Mountain Lion) and newer

To download the TigerConnect Desktop Application to your Windows or Mac, Click Here.

To ensure the integrity of TigerConnect message delivery, please implement the system requirements shown below.

AMAZON CDN

TigerConnect runs on the Amazon Web Services (AWS) elastic cloud infrastructure. Due to the nature of elastic scaling in response to dynamic throughput needs, the TigerText server application may communicate from any number of IP addresses. Clients with network firewalls in place must proactively allow communications to this range of IP addresses. As of September 29, 2015, there are over 10 million public IP addresses contained within the AWS infrastructure. For this reason, TigerConnect strongly discourages the use of an OSI Layer 3 (network) firewall to restrict access via whitelisted IP addresses, as this may unnecessarily open the customer systems to a wider attack surface. Rather, we encourage the use of OSI Layer 7 (application) firewall rules to restrict access and only allow HTTPS traffic to the *.tigertext.com and *.tigertext.me domains.

For LDAP Authentication Only

Please reference the following websites to enable and utilize Push Notifications over Wi-Fi connections for iOS and Android devices:

iOS Push Notifications

https://support.apple.com/kb/TS4264

Android Push Notifications

https://developer.android.com/google/gcm/gcm.html

Note: If your organization has a firewall that restricts the traffic to or from the Internet, you need to configure it to allow connectivity with GCM. The ports to open are: 5228, 5229, and 5230. GCM typically only uses 5228, but it sometimes uses 5229 and 5230. GCM doesn’t provide specific IPs, so you should allow your server to accept incoming connections from all IP addresses contained in the IP blocks listed in Google’s ASN of 15169.

WiFi Setup

Access Control – Users must have access to a TigerConnect approved Wi-Fi network that does not require re-authentication.

Mobile Wi-Fi Setup – All users must turn off “Ask to Join Networks” on their mobile devices.

Bypass – TigerConnect does not currently support the use of HTTP Proxies or Content Filters. Traffic to the TigerConnect HTTPS and XMPP service ports must bypass HTTP Proxies and Content Filters.

Note: This is only applicable to those who have opted for Client-Hosted archiving. This does not apply to TigerConnect-Hosted Archiving.

TLS must be enabled

Port 587 must be open

White-list the following:

54.208.189.22 (MTA Server IP address).

ttarchiver@tigermpn.com (all archive messages will originate from this email address)

Rate Limits/Rate Control

Email Security Gateways with strict mail flow settings may result in throttling of the TigerConnect MTA. This is common with organizations that generate large message volume. To ensure that you are able to receive all archived messages in a timely manner, remove any rate-limiting applied to TigerConnect Archiving messages.