User's Manual

Centralized phone A Avaya Aura core servers (including Session Manager and CM-FS)
centralized phone B
Note:
The B5800 Branch Gateway is not involved in handling the call in this scenario.
The call flow descriptions in this document are intended to clarify the call flow between the
branch and the core with focus on B5800 Branch Gateway involvement. For brevity, they do
not elaborate on the processing of the call within the core, among the different elements of the
Avaya Aura
®
server infrastructure at the enterprise core. For example, a more complete
depiction of the call flow for this scenario would be:
Centralized phone A
Session Manager origination-side processing by the CM-FS
responsible for user of phone A
Session Manager termination-side processing by the CM-
FS responsible for user of phone B Session Manager centralized phone B
This depiction of the call flow includes the core Avaya Aura
®
Communication Manager acting
as the feature server for the centralized user. The Communication Manager Feature Servers
(CM-FSs) for user A and user B may be the same CM server or two different CM servers,
depending on the provisioning of the users on the core CM servers. Furthermore, additional
application servers may be sequenced in the call flow by Session Manager if additional core
sequenced applications are deployed by the enterprise. See the Avaya Aura
®
Session Manager
documentation for more information regarding the operation of the CM-FS with Session
Manager, and regarding Session Manager application sequencing.
2. Centralized phone to local phone (dialing local phone’s enterprise number)
Centralized phone
Session Manager CM-FS Session Manager B5800 Branch
Gateway local phone
3. Centralized phone to PSTN (using local trunking)
Centralized phone
Session Manager CM-FS Session Manager B5800 Branch
Gateway B5800 Branch Gateway trunk (e.g. FXO, ISDN, SP SIP trunk) PSTN
4. Centralized phone to PSTN (using centralized trunking)
Centralized phone
Session Manager CM-FS Session Manager central gateway/SBC
PSTN
Note:
The B5800 Branch Gateway is not involved in handling the call in this scenario.
5. Centralized phone to headquarters or other enterprise site
Centralized phone
Session Manager CM-FS Session Manager target phone’s
controller (if target phone does not register directly to SM) target phone
Note:
The B5800 Branch Gateway is not involved in handling the call in this scenario.
B5800 Branch Gateway call flows
310 Implementing the Avaya B5800 Branch Gateway November 2011
Comments? [e-mail]