Branch Gateway Controller (MGC) controls telephone services on Branch Gateway. You can use a server with the Communication Manager software as MGC. Branch Gateway supports External Call Controllers (ECC) and Internal Call Controllers (ICC). ECC is an external server communicating with Branch Gateway over the network. ICC is Avaya S8300 Server that you install in Branch Gateway as a media module.

When Branch Gateway uses ECC, it can use a local S8300 as a backup controller for Enhanced Local Survivability (ELS). S8300 functions in the Survivable Remote Server (SRS) mode. If ECC stops serving Branch Gateway, S8300 takes over the service.

Release 7.1 and later support the following commands:

• set allow-unencrypted: To allow or disallow media encryption requests from Communication Manager.

• set link-encryption: To specify what TLS versions the gateway offers when connecting to a server.

Media Gateway supports the following new enhancements from Release 10.1:

• Edge Gateway: With the Edge Gateway feature, endpoints and gateways can operate in local NAT address domains at the branch office sites, while the Avaya server products remain in the data centers. The data centers also operate in a private address space. Avaya Session Border Controller (ASBCE) is the conversion element that supports end-to-end communication from the data centers to public service provider networks and the branch office sites. For details on configuring the ASBCE Edge Gateway feature, see Administering Avaya Session Border Controller.

• Management link: Edge Gateway supports a new management link (MGSBC) with Session Border Controller. The link is required to support the following:

  • SNMP TRAP messages sent up a link to UDP port 162 on the host Communication Manager.

  • The transport of SSH administration and maintenance sessions between Communication Manager and Edge Gateway.