Specifications

MBG Engineering Guidelines, Release 8.0
2 Supported Configurations
2.1 Services
MBG provides the following services:
Remote MiNet IP Phones The classic use of MBG, formerly known as the Teleworker Solution, permits
remote MiNet phones to securely access the corporate phone network over the Internet.
Remote SIP IP Phones Permits Teleworker functionality for SIP hard or soft phones over the Internet.
SIP Trunking Allows a corporate phone switch to connect SIP trunks to a SIP trunk provider, protecting
the switch from malformed messages, unauthorized use, and various attacks, and providing an anchor
point for media streams.
Call Recording Formerly the Secure Recording Connector, this service allows secure recording of
phone calls by a third-party application
In addition, the MBG server can host the Remote Proxy Services blade to provide the following services:
Web Proxy: end-user access from the WAN to applications hosted inside the firewall
Remote Management Service: administrative access from the WAN to applications hosted inside the
firewall
Please refer to the Remote Proxy Services documentation for details.
MBG can be deployed in several ways depending on the services required.
2.2 Teleworkers and Remote Offices
Overview
The original design intent of MBG is to provide a Teleworker solution. Once an MBG server is installed,
extensions from the office PBX can be extended across the Internet to permit MiNet phones to work from homes,
remote offices, hotels, etc.
In this use-case, either the server-gateway profile or DMZ profile could be used depending where on the network
MBG is to be deployed. If deploying behind an existing firewall on a DMZ, then a single network interface and
DMZ profile is appropriate. If deploying beside an existing firewall, or if there is no existing firewall, then server-
gateway profile is appropriate.
Failure to follow these guidelines will result in one-way or no-way audio.
Warning: Some firewalls which use port-forwarding to simulate a DMZ are Port-forwarding Firewalls. See
the Common Requirements chapter for full details.
2