Architectural Overview of Trunk Devices

Figure 4-1 shows the block structure of CallManager. CallManager contains several signaling layers, each of which has distinct functions. For example, the Call Control Layer handles the call signaling that controls call setup, teardown, and call routing.

Figure 4-1. CallManager Block Structure Diagram

The software in the Media Control Layer coordinates all media connections that CallManager makes between devices. It can insert other media processing devices into a call and create appropriate streaming connections to those devices. As indicated in Chapter 1, "Cisco CallManager Architecture," in the Cisco VoIP solution, the actual media always streams directly between the end devices involved in a call. However, CallManager can also insert other media processing devices into a call, such as audio transcoding and conference bridge resources, depending on the media requirements needed for each call. Chapter 5, "Media Processing," contains more information about CallManager's handling of media devices.

The Protocol and Aggregator Layers handle all protocol-specific signaling required for specific devices. These blocks serve to translate protocol-specific signaling into the internal signaling used to communicate with the Call Control and Media Control Layers.

Figure 4-1 indicates with shading the software layers and blocks within CallManager that this chapter describes. In particular, CallManager implements logic in the Protocol Layer to communicate with gateways via native VoIP signaling protocols such as H.225, MGCP, and SIP and logic in the Media Control Layer to handle H.245 media.

Figure 4-2 shows how gateway devices enable communication between CallManager and circuit-switched networks such as the PSTN. From a control point of view, Cisco VoIP gateways act very much like IP phones. They are VoIP endpoints that happen to mediate between the packet- and circuit-switched worlds.

Figure 4-2. Gateway Trunking Devices

Like IP phones, CallManager controls Cisco VoIP gateways using signaling control protocols (which in an Alice-to-Bob call answers the question "Does Bob want to talk to Alice?") and media control protocols (which answers the question "How should Alice and Bob talk?").

In the case of IP phones, the endpoint always terminates both the signaling and the media protocols. On the other hand, VoIP gateways, although they always terminate the media control protocol, sometimes simply pass through the signaling control protocol used by the circuit-switched network. This process is called backhauling.

To understand how a particular gateway interacts with CallManager, therefore, you need to concentrate mainly in two areas:

  • What protocol the gateway is using to connect to the circuit-switched network
  • What protocol the gateway is using to connect to CallManager

For connectivity between the gateway and the circuit-switched network, Cisco voice gateways support a range of traditional analog and digital interfaces.

The following section, "Overview of Circuit-Switched Interfaces," discusses the analog and digital protocols that traditional telephony networks use to communicate with Cisco voice gateways.

For connectivity between CallManager and the VoIP gateway, CallManager supports four protocols:

  • Skinny Gateway Control Protocol (SGCP) The analogous protocol to Skinny Client Control Protocol (SCCP), which CallManager uses to provide signaling and media control functions for Cisco IP Phones. Cisco no longer sells any VoIP gateways that run SGCP, so this book doesn't discuss this protocol in detail.
  • H.323 An ITU-T recommendation that uses the ITU-T recommendations H.225 for signaling; H.245 for media control; and the Registration, Admission, and Status (RAS) protocol for registration and call admission. The section "H.323 Gateways" goes into detail about this protocol.
  • Media Gateway Control Protocol (MGCP) An IETF standard protocol, defined in RFCs 2705 and 3435 among others, that uses a text-based protocol to permit a Media Gateway Controller (MGC)a function that CallManager fulfillsto establish and tear down calls. MGCP messages provide good media control messages and some rudimentary signaling messages. The section "MGCP Gateways" describes this protocol.
  • Session Initiation Protocol (SIP) An IETF standard related to Hypertext Transfer Protocol (HTTP) that uses a text-based protocol for both signaling and, via Session Description Protocol (SDP) bodies, media control. The section "SIP" describes this protocol.

Cisco CallManager Architecture

Call Routing

Station Devices

Trunk Devices

Media Processing

Manageability and Monitoring

Call Detail Records

Appendix A. Feature List

Appendix B. Cisco Integrated Solutions

Appendix C. Protocol Details


Cisco CallManager Fundamentals
Cisco CallManager Fundamentals (2nd Edition)
ISBN: 1587051923
EAN: 2147483647
Year: 2004
Pages: 141 © 2008-2020.
If you may any questions please contact us: