Specifications

MBG Engineering Guidelines, Release 8.0
Reduced Bandwidth for Remote Sites
If MBG is providing access for a remote office environment where the users often call one another, an MBG
server can be provided on site and daisy-chained to the MBG server at the main office. This is not needed for
MiNet to MiNet calls behind the same remote NAT because the MBG local streaming feature will handle that
case. However, this deployment can be used to keep MiNet to SIP calls in the remote office. This configuration,
illustrated in Figure 10, can save bandwidth on the link between the remote and main offices.
The upstream server can be deployed in either a Gateway or a DMZ configuration.
Warning: Management of all remote office sets must be done on the upstream (main office) server only.
When the downstream server is put into daisy-chain mode, it will automatically disable all MiNet and SIP
connection restrictions, and pass all connection attempts up to the upstream server for authentication.
The remote office (downstream) MBG can also be configured for either a Gateway or DMZ deployment. Note
that there is no restriction on the location of the remote office sets; they do not have to be on the LAN. It may be
desirable to configure certain teleworker sets to connect to remote office MBGs (rather than the main office
MBG) in order to cause direct streaming of those teleworkers' calls to sets in the remote office. This case
requires Local streaming to be enabled on the upstream (main office) server.
It is even possible to deploy multiple downstream MBG servers at different remote offices. If upstream (main
office) server has Local Streaming enabled, calls within each remote office remain local to that office: signaling
12
Figure 10: Daisy-chained MBGs to save bandwidth