...

You can decide how to distribute the services of

Brand
brand server

using the "network segregation" tools which you can access via the Services link in the main menu.

2.2.1 Services

The page is divided in three parts: the first one is actually about the network segregation itself:

...

• SQL/3306 - DataBase: that's the remote access to the DBMS (Data Base Management 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 signaling protocol, protected by TLS connection, for secure calls.
• SIP/UDP: VoIP 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

  Brand
  brand server

  in order to make the

  Brand
  brand client

  clients work fine:
  • Licence Cache 
  • Presence
  • Provisioning

Please note that the configuration shown in 

Xref
AnchorName application_matrix

 represents a likely production one as suggested in PSAM 2.9 Suggested network configuration

Info
The NICs on the appliance are automatically detected by Brand brand server and listed here.

...

Warning
The NIC are shown as applicable even if they are not configured, so please check your Network configuration before assigning or deverting a service from a NIC.

2.2.2 TLS Certificates

The second part is about certificate assign. When you divide your services amongst the NIC you are using them on different IPs as well. This implies you might choose different certificates each one related to each IP of the NIC your service is bound to. 

...

After you're done, just press the "Update" button.

2.2.3 Provisioning

The third part is about configuring the hostnames that are going to be used for provisioning service.

...

The HTTPS - Smartphone Web Services URI is the base URL for downloading both the

Brand
brand client

application and its configuration. This can be perceived as tricky but here's how it works. When we send an Automatic Activation SMS (cfr PSAM 2.7 Automatic Activation) what we really send is the URI for the configuration resource. This resource is MIME formatted so that the Mobile OS knows it needs

Brand
brand client

in order to manage it. Thus when the customer clicks on the URI in the SMS, the operating system opens the browser, contacts via HTTPS the server hostname we specified here and ultimately asks for the configuration resource. Then (via the MIME configuration) it asks

Brand
brand client

to handle it. Once you understood this mechanism it should be pretty straightforward what this field is about: it's the protocol://hostname part of the link that would be sent for any automatic activation.

...