IP Office user phone to IP Office user phone

IP Office user phone A > IP Office > IP Office user phone B

IP Office user phone to PSTN (using local trunking)

IP Office user phone > IP Office > IP Office trunk > PSTN

IP Office user phone to PSTN (using centralized trunking)

IP Office user phone > IP Office > Session Manager > central gateway/SBC > PSTN

IP Office user phone to headquarters or other enterprise site

IP Office user phone > IP Office > Session Manager > target phone’s controller > target phone

From PSTN to IP Office user phone via IP Office auto-attendant (branch auto-attendant LDN is associated with local IP Office trunk)

PSTN > IP Office trunk > IP Office auto-attendant > caller enters extension number > IP Office user phone

From PSTN direct to IP Office user phone’s DID (LDN is associated with local IP Office trunk)

PSTN > IP Office trunk > IP Office > IP Office user phone

From headquarters (or other enterprise site) to IP Office user phone’s enterprise number

Originating phone > originating phone’s controller > Session Manager > IP Office > IP Office user phone

From headquarters (or other enterprise site) to IP Office user phone via IP Office auto-attendant

Originating phone > originating phone’s controller > Session Manager > IP Office > IP Office auto-attendant > caller enters extension number > IP Office user phone

Centralized phone A to centralized phone B in the same branch

Centralized phone A > Avaya Aura core servers (including Session Manager and CM-FS or CM-ES) > centralized phone B

The call flow descriptions in this document are intended to clarify the call flow between the branch and the core with focus on IP Office 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 or CM-ES responsible for user of phone A > Session Manager > termination-side processing by the CM-FS or CM-ES 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) or Communication Manager Evolution Servers (CM-ESs) 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 or CM-ES with Session Manager, and regarding Session Manager application sequencing.

Centralized phone to IP Office user phone (dialing IP Office user phone’s enterprise number)

Centralized phone > Session Manager > CM-FS or CM-ES > Session Manager > IP Office > IP Office user phone

Centralized phone to PSTN (using local trunking)

Centralized phone > Session Manager > CM-FS or CM-ES > Session Manager > IP Office > IP Office trunk > PSTN

Centralized phone to PSTN (using centralized trunking)

Centralized phone > Session Manager > CM-FS or CM-ES > Session Manager > central gateway/SBC > PSTN

Centralized phone to headquarters or other enterprise site

Centralized phone > Session Manager > CM-FS or CM-ES > Session Manager > target phone’s controller (if target phone does not register directly to SM) > target phone

From PSTN to centralized phone’s DID (LDN is associated with local IP Office trunk)

PSTN > IP Office trunk > IP Office > Session Manager > CM-FS or CM-ES > Session Manager > centralized phone

From PSTN to centralized phone via IP Office auto-attendant (branch auto-attendant LDN is associated with local IP Office trunk)

PSTN > IP Office trunk > IP Office auto-attendant > caller enters extension number > IP Office modifies extension number to user’s enterprise number > Session Manager > CM-FS or CM-ES > Session Manager > centralized phone

From PSTN to centralized phone’s DID (if LDN is ported to centralized trunks at the core)

PSTN > central gateway/SBC > Session Manager > CM-FS or CM-ES > Session Manager > centralized phone

From branch IP Office user phone to centralized phone (dialing phone’s enterprise number)

IP Office user phone > IP Office > Session Manager > CM-FS or CM-ES > Session Manager > centralized phone

From headquarters (or other enterprise site) to centralized phone’s enterprise number

Originating phone > originating phone’s controller > Session Manager > CM-FS or CM-ES > Session Manager > centralized phone

Centralized phone A to Centralized phone B in the same branch

Centralized phone A > IP Office > centralized phone B

Centralized phone to IP Office user phone (dialing either IP Office user phone’s enterprise number or short extension)

Centralized phone > IP Office > IP Office user phone

Centralized phone to PSTN

Centralized phone > IP Office > IP Office trunk > PSTN

Centralized phone to headquarters or other enterprise site

IP Office can be administered to send such calls over the PSTN. See below.

From PSTN to centralized phone’s DID

PSTN > IP Office trunk > IP Office > centralized phone

From PSTN to centralized phone via IP Office auto-attendant

PSTN > IP Office trunk > IP Office auto-attendant > caller enters extension number > centralized phone

From branch IP Office user phone to centralized phone (dialing either IP Office user phone’s enterprise number or short extension)

IP Office user phone > IP Office > centralized phone