Specifications

MBG Engineering Guidelines, Release 8.0
still flows back to the main office, but voice streams for calls between offices will only traverse the path between
the two MBGs. This minimizes bandwidth use on the main office's connection.
Caveat: All MBG servers in the daisy chain must be at the same release.
Refer to the MBG Installation and Maintenance Guide for a full description of setting up daisy-chaining.
2.8 MBG in MAS
There are two supported deployments of MBG in MAS: on the LAN and on the network edge (Gateway mode).
Deployment in the DMZ is not supported.
MAS on the LAN
The safest way to deploy MBG is to leave MAS and its applications on the LAN, and deploy a second server
running MBG (either standalone or single-app MAS) in the DMZ or in Gateway mode at the network edge.
Remote access to the LAN MAS can be provided via Web Proxy on Internet-facing MBG. If centralized
management is desired, the two MBG applications can be clustered. All changes made on the LAN server will be
reflected on the edge MBG. Refer to the MAS documentation set for details on clustering MBG with MAS.
MAS on the Network Edge
13
Figure 11: Multiple downstream MBGs