Cisco 2900 - Catalyst Expansion Module Gegevensblad - Pagina 2

Blader online of download pdf Gegevensblad voor {categorie_naam} Cisco 2900 - Catalyst Expansion Module. Cisco 2900 - Catalyst Expansion Module 20 pagina's. Rack-mounting instructions
Ook voor Cisco 2900 - Catalyst Expansion Module: Montage-instructies (8 pagina's)

IP Telephony Phased Migration
The Cisco 1861 and Cisco 2800, 3800, 2900, 3900, and 3900E Series unified communications routers can help
you immediately deploy an end-to-end unified communications network architecture or gradually shift voice traffic
from traditional circuit-switched networks to a single infrastructure carrying data, voice, and video over packet
networks.
Initially, you can use these unified communications routers to interconnect older PBXs over the packet
infrastructure and still maintain PSTN (off-net) connectivity through your circuit-switched PBXs. Later, you can
migrate PSTN (off-net) connectivity to the unified communications routers and start to incorporate IP phones at
larger sites (Figure 1). After all sites are running IP telephony, you can begin deploying IP-based applications such
as IP unified messaging, personal assistants, and extension mobility.
The unified communications routers are an ideal solution for circuit-switched PBX and PSTN access within a Cisco
Unified Communications Manager-based IP telephony architecture.
Figure 1.
IP Telephony Phased Migration: Migrate Circuit-Switched PSTN and PBX Connectivity to Unified Communications
As companies seek to deploy unified communications solutions across the entire enterprise - converging voice,
video, and data across potentially thousands of sites - they require a solution that offers simple administration,
virtually unlimited scalability, and high availability. The unified communications routers work in concert with the
Cisco Unified Communications Manager, deployed in either a distributed or centralized call-processing model, to
provide the unified communications solutions that enterprises require.
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 2 of 20