# Reach Through - Conditions

- Flow Through Provisioning must be enabled to the MiVoice Business network elements and the MiCollab database must be synchronized with the MiVoice Business network element databases (that is, the Reconcile Wizard Welcome page must identify that the databases are in sync).

- Reach through is enabled from MiCollab USP to the MiVoice Business (MiVB) system administration tool using the MiVoice Business "system" administrator account. The MiVoice Business must have an administrator account configured in the User Authorization Profiles form with Login ID "system" and System Admin authorization set to "True".

- Reach Through is only supported using Internet Explorer (version 9.0 or later) or Mozilla Firefox (version 33 or later) browsers and you must have installed the browser with the Mitel Root Certificate. If you attempt to use any other type of browser to reach through from MiCollabto MiVoice Business , reach through will be blocked. Note that Internet Explorer is not supported in Compatibility Mode.

- Reach through from MiCollab USP to the MiVoice Business System Administration Tool and from the MiVoice Business System Administration Tool to MiCollab USP is in the context of the "admin" account for audit purposes.

- You must enable the SNMP Agents on every element in the SDS Admin Group.

- It is not necessary to log in when performing Reach Through from the MiCollab USP application to the MiVoice Business System Administration Tool or vice versa. A trust relationship is established based on the fact that you have already logged in to one of these administration tools.

- If the MiVoice Business system is running on an Multi-Instance platform, you must add the IP addresses of the MiVoice Business System Administration Tool and the IP address of the Multi-Instance manager to the MiCollab trusted network.

For example, if the IP address of the system administration tool is 10.46.26.100, you would need to add the following IP addresses to the MiCollab trusted network:

10.46.26.100

10.46.26.101.

A simpler option is to just add the subnet to the trusted network (that is, 10.46.26.1).