Date: Thu, 28 Mar 2024 17:15:33 +0100 (CET) Message-ID: <78297999.3985.1711642533614@static.9.57.119.168.clients.your-server.de> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3984_27676294.1711642533602" ------=_Part_3984_27676294.1711642533602 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The requirements to properly operate PrivateGSM are very important due t= o the huge amount of mobile devices hardware/software availability and to t= he highly variable characteristics of mobile networks.
In order to operate it properly several operating requirements must be s= atisfied.
Network behavior and quality is crucial to provide a good quality servic= e. Some requirements are mandatory to operate the solution, other requireme= nts affects the service quality, ranging from =E2=80=9Cnot very good=E2=80= =9D to =E2=80=9Cimpossible to a secure call=E2=80=9D.
All these requirements are mandatory to operate the solution. Even one s= ingle requirement not satisfied makes impossible to run the solution.
There is no support for Proxy Server (being HTTP or SOCKS), so PrivateGS= M when operated within an Intranet must be able to communicate directly wit= h the PrivateServer
Mobile Devices must be equipped with a =E2=80=9Cdata=E2=80=9D plan that = allow full internet communications without IP/TCP/UDP filters to the server= and without protocol filters (Es: VoIP filters, like Vodafone carrier does= ).
The SIM card must be enabled to do full traffic without restriction (Es:= WAP or WEB only subscription are not usable).
In presence of protocol specific filters it=E2=80=99s required to enable= VoIP data option. Whenever this option it=E2=80=99s not available and VoIP= is blocked (Es: UAE), the protocol obfuscation of PrivateGSM typically let= it bypass but without guarantee on transport quality.
All the mobile devices must be equipped with a 2G/3G and/or WiFi connect= ion that=E2=80=99s not subject to high radio interference.
In presence of Radio Interference (due to high load of network, to other= equipment using same frequency or to distance/obstacles between mobile dev= ices and radio concentrator) the voice quality would not be good due to hig= h number of packet loss.
On critical network conditions it=E2=80=99s possible to finely tune Priv= ateGSM to operate like in a tactical environment, with reduced performance = but higher reliability.
PrivateGSM must keep an always on connection to the PrivateSer= ver with SIP/TLS over a TCP channel. It exchange keep-alive packet once eve= ry 10/20 minutes depending on the mobile platform.
The Firewall managing the connection of the server and of the client mus= t allow TCP idle connection of at least 21 minutes.
The typical timeout is 30-60 minutes, but in some environment this defau= lt value is lowered for security/performance reasons.
Whenever these requirements are satisfied, the users will perceive good = quality and will have nice feedback.
(QoS) requirements affects the perceived audio qu= ality during secure calls. When the following requirements are met audio wi= ll be clear, not distorted, continuous, without gaps and with almost not pe= rceivable delay:
It is important to have high Call Success Ratio (CSR).
Unstable network connection can lead to inability to dial/receive calls,= abruptly broken calls while speaking and impossibility to dial long calls.=
To provide good quality, is required to have a stability wi= ndow on both side of the call, caller and called. The stabili= ty window must cover the call duration and also the preceding 10 minutes:= p>
Pre-call stability window is particularly critical with iPhone devices, = which, currently, do not have a true multitasking OS and can adapt to netwo= rk change typically within 10 minutes window period.
The following configuration is needed to enable the update feature on th= e PrivateServer:
We suggest to keep the following concept:
but the product is known to run smoothly on slower ones.<= /p>
A minimum of 2GB of RAM for each PrivateServer (Consi= der quickly scaling up to 4GB of RAM)
A minimum of 50GB of storage for each PrivateServer (= consider raising up to 100GB in case of high number of users of a specific = server)
A minimum of one 100/1000 Mb/s NIC (or more NICs to s= etup the Network Segregation)
Almost one public IP Address, NATted to the server's = NIC or directly assigned to it
One public hostname (with correct DNS resolution)
=One SSL Certificate (accordingly with the hostname)= p>