Specifications

MBG Engineering Guidelines, Release 8.0

3 Common Requirements

This section provides general guidance common to all types of deployments and all services. Please read it

carefully.

3.1 Supported ICP Versions

At least one of the following compatible ICP products is required to use Mitel Border Gateway:

• Mitel Communications Director (MCD) release 4.0 or later. (Includes vMCD, MICD, 3300 platforms.)

• Broadview Networks silhouette release 4.0.0.3 or later. (Contact Broadview for the required MBG

version.)

• Mitel 5000 CP. (SIP Trunking only for release 5, add MiNet Teleworker with release 6)

3.2 Administrative Access

MBG provides a web-based management GUI for normal administration, log access, etc. This service can be

accessed with any of the following supported web browsers:

• Mozilla Firefox 3.0 or higher

• Microsoft Internet Explorer 6.0 or higher

Although not officially supported, the following browsers are tested occasionally and should also work:

• Google Chrome

• Apple Safari

• any browser using the Mozilla Gecko engine or the Apple WebKit engine

Note: the MBG GUI requires a browser that supports JavaScript. The built-in MSL text-mode browser does not

support JavaScript and cannot be used to manage MBG.

Some troubleshooting or advanced configuration requires command-line access. SSH is the only supported

mechanism to reach the MSL command line remotely. On Microsoft Windows, Mitel recommends the use of

PuTTY (a small, free SSH client). OpenSSH is included with Apple Mac OS X (open Terminal and type “ssh”),

and is included with or available for most flavors of Unix.

3.3 Firewalls (DMZ deployment)

MBG can be deployed into the DMZ of most third-party firewalls. However, a compatible firewall must have

certain characteristics.

1. The firewall must provide at least three interfaces: external network, internal network, and DMZ.

2. The firewall must provide static 1:1 NAT between an externally-visible address and the DMZ address of

the MBG server.

3. The public address used for MBG must be a static IP address visible from the external network

(Internet). This should be a separate address from the external IP address of the firewall, although some

firewalls that support port forwarding may allow sharing the address. It is vital that this address actually

be static as any change of the address will cause remote sets to lose connectivity.

4. The firewall must preserve the TCP and UDP port numbers in packets exchanged between the MBG

and the external network. In other words, only the address field may be changed.

For deployment in a DMZ, MSL must be installed in “server-only” mode with only a single NIC configured. This