Avaya B5800 User Manual Page 14

  • Download
  • Add to my manuals
  • Print
  • Page
    / 342
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 13
Branch user model at the same time. The extensions supported in the Centralized Branch
user model are SIP extensions only.
Centralized solution
The B5800 Branch Gateway can be deployed as a Distributed branch, a Centralized branch,
or a Mixed branch. Both Distributed and Centralized branches can benefit from centralization.
In Distributed branch deployments, the option to leverage centralized PSTN trunking and
centralized applications such as voice mail and conferencing is provided. In Centralized branch
deployments, in addition to the above, phone registration and call processing is also
centralized.
The centralized solution is based primarily on the central Avaya Aura
®
infrastructure at the
enterprise core. During normal operation, the centralized users located in the branches receive
their service from the core, like users in the main office do. The phones register directly to the
Avaya Aura
®
Session Manager in the enterprise core, get their features from the central
Communication Manager Feature Server (CM-FS) or Communication Manager Evolution
Server (CM-ES), and utilize the Avaya Aura
®
applications.
The local B5800 Branch Gateway can be accessed as a SIP gateway connected to the core
Avaya Aura
®
Session Manager to provide access to local PSTN trunks and services when
required. In addition, if WAN connectivity to the Avaya Aura
®
Session Manager is lost, the
centralized SIP phones automatically failover and register with the B5800 Branch Gateway
which provides them with basic telephony survivability. When connection to the Avaya
Aura
®
Session Manager is available again, failback occurs where the SIP phones return to
being controlled by Avaya Aura
®
Session Manager.
In the centralized solution, the users must be administered on the Avaya Aura
®
Session
Manager and the core Communication Manager, as well as on the local B5800 Branch
Gateway. The centralized users' extension numbers must be defined according to the
enterprise numbering plan of the Avaya Aura
®
Session Manager. In addition to general
administration of the Avaya Aura
®
Session Manager and the core Communication Manager,
special consideration must be given to the design and configuration of branch location-
dependent functionality in the Session Manager and optionally also in the core Communication
Manager. It is also important to verify the readiness of the underlying IP network since in the
centralized solution, VoIP is transported over the WAN.
PSTN trunking configurations
With the ability to administer call control at both the B5800 Branch Gateway and the Avaya
Aura
®
Session Manager, there are many ways you can optimize external PSTN trunk usage.
The B5800 Branch Gateway is a full PABX and by default uses its own PSTN trunks. However
Overview
14 Implementing the Avaya B5800 Branch Gateway November 2011
Page view 13
1 2 ... 9 10 11 12 13 14 15 16 17 18 19 ... 341 342

Comments to this Manuals

No comments