Home > Articles > Cisco Certification > CCNP Security / CCSP > CCSP CSI Exam Certification: SAFE IP Telephony Design

CCSP CSI Exam Certification: SAFE IP Telephony Design

  • Sample Chapter is provided courtesy of Cisco Press.
  • Date: Dec 30, 2004.

Chapter Description

This chapter will help you prepare for the CCSP CSI Exam, with a focus on SAFE IP Telephony Design. Sample questions are included to help you study.

Foundation Topics

Examining SAFE IP Telephony Design Fundamentals

The "SAFE: IP Telephony Security in Depth" whitepaper provides best-practice information for the deployment of IP telephony in the various SAFE blueprints. Although this whitepaper covers a wide range of topics related to IP telephony, it does not discuss many other topics, including quality of service (QoS) applied to the voice traffic to eliminate echoes and jitter, and the security of the voice protocols between the voice gateways. Because of the nature of IP telephony and the requirements for low latency, QoS is an extremely important feature that you must enable network-wide before deploying IP telephony. The whitepaper focuses on centralized call processing, not distributed call processing. It is assumed, however, that all remote sites have a redundant link to the headend or the local call-processing backup, in case of headend failure. Finally, the interaction between IP telephony and Network Address Translation (NAT) is not covered.

The following design objectives guided the decision-making process for the SAFE IP telephony whitepaper:

  • Security and attack mitigation based on policy

  • Quality of service

  • Reliability, performance, and scalability

  • Authentication of users and devices (identity)

  • Options for high availability (some designs)

  • Secure management

The SAFE IP telephony design must provide telephony services in the same way that current telephony services are deployed. In addition, it must maintain the same characteristics as traditional telephony in as secure a manner as possible. Finally, it must integrate with existing network designs.

IP Telephony Network Components

IP telephony adds four voice-specific devices to a network:

  • IP telephony devices—This category includes any device that supports placing calls in an IP telephony network, such as IP phones and PC softphones (IP phone software running on a PC).

  • Call-processing manager—This system is the server that provides call control and configuration management for IP telephony devices in the network. It provides bootstrap information for IP telephony devices, call setup, and call routing throughout the network to other voice-enabled devices such as voice gateways and voice-mail systems.

  • Voice-mail system—This system primarily provides IP-based voice-mail storage services. In addition, it can provide user directory lookup capabilities and call-forwarding features.

  • Voice gateway—This is a generic term that refers to any gateway that provides voice services, such as IP packet routing, backup call processing, Public Switched Telephone Network (PSTN) access, and other voice services. This device is the interface between the legacy voice systems that can provide backup for the IP telephony network in case of failure. This device is typically not a full-featured call-processing manager; it supports a subset of the call-processing functionality provided by the call-processing manager.

VoIP Protocols

At the time of writing of the "SAFE: IP Telephony Security in Depth" whitepaper, these were the three predominant protocol standards for voice over IP (VoIP):

  • H.323

  • Session Initiation Protocol (SIP)

  • Media Gateway Control Protocol (MGCP)

The following sections describe each standard in detail.


The International Telecommunication Union (ITU) H.323 standard covers IP devices that participate in and control H.323 sessions, along with elements that interact with switched-circuit networks. This standard does not cover the LAN itself or the transport layer within the network. H.323 provides for point-to-point or multipoint sessions. The H.323 standard is composed of several components, including other standards that describe call control, signaling, registration, and packetization/synchronization of media streams. Table 19-2 lists these components.

Table 19-2 Core Components of H.323




Specifies messages for call control, signaling, registration, admission, packetization, and synchronization


Specifies the requirements for opening and closing channels for media streams and other commands




Video codec for audiovisual services


Specification for a new video codec for basic video telephone service


Audio codec—3.1 kHz at 48, 56, and 64 kbps (normal telephony)


Audio codec—7 kHz at 48, 56, and 64 kbps


Audio codec—5.3 kbps and 6.3 kbps modes


Audio codec—3.1 kHz at 16 kbps


Audio codec—3.1 kHz at 8 kbps

Ports used for H.245 signaling and media channels dynamically are negotiated between the endpoints. This makes it especially difficult to impose security policy and traffic shaping. Additionally, the control channel of H.245 uses TCP as a transport protocol, but the media stream channels utilize UDP as a transport protocol. For a firewall to be placed between two (or more) H.323 endpoints, the firewall must be either H.323 enabled (that is, it must be intelligent enough to allow H.323 traffic through, appropriately utilizing an H.323 proxy) or it must monitor the control channel to determine which dynamic ports are in use for the H.323 sessions.


The Session Initiation Protocol (SIP) is an ASCII-encoded application layer control protocol that is defined in RFC 2543. You can use SIP to establish, maintain, and terminate calls between two or more endpoints. Like other protocols, it is designed to address the signaling and session-management functions in an IP telephony network. SIP does this by allowing call information to be carried across network boundaries and also by providing the capability to control calls between any endpoints.

