Define Deployment Configurations

Installing the Systems

MiCollab

Install MiCollab on the LAN:  

1. Install and configure the MSL operating system software, configuring only the "Local" (internal) adapter.

2. Enter the ARID and install the application software.

MBGs

Install MBG(s) in the DMZ:

1. Install and configure the MSL operating system software, configuring only the "Local" (internal) adapter.

2. Enter the ARID.

3. Configure the network profile:

   1. Under Applications, select MiVoice Border Gateway.

   2. Select System Configuration > Network Profiles.

   3. Select Server-only on network DMZ.

   4. Click Apply.

4. Configure the SIP options:

   1. Under System Configuration, select Settings.

   2. For SIP support the recommended setting is TLS. To support SIP resiliency, select TLS or TCP. Configure matching values in the MiCollab Mobile Client deployment profiles (below).  

   3. For Allowed URI names, enter the addresses that MBG should accept in SIP requests, in addition to its own. For example, if DNS is being used to resolve the MiCollab server on the LAN, enter its server name in FQDN format (mycompany.com). Configure matching values in the MiCollab Mobile Client deployment profiles (below).  

5. Configure the LAN server web proxy:

   1. Under Applications, select Remote proxy services.

   2. Select Add new LAN server proxy.

   3. Enter the WAN-side FQDN of MiCollab Client Deployment.

   4. Select MiCollab as the server type and Deployment Unit as the user interface.

   5. Enable the new server and click Save.

Configuring the Firewall

Firewall

1. Program firewall rules to allow the Client Deployment Service – which resides on your MiCollab Server – to reach the Redirect Servers (mcdepl01.easydeploy.net and mcdepl02.easydeploy.net) on port 443/tcp. This is required to send data to the Redirect Servers which help the clients to find the respective MiCollab server and which will also send the deployment emails to the end user’s email address.

2. If you are using MBG Teleworker service in the DMZ, consult the MiCollab Engineering Guidelines for a description of the port usage and firewall settings.

Clustering the MBGs

MiCollab and MBGs

Create a cluster:  

1. Access the MiCollab MBG and create a new cluster:

   1. Designate the MiCollab MBG as a master by clicking Create a cluster.

   2. Enter the IP address of the server you have selected to be the slave as the IP Address of peer node.

   3. Click Save.

2. Access the slave MBG and add it to the cluster:

   1. Designate the MBG as a slave by clicking Join.

   2. Enter the IP address of the master server as the IP Address of peer node.

   3. Click Save.

3. Synchronize the master/slave databases.

4. Set the weight of both the master and slave to 100.

5. If there are any other MBGs in the DMZ, add them as slaves and adjust their weight value to 100.

Subdivide the cluster into two logical zones:

1. Access the MiCollab MBG and add a new cluster zone called "DMZ". Rename the "Default" zone as "LAN" zone, add the current node to it, and set "DMZ" as the backup zone. (You can use other names if you wish.)

2. Access the MBGs in the DMZ, add them to the "DMZ" zone, and set the "LAN" as the backup zone.

3. Direct LAN-based devices to the a "LAN" zone and Internet-based devices to the "DMZ" zone.

Configuring MiCollab Client Deployment

MiCollab

Connect to the MBG(s):

1. Access MiCollab Client Deployment and create a connection to an MBG in the DMZ. First enter configuration details and then generate an authentication request.

2. Access the MBG in the DMZ, open Web Services, approve the authentication request and copy the verifier.

3. Access MiCollab Client Deployment and paste the verifier into the newly created MBG connection. The connection is validated with a token.

4. If there are any other MBGs in the DMZ, connect to them to the MiCollab Client Deployment as described above.

Create deployment profiles for the MBG(s):

1. Access the MiCollab Client Deployment and either modify the default profile (which is currently associated with the local MBG) or add a new profile.

2. Configure the profile, ensuring that the following settings are correct:

   • Use Teleworker - Select to enable Teleworker clients to register via the MBG instead of directly to the PBX.

   • MBG - Select the MBG connection in the DMZ that this profile will employ.  

   • Config download host - Specify where clients can download the configuration. To have clients connect using DNS, select MiCollab Server FQDN or Custom. In most cases, you will need to set this to Custom and enter the FQDN of the MBG configured in external DNS.  If multiple MBGs are providing SIP device resiliency, a single FQDN can be used to resolve to them. For example, use mycompany.com to resolve to mbg1.mycompany.com and mbg2.mycompany.com.

   • MBG SIP host - Specify on which interface that Teleworker clients must use to register via the MBG.To have clients connect using DNS, select MBG’s FQDN or Custom DNS SRV and enter the FQDN of the MBG configured in external DNS. If multiple MBGs are providing SIP device resiliency, a single FQDN can be used to resolve to them. For example, use mycompany.com to resolve to mbg1.mycompany.com and mbg2.mycompany.com.

   Note: If DNS is used to resolve a single FQDN to multiple hosts, you must enter this FQDN in the Allowed URI names field in the MBG configuration settings.

   • SIP transport protocol -  Recommended setting is TLS. To support SIP resiliency, select TLS or TCP. This setting must match the SIP support setting on the MBG.

3. If there are any other MBGs in the DMZ, create deployment profiles for them.

Assign deployment profiles to users:

1. Access MiCollab Client Deployment and either modify an existing user or add a new user.

2. Select the deployment profile that this user account will employ.

Add Web Server Certificate

MBGs and MiCollab

You are required to purchase a Third-Party SSL Certificate and install it on the MBG(s) in the DMZ and the MiCollab on the LAN.  See MiCollab in LAN Mode with MBGs in DMZ.

