...
Sangoma Phone Desktop Client Service (Secure Port Required)
This port number will need to be given to users, because they will need to include it with the host address during login
This port can be set through Admin→System Admin→Port Management
UCP (Secure Port Recommended for remote users)
This is required to use the Forgot Password option from the login screen. The UCP login page will be loaded in a web browser, which has a Forgot Password tool. The same credentials are used for UCP and the Sangoma Connect Desktop client.
Ports 6000-6199 - These should not need to be forwarded since they will only be used internally
This range of ports should not be used for any other options set by the admin. This is a range we are reserving the right to use for internal purposes.
If an admin set things up to use one of these ports before we started enforcing things, it is recommended they choose a different port
https://wiki.freepbx.org/display/PPS/Ports + used + on + your + PBX
Firewall Settings
For some environments where Sangoma Phone will be used from remote networks, the zone accessibility settings must be set properly for the Sangoma Phone Desktop Client Service port.
These settings are found in Connectivity->Firewall->Services→Extra Services. By default, the service is open only to the Local zone, enable for other zones only as needed.
Asterisk SIP Settings
...
Set the PBX's host address in Admin→SangomaConnect→Settings
To avoid potential issues, the following is advised:
Client users will use this same Address value, along with the PBX's "Sangoma Phone Desktop Client Service" Secure Port when logging in. With that in mind, this Address will need to be something that is resolvable from the client user's desktop.
A proper Fully Qualified Domain Name is recommended
A Secure Port must be enabled for "Sangoma Phone Desktop Client Service" in Admin→System Admin→Port Management
This address should also match what is used as the PBX's HTTPS SSL cert's Common Name
In most cases, this address should be what is found in Admin→System Admin→Hostname
While an FQDN and valid SSL certificate is recommended, an IP address can be set here as long as a self-signed certificate with the IP address as its common name is used during the HTTPS setup when enabling Secure Ports in Port Management.
Generating a self-signed certificate with an IP for its common name can be done through Admin→Certificate Management
To do this, you will likely need to remove all existing Self-signed certificates by clicking the Delete Self-Signed CA button. This is because a typical install will have added a Default Self-Signed certificate which is based on a local hostname. Adding new self-signed certs while that exists will not work as expected. After deleting the default cert, choose the option to Generate Self-Signed Certificate, and set the pbx ip address as the hostname.
This method can lead to issues if not all client users will be logging in with the same IP address set here. For example, some situations might have users logging in using the PBX's external IP vs internal IP.
...
Each Sangoma Phone user will need to be based on an existing PJSip extension.
In User Manager, the Sangoma Phone users will need to have "Enable Sangoma Phone Login" option enabled in the SangomaConnect tab of their user settings.
Language Settings
The desktop client's Login screen will always be in English.
After logging in successfully, the client will be translated if the User's Language Setting matches a language supported by the client. Otherwise, it will default to English.
The User's Language Setting can be set through Admin->User Management, by editing a User or Group.
The current list of supported languages include:
English (United States)
English (United Kingdom)
French (France)
German (Germany)
Italian (Italy)
Spanish (Spain)
...