Avaya 1000 Installation And Commissioning Manual page 20

Overview
processing for the IP Phones in both the main office and Branch Office locations. The MG 1000B
Core provides call processing functionality to local digital telephones and analog devices. The MG
1000B Core also provides digital and analog trunk access to the local Public Switched Telephone
Network (PSTN).
The MG 1000B platform connects to the Main Office over Virtual Trunks on a LAN/WAN. The Main
Office transmits and controls IP Phone calls and IP network connections. If the Main Office fails to
function, or if there is a network outage, the Server in MG 1000B Core provides service to the
telephones located at the Branch Office location. This enables the IP Phones to survive the outage
between the Branch Office and the Main Office.
You can configure the Media Gateway 1000B Branch Office with the following hardware
configurations:
• A Server and a Gateway Controller in a Media Gateway
• Co-resident Call Server and Signaling Server (Co-res CS and SS)
• VxWorks CP PM with a Linux Signaling Server
For both hardware platforms the Main Office must use a CS 1000E system, or a CS 1000M CP PIV
or CP PM system. The Main Office can support a combination of up to 255 of the two Branch Office
hardware platforms.
You can implement the Branch Office feature as a new hardware configuration. You can also create
it by converting an existing Small System to an MG 1000B platform (see
to a Branch Office on page 90). The functionality is the same in both configurations.
Important:
If you have a Co-resident Call Server and Signaling Server, converting to a Branch Office is
different. The procedure is the same for a CP PM VxWorks-based Calling Server migration but
the Signaling Server installation is not. For more information about installing a Signaling Server,
see Avaya Signaling Server IP Line Applications Fundamentals, NN43001-125
A Branch Office works with a main office only if the two offices use a common dialing plan. Any
other configuration is not guaranteed to work properly. For example, as seen with the following
Dialed Numbers (DN), Branch User ID is different from a DN.
31415 as DN on BO 27181 as DN on MO
Vacant number routing for Branch Office calls does not route to the Main Office properly because
31415 is sent to the network, and 27181 is not because it is configured at the Main Office. This is
why it is important to have the same extensions on a phone in normal and local mode.
Figure 1: Branch Office associated with a CS 1000E main office
Office network.
Branch Office Installation and Commissioning
20
Comments? infodev@avaya.com
Converting a Small System
on page 21 shows a Branch
June 2014