Scribd
Upload
92 views1 page

Technical Prerequirements

The document outlines the technical prerequisites for connecting a device to the Secomea Remote Assistance system, including requiring an IP address that can reach a specific public IP to connect on ports 80, 443, or 11444 without any SSL inspection. It also notes an HTTP proxy could be used if it does not filter content or URLs.

Uploaded by

For Testing
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
92 views1 page

Technical Prerequirements

The document outlines the technical prerequisites for connecting a device to the Secomea Remote Assistance system, including requiring an IP address that can reach a specific public IP to connect on ports 80, 443, or 11444 without any SSL inspection. It also notes an HTTP proxy could be used if it does not filter content or URLs.

Uploaded by

For Testing
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Technical prerequisites for Remote Assistance system Secomea:

1. A private IP address, netmask, default gateway (optionally DNS).


The device doesn’t need any public IP.
2. The IP can be statically or automatically assigned via DHCP.
In case of assignment via DHCP, be sure that MAC based filter is not applied
3. The IP address should be able to reach this public IP:
gm.ima.it IP 81.208.52.93
* note : the device doesn’t need to access the whole internet, but only a single IP.
4. The device use needs to connect to 81.208.52.93 one of these ports:
443 (HTTPS), 80 (HTTP), 11444 with an SSL-like traffic.
One of these ports, should be opened on the firewall from inside to outside.
No SSL/TLS inspection systems are allowed between the device and the gm.ima.it server.

Note1: the device doesn’t need any ports opened from outside to inside on the Company
firewall.
Note2: the firewall must not apply any kind of SSL inspection on https traffic
5. Optionally an HTTP proxy can be used, the device can work with proxy for internet access.
The only constrain, is that the proxy must not apply any kind content filtering or any kind of
URL filtering, because the devices do HTTP tunnelling and encrypted traffic could be filtered by
mistake.
* note: since the connection is limited to only one, well known, IP address, it would be better (if
possible), to bypass the proxy and get a direct connection or set an exception for the single
gatemanager ip address.

Required parameters to configure the device:


Connection via physical cable:
 DHCP
 Static
IP Address
Subnet Mask
Default Gateway
DNS

Wi-Fi connection (only if the device model with integrated Wi-Fi is provided):
WiFi SSID
WiFi Key
 DHCP
 Static
IP Address
Subnet Mask
Default Gateway
DNS

If the connection to reach the server IMA must going through a proxy, this is datas that must be
specified:
Proxy
Port
User name
Password

Page 1/1 Last Document Update: 17/12/2020 11:17 Revision Document: 4


© Reproduction of this document by any means, in whole or in part, is prohibited without the authorization of IMA S.p.A.
www.ima.it

You might also like