By default, PrivateServer's services runs on all network interfaces. Actual availability depends on embedded firewall, which can be configured.
You can decide how to distribute the services of PrivateServer using the "network segregation" tools which you can access via the Services link in the main menu.
...
- SQL/3306 - DataBase: that's the remote access to the DBE DBMS (Data Base EngineManagement System), useful for exporting views and access data used by the appliance
- HTTPS - Management Console: here you have the very same web administrative console you are actually using
- SSH - Secure Shell: the well known secure text console for remote administration. This is useful for extraordinary management tasks.
- SIP/TLS: VoIP service (signaling part) over signaling protocol, protected by TLS connection. Long story short: Secure VoIP., for secure calls.
- SIP/UDP: dsfafas part of the VoIP service used to connect the PrivateServer appliance to another PBXVoIP signaling protocol, without protection, useful to connect company and/or legacy PBX that do not support secure calls.
- TCP/5666: by activating this service it becomes possible to reach the Nagios monitoring service on the appliance.
- HTTPS/SmartPhone Web Service: Services provided by the PrivateServer in order to make the PrivateGSM clients work fine:
- Licence Cache
- Presence
- Provisioning
Please note that the configuration shown in
| Xref | ||
|---|---|---|
|
...