Supported Devices & System Requirements

From Apple iOS & Android devices to Desktops,
learn what System Requirements you will need

 

LAST UPDATED: March 7, 2023

TigerConnect works on both iOS and Android smartphones and tablets as well as popular web browsers. Compatible devices include the 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.

  • System Requirements
    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 TigerConnect server application may communicate from a range of different IP addresses. Clients with network firewalls in place must proactively allow communications to this range of IP addresses. 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’s infrastructure 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, *.tigertext.me, *tigerconnect.com, *.med.tc domains.

    Customers may decide to use OSI Layer 3 firewalls, accepting the risk inherent in whitelisting large ranges of IP addresses that may not be used for TigerConnect, including without limitation the risk of allowing access to the customer’s private network by outside parties. The list of current AWS IP addresses may be consumed in JSON format from Amazon. See https://aws.amazon.com/blogs/aws/aws-ip-ranges-json for more information.

    Proxy or Firewall

    Ensure that the following sites are not blocked:

    NOTE: Append both ‘https://’ or ‘https:// to properly whitelist the below URLs.

    • *.env-tigerconnect-premium.kinsta.cloud
    • *.tigertext.com
    • *.tigertext.me
    • *.med.tc

    If a wildcard domain is not an option, below are the Fully Qualified Domain Names (FQDNs):

    • access.tigertext.com
    • api.tigerconnect.com
    • api.tigertext.me
    • app.tigerconnect.com
    • assets.tigerconnect.com
    • downloads.tigertext.com
    • home-static.tigertext.com
    • home.tigertext.com
    • idp.tigerconnect.com
    • login.tigerconnect.com
    • static.pro.tigertext.com
    • static.tigertext.me
    • tigerconnect.com
    • tigertext.me
    • d17gddqtitu3hh.cloudfront.net
    • d18oyzjkq5093g.cloudfront.net
    • d1j0wfatttsmrb.cloudfront.net
    • d1n6bomzxlt9xn.cloudfront.net
    • d1pja6kym1wocc.cloudfront.net
    • d20fxgql1qhj06.cloudfront.net
    • d2cfk2smgkkpz1.cloudfront.net
    • d3gw707yjo51bv.cloudfront.net
    • d3jad50r2eiw1v.cloudfront.net
    • d3q3w8yum1wsen.cloudfront.net
    • d4ksvvza57hut.cloudfront.net
    • db5362zp12d6h.cloudfront.net
    • Doypq9et62aku.cloudfront.net
    • dpiu6qal3wq6l.cloudfront.net

    NOTE: Similar to whitelisting all AWS IP addresses, it is the customer’s responsibility and risk should they choose to whitelist the entire *.cloudfront.net domain.

    Third-party domains:

    • api.mixpanel.com
    • m.onelink.me
    • sendgrid.net

    White Listing

    TigerConnect Service

    The following IP addresses and ports must be allowed for outgoing (egress) traffic from your network:
    Include Port: 443

    54.208.152.37 54.208.129.17 54.209.103.170
    52.8.55.232 52.8.75.252 52.9.196.218


    Email White-Listing

    Please ensure the following email addresses are whitelisted to ensure proper delivery of TigerConnect communications:

    • *@*.tigertext.me
    • sendgrid.net

    Aliases and reply-to email addresses for TigerConnect emails:

    • messages-noreply@bounce.tigertext.me
    • messages@tigertext.me
    • notification@tigertext.com
    • password-help@tigertext.com

    For LDAP Authentication Only

    The following IP address and ports must be allowed for users with LDAP Authentication:

    IPs Ports
    54.208.46.68 IIS – 443
    LDAPS – 636
    54.208.66.88
    54.208.83.219
    52.8.103.227
    52.8.175.5
    52.9.188.15

    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.
  • VoIP and TigerConnect Patient Engagement Video Requirements

    Note: This is only applicable to those who utilize TigerConnect’s VoIP Audio or Video Calling feature, or our TigerConnect Patient Engagement Patient Video Feature.

    • Port 443 must be open

    If Layer 7 filtering is used whitelist the following URLs:

    • global.vss.twilio.com
    • us1.vss.twilio.com
    • us2.vss.twilio.com
    • endpoint.twilio.com
    • mobile-endpoint.twilio.com
    • sdkgw.us1.twilio.com
    • ecs.us1.twilio.com

    If Layer 3 filtering is used whitelist the following IP Addresses ranges:

    • 168.86.128.0/18 with a UDP port range 10000-60000 

     

  • TigerConnect Web (Browser-Based) Requirements

    Note: TigerConnect provides support on the below browsers for the following URLs:

    • TigerConnect Web Messenger: https://login.tigerconnect.com
    • TigerConnect Physician Scheduling: https://schedule.tigerconnect.com

    Supported Browsers for TigerConnect Clinical Collaboration and TigerConnect Physician Scheduling include:

    • Mozilla Firefox
      • PC/Mac: Latest released version
    • Google Chrome
      • PC/Mac: Latest released version
    • Apple Safari
      • (MacOS only): Latest released version
    • Microsoft Edge
      • (Windows Only): Latest released version

    TigerConnect Web App

      • Latest TigerConnect web app version

     

  • System Requirements for TigerConnect Alarm Management & Event Notification

    Supported browsers include:

    • Windows – Latest released versions of Edge, Chrome
    • Mac – Latest released versions of Safari, Chrome

    Supported desktop and servers:

    • Desktop — Support Windows 10 Pro 64
    • Windows Server OS:
        • Windows Server 2019 x64 (recommended)
        • Windows Server 2016 x64 (minimum)
    • General Browser Setting:
        • Please verify you have enabled cookies

     

     

  • TigerConnect Desktop App Requirements

    The TigerConnect Clinical Collaboration Desktop App is available on the systems listed below and includes all the features you need to streamline your workflows.

    Hardware

    • The TigerConnect Desktop App installer is less than 250 MB and requires at least 750 MB of disk space for installation.

    Windows

    • Windows 10 (32/64-bit)
    • Windows 11 (64-bit)

    Mac

    • OS X – Three latest released versions (64-bit only)

    Linux

    • Debian – Three latest released versions
    • Ubuntu – Three latest released versions

    TigerConnect Desktop App

    • Latest TigerConnect Desktop app version

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

     

     

     

     

  • TigerConnect Mobile App Requirements

    Apple

    • iOS Operating System – 2 most recent major versions of iOS
    • WatchOS Operating System – 2 most recent major versions of watchOS
    • TigerConnect Clinical Collaboration Mobile App – Latest app version
    • TigerConnect Physician Scheduling Mobile App – Latest app version

    Android

    • Android Operating System – 5 most recent major versions of Android
    • TigerConnect Clinical Collaboration Mobile App – Latest app version
    • TigerConnect Physician Scheduling Mobile App – Latest app version

    Please note: Updates from TigerConnect app versions that are older than the two most recent versions may require users to log back in. TigerConnect Physician Scheduling app releases may require users to log back in.

  • TigerConnect Patient Engagement (Patient Device Requirements)

    Apple

    • Latest released browser version of Safari

    Android

    • Latest released browser versions of Chrome, Firefox, and Samsung Internet
  • TigerConnect PBX System Support

    PBX System Support

    On-Premise

      • Cisco Unified Communications Manager
      • Avaya Communications Manager/Aura
      • Mitel

    Cloud

      • RingCentral
      • Vonage
      • 8×8

    SBC Support

      • Oracle
      • Ribbon
      • AudioCodes
      • Sansay
  • Mobile (iOS and Android) Push Notification Requirements
    Please reference the following websites to enable and utilize Push Notifications over Wi-Fi connections for iOS and Android devices:

    iOS Push Notifications

    Android Push Notifications

    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 FCM. The ports to open are 5228, 5229, and 5230. FCM typically only uses 5228, but it sometimes uses 5229 and 5230. FCM 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.
  • Archiving (CLIENT-HOSTED ONLY)

    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:
      • MTA Server IP addresses:
        • 54.208.46.68
        • 54.208.66.88
        • 54.208.83.219
        • 52.8.103.227
        • 52.8.175.5
        • 52.9.188.15
      • tigermpn.com
      • 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 send a large volume of messages.
         To ensure that you are able to receive all archived messages in a timely manner, remove any rate-limiting applied to TigerConnect Archiving messages.
  • Other
    • We support the latest version of the TigerConnect SSO Connector.

Questions

For further questions, please contact your Implementation Specialist or email TigerConnect’s Client Care team at prosupport@tigerconnect.com.