Installing the Systems

MiCollab

Install MiCollab on the network edge:  

1. Install and configure the MSL operating system software, configuring only the "Local" (internal) adapter.

2. Enter the ARID and install the application software.

MBGs

Install MBG(s) on the network edge:

1. Install and configure the MSL operating system software, configuring the "Local" (internal) and "WAN" (external) adapters.

2. Enter the ARID.

3. Configure the network profile:

   1. Under Applications, select MiVoice Border Gateway.

   2. Select System Configuration > Network Profiles.

   3. Select Server-gateway on network edge.

   4. Click Apply.

4. Configure the SIP options:

   1. Under System Configuration, select Settings.

   2. For SIP support the recommended setting is TLS. To support SIP resiliency, select TLS or TCP. Configure matching values in the MiCollab Mobile Client deployment profiles (below).

   3. For Allowed URI names, enter the addresses that MBG should accept in SIP requests, in addition to its own. For example, if DNS is being used to resolve the MiCollab server on the LAN, enter its server name in FQDN format (mycompany.com). Configure matching values in the MiCollab Mobile Client deployment profiles (below).  

5. Configure the LAN server web proxy:

   1. Under Applications, select Remote proxy services.

   2. Select Add new LAN server proxy.

   3. Enter the WAN-side FQDN of the MiCollab Client Deployment.

   4. Select MiCollab as the server type and Deployment Unit as the user interface.

   5. Enable the new server and click Save.

6. Enable MiCollab Client connector:

   1. Under Service configuration, select Application integration.

   2. Under Mobile Client, select Mobile Client connector enabled and enter the Mobile Client hostname or server IP address.  

Configuring the Firewall

Firewall

If you are using MBG Teleworker service on the network edge, consult the MiCollab Engineering Guidelines for a description of the port usage and firewall settings.

Clustering the MBGs

MiCollab and MBGs

Create a cluster:

1. Access the MiCollab MBG and create a new cluster:

   1. Designate the MiCollab MBG as a master by clicking Create a cluster.

   2. Enter the IP address of the server you have selected to be the slave as the IP Address of peer node.

   3. Click Save.

2. Access the slave MBG and add it to the cluster:

   1. Designate the MBG as a slave by clicking Join.

   2. Enter the IP address of the master server as the IP Address of peer node.

   3. Click Save.

3. Synchronize the master/slave databases.

4. Set the weight of both the master and slave to 100.

5. If there are any other MBGs on the network edge, add them as slaves and adjust their weight value to 100.

Subdivide the cluster into two logical zones:

1. Access the MiCollab MBG and add a new cluster zone called "Edge". Rename the "Default" zone as "LAN" zone, add the current node to it, and set "Edge" as the backup zone.  (You can use other names if you wish.)

2. Access the MBGs on the Edge, add them to the "Edge" zone, and set the "LAN" as the backup zone.

3. Direct LAN-based devices to the a "LAN" zone and Internet-based devices to the "Edge" zone.

Configuring MiCollab Client Deployment

MiCollab

Connect to the MBG(s):

1. Access MiCollab Client Deployment and create a connection to an MBG on the network edge. First enter configuration details and then generate an authentication request.

2. Access the MBG on the network edge, open Web Services, approve the authentication request and copy the verifier.

3. Access MiCollab Client Deployment and paste the verifier into the newly created MBG connection. The connection is validated with a token.

4. If there are any other MBGs on the network edge, connect to them to MiCollab Client Deployment as described above.

Create deployment profiles for the MBG(s):

1. Access MiCollab Client Deployment and either modify the default profile (which is currently associated with the local MBG) or add a new profile.

2. Configure the profile, ensuring that the following settings are correct:

   • Use Teleworker - Select to enable Teleworker clients to register via the MBG instead of directly to the PBX.

   • MBG - Select the MBG connection on the network edge that this profile will employ.  

   • Config download host - Specify where clients can download the configuration. To have clients connect using DNS, select MiCollab Server FQDN or Custom. In most cases, you will need to set this to Custom and enter the FQDN of the MBG configured in external DNS.  If multiple MBGs are providing SIP device resiliency, a single FQDN can be used to resolve to them. For example, use mycompany.com to resolve to mbg1.mycompany.com and mbg2.mycompany.com..

   • MBG SIP host - Specify on which interface that Teleworker clients must use to register via the MBG. To have clients connect directly to the MBG, select MBG’s External Interface and enter the address of the MBG's public interface on the enterprise firewall. To have clients connect using DNS, select MBG’s FQDN or Custom DNS SRV and enter the FQDN of the MBG configured in external DNS. If multiple MBGs are providing SIP device resiliency, a single FQDN can be used to resolve to them. For example, use mycompany.com to resolve to mbg1.mycompany.com and mbg2.mycompany.com.

   Note: If DNS is used to resolve a single FQDN to multiple hosts, you must enter this FQDN in the Allowed URI names field in the MBG configuration settings.

   • SIP transport protocol -   Recommended setting is TLS. To support SIP resiliency, select TLS or TCP. This setting must match the SIP support setting on the MBG.

3. If there are any other MBGs on the network edge, create deployment profiles for them.

Assign deployment profiles to users:

1. Access MiCollab Client Deployment and either modify an existing user or add a new user.

2. Select the deployment profile that this user account will employ.

Add Web Server Certificate

MBGs and MiCollab

You are required to purchase a Third-Party SSL Certificate and install it on the MBG(s) on the network edge and the MiCollab on the LAN. See MiCollab Server in LAN Mode.