- Connectivity Requirements (Wired and Wi-Fi)
- Speed and Uplink Requirements
- IP Ranges and Domains for Allowlisting
Connectivity Requirements (Wired and Wi-Fi)
MealSuite Touch is a cloud-based SaaS application with Android™, iOS®, and Windows® app equivalents.
MealSuite Point of Sale (POS) is a cloud-based SaaS application with Android™ and iOS® app equivalents.
Touch and POS work on both a wired connection and a Wi-Fi connection, with a wired connection being recommended to reduce the risk of service quality disruption.
Wired Connection Recommended
Although the Touch and POS applications transmit very little data, a stable and low latency connection provided by a wired connection allows activities such as POS transactions, table-side orders and kitchen order fulfilment to be performed in real-time, ensuring a good user experience.
Conduct Ping Test for a Wi-Fi Connection
It is understood that a wired internet connection may not be possible, and as such a Wi-Fi connection will be required. If so, it is recommended that your IT team audit the locations where the devices will be installed by conducting a 'ping' test as follows:
- Connect a laptop or similar device to your network.
- Turn on any nearby microwaves or convective ovens.
- Initiate a ping test to app.mealsuite.com.
- The ping test will show if there are losses or reduction of quality in the connection.
WebSocket Protocol
Both applications utilize the WebSocket protocol to maintain continuous communication tunnels to the MealSuite datacenters.
Note that firewalls with web proxies or filtering may impact the stability of the WebSocket connection. The MealSuite IP network ranges (below) should be allowlisted from any traffic filtering.
Speed and Uplink Requirements
The network should have a firewall with a minimum of two different internet provider uplinks through alternate mediums, such as fiber optic and coaxial, to ensure connectivity if one medium is cut.
The firewall should automatically failover to the backup connection without manual intervention to ensure the continuous operation of the system.
When possible, a quality of service (QoS) rule should applied to the MealSuite IP ranges to guarantee a minimum 1mbps up/down with a routing priority above any guest, public or general internet browsing.
IP Ranges and Domains for Allowlisting
MealSuite uses a variety of open-source frameworks such as JQuery, Angular and Google Fonts in addition to AWS S3 for image storage. If your network security policies are highly restrictive and do not permit HTTPS web traffic via port 443, please advise the MealSuite team.
IP Ranges
The MealSuite IP ranges (in form of CIDRs) are as follows:
- 192.235.96.0/25
- 198.35.62.0/25
Domains - MealSuite Products
All MealSuite products use the following domains:
Domain | Remote Ports | Purpose |
*.mealsuite.com | 443 |
Core services |
*.amazonaws.com | 443 | Images |
cdn.lr-ingest.io lr-in-prod.com *.lr-in-prod.com *.lr-in.com |
443 | Replaying of user sessions for Support (i.e., error reporting) |
rum.browser-intake-datadoghq.com session-replay.browser-intake-datadoghq.com agent-intake.logs.datadoghq.com agent-http-intake.logs.datadoghq.com |
443 | Error tracking & session replay |
manage.eloview.com | 443 | MDM (mobile device management) |
io.eloview.com | 443 | Device definition |
*.scalefusion.com | 443 |
Android OS updates |
db5xszokwvv76.cloudfront.net | 443 |
Android OS updates |
*.pushy.me | 443 |
Android OS updates |
*.pushy.io | 443 |
Android OS updates |
Domains and IP Addresses - PIN Pads Integrated with Stripe
All the domains and IP addresses listed on https://stripe.com/docs/ips must be allowlisted within your firewall settings, in addition to non-Stripe domains listed below.
Domains | Ports | IP Addresses |
*.stripe.com |
|
See https://stripe.com/docs/ips for latest list. |
*.stripecdn.com | ||
m.stripe.network | ||
api.emms.bbpos.com | ||
*.terminal-events.stripe.com | ||
pool.ntp.org | ||
time.android.com | ||
*.[random-string].device.stripe-terminal-local-reader.net |
Domains - PIN Pads Integrated with Datacap TranCloud™ Server
If using PIN pads integrated with Datacap Trancloud™ Server:
Domains | Source Ports | Remote Ports |
dms1.dsipscs.com | 1024 through 5000 | 443 |
dms2.dsipscs.com | ||
iptran1.dsipscs.com | ||
iptran2.dsipscs.com | ||
*.hearltlandportico.com (if using Heartland as payment processor)
|
||
trancloud.dsipscs.com | 1024 through 5000 | 5080 |
sslprod.secureexchange.net | 1024 through 5000 | 22345, 22346 |
Domains - PIN Pads Integrated with DC Direct™
Domains | Source Ports | Remote Ports |
prod1.netepayhosted.dcap.com prod2.netepayhosted.dcap.com |
1024 thru 5000 |
9000 |
trancloud.dsipscs.com |
443 |
|
rbaloader1.dsipscs.com rbaloader2.dsipscs.com lfc.dcap.com |
||
webroute.dcap.com |
||
temterminalsnar02.icloud.ingenico.com temterminalsnar01.preprod.icloud.ingenico.com |
7002 |
DC Direct™ IP Port Requirements by Processor
Processor* |
Products |
URL(s) |
Source Port |
Remote Port |
Nashville (FDMS) |
NETePay |
vxn.datawire.net vxn1.datawire.net vxn2.datawire.net vxn3.datawire.net |
1024 thru 5000 |
443 |
*If you do not see your processor here, please contact support@mealsuite.com.
IP Port Requirements for Datacap Products: https://datacapsystems.com/ip-port-requirements
Domain - Temperature Sensor for Cold Storage Location
If using temperature sensors for cold storage location:
Remote Port |
3000 |