SIP can identify the location of an endpoint through the use of address resolution, name mapping, and call redirection. Additionally, through the use of the Session Description Protocol (SDP), the protocol can determine the least common denominator of possible services between the two endpoints. This provides the capability to establish conference calls using only the media capabilities that all participants can support. SIP also can handle the transfer and termination of calls and the determination of the availability of a given endpoint, and can establish a session between two or more endpoints (as in a conference).


The Media Gateway Control Protocol (MGCP) is a master/slave protocol implemented in media gateway controllers or call agents. These controllers/agents run on telephony gateways, which are devices that provide the conversion of data packets used in IP telephony to audio signals that are carried on PSTN circuits. The controllers/agents provide the control, signaling, and processing skills to control the telephony gateways and implement the signaling layers of H.323. To other H.323 devices, these controllers/agents appear as an H.323 gatekeeper or as one or more H.323 endpoints.

Threats to IP Telephony Networks

Various threats are inherent in all networks but are of particular importance where IP telephony is deployed. This section describes the following threats:

  • Packet sniffers/call interception

  • Virus and Trojan horse applications

  • Unauthorized access

  • Caller identity spoofing

  • Toll fraud

  • Repudiation

  • IP spoofing

  • Denial of service

  • Application layer attacks

  • Trust exploitation

Packet Sniffers/Call Interception

A packet sniffer can monitor and capture the traffic in a network. A packet sniffer in a voice VLAN can capture unencrypted conversations and save them to a file. These conversations can then be reassembled for listening using such tools as Voice over Misconfigured IP Telephony (VOMIT).

Virus and Trojan Horse Applications

Viruses are malicious software that attached to other files and programs and executed by either the user opening the file or program startup. Examples of viruses include the Melissa virus and the more recent MyDoom and W32.bagle viruses.

A Trojan horse application is a program designed to appear innocuous to the user while it executes additional commands without the user's direct knowledge. A simple example is a computer game that, while the user is playing it, deletes specific files from the machine or installs a back-door mechanism for an external attacker to gain access to the system. A Trojan horse application is of particular concern because if the targeted PC is on the data segment of a network with IP telephony deployed and a PC softphone installed (thereby requiring access to the voice VLAN), an attacker might be able to bypass the segmentation between the two VLANs by installing a Trojan horse application on that system.

Unauthorized Access

Although these are not specific types of attacks, they are the most common attacks executed in today's networks. Many modern IP phones also behave as a switch providing access to both the voice and the data VLAN. An attacker could plug into the back of an IP phone and gain instant access to the network, possibly without requiring authentication.

Caller Identity Spoofing

Caller identity spoofing is much like IP spoofing. The attacker's main goal is to trick a remote user into believing that he or she is communicating with someone other than the attacker. This attack typically requires that the hacker assume the identity of someone who is not familiar to the target and can be either complex enough to require the placement of a rogue IP phone on the network or as simple as using an unattended IP phone.

Toll Fraud

Toll fraud encompasses a wide variety of illegal behavior. Typically, this involves the theft of the phone service. In its most basic form, toll fraud involves an unauthorized user accessing an unattended IP telephone and placing calls. Other attacks include placing a rogue IP phone or gateway in the network to place unauthorized calls.


Repudiation attacks are difficult to mitigate. If two parties talk over the phone and one party decides later to deny that the conversation took place, the other party has no proof that the conversation ever took place. However, call logging can be used to verify that a communication did take place. Without strong user authentication, however, validating who placed the call is not possible.

IP Spoofing

IP spoofing involves the impersonation of a trusted system. To do this, an attacker uses either an IP address that is within the range of trusted IP addresses or a trusted external IP address that also is provided access to target resources on the network. IP spoofing typically is associated with certain types of attacks, such as a denial-of-service (DoS) attack, in which the attacker wants to hide his or her true identity.

Denial of Service

Denial-of-service (DoS) attacks are one of the most difficult attacks to mitigate completely. DoS attacks against the call-processing manager in an IP telephony deployment can bring down the entire phone system.

Application Layer Attacks

Application layer attacks are attacks against an application such as IIS, sendmail, or Oracle that are running on a system. Exploiting weaknesses in these applications can provide an attacker with access (sometimes privileged access) to the system. Because these attacks are against applications that have ports that often are allowed through a firewall, it is critical that these attacks be mitigated through other means. For IP telephony networks, the most important element is the call-processing manager. Because many call-processing managers run a web server for remote access to manage-ment functions, they can be attacked through that application. It is important that a host-based IPS be installed and active on call-processing managers even though they might be protected by a stateful firewall to prevent application layer attacks.

Trust Exploitation

A trust-exploitation attack as it relates to IP telephony can be executed if voice and data servers have a trust relationship. The exploitation of the data server, such as a web server, then could result in the exploitation of the central call-processing manager. This provides the attacker with significant access into not just the data VLAN, but also the voice VLAN.

3. Understanding SAFE IP Telephony Axioms | Next Section Previous Section

Cisco Press Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Cisco Press and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Cisco Press products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@ciscopress.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by Cisco Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.ciscopress.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020