Severity: Warning
Message: fopen(/home/np94ga2geed7/public_html/system/ci_sessione8f7d1f76261daf09bda91036e304a17): failed to open stream: Disk quota exceeded
Filename: drivers/Session_files_driver.php
Line Number: 156
Backtrace:
File: /home/np94ga2geed7/public_html/application/controllers/Site.php
Line: 9
Function: __construct
File: /home/np94ga2geed7/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_start(): Failed to read session data: user (path: /home/np94ga2geed7/public_html/system)
Filename: Session/Session.php
Line Number: 140
Backtrace:
File: /home/np94ga2geed7/public_html/application/controllers/Site.php
Line: 9
Function: __construct
File: /home/np94ga2geed7/public_html/index.php
Line: 315
Function: require_once
Implementing VoIP Support in an Enterprise Network (Cisco VoIP Implementations)
This section is intended to give you an overview of telephony deployment models and their necessary elements and components in an enterprise network. It briefly introduces Cisco Unified CallManager, and it discusses a few different implementation options for CallManager clusters. The last part of this section includes a simple configuration for a Cisco voice gateway and concludes with a brief discussion of CAC.
Enterprise Voice Implementations
The main telephony elements of an enterprise Cisco VoIP implementation are gateway, gatekeeper, Cisco Unified CallManager, and Cisco IP phones. Cisco IP phones need CallManager, because it acts as an IP PBX for the Cisco IP phones. The gateways provide connectivity between analog, digital, and IP-based telephony devices and circuits. Gatekeeper is an H.323 device that provides call routing or CAC services.
Enterprise voice implementations can vary based on many factors. One of those factors is the number of sites, and the preferred method of data and voice connectivity (primary and backup) between the sites. Some sites might not have VoIP implemented; other sites might have VoIP connectivity but no IP phones or other IP Telephony services. The sites with IP phones and services might have the control components, such as Cisco Unified CallManager cluster, locally present, or they might have to communicate with the control devices that reside at another branch or site. Figure 1-15 displays an enterprise with three branches: Branch A, Branch B, and Branch C.
Figure 1-15 VoIP Implementation Within an Enterprise