Implementing Cisco TelePresence Vol1

ITS
Implementing Cisco
TelePresence
Solutions
Volume 1
Version 1.1
Student Guide
Text Part Number: 97-2994-01

DISCLAIMER WARRANTY: THIS CONTENT IS BEING PROVIDED “AS IS” AND AS SUCH MAY INCLUDE TYPOGRAPHICAL,
GRAPHICS, OR FORMATTING ERRORS. CISCO MAKES AND YOU RECEIVE NO WARRANTIES IN CONNECTION WITH THE
CONTENT PROVIDED HEREUNDER, EXPRESS, IMPLIED, STATUTORY OR IN ANY OTHER PROVISION OF THIS CONTENT OR
COMMUNICATION BETWEEN CISCO AND YOU. CISCO SPECIFICALLY DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING
WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE, OR ARISING FROM A
COURSE OF DEALING, USAGE OR TRADE PRACTICE. This learning product may contain early release content, and while Cisco believes it to
be accurate, it falls subject to the disclaimer above.
Student Guide © 2011 Cisco and/or its affiliates. All rights reserved.
Students, this letter describes important
course evaluation access information!
Welcome to Cisco Systems Learning. Through the Cisco Learning Partner Program,
Cisco Systems is committed to bringing you the highest-quality training in the industry.
Cisco learning products are designed to advance your professional goals and give you
the expertise you need to build and maintain strategic networks.
Cisco relies on customer feedback to guide business decisions; therefore, your valuable
input will help shape future Cisco course curricula, products, and training offerings.
We would appreciate a few minutes of your time to complete a brief Cisco online
course evaluation of your instructor and the course materials in this student kit. On the
final day of class, your instructor will provide you with a URL directing you to a short
post-course evaluation. If there is no Internet access in the classroom, please complete
the evaluation within the next 48 hours or as soon as you can access the web.
On behalf of Cisco, thank you for choosing Cisco Learning Partners for your
Internet technology training.
Sincerely,
Cisco Systems Learning

Table of Contents
Volume 1
Course Introduction 1
Overview 1
Learner Skills and Knowledge 1
Course Goal and Objectives 2
Course Flow 4
Additional References 5
Introduction to Cisco TelePresence 1-1
Overview 1-1
Module Objectives 1-1
Exploring the Cisco TelePresence Solution 1-3
Overview 1-3
Objectives 1-3
What Is Telepresence? 1-4
Traditional Video Conferencing 1-5
Primary Attributes of Cisco TelePresence 1-6
Cisco TelePresence Endpoint Design Principles 1-9
Advantages of Cisco TelePresence 1-11
Shaping the Future of the Internet 1-12
High-Level Network Requirements 1-13
High-Level NPA 1-14
Summary 1-15
Exploring the Cisco TelePresence Environments 1-17
Overview 1-17
Objectives 1-17
The Cisco TelePresence Solution 1-18
Cisco TelePresence Endpoint Portfolio 1-22
Cisco TelePresence System 3200 1-24
Cisco TelePresence Systems 1100 and 1300 1-26
Cisco TelePresence Generation 2 Wiring Diagram 1-31
Acoustic Properties 1-32
Illumination Properties 1-33
Cisco TelePresence Auto Collaborate 1-34
The Cisco TelePresence Multipoint Switch 1-36
Cisco TelePresence Recording Server 1-39
Cisco TelePresence Manager 1-40
Cisco TelePresence Connectivity and Experience Options 1-42
Intercompany Communications 1-43
Cisco TelePresence Planning, Design, and Implementation Service 1-45
Summary 1-47
Planning a Cisco TelePresence Room Design 1-49
Overview 1-49
Objectives 1-49
Room Design Considerations 1-50
Corporate Identity 1-51
Background Aesthetics 1-52
Room Design Examples 1-53
Van Ness 1-54
Pacific 1-55
Haight 1-56
Ashbury 1-57
Marina 1-58
Sloat 1-59
Wall Finishes 1-60
Background Color 1-63
Summary 1-65
Module Summary 1-67
References 1-68
Module Self-Check 1-69
Module Self-Check Answer Key 1-72
Cisco TelePresence Call Control 2-1
Overview 2-1
Integrating Cisco TelePresence Endpoints with Cisco Unified Communications
Manager 2-3
Overview 2-3
Objectives 2-3
A Complete End-to-End Solution 2-4
The Cisco TelePresence Codec 2-5
Cisco TelePresence System Administration 2-7
Configuration > IP Settings 2-9
Configuration > Cisco Unified Communications Manager Settings 2-10
Configuration > Telephony Settings 2-12
Configuration > System Settings 2-14
Troubleshooting > Hardware Setup 2-15
Troubleshooting > Log Files 2-16
Troubleshooting > SIP Messages 2-17
Monitoring > Call Statistics 2-18
Cisco Unified Communications Manager 2-21
Codec-to-Cisco Unified Communications Manager Registration 2-25
Protocol Interaction 2-26
Cisco TelePresence System Media Path 2-27
Cisco Unified Communications Manager Configuration for Cisco TelePresence 2-29
Cisco Unified IP Phone 797xG 2-38
Device > Phone 2-39
CAC Considerations 2-48
Troubleshooting 2-50
Summary 2-57
ii Implementing Cisco TelePresence Solutions (ITS) v1.1 © 2011 Cisco Systems, Inc.
Examining the Cisco TelePresence User Interface 2-59
Overview 2-59
Objectives 2-59
Cisco TelePresence Phone User Interface 2-60
One-Button-to-Push Meeting 2-69
Conferencing an Audio Call 2-75
Multiple Audio and Video Call Support 2-79
Meeting Control Options 2-80
View Control 2-80
Meeting Access 2-81
Controlling the Document Camera 2-82
Cisco Auto Collaborate Privacy Alert 2-83
Cisco TelePresence User Interface—In-Call Icons 2-84
On Phone Alerts, Status, and Messages 2-87
Alert—Upcoming Meeting 2-87
Alert—Meeting Is Scheduled to End in 10 Minutes 2-88
Error—No Dial Number Provided 2-89
Error—Meeting Is Outside the Start Window 2-90
Network Congestion 2-91
System Information 2-92
Error—This System is Not Currently Registered 2-93
Call Status 2-94
Peripheral Status 2-95
Alert—Resolution Not Supported 2-96
Alert—Troubleshooting in Progress 2-97
Peripheral Upgrade 2-98
Summary 2-99
Module Summary 2-101
References 2-102
Cisco TelePresence Network Architecture 3-1
Overview 3-1
Deploying a Cisco TelePresence Network 3-3
Overview 3-3
Objectives 3-3
Codec Communication 3-4
Primary Codec 3-4
Deployment Models 3-5
Intracampus Deployment Model 3-5
Intra-Enterprise Deployment Model 3-6
Intercompany Network Deployment Model 3-7
Multipoint 3-8
Cisco Device Configuration 3-9
Summary 3-26
 2011 Cisco Systems, Inc. Implementing Cisco TelePresence Solutions (ITS) v1.1 iii
Shaping and Policing 3-27
Overview 3-27
Objectives 3-27
Recommendations for Provisioning 3-28
Understanding Bursts 3-29
Traffic Policing and Shaping 3-32
Example: Token Bucket as a Piggy Bank 3-37
Traffic Characteristics of Cisco TelePresence 3-39
Packet Jitter 3-41
Frame Jitter 3-41
Provisioning for Bursts 3-49
Example Burst Calculations 3-56
Summary 3-59
Setting a QoS Policy 3-61
Overview 3-61
Objectives 3-61
Latency, Jitter, and Loss 3-62
Latency Target 3-67
Latency Threshold No. 1 3-67
Latency Threshold No. 2 3-67
Satellite Mode—Latency Thresholds 3-67
Understanding Latency Measurements in Multipoint Meetings 3-67
Jitter Target 3-69
Satellite Mode—Jitter Thresholds 3-70
Loss Target 3-72
Satellite Mode—Loss Thresholds 3-73
Latency Threshold Changes in Cisco TelePresence System Release 1.5 3-74
Jitter Threshold Changes in Cisco TelePresence System Release 1.5 3-75
Packet Loss Changes in Cisco TelePresence System Release 1.5 3-75
IP Packet Classification and Marking 3-76
Cisco Catalyst Switch Queuing Model for Telepresence Traffic 3-80
Catalyst 3750 1P3Q3T Queuing Configuration Example 3-83
Catalyst 6500 1P&Q4T Configuration Example 3-90
Campus QoS Policies Overview 3-93
Access Edge Switch Port QoS Policies 3-93
Campus Interswitch Link QoS Policies 3-95
Summary 3-96
Designing WAN and Branch QoS Policies 3-97
Overview 3-97
Objectives 3-97
WAN—Converged vs. Overlay 3-98
WAN and Branch Policies Overview 3-101
LLQ vs. CBWFQ Considerations and Recommendations 3-104
WAN Edge Models 3-107
MPLS VPN Policies Overview 3-112
Subline Rate Access Overview 3-115
Metro Ethernet Subline Rate QoS Policies 3-115
Service Provider Recommendations 3-120
Summary 3-124
iv Implementing Cisco TelePresence Solutions (ITS) v1.1 © 2011 Cisco Systems, Inc.
Understanding the NPA 3-125
Overview 3-125
Objectives 3-125
What Is the NPA? 3-126
NPA Tools 3-136
Cisco TelePresence Codec Call Statistics 3-137
Cisco IOS IP Service Level Agreement 3-139
Video SLA Assessment Agent 3-151
Cisco TelePresence Manager PreQualification Assistant 1.5 3-158
Summary 3-159
Using the VSAA 3-161
Overview 3-161
Objectives 3-161
What Is the VSAA? 3-162
Configuring VSAA Bootable USB Drives 3-163
The VSAA Reporting Process 3-167
Method 1 3-171
Method 2 3-172
Summary 3-177
Module Summary 3-179
References 3-180
 2011 Cisco Systems, Inc. Implementing Cisco TelePresence Solutions (ITS) v1.1 v
vi Implementing Cisco TelePresence Solutions (ITS) v1.1 © 2011 Cisco Systems, Inc.
ITS
Course Introduction
Overview
Implementing Cisco TelePresence Solutions (ITS) v1.1 is an instructor-led course presented by
Cisco Learning Partners to their end-user customers. The Cisco TelePresence solution offers an
advanced system, combined with a robust group of partners, so an enterprise can scale globally
and benefit from an exceptional meeting experience. Selected Cisco partners must quickly and
effectively deliver the high-quality Cisco TelePresence experience and operational services,
from installation to ongoing management. This skill set requires the proper training for a
smooth and successful customer deployment.
Learner Skills and Knowledge

This subtopic lists the skills and knowledge that learners must possess to benefit fully from the
course. The subtopic also includes recommended Cisco learning offerings that learners should
first complete to benefit fully from this course.
Learner Skills and Knowledge

 Knowledge and skills equivalent to those learned in
Interconnecting Cisco Networking Devices, Part 1
 Knowledge and skills equivalent to those learned in
Interconnecting Cisco Networking Devices, Part 2
 Knowledge and skills equivalent to those learned in Implementing
Cisco Quality of Service
 Knowledge and skills equivalent to those learned in Implementing
Cisco Unified Communications Manager, Part 1
© 2011 Ci sc o Sy s tems, Inc . All rights reserv ed. ITS v1.1—3

Course Goal and Objectives
This topic describes the course goal and objectives.
Course Goal
“Design, deploy, and support the Cisco

TelePresence meeting solution”
Implementing Cisco TelePresence Solutions
Upon completing this course, you will be able to meet these objectives:
 Describe a Cisco TelePresence solution and the technology that makes it work
 Describe and configure a Cisco TelePresence system endpoint
 Describe the Cisco TelePresence architecture
 Describe the extended features of Cisco TelePresence
2 Implementing Cisco TelePresence Solutions (ITS) v1.1 © 2011 Cisco Systems, Inc.
General Administration
Class-Related Facilities-Related
 Sign-in sheet  Course materials
 Length and times  Site emergency procedures
 Break and lunch room  Restrooms
locations  Telephones and faxes
 Attire
The instructor will discuss these administrative issues so that you know exactly what to expect
from the class:
 Sign-in process
 Starting and anticipated ending times of each class day
 Class break and lunch facilities
 Appropriate attire during class
 Materials that you can expect to receive during class
 What to do in the event of an emergency
 Location of the restrooms
 How to send and receive telephone and fax messages
© 2011 Cisco Systems, Inc. Course Introduction 3

Course Flow
This topic presents the suggested flow of the course materials.
Course Flow
Day 1 Day 2 Day 3 Day 4
Course
Introduction Cisco
A Cisco Cisco TelePresence
M Introduction to TelePresence TelePresence Extended System
Network Extended
Cisco Features
Architecture System Features
TelePresence (Cont.)
Lunch
Cisco Wrap Up
Cisco Cisco
TelePresence
P Call Control TelePresence TelePresence
M Network Extended
Architecture System Features
(Cont.) (Cont.)
The schedule reflects the recommended structure for this course. This structure allows enough
time for the instructor to present the course information and for you to work through the lab
activities. The exact timing of the subject materials and labs depends on the pace of your
specific class.
Additional References
This topic presents the Cisco icons and symbols that are used in this course
Cisco Icons and Symbols

Cisco
Cisco Unified
Cisco TelePresence Cisco
System Communications
TelePresence Manager ASA 5500
Primary Codec
System 500
Cisco
Cisco TelePresence Cisco Router
TelePresence System TelePresence
Sys tem 1000 or Secondary/HFR SBC
1100 Codec
Workgroup
Switch:
Cisco Voice-
TelePresence Cisco Cisco
TelePresence TelePresence Enabled
Sys tem 1300
Multipoint Recording
Series
Switch Server
Server
Cisco
TelePresence
Sys tem 3000 Cisco
Edge Label
TelePresence Switch
Cisco Manager Router Network
Cloud
TelePresenc e
System 3200
The figure shows the common icons that are used throughout this course.
© 2011 Cisco Systems, Inc. Course Introduction 5

Learner Introductions
 Name
 Company
 Job responsibilities
 Skills and knowledge
 Brief history
 Objective
Prepare to share this information:

 Your name
 Your company
 Your job responsibilities
 The prerequisite skills that you have
 A brief profile of your experience
 What you would like to learn from this course
Module 1
Introduction to Cisco
TelePresence
Overview
To thrive in the economy today, you need to collaborate instantly with colleagues, partners, and
customers around the globe. At the same time, you need to conduct your business to enhance
the quality of your relationships. In the past, building and maintaining crucial business
relationships meant expensive face-to-face meetings and productivity challenges, as well as
time spent away from home and family.
Cisco TelePresence creates a live, face-to-face communication experience over the network,
empowering you to collaborate as never before. The Cisco TelePresence experience embodies
three important principles: quality as good as being there, simplicity of use, and a low total cost
of ownership (TCO). Cisco TelePresence was designed to make you look and sound like you
do in person. Cisco TelePresence delivers rich, interpersonal interactions over the network.
Increased productivity, accelerated business transformations, and real, sustainable competitive
advantages are just a few of the benefits that can be gained by using Cisco TelePresence and
the network.
Module Objectives
Upon completing this module, you will be able to describe a Cisco TelePresence solution and
the technology that makes it work. This ability includes being able to meet these objectives:
 Describe the Cisco TelePresence experience and how it changes the way businesses
collaborate
 Define the components of a Cisco TelePresence solution
 Describe various Cisco TelePresence room design considerations and how they affect the
aesthetics and corporate identity of the room
1-2 Implementing Cisco TelePresence Solutions (ITS) v1.1 © 2011 Cisco Systems, Inc.
Lesson 1
Exploring the Cisco

TelePresence Solution
Overview
Cisco TelePresence creates a unique “in-person” experience by using innovative video, audio,
and interactive hardware and software elements over the network. Cisco TelePresence can help
people meet, share content, create high-quality video recordings and events, consult with
experts, and deliver powerful personalized services—all by using the power of the network for
an immersive experience. This lesson provides a high-level background of Cisco TelePresence.
Objectives
Upon completing this lesson, you will be able to list the Cisco TelePresence features and to
describe how Cisco TelePresence can change the way that you collaborate. This ability includes
being able to meet these objectives:
 Define telepresence and the use of technology to immerse a participant in the experience
 Identify the limitations of traditional video communications
 Explain the original design attributes for Cisco TelePresence
 Describe the Cisco TelePresence endpoint design principles
 Describe the advantages of the Cisco TelePresence solution
 Discuss the vision for Cisco TelePresence and how it can help create a next-generation,
rich-media network
 Discuss the high-level network requirements for Cisco TelePresence
 Provide a high-level overview of the NPA
What Is Telepresence?
This topic describes the industry-accepted definition of telepresence.
What Is Telepresence?
 Telepresence describes
technologies that allow
participants in a remote
location to feel present.
 Participants are fully
immersed, without being
aware of the technology.
 Voice, facial expressions,
and body movements are
transmitted in real time.
 Telepresence creates the
illusion of a face-to-face
conversation.
 Participants experience
nonverbal communication
from a remote location.
© 2011 Cis co S ys t em s, I nc. A ll rights res erved. IT S v1.1—1-2
The term telepresence is an industry-accepted definition of technologies that allow participants,

who might be thousands of miles apart, to feel as if they are in the same location. Because body
language provides more than 60 percent of what is being communicated, participants must be
fully immersed into the telepresence session without being aware of the technology that is used
to create the environment. This ability requires the telepresence system to transmit and display,
in real time, the position, voice, and body movements of each participant in each location, to
create the illusion of a face-to-face conversation.
Traditional Video Conferencing
This topic describes the limitations of traditional video conferencing and its failure to move out
of a niche market status.
Traditional Video Conferencing

Video conferencing has the following limitations:
 Does not feel as though you were in the room with remote participants
 Does not allow the participants to be seen and heard adequately
 Cannot replace a face-to-face meeting
 Is not heavily used or is not used at all
 Is not user-friendly
 Does not provide the experience that telepresence provides
You should not confuse telepresence with traditional videoconferencing. Traditional video
conferencing has not achieved an in-person experience and has failed for 15 years to move out
of a niche market status. Video conferencing typically uses analog video and mono audio that is
below CD quality. The participants must lean up to a microphone to talk and cannot be
adequately seen or heard, causing them to easily disengage from the meeting.
Because video conferencing cannot duplicate true eye contact, it does not provide the sensation
of being in the same room as the remote participants. The representation of the remote users on
the monitor is not a substitute for an actual face-to-face meeting. Video-conferencing
participants are constantly aware of the technology that they are using to collaborate. Because
of these limitations, many video-conferencing solutions are under-utilized or are not used at all.
© 2011 Cisco Systems, Inc. Introduction to Cisco TelePresence 1-5

Primary Attributes of Cisco TelePresence
This topic describes the primary attributes of the Cisco TelePresence solution.
Primary Attributes of Cisco

TelePresence
Cisco TelePresence combines high-definition video, high-
quality audio, and interactive elements to deliver an
in-person meeting experience over your IP network.
Cisco TelePresence is an innovative technology that lets you interact and collaborate with other
people, across remote locations, like never before. Using high-definition video, advanced
audio, and a finely tuned environment with the underlying network as the platform, Cisco
TelePresence delivers live, immersive, face-to-face experiences.
Cisco TelePresence gives you a way to balance business goals with corporate citizenship by
supporting environmental initiatives, such as reducing fuel use and emissions by offering a
truly viable alternative to travel. The technology can also help you address business-continuity
concerns by offering immediate, highly effective communications.
Cisco TelePresence allows you to feel as if you were in the same room with remote
participants, and it is simple to operate. Cisco TelePresence allows you to travel the world and
meet “in person” with customers, vendors, and partners— without leaving your office. Cisco
TelePresence delivers an experience that is as good as being there and can lead to greater
connection and understanding by delivering subtleties of communication in tone, facial
expressions, and body language.
Original Primary Design Attributes
The Cisco TelePresence experience was originally
designed to achieve the following mandated attributes:
 Present far-end participants in life-size format.
 Provide users with the ability to make virtual eye contact.
 Deliver high-quality video resolution that depicts a lifelike image.
 Break the virtual table, with no images other than people.
 Deliver audio that appears to emanate from the person speaking.
 Reproduce audio with the same fidelity as the original source.
 Allow users to speak at normal voice levels yet be heard by all
participants.
 Protect the spatial audio reproduction against pollution from other
nonvisible sources of audio.
The in-person experience that Cisco TelePresence creates incorporates the nonverbal human
factors that are missing in previous technologies. The virtual experience of being in one room is
invaluable in the decision-making process and improves the trust relationships with others by
allowing the face-to-face contact that is so important.
When developing the Cisco TelePresence solution, Cisco mandated the following design
attributes, which define the Cisco TelePresence experience:
 Present the far-end participants in life-size format.
 Provide users with the ability to make virtual eye contact.
 Deliver high-quality video resolution that depicts a lifelike image.
 Break the virtual table with no images other than people.
 Deliver audio that appears to emanate from the speaking person.
 Reproduce audio with the same fidelity as the original source.
 Allow users to speak at normal voice levels and yet be heard by all participants.
 Protect the spatial audio reproduction against pollution from other nonvisible sources of
audio.

Original Primary Design Attributes
(Cont.)
 Make establishing an unscheduled Cisco TelePresence call as
easy as making a phone call.
 Initiate scheduled Cisco TelePresence calls, with the push of a
single button.
 Make the technology invisible to the user.
 Guarantee every user a defined position at the virtual table, in his
or her own logical seat.
 Provide the reliability of a telephone call, when calling another
Cisco TelePresence endpoint.
 Require no building permits to install.
 Allow installation in two days or less, when all components are
present.
 Make establishing an unscheduled Cisco TelePresence call as easy as making a phone call.
 Initiate scheduled Cisco TelePresence calls, with the push of a single button.
 Make the technology invisible to the user.
 Guarantee every user a defined position at the virtual table, in his or her own logical seat.
 Provide the reliability of a telephone call, when calling another Cisco TelePresence
endpoint.
 Require no building permits to install.
 Allow installation in two days or less, when all components are present.
By adhering to the original primary attributes of Cisco TelePresence during product

development, Cisco created the ultimate communication solution, whether between chief
experience officers, employees, customers, partners, or suppliers. In a global marketplace,
executives and employees must be able to connect immediately, and experts must be able to
meet with customers, solve problems, and focus on global concerns.
Cisco TelePresence Endpoint Design Principles
This topic describes the Cisco TelePresence endpoint design principles.
Cisco TelePresence Endpoint

Design Principles
 Experience the meeting, not the
technology. Displays Cameras
 Life-size, high-definition display allows
participants to make eye contact and to
discern body language.
 Audio provides natural, multichannel,
full-duplex, spatial sound.
 Large display conveys IMAX-like
Microphones Environmentals
emersion.
 Unidirectional microphones reduce
background noise.
 Multiple audio channels provide
directional cues to locate the remote
speaker (on Cisco TelePresence 3000 Furniture
or 3200).
 Furniture design for the Cisco
TelePresence 3000 or 3200 places
user in optimal view of cameras.
Cisco TelePresence uses a new and innovative philosophy to ensure that you look and sound
the same in a Cisco TelePresence conference or meeting as you do in person. With high-quality
audio, high-definition video at low latency, and an optimized meeting environment, you can
communicate and converse in real time, catching every comment, gesture, expression, and
nuance of the conversation.
The goal is to create an in-person experience over the IP network infrastructure. Cisco
TelePresence focuses on the virtual experience that is achieved when communicating with
others at remote locations. The illusion of being in the same room—using life-size, high-
definition imagery—allows the participants to concentrate on the task rather than on logistics or
the severe limitations of legacy technologies.
The Cisco TelePresence System 3000 and Cisco TelePresence System 3200 include purpose-
built office furniture. This furniture incorporates cameras and displays, lighting, speakers,
microphones, and projection capability into a specially designed table, to place the user in
optimal view of the cameras.

IP Network as the Delivery Platform
 Hardware was designed with a network focus:
– Hardware combines multiple audio and video channels
into a single stream across an IP network.
– Revolutionary ASICs were designed for very low latency and
high definition.
 Multiple patents pending include video, audio, network integration,
and user experience.
 Innovative, fully integrated system leverages Cisco Unified
Communications systems and the network as the platform.
Cisco TelePresence technology was developed from the beginning to use standard IP
technology and to run on an integrated voice, video, and data network. Cisco TelePresence
coder-decoders (codecs) combine multiple audio and video channels into a single stream that is
transmitted across an IP network. To accomplish this seemingly impossible task, revolutionary
ASICs were designed to support high-definition traffic with very low latency. Cisco designed
the hardware to incorporate processors that could process high-quality and high-definition
video compression in real time. The goal was to use the IP and video expertise of Cisco to
develop the ultimate collaboration product, with a network focus. Cisco now has multiple
patents that are pending for video, audio, and network integration, to revolutionize the user
experience and the way that organizations collaborate across the network.
Cisco TelePresence was designed to take advantage of the tools that you use every day, to
integrate with enterprise groupware and unified communications so that scheduling and starting
meetings is extremely easy. There is no need for staff, training, menus, or manuals. With dial-
tone reliability and global connectivity, Cisco TelePresence provides far greater return on
investment (ROI) than traditional video communications. You can virtually be anywhere in the
world, at the touch of a button.
Advantages of Cisco TelePresence
This topic describes the advantages of the Cisco TelePresence solution.
Advantages of Cisco TelePresence

Cisco TelePresence Advantages Cisco TelePresence deploys into existing
customer rooms and facilities.
Cisco supplies the high-end technology, but the room

and environment belong to the customer.
Customers can create a personalized Cisco

TelePresence room experience that tailors to their
brands.
A broad range of aesthetic direction is available

within the Cisco TelePresence color palette.
Rooms integrate and blend with the corporate look

and the atmosphere of surrounding facilities.
© 2011 Cisco Systems, Inc. All rights reserved. ITS v1.1—1-9
Cisco TelePresence deploys into existing customer rooms and facilities with minimal room
remediation. Unlike other vendor solutions, there are no expensive construction requirements.
Although Cisco supplies the high-end technology, the room and environment belong to and
remain under the control of the customer. You can place a room that meets the requirements of
Cisco TelePresence anywhere in the organization. Customers can tailor the Cisco TelePresence
room experience to their brands.
A broad range of aesthetic direction is available within the Cisco TelePresence color palette,
which provides consistency throughout the Cisco TelePresence deployment. Rooms can easily
integrate and blend with the corporate look and the atmosphere of the surrounding facilities.

Shaping the Future of the Internet
This topic describes the vision that Cisco has for the Internet and the future of Cisco
TelePresence.
Shaping the Future of the Internet

 The Internet is transforming
the way people work, live,
play, and learn.
 Cisco TelePresence uses the
power of a global IP network.
 The network delivers a
telepresence experience that
is powerful, flexible, and easy
to use.
 The vision for Cisco
TelePresence is to provide
virtual experiences across the
Internet, in many
environments.
 This new technology will
influence how everyone uses
the Internet.
© 2011 Cis co S ys t em s, I nc. A ll rights res erved. I TS v1. 1— 1-10
The Internet is transforming the way that people work, live, play, and learn. In addition to a
network of computers, the Internet is a network of people and human connections. This
technology is revolutionizing many aspects of life.
Cisco TelePresence uses the power of a global IP network and unified communications to
enable collaboration between users like never before. The Cisco TelePresence system
seamlessly integrates with existing corporate networks and their communications technologies.
This integration makes the technology both easier to use and far more productive, by greatly
reducing the management, technical support, and training overhead that is associated with the
system.
The network delivers a telepresence experience that is powerful, flexible, and easy to use. This
approach sets the stage for Cisco TelePresence to become an everyday business tool. However,
the vision for Cisco TelePresence is also to provide virtual experiences in other environments—
experiences that are not possible using traditional video technologies. Cisco TelePresence can
eventually change how everyone collaborates and can influence how you use the Internet.
High-Level Network Requirements
This topic discusses the high-level network requirements for Cisco TelePresence.
Requirements for Cisco TelePresence

 Service level requirements: Measured end-to-end in each
– Latency ≤ 150 ms direction (not round trip)
– Jitter ≤ 50 ms
– Loss ≤ 0.05%
 Maximum bandwidth per second Cisco
– Cisco TelePresence Systems 500, 1000, TelePresence
1100, and 1300 Series = 5.5 Mb/s (at 1080p)
– Cisco TelePresence Systems 3000 and 3200
Traffic Profile
= 15.3 Mb/s (at 1080p)
Bytes
– Cisco TelePresence Multipoint Switch =
198 Mb/s (5.5 Mb/s * 36 sites)
 Average packet size and packets/second
33-ms Frame Intervals
– Average 1100 bytes per packet
 Cisco TelePresence Systems 500, 1000,  30 f/s
1100, and 1300 Series at 5.5 Mb/s =
average 625 p/s  Variable bit rate
 Cisco TelePresence Systems 3000 and  Large packet sizes
3200 at14.6 Mb/s = average 1740 p/s
 High packets/second
The Cisco TelePresence profile uses 30 frames per second (f/s), a variable bit rate, large packet
sizes, and a high rate of packets per second. Although the details of the Cisco TelePresence
service level requirements are still being defined through testing, initial tests have produced the
following requirements:
 Service level requirements
— Latency ≤ 150 ms
— Jitter ≤ 50 ms
— Loss ≤ 0.05 percent
 Maximum bandwidth per second
— Cisco TelePresence Systems 500, 1000, 1100, and 1300 = 5.5 Mb/s (at 1080p)
— Cisco TelePresence Systems 3000 and 3200 = 15.3 Mb/s (at 1080p)
— Cisco TelePresence Multipoint Switch = 198 Mb/s (5.5 Mb/s * 36 sites)
 Average packet size and packets per second
— Average 1100 bytes per packet
— Cisco TelePresence Systems 500, 1000, 1100, and 1300 at 5.5 Mb/s = average 625
p/s
— Cisco TelePresence Systems 3000 and 3200 at 14.6 Mb/s = average 1740 p/s
Note These values are measured end-to-end in each direction, not round trip, and do not include
a high frame rate (HFR) codec or interoperability.

High-Level NPA
This topic provides a high-level overview of the network path assessment (NPA).
What Is the NPA?

Customer Wants Implementation
Cisco TelePresence Success
Network
Remediation
Network Discovery Gap Analysis Remediation and

Phase Recommendations
 Infrastructure as sessment Data analysis, based on Final remediation and
– QoS strategies Cisco Advanced Services recommendation
best prac tices and design
– Hardware aspects for Cisco
– Campus LAN, W AN TelePresence:
– Software  Survey
– Bandwidth (high level)  Site analysis
 Path meas urement
– Latency, jitter, packet-loss
measurement
The NPA is a consultative process that prepares a customer network for broadband
deployments of Cisco TelePresence, both on the LAN and WAN. An NPA must be performed
before the deployment of Cisco TelePresence systems, to proactively detect common problems
and to help ensure the expected telepresence experience. The NPA leads to higher customer
satisfaction and has three major steps:
 Network discovery phase
— Infrastructure assessment
 Quality of service (QoS) strategies
 Hardware
 Campus LAN, WAN
 Software
 Bandwidth (high level)
— Path measurement
 Latency, jitter, and packet-loss measurement
 Gap analysis
— Data analysis that is based on Cisco Advanced Services best practices and design
aspects for Cisco TelePresence
 Survey
 Site Analysis
 Remediation and recommendations
Summary
This topic summarizes the key points that were discussed in this lesson.
Summary
 Telepresence is an industry-accepted term that describes
technologies that provide an in-person collaboration experience.
 Telepresence should not be confused with traditional video
conferencing, which failed to move out of its niche market.
 Cisco TelePresence combines high-quality audio, high-definition
video, and interactive elements to deliver an in-person meeting
experience over the customer IP network.
 The innovative philosophy of Cisco TelePresence was designed and
built to provide a fully integrated system.
 The Cisco TelePresence solution provides many advantages, using
the existing customer facilities and IP network.
 Cisco TelePresence will shape the future of the Internet by providing
virtual experiences in many environments.
 The Cisco TelePresence profile uses 30 f/s, a variable bit rate, large
packet sizes, and high rate of packets per second.
 The NPA has three major steps: network discovery phase, gap
analysis, and remediation and recommendations.

Lesson 2
Exploring the Cisco

TelePresence Environments
Overview
This lesson provides an overview of the Cisco TelePresence components that use ultrahigh-
quality, two-way video and audio to revolutionize remote collaborations, pioneering a new
form of digital communications that rivals the effectiveness of “in-person” meetings.
Objectives
Upon completing this lesson, you will be able to describe the Cisco TelePresence solutions.
This ability includes being able to meet these objectives:
 List the components of the Cisco TelePresence solution and which role each component
fulfills
 Identify the endpoints in the Cisco TelePresence portfolio and describe the level of
experience that each model provides
 Discuss the wiring for the Cisco TelePresence generation 2 primary codec
 Describe the acoustic properties of the Cisco TelePresence room
 Describe the Cisco TelePresence illumination specifications
 Describe the Cisco TelePresence Auto Collaborate feature
 Describe the capabilities of the Cisco TelePresence Multipoint Switch
 List the capabilities of the Cisco TelePresence Recording Server
 Define the capabilities of Cisco TelePresence Manager
 Describe the Cisco TelePresence experience, as well as video and audio characteristics
 Define the Cisco TelePresence architecture for intercompany communications
 Discuss the purpose of the Cisco TelePresence Planning, Design, and Implementation
Service
The Cisco TelePresence Solution
This topic describes the overall Cisco TelePresence solutions.
The Cisco TelePresence Solution

Cisco • Group and executive
TelePresence • Auto Collaborate peripherals
Systems • Integrated voice and data
Cisco TelePresence Solution
• Next-generation multipoint switching

Multipoint • Cisco Unified Videoconferencing interoperability
Collaboration • Cisco Unified MeetingPlace, and Cisco WebEx
integration
Management • Cisco Unified Communications Manager

& Scheduling • Cisco TelePresence Manager
• QoS
Network as • Routing and switching
the Platform • NAT and firewall traversal
• Cisco SBC
Cisco • Plan, design, and implement
Lifecycle • Room and network readiness assessments
• Cisco TelePresence experience verification
Services • Remote operations services
• High-definition recording studio
Recording • Intuitive user interface
Server • Delivery of high-quality video
• Easily distributed and viewed video content
As a breakthrough technology for remote meetings, Cisco TelePresence integrates advanced

audio, high-definition video, and interactive elements with the power of the underlying
network, to deliver an immersive meeting experience. Through a powerful combination of
technologies and design that allows you and remote participants to feel as though you are all in
the same room, Cisco TelePresence has the potential to transform your business.
The life-size images and amazing clarity allow you to see every expression; the rich, CD-
quality audio allows you to hear every word. The ease of use and the integrated, optimized
environment make scheduling and launching calls easy: Simply push one button. Integration
with the highly available Cisco network offers reliability, quality of service (QoS), Network
Address Translation (NAT), and security. This integration gives you the confidence to use
Cisco TelePresence for both internal and external meetings. The Cisco Session Border
Controller (SBC) bridges a connection between two separate Multiprotocol Label Switching
(MPLS) virtual private networks (VPNs), to perform secure inter-VPN communication between
enterprises.
Cisco TelePresence comes to market with a wide product breadth:

 Cisco TelePresence solutions for either a group or executive office
 High-definition multipoint video switch for multisite interactivity
 Management and scheduling software solutions that simplify the experience
 Middleware that is the connection to your network and Cisco IP Unified Communications
platforms
 Cisco Lifecycle Services that are specially designed to enhance the Cisco TelePresence
experience
 Cisco TelePresence Recording Server, which transforms endpoints into high-definition
recording studios

Cisco TelePresence Solution
Components
Management and Calendaring Components
Extended Reach at
Interoperability 720p Using Lower Cisco
with Most Video- Bandwidths Cisco Unified TelePresence
Conferencing Communications Recording
Endpoints Manager Cluster Server
Call Control Mul tipoint
Network Infrastructure
Cisco TelePresence Cisco TelePresence

System Endpoi nts
System Endpoints
Microsoft Outlook
Microsoft Active Microsoft Cisco Cisco Unified
Lotus Notes Exchange Server Tel ePresence
Client Directory Contact Center
Domino Directory IBM Lotus Domino Manager
Cisco TelePresence takes advantage of the enterprise groupware and unified communications
tools that you use every day, so scheduling a Cisco TelePresence meeting is as simple as
booking a meeting. The simple and intuitive user interface eliminates operational overhead and
costs so that your organization can focus on opportunities.
Cisco TelePresence uses an Intelligent Network (IN) architecture, with innovative services,
integrated security, and industry-leading reliability, to connect internally and with external
people or organizations. As the leading global provider of IP networks, Cisco is uniquely
qualified to deliver secure, intercompany Cisco TelePresence connectivity over your existing
enterprise and service provider IP networks. Using transparent multipoint intercompany and
intracompany services, you can effortlessly and securely communicate with your colleagues,
customers, and partners in other Cisco TelePresence locations, including public Cisco
TelePresence suites around the globe.
Integration with Cisco Unified Communications enables easy call launch and telephony
features such as hold, mute, and conference, as well as applications such as Cisco Unified
Contact Center. Cisco TelePresence Expert on Demand combines any Cisco TelePresence
endpoint with Cisco Unified Contact Center, offering a powerful contact-center application so
that organizations can scale the expertise of their employees to provide instant in-person
customer service.
Taking the Cisco TelePresence experience beyond meetings, Cisco TelePresence Recording
Server cost-effectively transforms meeting rooms into high-definition recording studios, in
which you can create and distribute high-quality video.
Using Cisco TelePresence Extended Reach, you can now have a Cisco TelePresence experience
at 720p resolutions, using lower bandwidths or alternate access connections. Cisco
TelePresence Extended Reach provides 30 frames per second (f/s) and low-latency
performance, which is crucial to providing an immersive experience, with minimal effect on
picture quality.
Interoperability with standards-based video conferencing allows Cisco TelePresence endpoints

to communicate with virtually all video-conferencing endpoints that are installed today.

Cisco TelePresence Endpoint Portfolio
This topic describes the collection of Cisco TelePresence endpoints.
Cisco TelePresence Endpoint Portfolio
Cisco Cisco Cisco Cisco Cisco

TelePresence TelePresence TelePresence TelePresence TelePresence
System 500 System 1000 Systems 1100 System 3000 System 3200
1–2 Seats 1–2 Seats and 1300 Series 6 Seats 14–18 Seats
2 or 6 Seats
 Flexible use  High  One screen  High  Transforming

immersion immersion governance
 Private office  High process
 Flexible immersion  Transforms
 Telecommuter
deployment business  Distanced
 Rapid
process learning
deployment
Personal Multipurpose Group or Team
Cisco TelePresence comprises several endpoint models to meet many types of meeting needs:
 The Cisco TelePresence System 3200 is a purpose-built room for large group meetings and
has been enhanced with specially designed tables, to seat as many as 18 participants per
room.
 The Cisco TelePresence System 3000 is a purpose-built room for business meetings. This
model has a specially designed table that seats six participants on one side of the virtual
table, using three screens and three cameras.
 The Cisco TelePresence System 1300 Series is designed for group meetings in
multipurpose conference rooms with as many as six participants per room, using one screen
and three cameras. The Cisco TelePresence System 1100 uses the same hardware as the
Cisco TelePresence System 1300 Series but has only one camera and supports only two
participants.
 The Cisco TelePresence System 1000 is designed for one or two users. This system works
for small group meetings and one-on-one conversations in a multipurpose conference room.
 The Cisco TelePresence System 500 has a smaller footprint that is designed for one or two
users and gives organizations the flexibility to deploy the application within personal
offices.
These endpoints work with the complete Cisco TelePresence solution to provide the following:
 Easy call scheduling and setup
 Scalable, zero-latency multipoint calls
 Secure intercompany communications
 A host of compelling collaboration applications that scale different meeting types, high-
definition broadcasting, and industrial applications

Cisco TelePresence System 3200
This subtopic describes the Cisco TelePresence 3200.

 14 to 18 seats
 Custom-built room
 1080p and 720p high
definition
 Three 65-in. plasma
displays
 Spatial wideband audio
 Imperceptible latency
 Available upgrade kit
The Cisco TelePresence 3200 brings the power of Cisco TelePresence technology to larger-
room venues. The Cisco TelePresence 3200 allows large teams to meet and collaborate
virtually. You can use Cisco TelePresence when much of the team is in one physical location,
making this model ideal for headquarters sites or large regional offices.
With seating that can accommodate 14 to 18 participants in one room, the system delivers the
same superior video and audio quality as the rest of the Cisco TelePresence portfolio.
Applications for the Cisco TelePresence 3200 include large team meetings, cross-functional
team meetings, and training or classroom events. Cisco TelePresence can now scale to fit the
wide range of meeting needs of your organization.
The Cisco TelePresence 3200 is ideal for large group meetings that have many participants in
one location, connecting to other satellite groups in remote locations. The system provides an
equal seat at the table for participants of these types of applications:
 Operations reviews
 Status-update meetings
 Quarterly meetings with clients or partners
 Executive presentations
 Meetings that require staff to be present
Note You can update the Cisco TelePresence 3000 to the Cisco TelePresence System 3200, by
using an upgrade kit.

 Six seats
 Purpose-built room
definition
 Three 65-in. plasma
displays
 Spatial wideband audio
The Cisco TelePresence 3000 provides a boardroom-style table that seats six participants in one
room. The system provides an optimized experience by using the following integrated
equipment, all of which has been specially tuned for the large-group environment:
 Three 65-inch plasma screens
 Spatial audio
 Microphones
 Lighting
 Integrated Ethernet and power
 Multiple ultrahigh-definition coder-decoders (codecs) and cameras
The Cisco TelePresence 3000 is ideal for large group meetings, comfortably seating
participants around a virtual table for applications such as customer engagements, presentations
to groups, supply-chain dealings, press briefings, operational or engineering reviews,
negotiations, or regular team meetings.

Cisco TelePresence Systems 1100 and 1300
This subtopic describes the Cisco TelePresence 1100 and Cisco TelePresence 1300 Series.
Cisco TelePresence Systems

1100 and 1300 Series
 Two or six seats
 General-purpose rooms
 Immersive 1080p experience
 Single 65-in. display
 One or three cameras
The Cisco TelePresence 1300 Series provides a flexible option for organizations that want to
scale Cisco TelePresence to more global locations. This model uses a single 65-inch, 1080p,
high-definition plasma screen with three cameras; the model can support meetings with as
many as six people in a regular conference room. This system provides effortless participation
with automatic segment switching, which allows meeting participants to focus on business
needs rather than the meeting technology.
With the Cisco TelePresence 1300 Series, you can use almost any conference room with its
existing table. Built-in support for audio conferencing and display for presentations provide
extra value. Bandwidth needs are reduced to a single video stream of the active speakers, to
optimize return on investment (ROI).
The Cisco TelePresence 1300 Series includes the Presentation-in-Picture (PiP) mode, which is
suitable for space-constrained environments.
The Cisco TelePresence 1100 uses the same hardware as the Cisco TelePresence 1300 Series.
However, the Cisco TelePresence 1100 has only one camera and supports only two people in a
regular conference room.

 Two seats
 General-purpose room
definition
 65-in. plasma display
 Wideband audio
The Cisco TelePresence 1000 accommodates two participants in a single room. Integrated
equipment for an optimized user experience includes the following, which have been specially
tuned to the small-group environment:
 One 65-inch plasma screen
 A speaker and microphone with echo cancellation
 Lighting
 An ultrahigh-definition codec and camera
The Cisco TelePresence 1000 is ideal for small group meetings, such as customer engagements,
supply-chain dealings, negotiations, job interviews, engineering reviews, one-on-one meetings,
or team meetings.


 One or two seats
 General-purpose room
definition
 37-in. LCD display
 Wideband audio
The Cisco TelePresence 500 brings the virtual in-person experience of Cisco TelePresence
directly into the private office. The Cisco TelePresence 500 creates a category of Cisco
TelePresence called personal TelePresence, which allows individuals, subject matter experts
(SMEs), and executives to join Cisco TelePresence calls, with equal stature. The participant
using the Cisco TelePresence 500 appears life-size on the Cisco TelePresence 3000 and other
endpoints.
The Cisco TelePresence 500 is ideal for joining large, multilocation group meetings, such as
operational reviews, status-update meetings, and quarterly customer presentations. The system
also supports personal meetings such as negotiations, job interviews, and personnel reviews.
You can integrate the Cisco TelePresence 500 with Cisco Digital Media System, which is a
comprehensive suite of digital signage, Cisco Enterprise TV, and desktop video applications.
You can integrate external video sources into a Cisco TelePresence meeting or you can use the
Cisco TelePresence 500 for other purposes.
The Cisco Digital Media Player (DMP) is an integrated component of the Cisco Digital Media
System. The Cisco DMP is a highly reliable, IP-based hardware endpoint that enables digital
signage and enterprise TV through the ability to play high-definition, live and on-demand
video, motion graphics, web, and dynamic content on digital displays. The Cisco DMP
hardware options include support for standard-definition and high-definition MPEG-2 and
MPEG-4/H.264, Flash, Really Simple Syndication (RSS), and other web formats and dynamic
data.
Cisco TelePresence System 500 (Cont.)
Unique features:
 Personal telepresence
– Compact solution
– Ease of installation
 Multipurpose 37-in. LCD
– Embedded speaker
– Embedded microphone
 Embedded camera
 Auto Collaborate
– PiP or external display
 Cisco Unified IP Phone 7975G
 Can be integrated with Cisco
Digital Media System
The smaller footprint of the Cisco TelePresence 500 gives organizations the flexibility to
deploy Cisco TelePresence within personal offices, to support remote one-on-one meetings or
to join large multipoint Cisco TelePresence calls. The Cisco TelePresence 500 delivers the
same award-winning video, audio, and environmental elements that create the immersive, face-
to-face experience across the entire Cisco TelePresence portfolio.
Although the Cisco TelePresence 500 is built on the same core technology as all of the Cisco
TelePresence endpoints, the Cisco TelePresence 500 differs in four ways:
 The 37-inch LCD display and streamlined speakers have a smaller footprint.
 A specially designed microphone is built into the bezel of the display.
 The camera uses a wider-angle lens that allows the user to sit closer to the system.
 You accomplish data or graphics content sharing by using an external monitor or PiP
format for space-constrained offices.
Note The Cisco TelePresence 500 comes with a Cisco Unified IP Phone 7975G.
The Cisco TelePresence 500 uses the same camera as the other Cisco TelePresence endpoints
but uses a wider-angle lens. This lens enables the user to sit closer to the unit: 4 to 6 feet away,
rather than the 8.5 feet that the other Cisco TelePresence endpoints require. This distance is a
comfortable conversation distance in a typical office configuration.
The Cisco TelePresence 500 uses the same codec and camera cluster as the other Cisco
TelePresence endpoints but uses a different lens. The system also uses the same data
collaboration, One-Button-to-Push meetings, impromptu calling, and multipoint capabilities.

The Cisco TelePresence 500 is optimized to project one or two users, with complete
telepresence audio and video quality, to any Cisco TelePresence endpoint. The Cisco
TelePresence 500 uses an immersive design with speakers and a specially designed microphone
that is built into the bezel of the display, eliminating cables. When users face the Cisco
TelePresence 500 display, they directly face the camera, microphone, and speakers.
The Cisco TelePresence 500 offers an elegant design with a 37-inch display, camera,
microphone, speakers, and lighting that require a small footprint. This sophisticated, discreet
interface is suited for private and executive offices.
The Cisco TelePresence 500 is available in the following configurations:

 Free-standing pedestal
 Desktop
Note Although the Cisco TelePresence 500 can be wall mounted, Cisco does not ship a wall-
mount kit.
The flexible options of the Cisco TelePresence 500 make it easy to install with little or no room
remediation or construction costs. One person can perform a typical installation in 1 hour.
The Cisco TelePresence high frame rate (HFR) codec is an optional graphics-sharing feature
that adds a dedicated presentation codec to enable high-frame-rate autocollaboration at 30 f/s.
People in all rooms can instantly see and share information or objects with others, simply by
plugging in a device such as a laptop computer or the optional, integrated, high-definition
document camera.
Cisco TelePresence Generation 2 Wiring Diagram
This topic discusses the wiring for the Cisco TelePresence generation 2 primary codec.
Cisco TelePresence Generation 2

Primary Codec
Left Speaker (Out) Document Camera Control
Center Right Speaker (Out)
Speaker (Out) Main Video (Out)
Right Secondary Codec
Left Sec ondary Codec
PC Video (In)
Unused
Cisco
TelePresence Audio/Video Auto Collaborate Video (Out)
System 500 Extension Unit Document Camera Video (In)
Headset
(In/Out) Main Camera Video (In)
Center Front Microphone (In) Main Camera Control
PC Audio/DMP Audio (In) To Cisco Unified IP Phone 7975G

To Network
The generation 2 primary codec is the interface between the Cisco TelePresence system and the
network infrastructure. The primary codec connects to the network access edge switch via an
RJ-45 10/100/1000 port. The access edge switch to which the codec connects provides IP
services, IEEE 802.1Q/p and VLAN services, QoS services, and security services to the Cisco
TelePresence endpoint.
Additionally, the primary codec has an RJ-45 connection to the Cisco Unified IP Phone 7975G,
to which the codec supplies IEEE 802.3af Power over Ethernet (PoE). When the IP phone
boots, it sends a Cisco Discovery Protocol message to the primary codec. The codec receives
this message and passes the message on to the access edge switch, supplementing the message
with its own Cisco Discovery Protocol advertisement. The access edge switch and codec
exchange Cisco Discovery Protocol messages. The switch (if configured according to best-
practice recommendations for IP telephony deployments) places the primary codec and the
Cisco Unified IP Phone 7975G in an 802.1Q voice VLAN, wherein 802.1Q/p class of service
(CoS) markings are trusted. The primary codec passes 802.1Q tags between the Cisco Unified
IP Phone 7975G and the network access edge switch, extending the voice VLAN all the way to
the IP phone.
The generation 2 primary codec has the following ports:

 Center, left, and right speakers out (one unused speaker port)
 PC audio/DMP audio (in)
 Cisco TelePresence 500 headset (in/out)
 Center front microphone (in)
 Audio/video extension unit (for all other microphones)

Acoustic Properties
This topic describes the acoustic properties of the Cisco TelePresence room.
Acoustic Properties
 Ambient noise (based on the three
participant zones) 45 dBA
 HVAC 45 dBA
 Reverberation
– 500 Hz–2 kHz critical < 500 ms
– 125–250 Hz and 4 kHz
noncritical voice < 700 ms
 Privacy to adjacent areas
 Volume level on endpoint
 In-call volume levels
 Speech intelligibility
 Frequency response
 Sustained sound quality end to end
Controlling the acoustic properties of the Cisco TelePresence room is essential in creating an
environment that provides the ultimate virtual experience. You can control ambient noise levels
and reverberation through recommended room remediation. These recommendations include
types of ceiling lights and acoustic wall treatments.
Acoustic recommendations include the following:

 Walls: The audio subsystem is designed to deliver excellent performance for normal
drywall room surfaces. Standard sheetrock (drywall) walls with a smooth finish are
preferred; walls and wall coverings with a heavy texture are highly discouraged. Cinder
block and brick can be highly reverberant and therefore will likely require acoustical wall
treatment. Also, thin walls and doors can allow unwanted sound to leak into the room from
adjoining rooms, reducing the quality of the experience.
 Ceiling: Standard business-office acoustic ceiling tiles help absorb reverberation and
unwanted sound.
 Flooring: Standard office carpeting is recommended. Sound-reflective surfaces such as
linoleum and hardwood will likely require carpeting to reduce reverberation.
 Heating, ventilation, and air conditioning (HVAC): The cooling and heating systems are
required to compensate for heat that is dissipated by the system. This requirement generally
requires much airflow, which can generate unwanted sound. Special sound-dampening
registers and baffles can help reduce this noise.
Illumination Properties
This topic describes the Cisco TelePresence illumination specifications.
Illumination Specifications
 Light measurements much more detailed during Cisco
TelePresence experience certification process
 12 zones on vertical plane 250–300 lux
 Six zones for horizontal plane < 700–800 lux
 Participant zone within tolerance to adjacent zones 150 lux
 Vertical vs. horizontal
 Lighting facade levels
Dispersed light that is centered over the telepresence table (rather than directly over the
monitors or behind the participants) is highly desirable. Color temperature is also an important
factor because it helps to unify the environment and provide a higher-quality experience. The
following are recommendations for the illumination of the Cisco TelePresence room:
 Fixtures: The room should use 100-percent indirect fluorescent fixtures that provide 250 to
300 lux of vertical face lighting.
 Bulbs: Bulbs must be high wattage, 4100-Kelvin, fluorescent bulbs. This lighting is best
for true color comparison, facial detail, and the overall experience.

Cisco TelePresence Auto Collaborate
This topic describes Cisco TelePresence Auto Collaborate options.
Cisco TelePresence Auto Collaborate

 Auto Collaborate enables you to
share graphics from a laptop or
objects via a document camera.
 Auto Collaborate is “plug-and-
play.”
 The images are automatically
displayed for all sites in the
meeting.
 Auto Collaborate uses the
fourth (auxiliary) video channel.
– H.264 video codec
– Input resolution 1024 x 768 at
60 Hz
– 5 f/s
– Optional HFR codec at 30 f/s
The Auto Collaborate feature of Cisco TelePresence supports simple information sharing that
allows you to display any object, document, or PC application in a “plug-and-play” fashion,
which means that the feature will work as soon as it is active in the network. Auto Collaborate
enables you to share images instantly in multiple locations by plugging in a laptop computer or
high-definition, ceiling document camera. The built-in projector of the Cisco TelePresence
3200 and Cisco TelePresence 3000 automatically displays images from the most recently
activated device at 5 f/s, using the fourth (auxiliary) video channel on the codec.
Note An optional HFR codec supports 30 f/s.
Ceiling cameras are perfect for capturing images of objects that are too valuable to ship or that
cannot easily be copied or sent electronically. Cisco recommends and supports document
cameras that are made by WolfVision, specifically the WolfVision Visualizer products. The
WolfVision Visualizer is a special live-camera system that is designed to pick out any object on
a working surface, with perfect illumination and depth of focus. The WolfVision Visualizer can
quickly and easily pick out all types of objects, such as photos, books, brochures,
transparencies, slides, or three-dimensional objects. Meeting participants can use a wireless
remote to control the light, zoom, or focus. The ceiling document camera is not supported on
the Cisco TelePresence 1300 Series.
Cisco TelePresence Systems 3200, 3000, 1300 Series, 1100, and 1000 support the Auto
Collaborate feature. This feature allows meeting organizers to project content in multiple
locations, including above or below displays or on the side of a room. Data collaboration on the
Cisco TelePresence 500 is supported through an external monitor or the PiP feature. An
additional display is not required for PiP because the autocollaborated video is displayed on the
LCD. The user can toggle the position of the PiP between the center, left, or right locations on
the screen by using the telephone user interface (TUI).

The Cisco TelePresence Multipoint Switch
This topic describes the functionality of the Cisco TelePresence Multipoint Switch.
Cisco TelePresence Multipoint Switch

 Supports Cisco TelePresence meetings for more than two
endpoints
 Supports as many as 48 segments
 Provides software-based low latency switching
(less than 10 ms)
 Allows scheduling of multipoint meetings with the
One-Button-to-Push feature
 Is interoperable with systems other than
Cisco TelePresence
 Supports video-conferencing interoperability with H.323 and SIP
video-conferencing endpoints
The Cisco TelePresence Multipoint Switch is an affordable, purpose-built appliance that is easy
to install and that offers superior scalability, with as many as 48 segments in a single meeting.
The Cisco TelePresence Multipoint Switch is ideal for organizations that have geographically
dispersed teams and that want to quickly and easily include, in one meeting, participants at
three or more locations. One-Button-to-Push meetings with the in-room Cisco IP phone can
launch scheduled or nonscheduled meetings for the following:
 As many as 48 single-screen Cisco TelePresence systems
 16 three-screen Cisco TelePresence systems
 A combination of both single-screen and three-screen systems in one meeting
The Cisco TelePresence Multipoint Switch is a software-based solution that integrates with the
Cisco TelePresence Manager software and provides easy meeting scheduling through enterprise
groupware, such as Microsoft Outlook or IBM Lotus Notes. Because you can start multipoint
meetings with just a push of a button on the meeting room phone, support personnel do not
need to set up meetings for you. A Session Initiation Protocol (SIP) trunk provides support for
Cisco Unified Communications Manager communications.
Voice-activated switching maintains spatial audio and seating locations on screen, as switching
occurs. This switching has a latency of less than 10 ms, to provide transparent switching
between rooms (sites) or speakers (table segments) during a multipoint call.
The Cisco TelePresence Multipoint Switch is a standards-based platform that uses SIP
signaling, H.264 high- and standard-definition video, and advanced audio coding with low
delay (AAC-LD) and G.711 audio. The H.264 video codecs offer native high-definition
resolution at 1080p and 720p. Video-conferencing interoperability is supported through H.323
and SIP video-conferencing endpoints. The data-sharing and autocollaboration feature is
available to share images with all the other participants and rooms.

Cisco TelePresence Interoperability
 By cascading the Cisco TelePresence Multipoint Switch with the
Cisco Unified Videoconferencing 5200 Series, you can provide
interoperability between Cisco TelePresence and standard-
definition video conferencing and video telephony.
– Maintains rich, immersive experience between Cisco
TelePresence participants
– Provides a bridge to existing video-conferencing and video-
telephony devices
Ci sco TelePresence Cisco Unified

Mul tipoint Swi tch Vi deoconferencing
Cisco TelePresence interoperability is supported through the Cisco TelePresence Multipoint

Switch and Cisco Unified Videoconferencing 5200 Series, which also support multipoint for
standard video-conferencing streams via the Cisco Unified Videoconferencing 5200 Series.
This feature provides a transition strategy for companies to migrate from existing video
conferencing to immersive visual communications.
With Cisco TelePresence interoperability, the meeting preserves the experience for Cisco
TelePresence users, while allowing standards-based video-conferencing users to participate in
the meeting. This ability provides seamless interoperation with more than 90 percent of existing
video-conferencing equipment.
Cisco TelePresence Recording Server
This topic describes the Cisco TelePresence Recording Server.
Cisco TelePresence Recording Server—

Specifications
 Supports 24 simultaneous
Cisco TelePresence recording
or playback sessions
 Stores as many as 300 hours
of 1080p high-definition video
content along with the data
presentation channel and CIF
version for PC browser
playback
 Builds on Cisco MCS 7845
Series platform (Linux-based)
 Plays back on Cisco
TelePresence System or PC
 Controls recording from phone
The Cisco TelePresence Recording Server transforms the Cisco TelePresence system into a
high-definition recording studio. The server has an intuitive user interface that enables you to
create high-quality video to immediately deliver rich, immersive messages for internal and
external communications, such as training or crisis management. Distributing and viewing
video content is easy, and you can replay recordings on Cisco TelePresence endpoints or on the
web, by using standard browser-based players.
The recording capability creates a category of experience for Cisco TelePresence technology
that takes the solution beyond meetings. Studio-mode operation provides onscreen prompting
and visual aids that make the recording experience comfortable and easy to use. Recorded
content is ready for immediate playback, allowing you to review the recorded session upon
completion; you can then distribute that content to the appropriate parties.
The Cisco TelePresence Recording Server is built on the Cisco Media Convergence Server
(MCS) 7845 Series and is a Linux-based solution. The Cisco TelePresence Recording Server
stores as many as 300 hours of 1080p high-definition video content, along with the data
presentation channel and Common Intermediate Format (CIF) version for PC browser
playback. Because of the easy-to-use, intuitive Cisco IP phone interface that the Cisco
TelePresence Recording Server uses, you do not need any training to take advantage of the new
features.

Cisco TelePresence Manager
This topic describes Cisco TelePresence Manager.

 Calendaring integration and management
 Middleware connection between Cisco TelePresence Systems,
Cisco Unified Communications Manager, and corporate
calendaring systems
 One-Button-to-Push feature, to access scheduled meetings
 Resource and location management for multipoint services
 Helpdesk and Live Desk services
Cisco Unified Control Exchange Server/
Communications Lotus Domino
Manager LDAP
Cisco TelePresence
Manager
Multipoint
Application Endpoints
Cisco TelePresence Manager is the connection between Cisco TelePresence, the Cisco network,
and Cisco Unified Communications platforms. Cisco TelePresence Manager is essential for
delivering the complete value of Cisco TelePresence. This software collects information about
Cisco TelePresence systems from Cisco Unified Communications Manager and associates
those systems to their physical locations, as defined in Microsoft Active Directory and
enterprise groupware. Cisco TelePresence Manager also automatically collects information
about multipoint capabilities and allocates those resources when needed, allowing you to
schedule both point-to-point and multipoint Cisco TelePresence meetings from Microsoft
Outlook or Lotus Notes. Calendaring meeting information is automatically sent to the Cisco
TelePresence in-room phone.
To provide ease of use for the customers, Cisco TelePresence Manager enables you to use
enterprise groupware to schedule rooms. The Cisco Unified IP Phone 797xG user interface
displays the daily agenda on the phone. The participants simply use the One-Button-to-Push
feature to launch a Cisco TelePresence session. Cisco Unified Contact Center integration
provides virtual Live Desk services, and Cisco Unified Communications Manager manages the
Call Detail Record (CDR) and reporting.
Cisco TelePresence Manager uses the same platform infrastructure as Cisco Unified
Communications Manager Release 5.1(2b) uses, following its appliance model principles. The
Cisco TelePresence Manager administrative user interface is a single software that provides
access to a web-based GUI for initial setup and installation. You retrieve information by using
standard interfaces such as XML, Simple Object Access Protocol (SOAP), computer telephony
integration (CTI), and Web-Based Distributed Authoring and Versioning (WebDAV). Cisco
TelePresence Manager is loaded on a Cisco MCS 7845 MCS system and is run as a standalone
application. The software cannot be deployed coresident with any other Cisco application on
that hardware.

Cisco TelePresence Connectivity and Experience
Options
This topic describes the Cisco TelePresence experience and resolution levels.
Cisco TelePresence Connectivity and

Experience Options
Cisco TelePresence Experience and Resolution
Extended Reach Optimized Immersive
 Working sessions  Internal meetings  Business decisions
Meeting  Immersiv e and  Operations reviews  Board meetings
optimized meetings  Crucial intercompany
type with remote  One-on-one meetings
meetings (customers,
participants  Supplier engagements partners, job interv iews)
 Home office  Corporate campus
Location  Small office
 Branch office
 Regional office
 Multiscreen  Multiscreen
Endpoint  Single sc reen
 Single s creen  Single screen
 T1/E1 with QoS
 Premium broadband  MPLS, DS3, and high-
Network (FiOS, c able) with capacity networks with QoS  MPLS, DS3, and high-
types separate support capacity networks with QoS
 Bonded
BondedT1/E1
T1/E1
model—best effort
only
 720p Lite
Resolution  720p Good  720p Good/Better/Best  1080p Good/Better/Best
You can deploy Cisco TelePresence systems in your enterprise, at several experience levels that
support 720p and 1080p resolutions and at one of three quality levels, with bandwidth ranges of
2 to 5 Mb/s per screen. These quality levels help to ensure an optimized Cisco TelePresence
experience and are fully supported through installation and operate services:
 Extended Reach: The Cisco TelePresence Extended Reach option enables customer sites
where Cisco TelePresence systems have had limited presence. You can now enable small
offices or home offices, where high-capacity bandwidth is unavailable or too costly, with
one single-screen Cisco TelePresence system, to enable SMEs or remote executives to join
Cisco TelePresence meetings. It can run across premium broadband network connections,
such as cable and Verizon fiber-optic service (FiOS).
 Optimized: A Cisco TelePresence Optimized meeting maintains ease of use and a quality
experience so that branch offices can communicate effectively with headquarters and each
other, through 720p resolution and lower bandwidth requirements. Operations reviews,
one-on-one meetings, and internal meetings are now possible on multiscreen and single-
screen Cisco TelePresence systems at remote locations.
 Immersive: A Cisco TelePresence Immersive meeting is a first-class immersive experience
for business decision meetings within the company and with external parties, such as
customers and vendors. This experience provides 1080p resolution and life-size video
images. This environment is ideal for corporate campuses and regional offices with
multiscreen and single-screen Cisco TelePresence systems. Cisco created a market category
with extraordinarily high usage rates, with the Cisco TelePresence system operating at
1080p.
Intercompany Communications
This topic describes intercompany communications that use Cisco TelePresence.
Intercompany Communications
QoS Enabled MPLS Network—Secure End-to-End
Intercompany
Cisco TelePresence
Service
Customer A Customer B
Headquarters MPLS MPLS Headquarters
VPN VPN
Service Provider
Network
Customer B
Branch Customer B
Branch
To support intercompany communication through Cisco TelePresence, Cisco introduced a

solution that enables service providers to introduce a commercial offering with value-added
services. Solution features include call processing, dial-plan management, and endpoint
authentication and encryption and in the future will include universal directory services and
fully automated scheduling.
Service providers will be able to offer differentiated Cisco TelePresence services to enterprise
customers and develop their own commercial, intercompany Cisco TelePresence services. The
solution is the first of several from Cisco that will enable service providers to build Cisco
TelePresence dial tone. This feature gives enterprise customers the ability to connect directly to
each other via Cisco TelePresence, as easily as they can now connect via the phone, with future
additional services and features. This ability is a step toward enabling global public Cisco
TelePresence networks.
As the demand for more Cisco TelePresence endpoints grows, service providers will not only
be able to offer bandwidth services but also hosted and other managed services. Service
providers are likely to come to market quickly with a basic offering and to add additional
capabilities for intercompany Cisco TelePresence communications over time.
The Cisco TelePresence solution for intercompany communications is a fully validated

reference architecture that enables an end-to-end solution for service provider and enterprise
networks. The solution was engineered from the beginning with an understanding of both
enterprise and service provider requirements, using the integrated Cisco Unified
Communications platform in the enterprise network in combination with the Cisco Service
Exchange Framework (SEF) infrastructure in the service provider network.

Cisco will enable service providers to offer an additional set of services for intercompany Cisco
TelePresence, including integrated scheduling, secure call processing, Meet-Me (hosted
multipoint), improved manageability, and concierge services. All these features will enable
service providers to offer enhanced Cisco TelePresence dial tone services.
Cisco TelePresence Planning, Design, and
Implementation Service
This topic describes the Cisco TelePresence Planning, Design, and Implementation service.
Cisco TelePresence Planning, Design,

and Implementation Service
 Prequalification  Detailed design development

 Project management  Implementation plan
 Requirements validation  System acceptance testing
 Site survey  End-user training
 Path qualification
The Cisco TelePresence Planning, Design, and Implementation Service delivers a

comprehensive service offering to help enterprises prepare, plan, and design their networks for
the successful implementation of the Cisco TelePresence solution. The service is available from
Cisco, in conjunction with a select group of Cisco Partners that have deep experience in
networking and Cisco Unified Communications and that have special training in virtual
presence technology. These partners rely on proven deployment methodologies to accelerate
the business benefits of Cisco TelePresence technology. With virtual-presence experts focusing
on planning and deploying the solution, enterprises can focus on business transformation.
The Cisco TelePresence Planning, Design, and Implementation Service provides

comprehensive support throughout the planning and deployment of a Cisco TelePresence
solution, helping organizations quickly realize the benefits of this new real-time, immersive
technology. This service provides the following, to help enterprises achieve their business
objectives:
 Assesses the existing network and physical environments
 Develops an implementation-ready design that is based on the requirements of the
organization
 Works with internal IT staff throughout the implementation and testing of the solution, as
well as through end-user training
 Expert Cisco or Cisco Partner engineers with deep backgrounds in Cisco Unified
Communications and a detailed understanding of all components of the Cisco TelePresence
solution, including hardware, software, and application configuration deliver the service.

Cisco and the Cisco Partners rely on the proven Cisco Lifecycle Services methodology, as well
as industry-leading Cisco intellectual property and networking expertise, to align Cisco
TelePresence service and support activities with the business and technology requirements of
the enterprise throughout the network life cycle. As a result, enterprises can deploy Cisco
TelePresence on their existing network, instead of building an overlay network. Enterprises can
also ensure smooth integration and interoperability with other Cisco Unified Communications
solutions and can gain maximum advantage from their converged infrastructure investment.
The Cisco TelePresence Planning, Design, and Implementation Service has several
components:
 Cisco TelePresence Prequalification
 Cisco TelePresence Project Management
 Cisco TelePresence Requirements Validation
 Cisco TelePresence Site Survey
 Cisco TelePresence Path Qualification
 Cisco TelePresence Detailed Design Development
 Cisco TelePresence Implementation Plan
 Cisco TelePresence System Acceptance Testing
 Cisco TelePresence End-User Training
Summary
Summary
 Cisco TelePresence integrates advanced audio, high-definition video,
and interactive elements with the power of the underlying network, to
deliver an immersive meeting experience.
 The Cisco TelePresence solutions include the Cisco TelePresence
System 3200, Cisco TelePresence System 3000, Cisco TelePresence
System 1300 Series, Cisco TelePresence System 1100, Cisco
TelePresence System 1000, and Cisco TelePresence System 500.
 The generation 2 primary codec is the interface between the Cisco
TelePresence system and the network infrastructure; the codec connects
to the network access edge switch via an RJ-45 10/100/1000 port.
 Acoustic property recommendations include tolerances for walls, ceiling,
flooring, and HVAC.
 Illumination specifications include recommendations for lighting fixtures
and bulbs.
 Cisco TelePresence provides the Auto Collaborate feature for graphics
sharing.
Summary (Cont.)
 The Cisco TelePresence Multipoint Switch offers superior scalability, with
as many as 48 locations in a single meeting.
 The Cisco TelePresence Recording Server converts endpoints into
recording studios and can record as many as 300 hours of 1080p high-
definition video content.
 Cisco TelePresence Manager is software that connects Cisco
TelePresence, the Cisco network, and IP communications platforms.
 Cisco TelePresence systems support 720p and 1080p resolutions at
Immersive, Optimized, or Extended Reach experience levels.
 The Cisco TelePresence solution for intercompany communications is a
fully validated reference architecture that enables an end-to-end solution
for service provider and enterprise networks.
 The Cisco TelePresence Planning, Design, and Implementation Service
provides comprehensive support throughout the planning and
deployment of Cisco TelePresence.

Lesson 3
Planning a Cisco
TelePresence Room Design
Overview
You can combine the Cisco TelePresence room design, wall coverings, and colors to create a
unique corporate identity. This design should provide not only continuity from one room to the
next, but it should also embody the business goal of the organization, without distracting from
the experience.
Objectives
Upon completing this lesson, you will be able to discuss various Cisco TelePresence room
design considerations and how they affect the aesthetics and corporate identity of the room.
 Discuss various questions that you should ask when designing a Cisco TelePresence room
 Discuss the importance of corporate identity on a conference room and how Cisco
TelePresence solutions provide the flexibility to incorporate corporate culture
 Discuss the importance of background aesthetics in creating a 3-D experience
 Describe Cisco TelePresence room design examples
 Discuss the effect that wall textures have on a Cisco TelePresence room
 List the approved background colors for a Cisco TelePresence room
Room Design Considerations
This topic describes Cisco TelePresence room design considerations.
Room Design Considerations

 Who is the intended user of the room?
 What is the corporate identity?
 How will the room represent the company?
 What style best suits the corporate culture of the company?
 What are the aesthetic sensibilities of the customer?
 What is the resource investment for room designs?
When you plan a Cisco TelePresence room design, you must consider many factors. All of the
participants in a Cisco TelePresence session should be comfortable with the surroundings but
not distracted by the decor. The goal is to immerse everyone in the meeting, not disengaged.
The virtual conference room experience might be the first impression that a potential customer
has of the organization. This impression is a visual representation of the company. The design
should represent the organization.
The following is a list of questions that you should ask when contemplating a Cisco
TelePresence room design:
 Who is the intended user of the rooms?
 What is the corporate identity?
 How will the room represent the company?
 Which style best suits the corporate culture of the company?
 What are the aesthetic sensibilities of the customer?
 What is the resource investment for room designs?
Corporate Identity
This topic describes how you can integrate the corporate identity into the Cisco TelePresence
rooms.
Corporate Identity
 The flexibility of Cisco TelePresence offers customers the
opportunity to integrate corporate identity into rooms.
 Cisco TelePresence becomes another marketing tool to express
the brand of a company to customers, partners, and vendors.
 The Cisco TelePresence solution is flexible enough to work with
an array of conference room styles.
 Companies should work with their design and facilities groups to
identify the values and individuality of the company.
The corporate identity is the persona of the company and should represent the corporate culture
in the design of each Cisco TelePresence room. This identity should be a visual mission
statement with branding and use of company trademarks. The flexibility of Cisco TelePresence
offers customers the opportunity to integrate corporate identity into rooms. The Cisco
TelePresence rooms become another marketing tool to express the brand of a company to
customers, partners, and vendors.
The Cisco TelePresence room-experience solution is flexible enough to work with an array of
conference-room styles. Companies should work with their design and facilities groups to
identify the values and individuality of the company. Companies should give this task serious
consideration during the deployment.

Background Aesthetics
This topic describes background aesthetics that help create depth.
Background Aesthetics
 The Cisco TelePresence experience is created via the in-room
experience and the on-camera experience.
 The experience is enhanced by creating depth in the background.
 Textures and decorative elements help render a more 3-D
environment.
 Aesthetic elements help carry continuity of the room through all
screens of the Cisco TelePresence system.
 You can achieve dimensionality by using wallpaper, fabrics,
furniture, decorative elements, plants, and signage.
The in-room and the on-camera experiences create the Cisco TelePresence experience. Creating
depth in the background enhances both of these experiences. The textures and decorative
elements help render a three-dimensional (3-D) environment, and the aesthetic elements help
carry the continuity of the room through all three screens of the Cisco TelePresence system.
You can achieve dimensionality by using wallpaper, fabrics, furniture, decorative elements,
plants, and signage. Textures and adornments on the walls should be similar to those on the
walls in the other rooms, to complete the feeling of a unified environment.
Room Design Examples
This topic describes three examples of corporate design.
Room Design Examples

 Executive:
– Much larger room size, to accommodate furniture
– Acoustics at near-studio quality
– Custom lighting for both performance and aesthetics
 Professional:
– Spot treatments for acoustics
– Primarily standard lighting, augmented with decorative lighting
– Additional furniture, such as chairs and tables
– Fabric wall covering
 Classic:
– Painted walls
– Some decorative accents
The level of room design depends on the personality of the organization. The design should
express the business style of the company and define its uniqueness. The design should
represent the day-to-day work style of the company and how it conducts business. The level of
room design should convey the company image.
The following three categories are examples of corporate design styles:

 Executive
— Room size that is much larger, to accommodate furniture
— Acoustics that perform at near-studio quality
— Custom lighting for both performance and aesthetics
 Professional
— Spot treatments for acoustics
— Primarily standard lighting that is augmented with decorative lighting
— Additional furniture, such as chairs and tables
— Fabric wall covering
 Classic
— Painted walls
— Some decorative accents

Executive Design Example: Cisco
TelePresence Systems 3000 and 3200
Van Ness
 Employee grade—Executive
 Room size—24 ft 10 in. x 21 ft 7 in.
 W all finis h— Fabric
 Acoustics— Acoustic paneling along Cisco
TelePres ence microphone level
 Lighting—Soffit with indirect fluorescent
lighting (primary source of illumination)
 Concept—Higher-end environment
 Cherry wood baseboards and upper paneling
 Hanging pendant lights (aesthetic finish,
not a primary source)
 W all wash and s potlights along perimeter to
help c reate a perception of depth
 Customized ceiling plan to reflect a more
sophisticated style
 Aesthetics, acoustics , and lighting all
upgraded in parallel
 Addressed larger room depth by adding
seating and decor
Van Ness
The following are the primary aspects of the Van Ness design, which is an example of an
executive design for Cisco TelePresence 3000 or Cisco TelePresence 3200:
 Employee grade: Executive
 Room size: 24 feet 10 inches x 21 feet 7 inches
 Wall finish: Fabric
 Acoustics: Acoustic paneling in the room, along the Cisco TelePresence microphone level
 Lighting: A soffit with indirect fluorescent lighting (as a primary source of illumination)
 Concept: A higher-end environment
In addition, the room has the following elements:

 Cherry-wood baseboards and upper paneling
 Hanging pendant lights (for an aesthetic finish, not as a primary light source)
 Wall wash and spotlights along the perimeter, to help create the perception of depth
 A ceiling plan that is customized to reflect a more sophisticated style
 Aesthetics, acoustics, and lighting that all are upgraded in parallel
 A larger room depth that is addressed by adding seating and decor
Professional Design Example: Cisco
Pacific
 Employee grade—
manager, director, executive
 Room size—17 ft x 22 ft
 W all finis h— Fabric
 Acoustics— Acoustic paneling
wrapped in fabric, staggered
 Lighting—100% indirect rec ess ed
fixture with wide distribution of light
 Concept—Added ac oustic property
without full wall treatments
 Painted drywall
 Spotlights to create a wall wash and
promote the perception of depth
 Panel color predominant;
nonrecommended (and nonprominent)
background paint color
Pacific
The following are the primary aspects of the Pacific design, which is an example of a
professional design for Cisco TelePresence 3000 or Cisco TelePresence 3200:
 Employee grade: Manager, Director, or Executive
 Room size: 17 feet x 22 feet
 Wall finish: Fabric
 Acoustics: Acoustic paneling that is wrapped in fabric and that is staggered
 Lighting: 100-percent indirect, from a recessed fixture with wide distribution of light
 Concept: Added acoustic property without full wall treatments

 Painted drywall
 Spotlights, to create a wall wash and to promote the perception of depth
 A panel color that is predominant on camera so that the background paint can be a
nonrecommended Cisco TelePresence color

Professional Design Example: Cisco
Haight
 Employee grade—
manager, director, executive
 Room size—15 ft 6 in. x 25 ft
 Wall finish— Wallpaper
 Acoustics—Wall art in credenza
alcove to diffuse sound
reflections
 Lighting—Traditional commercial
fixtures with added diffusers for a
more even diffusion of light
 Concept—Wall texture to help
create depth on camera
 Wall art to carry continuity across
three screens
Haight
The following are the primary aspects of the Haight design, which is another example of a
professional design for Cisco TelePresence 3000 or Cisco TelePresence 3200:
 Employee grade: Manager, Director, or Executive
 Room size: 15 feet 6 inches x 25 feet
 Wall finish: Wallpaper
 Acoustics: Wall art in a credenza alcove, to diffuse sound reflections
 Lighting: Traditional commercial fixtures with added diffusers, for a more even diffusion
of light
 Concept: Wall texture that helps to create depth on camera
In addition, wall art carries continuity across three screens.
Classic Design Example: Cisco
Ashbury
 Employee grade—Staff
member
 Room size—16 ft 5 in. x 25 ft
 Wall finish—Paint
 Acoustics—None
 Lighting—Linear pendant
fixture, 100% indirect
illumination for even
illumination
 Concept—Standard room
deployment with the addition
of decor
 Wall art to carry continuity
across three screens
 Balanced decor for in-room
experience as well as
on-camera experience
Ashbury
The following are the primary aspects of the Ashbury design, which is an example of a classic
design for Cisco TelePresence 3000 or Cisco TelePresence 3200:
 Employee grade: Staff member
 Room size: 16 feet 5 inches x 25 feet
 Wall finish: Paint
 Acoustics: None
 Lighting: Linear pendant fixture, 100-percent indirect illumination for even illumination
 Concept: A standard room deployment with the addition of décor

 Wall art that carries continuity across three screens
 A balanced décor that is appropriate for both the in-room and on-camera experiences

Executive Design Example:
Marina
 Employee grade—Executive
 Room size—12 ft 5 in. x 16 ft 4 in.
 Wall finish—Wallpaper
 Lighting—Linear pendant fixture for
primary illumination
 Concept—Multipurpose meeting room
 Wall sconce for added fill light
 Wall wash fixtures to promote depth and
add interest to the background
 Metallic tones of lighting and wallpaper
to give the room a more polished feel
 Miniatures of buildings in background to
help build depth on camera
Marina
The following are the primary aspects of the Marina design, which is an example of an
executive design for Cisco TelePresence 1000:
 Employee grade: Executive
 Wall finish: Wallpaper
 Acoustics: None
 Lighting: Linear pendant fixture for primary illumination
 Concept: Multipurpose meeting room

 Wall sconce for added fill light
 Wall-wash fixtures, to promote depth and add interest to the background
 Metallic tones of lighting and wallpaper, to give the room a more polished feel
 Miniatures of buildings in the background, to build depth on camera
Classic Design Example:
Sloat
 Employee grade—Staff member
 Room size—
13 ft 4 in. x 10 ft 10 in.
 Wall treatment—Paint
 Lighting—100% indirect recessed
fixture with wide distribution of
light
 Concept—Standard small
conference room
 Multipurpose for meetings other
than Cisco TelePresence
 Decorative touches to help lessen
the sterile feel of flat paint
Sloat
The following are the primary aspects of the Sloat design, which is an example of a classic
design for Cisco TelePresence 1000:
 Employee grade: Staff member
 Wall treatment: Paint
 Acoustics: None
 Lighting: 100-percent indirect, recessed fixture with wide distribution of light
 Concept: Standard small conference room

 Multipurpose, for meetings other than telepresence
 Decorative touches that lessen the sterile feel of flat paint

Wall Finishes
This topic describes various Cisco TelePresence room wall-finish possibilities.
Wall Finishes
 Wall treatment choices introduce varying levels of sophistication
and ambience to the experience.
 Selections should be based on style that is appropriate for the
customer.
Paint Wall Covering Fabric
Wall treatment choices should introduce varying levels of sophistication and ambience to the
overall Cisco TelePresence experience. The following are three possibilities for wall finishes:
 Paint: You can paint drywall with warm colors and adorn walls with artwork that gives the
room a 3-D look, without distracting from the conference experience.
 Wall covering: Wall covering can add a textured look and improve room acoustics.
 Fabric: You can add fabric to a wall to break up the look and to improve room acoustics.
Note You should base the final selections on a style that is appropriate for the customer.
Background Objects
Certain items can help add Other items can be
dimension and depth on distracting and take away
camera. from the overall
 Adornments on the walls, experience.
plants in the corners of the  Windows, reflective surfaces
room such as dry-erase boards
Check with local building codes to determine whether a room is large

enough to accommodate background elements.
Certain background objects and items can help add dimension and depth on camera, to enhance
the Cisco TelePresence experience. Adornments on the walls and plants in the corners of the
room can add the final touch to a well-designed room. However, other items can be distracting
and can take away from the overall experience. Try to avoid having windows and reflective
surfaces, such as dry-erase boards, in the background. The goal is to add the final design touch
to the Cisco TelePresence room, but not to be excessive.
Note Check with local building codes to determine whether a room is large enough to
accommodate background elements.

Backgrounds to Avoid
Minimize the use of busy patterns and contrasting colors
on the back wall, behind the participants.
The wall finishes should make a statement about the company, but keep finishes simple.
Minimize the use of busy patterns and contrasting colors on the back wall, behind the
participants. Walls and wall coverings with a heavy texture are highly discouraged because
they are distracting and reduce the quality of the telepresence experience. Remember, the focus
should be on the participants and the collaborative effort.
Background Color
This topic describes various wall background-color considerations.
Background Color
Warm neutral background colors liven the participant and
keep the image from appearing stark to other endpoints.
Unpainted Background Effect of Color Background

The choice of background colors is very important. The customer should standardize on a
single company color palette to maintain a consistent experience.
Cisco has tested a broad spectrum of hues to identify the characteristics of paint colors that
compliment the coder-decoder (codec) and plasma technology, work well with the skin tones of
the on-camera participants, and feel comfortable in person. Cisco TelePresence technology
works best when colors are within a neutral tone, are chromatically tame, and fall within a
lower reflectance range. The first generation of Cisco TelePresence colors is a group of warmer
earth tones so that the technology can optimally portray the participants in the most accurate
manner.
Cisco provides a list of color recommendations that will complement most corporate standards,
while creating an environment that is both warm and inviting. These color selections provide
the best video quality.

Suggested Paint Colors
Proper color conditions allow the Cisco TelePresence technology to deliver optimal
performance in rendering the most accurate skin tones. Specific colors are recommended for
backgrounds to enable better recognition of attendees, without straining the capture capabilities
of the camera. One aspect to harmonizing color perception between rooms is to select colors
within a similar tonal range. Be aware of color and physical environment characteristics that
demand higher output from the video technology. Light colors are higher reflectivity and affect
the image output. Dark colors can dampen the perception of the in-room experience.
To translate colors to your local paint system, contact Benjamin Moore to request a color sheet.
You can order color sheets by going to https://bm.faicentral.com/logina/. For international
orders and to order by phone, call 888 854-9889.
The following is a list of suggested Benjamin Moore colors by name and paint number:
 Wilmington Tan, HC-34
 Huntington Beige, HC-21
 Woodstock Tan, HC-20
 Cork, 2153-40
 Classic Caramel, 1118
 Fairmont Gold, 1071
 Peach Brandy, 112
Summary
Summary
 Cisco TelePresence room-design considerations should reflect
the aesthetics and corporate identity of the company.
 Cisco TelePresence solutions provide the flexibility to incorporate
corporate culture into each room.
 Background aesthetics helps to create a 3-D experience in a
Cisco TelePresence session.
 Three design examples of Cisco TelePresence can be described
as executive, professional, and classic.
 Wall textures and finishes can have a profound influence on a
Cisco TelePresence room.
 Cisco provides a list of approved background colors for Cisco
TelePresence rooms.

Module Summary
This topic summarizes the key points that were discussed in this module.
Module Summary
 Cisco TelePresence creates a unique, "in-person" experience by
using innovative video, audio, and interactive hardware and
software elements, over the network.
 The Cisco TelePresence solution uses many components that
use ultrahigh-quality, two-way video and audio to revolutionize
remote collaborations, pioneering a new form of digital
communications that rivals the effectiveness of in-person
meetings.
 The Cisco TelePresence room design is an important factor in
creating a unique corporate identity for the virtual collaborative
experience.
Cisco has developed an innovative solution that creates an “in-person” meeting experience over
the converged network. Cisco TelePresence delivers real-time, face-to-face interactions
between people by using advanced visual, audio, and collaboration technologies. These
technologies transmit life-size, high-definition images and spatially discrete audio. Now,
discerning facial expressions during crucial business discussions and negotiations across a
virtual table is easier than ever.
The components of Cisco TelePresence use standard technologies with specialized applications
and hardware, to create an approachable solution that uses the network and Cisco Unified
Communications as core components. Cisco TelePresence uses the standard IP technology that
corporations deploy today and runs on an integrated voice, video, and data network. The Cisco
TelePresence portfolio includes solutions for personal, multipurpose, or group scenarios and
allows document sharing through the Auto Collaborate feature. Additional features include
multipoint switching, a recording server, simplified scheduling, multiple experience levels, and
intercompany communications.
The Cisco TelePresence Planning, Design, and Implementation Service is a comprehensive

service that can help enterprises prepare, plan, and design their networks for the successful
implementation of the Cisco TelePresence solution.
A Cisco TelePresence room design is an important factor in creating a unique corporate

identity. The virtual collaborative experience should represent the image of the company and its
mission.

References
For additional information, refer to these resources:
 Cisco Systems, Inc. Cisco TelePresence Solutions.
http://www.cisco.com/en/US/netsol/ns669/networking_solutions_solution_segment_home.
html.
 Cisco Systems, Inc. TelePresence Introduction.
http://www.cisco.com/en/US/products/ps7060/index.html.
Module Self-Check
Use the questions here to review what you learned in this module. The correct answers and
solutions are found in the Module Self-Check Answer Key.
Q1) Cisco TelePresence codecs combine multiple audio and video channels into a single
stream that is transmitted across an IP network by using revolutionary ASICS that are
designed to support high-definition traffic with very low latency. (Source: Exploring
the Cisco TelePresence Solution)
A) true
B) false
Q2) Which of the following statements is false? (Source: Exploring the Cisco TelePresence
Solution)
A) Cisco TelePresence deploys into existing customer rooms and facilities, with
minimal room remediation.
B) The high-end technology, the room, and the environment belong to and remain
under the control of Cisco.
C) A customer can tailor a personalized Cisco TelePresence room experience to
their brand.
D) Rooms can easily integrate and blend with the corporate look and the
atmosphere of the surrounding facilities.
Q3) Which of the following statements about the Cisco TelePresence 3000 is false?
(Source: Exploring the Cisco TelePresence Environments)
A) It supports either high definition 1080p or 720p.
B) It provides a boardroom-style table that seats six participants on each side,
providing a virtual table for 12 participants in a point-to-point meeting.
C) It is ideal for large group meetings, comfortably seating participants around a
virtual table.
D) It provides an optimized experience that uses integrated equipment, including
three 55-inch plasma screens and spatial audio through three speakers.
Q4) Which one of the following statements about the Cisco TelePresence 3200 is true?
A) It provides seating for as many as 20 participants in a single room.
B) It provides additional seating with two extra rows of tables.
C) It uses larger plasma displays than the Cisco TelePresence 3000 uses.
D) You cannot upgrade an existing Cisco TelePresence 3000 to Cisco
TelePresence 3200.
E) It provides seating for as many as 18 participants in a single room.
Q5) The Cisco TelePresence 1300 uses a single 65-inch, 1080p high-definition plasma
screen with three cameras, and it can support meetings with as many as six people in a
regular conference room. (Source: Exploring the Cisco TelePresence Environments)
A) true
B) false

Q6) Match the following statements with the appropriate Cisco TelePresence system.
A) It is an ideal solution for small group meetings, such as customer engagements,
supply-chain dealings, negotiations, job interviews, engineering reviews, one-
on-one meetings, or team meetings.
B) It uses a single 65-inch, 1080p high-definition plasma screen with three
cameras, and it can support meetings with as many as six people in a regular
conference room.
C) With seating for 14 to 18 participants in a single room, the system delivers the
same superior video and audio quality as the rest of the Cisco TelePresence
portfolio.
D) It provides a virtual table for 12 participants in a point-to-point meeting.
E) It brings the virtual in-person experience of Cisco TelePresence directly into
the private office.
_____ 1. Cisco TelePresence 3000
Q7) Cisco TelePresence supports simple information sharing through a powerful Auto
Collaborate feature that allows any object, document, or application to be displayed by
using special software that is loaded on a PC. (Source: Exploring the Cisco
TelePresence Environments)
A) true
B) false
Q8) The Cisco TelePresence Multipoint Switch is an affordable, purpose-built appliance
that is easy to install and offers superior scalability to as many as 68 locations in a
single meeting. (Source: Exploring the Cisco TelePresence Environments)
A) true
B) false
Q9) Which of the following statements about the Cisco TelePresence Recording Server is
false? (Source: Exploring the Cisco TelePresence Environments)
A) It transforms the Cisco TelePresence application into a high-definition
recording studio.
B) It is built on the Cisco MCS 7845 and is a Linux-based solution.
C) It stores as many as 300 hours of 1080p HD video content, along with the data
presentation channel and a CIF version for PC-browser playback.
D) It requires a special camera and audio equipment that you can move from room
to room.
E) The recording capability creates a category of experience for Cisco
TelePresence technology that takes the solution well beyond meetings.
Q10) Cisco TelePresence Manager offers room scheduling that you perform through
enterprise groupware, to provide ease of use for customers. (Source: Exploring the
Cisco TelePresence Environments)
A) true
B) false
Q11) Which of the following is not a Cisco TelePresence connectivity and experience
option? (Source: Exploring the Cisco TelePresence Environments)
A) immersive
B) optimized
C) extended reach
D) limited reach
Q12) Which one of the following statements about room design considerations is false?
(Source: Planning a Cisco TelePresence Room Design)
A) The corporate identity is the persona of the company and should represent the
corporate culture, through the design of each Cisco TelePresence room.
B) Textures and adornments on the walls should be different to those on the walls
in the other rooms, to help identify the remote locations.
C) All of the participants in a Cisco TelePresence session should be comfortable
with the surroundings but should not be distracted by the decor.
D) The Cisco TelePresence room is a visual representation of the company and the
room design should represent the organization.
Q13) Which one of the following statements about room design considerations is true?
(Source: Planning a Cisco TelePresence Room Design)
A) Dark colors have higher reflectivity and affect the image output; light colors
can dampen the perception of the in-room experience.
B) Cisco does not provide color recommendations, but you should choose colors
that will both complement most corporate standards and create an environment
that is warm and inviting.
C) Walls and wall coverings with a heavy texture are highly discouraged because
they will be distracting and will reduce the quality of the telepresence
experience.
D) You should not place adornments on the walls or place plants in the corners of
the room because they will distract from the telepresence experience.

Module Self-Check Answer Key
Q1) A
Q2) B
Q3) D
Q4) E
Q5) A
Q6) 1-D
2-C
3-B
4-A
5-E
Q7) B
Q8) B
Q9) D
Q10) A
Q11) D
Q12) B
Q13) C
Module 2
Cisco TelePresence Call

Control
Overview
Cisco TelePresence uses standard IP technology and runs on an integrated voice, video, and
data network. The technology works with IP-based phones, to simplify the launching of calls.
Integration with enterprise groupware solutions, such as Microsoft Outlook and IBM Lotus
Notes, accommodates easy scheduling of meetings and access to corporate information. An
existing Cisco Unified Communications architecture, with the addition of unique Datagram
Transport Layer Security (DTLS) key exchange, provides security for Cisco TelePresence
endpoints.
Module Objectives
Upon completing this module, you will be able to describe and configure a Cisco TelePresence
endpoint. This ability includes being able to meet these objectives:
 Describe and configure a Cisco TelePresence endpoint
 Use the Cisco TelePresence Unified IP Phone user interface
Lesson 1
Integrating Cisco
TelePresence Endpoints with
Cisco Unified Communications
Manager
Overview
Each of the Cisco TelePresence endpoints has a primary coder-decoder (codec) device that
communicates as a telephony endpoint from the perspective of the Cisco Unified
Communications Manager. The administrative interface of the Cisco TelePresence codec
allows you to configure, monitor, and troubleshoot a Cisco TelePresence endpoint. The Cisco
Unified Communications Manager Administration tool enables you to manage the integration
of all Cisco TelePresence endpoints, as well as the dial plan and call routing.
Objectives
Upon completing this lesson, you will be able to integrate Cisco TelePresence endpoints. This
ability includes being able to meet these objectives:
 Describe the complete end-to-end solution that the Cisco TelePresence solution provides
 Describe the Cisco TelePresence codec
 Configure and troubleshoot the Cisco TelePresence codec
 Describe Cisco Unified Communications Manager
 Describe the registration process between the codec and Cisco Unified Communications
Manager
 Describe the Cisco Unified Communications Manager configuration that is needed to
support the Cisco TelePresence system
 Describe the Cisco Unified IP Phone 797xG
 Describe Cisco TelePresence CAC considerations
 Troubleshoot Cisco TelePresence system issues
A Complete End-to-End Solution
This topic describes the complete end-to-end solution that the Cisco TelePresence solution
provides.
A Complete End-to-End Solution
LAN/WAN
Audio Streams
Video Streams
The Cisco Unified IP Phone 797xG connects to the primary codec. The primary codec supplies
IEEE 802.3af Power over Ethernet (PoE) to the IP phone and multiplexes audio and video
inputs from its secondary codecs in the Cisco TelePresence Systems 3000 and 3200. To
complete the telepresence call, the primary codec delivers the single Real-Time Transport
Protocol (RTP) stream for each audio and video stream to the far-end codec. On the receiving
side, the primary codec is responsible for demultiplexing the respective streams and delivering
them to the appropriate video display or audio speaker channel.
Cisco Unified Communications Manager communicates with and controls a Cisco
TelePresence codec as it would a telephony endpoint. The Cisco TelePresence codecs
communicate with each other in much the same way that any IP phone uses Session Initiation
Protocol (SIP) to communicate with another IP phone. Calls are point to point or IP address to
IP address.
Cisco Unified Communications Manager generates the SIP commands that are necessary to
manage the devices for events such as call setup and teardown. Audio and video streams also
communicate in much the same way as IP phones or Cisco Unified Videoconferencing devices,
using RTP over User Datagram Protocol (UDP). Therefore, you must properly configure the
underlying IP network for end-to-end service and dependability of Cisco TelePresence
endpoints.
The Cisco TelePresence Codec
This topic describes the Cisco TelePresence codec.
The Cisco TelePresence Codec

 Runs embedded Linux on integrated Flash
 Leverages Cisco Unified Communications Manager
 Built on open standards
– Cisco Discovery Protocol and 802.1Q
for VLAN assignment
– 802.1p and DSCP for QoS
– HTTP configuration and firmware downloads
– SSH, HTTPS, and SNMPv2 and SNMPv3
for administration
– SIP signaling
– Video: H.264 at 1080p, 720p, or CIF
– Audio: AAC-LD and G.711
– XML for making and terminating
scheduled and ad hoc calls
 Auto Collaboration for data sharing
 Audio add-in for audio-only participants
The Cisco TelePresence codec is the center of the Cisco TelePresence solution. The codec
tightly integrates with Cisco Unified Communications Manager and Microsoft Exchange
Server, to consistently deliver the Cisco TelePresence experience.
Cisco TelePresence is built on the following open standards:
 Cisco Discovery Protocol and IEEE 802.1Q for VLAN assignment
 IEEE 802.1p and differentiated services code point (DSCP) for quality of service (QoS)
 HTTP configuration and firmware downloads
 Secure Shell (SSH), HTTPS, Simple Network Management Protocol version 2 (SNMPv2),
and SNMP version 3 (SNMPv3) for administration
 SIP signaling
 H.264 at 1080p, 720p, or Common Intermediate Format (CIF—352 x 288 pixels) for video
(full high-definition, progressive-scan—not interlaced—video)
 Advanced audio coding with low delay (AAC-LD) and G.711 for audio add-in
 XML for making and terminating scheduled and ad hoc calls
The Cisco TelePresence codec supports autocollaboration for data sharing and audio add-in for
audio-only participants.
© 2011 Cisco Systems, Inc. Cisco TelePresence Call Control 2-5

Codec Internal Network Addressing: Cisco
 The primary codec uses internal private addresses to
communicate with components.
 The primary codec cannot communicate with external network
devices that overlap internal addresses.
Example:
Voice VLAN ID = 201 Interface Vlan201 = 10.88.210.1/24
Voice VLAN Subnet = 10.88.210.0/24
Pri mary codec appears as a
Gigabit Ethernet single endpoint wi th one
external address.
Ethernet and PoE
Gig0.201 = 10.88.210.23/24
192.168.1.0/24 192.168.2.0/24
Gi g1
10.88.210.50/24
192.168.3.0/24 192.168.3.0/24
192.168.3.0/24
192.168.4.0/24 192.168.4.0/24
192.168.4.0/24
From the perspective of the network, the Cisco TelePresence primary codec appears as a single
endpoint device with one external IP address. The primary codec uses a private network for
internal communications with the secondary codecs and cameras. By default, the internal
address range is 192.168.0.0/24 through 192.168.4.0/24. However, if the primary codec is
assigned a 192.168.x.x address from the network via DHCP, then the internal private network
will switch to 10.0.0.0/24 through 10.0.4.0/24. The primary codec will be unable to
communicate with any devices that use external addresses that overlap with the private internal
network.
The primary codec provides the functionality for the Cisco TelePresence solution. In the Cisco
TelePresence Systems 3000 and 3200 configuration, there is one primary and two secondary
codecs. Each primary codec obtains a DHCP-issued IP address, TFTP server address, and
switch-issued VLAN assignment—all based on the network configuration for the Cisco Unified
Communications Manager deployment. The codec, which is recognized as a voice-enabled
device much like the Cisco IP Phone 797xG, uses Cisco Discovery Protocol, which allows the
assignment of the codec to the voice VLAN. Then, the primary codec registers to its
appropriate Cisco Unified Communications Manager device, based on the information that it
receives from the Cisco Unified Communications Manager TFTP server.
The primary codec accepts input from the directly connected microphone and camera, as well
as from cameras that are directly connected to the secondary codecs. (All microphones attach
directly to the primary codec.) The software interface of the primary codec allows it to provide
basic management of both the primary and secondary codec attached devices. Secondary and
high frame rate (HFR) codecs obtain a DHCP-issued IP address from the closed network,
which exists between the primary and secondary codec devices. Secondary codecs do not
communicate outside of their local closed network. Only the Cisco TelePresence Systems 3000
and 3200 have secondary codecs.
The codec captures from one to four video streams (primary, two secondary, and an optional
HFR codec) and transmits them to other Cisco TelePresence endpoints via the local network
Ethernet connection, typically on the voice VLAN. The primary codec multiplexes video
streams and transmits them as a single RTP stream per node. The primary codec displays video
that it receives from other Cisco TelePresence endpoints on its directly connected monitors.
Cisco TelePresence System Administration
This topic describes how to use the Cisco TelePresence System Administration tool to
configure the Cisco TelePresence codec.
Cisco TelePresence System

Administration
The System Administration tool allows you to configure,
troubleshoot, and monitor an individual Cisco
TelePresence codec.
Cisco TelePresence System Administration is a web-based administrative interface that resides

on the Cisco TelePresence codec. Follow these steps to log into the Cisco TelePresence system
administrative GUI.
Step 1 Open a browser and enter the IP address of the codec.
Note The IP address of the codec is displayed on the center of the Cisco TelePresence screen,
after a bootup. If you do not know the IP address, you can connect directly to the camera
Ethernet port, and the codec will assign an IP address to your laptop. The codec is the first
IP address of the subnet that is assigned to your laptop.
Step 2 In the Admin field, enter admin.

Step 3 In the Password field, enter cisco.
Step 4 Click Login.

The main page of the Cisco TelePresence System Administration tool contains links to the
Configuration, Troubleshooting, and Monitoring sections. These links appear in the left pane,
under Device Information. After you choose one of the three major menu headings, submenus
appear in the right pane. These submenus provide additional descriptions for, and links to, the
subheadings, as shown in the figure (the Configuration submenu ). Simply choose the
appropriate subheading from either the left pane or right pane to navigate to the desired page of
information. The System Status pane, which appears in the lower left of the Cisco TelePresence
System Administration window, provides a quick glance at the status of the major components
of the Cisco TelePresence system. The System Status pane indicates whether the system is
currently hosting a telepresence call and displays the status of as many as three cameras, as
many as three displays, the Cisco IP Phone 797xG, and Cisco Unified Communications
Manager.
Configuration > IP Settings
 Configure a static IP address for the primary codec.
 Make note of the MAC address so that you can register it with
Cisco Unified Communications Manager.
Configuration > IP Settings

The IP Settings pane allows you to configure a static IP address for the primary codec.
Remember that secondary codecs receive DHCP addressing from the primary codec on the
closed internal private network and do not require configuration here. Make note of the MAC
address of the primary codec. You will need this MAC address to register the endpoint later in
The following table lists the fields on the IP Settings screen:
IP Settings
Field or Button Setting
MAC Address MAC address of the primary codec
Host Name Hostname of the endpoint
DHCP Enabled Configures whether DHCP is enabled
Domain Name Domain name where the codec resides
Use Static IP Address Displays Yes or No, based on the DHCP Enabled field
IP Address IP address for the Cisco TelePresence system
Subnet Mask Subnet mask that is used for the IP address that is supplied
Default Gateway Default gateway for the Cisco TelePresence system
DNS Server 1 IP address of the primary Domain Name System (DNS) server
DNS Server 2 IP address of the secondary DNS server

Configuration > Cisco Unified
Communications Manager Settings
 If DHCP lease options specify the TFTP server, then no further
configuration is needed.
 If DHCP lease options do not specify the TFTP server, then you
can manually configure them.
Configuration > Cisco Unified Communications Manager

Settings
The Cisco Unified Communications Manager Settings pane allows you to configure the TFTP
server settings. If the DHCP lease options (option 150) specify the Cisco Unified
Communications Manager TFTP server, then no further configuration is necessary in this pane.
If the DHCP lease options do not specify the TFTP server, or if a static IP address is in use,
then you might need to manually configure a TFTP address. To do so, click the Specify radio
button, as shown in the figure.
For the codec to register with Cisco Unified Communications Manager, the codec must receive
the TFTP information. A quick review of the example in the figure indicates that this codec has
been manually configured with a TFTP server address and then a Cisco Unified
Communications Manager address.
The following table lists the fields on the Cisco Unified Communications Manager Settings
screen.
Cisco Unified Communications Manager Settings
Use When you click the Yes radio button for the Use Cisco CallManager option, the
Configuration Automatic and Specify radio buttons appear in this field.
TFTP Servers ■ Click Automatic to set the default condition. With this option, the TFTP server
replies to DHCP requests for option 150 or for a list of TFTP servers that
indicate to network endpoints where to find Cisco Unified Communications
Manager configuration files.
■ Click Specify to manually supply the IP addresses of TFTP servers in the
interactive fields that are provided.
TFTP Server Enter the IP addresses of TFTP servers if you use the Cisco CallManager option
1–5 and the Use Configuration TFTP Server option.
Cisco Unified These read-only fields display the names of many as five
Communication Cisco Unified Communications Manager systems.
s Manager
1–5

Configuration > Telephony Settings
 Default settings are recommended for Cisco TelePresence
communication.
 Modifications can impair system performance.
Configuration > Telephony Settings

You can use the Telephony Settings pane to modify the default settings that are recommended
for Cisco TelePresence communication. However, you should not change the default settings
without specific reason, because modifications can impair system performance. Of particular
note are the DSCP settings. The DSCP value for audio is set to the standard audio DSCP of
Expedited Forwarding (EF) and applies to audio-only calls. Video is set at Assured Forwarding
41 (AF41). The Video label applies to all telepresence video and audio traffic. You can modify
these settings in Cisco Unified Communications Manager. Each of these settings is discussed in
the “Cisco TelePresence Network Architecture” module in this course.
The following table lists the fields on the Telephony Settings screen:
Telephony Settings
Auto Answer Click the Yes radio button to set automatic answering capability on the phone.
Click the No radio button to disable automatic answering.
Maximum Call This field sets the maximum length of a call, in minutes. Use this setting to define a
Length (mins) limit on a call if it is accidentally left connected.
The default setting is 0 minutes, which means that there is no limit to the call
duration. The maximum number of minutes that you can configure is
10,080 minutes (7 days).
The call automatically ends at the number of minutes that you configure. When the
default setting is used, the call never ends automatically.
DSCP For Cisco software provides traffic queuing techniques that define per-hop behavior,
Audio based on the DSCP value in the IP header of a packet. You can choose from the
DSCP For following DSCP settings for both audio and video traffic. Choices are specific to
Video traffic in the Cisco TelePresence system.
■ AF41 DSCP (100010)
■ AF42 DSCP (100100)
■ AF43 DSCP (100110)
■ CS3(precedence 3) DSCP (011000)
■ Default DSCP (000000)
■ EF DSCP (101110)
Start Media This value must be in the range from 16,384 to 32,766, and must be lower than the
Port End Media Port settings.
End Media This value must be in the range from 16,384 to 32,766, and must be higher than the
Port Start Media Port settings.

Configuration > System Settings
Verify and modify values such as administrative
username and password, video bandwidth allocation and
quality, locale and system language, and system type.
Configuration > System Settings

Use the System Settings pane to verify and modify values such as the administrative username
and password, video bandwidth allocation and quality, locale and system language, and system
type. In the example in the figure, the system type is the Cisco TelePresence 1300 Series,
indicating that the system supports three cameras and one display.
Troubleshooting > Hardware Setup
Perform the hardware setup during the initial setup and
any time that a significant change occurs.
Troubleshooting > Hardware Setup

Use the Hardware Setup pane when you perform the initial setup. Also, use it any time there is
a significant change in the Cisco TelePresence environment, such as a change in lighting or
acoustics. From this pane, you can adjust settings for displays, cameras, speakers, and
microphones.
The Hardware Setup features require the use of the displays in the meeting room. Therefore,
you should start troubleshooting by verifying that the displays work. If the displays show the
correct images, you can proceed to testing either the cameras or the speakers, as needed. You
must test the speakers before testing the microphones because the microphone test depends on
the correct functioning of the speakers.
Note The example in the figure shows a Cisco TelePresence System 1000.

Troubleshooting > Log Files
 Cisco TAC uses log files for in-depth troubleshooting.
 Select Problem Type label before generating log files.
Troubleshooting > Log Files

Cisco Technical Assistance Center (TAC) uses the log files to help perform in-depth
troubleshooting.
To create log files that you can provide to Cisco TAC, choose Troubleshooting > Log Files to
retrieve log files from the Cisco TelePresence system. When you have supplied the information
that is requested in the form, click Capture and Download New Log Files to collect the log
files. When that collection process is complete, click Download Existing Log Files to start the
file download process. The Cisco TelePresence System Administration software prompts you
to either view or save the log file.
Troubleshooting > SIP Messages
SIP messages can prove to be a significant resource
when troubleshooting call setup.
Troubleshooting > SIP Messages

SIP is an Internet Engineering Task Force (IETF) standard for multimedia conferencing over
IP. SIP is an ASCII-based, application-layer control protocol (defined in RFC 3261) that can
establish, maintain, and terminate calls between two or more endpoints. Like other VoIP
protocols, SIP is designed to address the functions of signaling and session management within
a packet telephony network. Signaling allows call information to travel across network
boundaries. Session management provides the ability to control the attributes of an end-to-end
call.
SIP request and response methods are used to establish communications between components
in the network and ultimately to establish a call or session between two or more endpoints. SIP
messages can be a significant resource when you are troubleshooting call setup.
SIP Message Types
Message Types Response Type
1xx Informational messages

2xx Successful responses
3xx Redirection responses
4xx Request failure responses
5xx Server failure responses
6xx General failure responses

Monitoring > Call Statistics
Call statistics provide basic information about real-time
and historical system usage and performance.
Monitoring > Call Statistics

Call statistics provide basic information about real-time and historical system usage and
performance.
 Real- Time Call Statistics: This section includes information about call start time, current
duration, called number, and negotiated bit rate (the basis for audio quality).
 Historical Call Statistics: This section includes information on the number of calls that
have been serviced, total service time, and configured video bit rate. A negotiated bit rate
that is lower than the configured bit rate can indicate network problems, which you might
need to investigate and correct.
Codec CLI
admin:
show upgrade detail
 Displays the current status of software upgrades

admin:
utils network ping ip-address
 Performs a ping
admin:
call start dn
 Performs a manual dial
The command-line interface (CLI) that resides on the Cisco TelePresence codec allows
administrators to configure, monitor, and troubleshoot a particular endpoint. You can access the
CLI by using SSH version 2 (SSHv2).
The Cisco TelePresence codec contains several subsystems that can take as long as an hour to
complete during an upgrade. Always check the upgrade status by using the codec CLI before
rebooting and powering off the codec.
Caution Powering down the codec during an upgrade can corrupt the onboard flash.
You can verify the upgrade status by using the show upgrade detail CLI command. To
perform a ping test from the CLI, execute the utils network ping x.x.x.x command. To test-dial
a directory number remotely from the CLI, use the call start dn command.

Codec CLI (Cont.)
admin:
utils service list
 Lists the status of services on the codec
admin:
utils service start service
 Starts a service on the codec

admin:
set ctstype [500|1000|1100|1300|3000|3200]
 Sets the codec type on a new install
 By default, new codecs are set to 1000
A newly installed Cisco TelePresence endpoint depends on access to a DHCP server to

complete its bootup and to provide access to the Cisco TelePresence System Administration
web interface. Access to this interface might be necessary if you attempt to perform a camera
tuning before the network and calling infrastructure is fully deployed.
Use the utils service list command form the codec CLI to list the status of services that are
running on the codec. To start a service, use the utils service start service_name command
from the codec CLI; for example:
admin:utils service start Calling_Services
Calling_Services Starting...done
The codec typically discovers its Cisco TelePresence system model type by registering with
Cisco Unified Communications Manager. If the network is unavailable, then you must
manually set the model type. You typically would need to set the model type manually only
when necessary, before camera tuning. Enter the set ctstype [500|1000|1100|1300|3000|3200]
command to set the Cisco TelePresence System model type from the codec CLI; for example:
admin:set ctstype 1000
Setting CTS type to 1000
Restarting Calling_Services, please...
Stopping cca...
Stopping cca... DONE
Starting cca...
Starting CCA... DONE
Cisco Unified Communications Manager
This topic describes Cisco Unified Communications Manager.

 Cisco TelePresence requires Cisco Unified Communications Manager
Version 7.0(2) or later.
 Cisco Unified Communication Manager views a Cisco TelePresence
system the same as a Cisco Unified SIP IP phone.
– Automated configuration and firmware
distribution
– Advanced call routing and CAC
– Management and CDR
 Cisco TelePresence Manager integrates with
Cisco Unified Communications Manager via
AXL/SOAP and CTI/QBE and provides device and call status.
 Cisco TelePresence Multipoint Switch functionality integrates
with Cisco Unified Communication Manager via a
SIP trunk.
 Cisco Unified IP Phone 797xG provides a simple user interface to the
Cisco TelePresence system.
The Cisco Unified Communications Manager Administration tool helps you to manage the
configuration and firmware of all Cisco TelePresence endpoints. The tool also helps you to
manage the dial plan and call routing for all Cisco TelePresence calls. Cisco TelePresence
requires Cisco Unified Communications Manager Version 7.0(2) or later. If a customer has
deployed a single Cisco Unified Communications Manager Version 7.0(2) or later cluster for IP
telephony and has no desktop video devices, then integrating Cisco TelePresence devices into
that cluster might be an acceptable option. However, most initial deployments are not expected
to meet these criteria, so the customer should deploy a separate Cisco Unified Communications
Manager cluster to support telepresence.
Cisco Unified Communications Manager views a Cisco TelePresence system in the same way
as it views a Cisco Unified SIP IP phone. The Cisco Unified Communications Manager
supports the following features:
 Automated configuration and firmware distribution
 Advanced call routing and Call Admission Control (CAC)
 Management and Call Detail Records (CDRs)
Cisco TelePresence Manager integrates with Cisco Unified Communications Manager via
Administrative XML Layer Simple Object Access Protocol (AXL/SOAP) and Computer
Telephony Interface Quick Buffer Encoding (CTIQBE) and provides both device and call
status. The Cisco TelePresence Multipoint Switch functionality integrates with Cisco Unified
Communications Manager via a SIP trunk. Finally, the Cisco IP Phone 797xG provides a
simple user interface that makes initiating a Cisco TelePresence session as easy as making a
phone call.

Earlier Release Requirements and
Recommendations
Cisco TelePresence Cisco Unified
Manager Communications Manager
Release 1.0(x) Version 5.0(4) or later
(November 2006)
Release 1.1(x) Version 5.1(2b) or later

(April 2007)

(November 2007) (Version 6.1(2) or later recommended)

(April 2008) (Version 6.1(2) or later recommended)

(August 2008) (Version 7.0(2) or later recommended)
Release 1.5(x) Version 6.1(3)

(December 2008) Version 7.0(2) MIDlets
Cisco TelePresence Manager uses the same platform infrastructure as Cisco Unified
Communications Manager, following its appliance model principles. The administrative user
interface is a single software entity that provides access to a web-based GUI for initial setup
and installation. Cisco TelePresence Manager Release 1.5(x) is a software application that is
loaded on a Cisco Media Convergence Server (MCS) 7845 Series and is run as a standalone
application. This application cannot be deployed coresident with any other Cisco application on
that hardware. The application is compatible with Cisco Unified Communications Manager
Version 6.1(3) and MIDlets version 7.0(2).
The following table offers a compatibility comparison of the different versions of software:
Release Requirements and Recommendations
Cisco TelePresence Manager Cisco Unified Communications Manager
Release 1.0(x) November 2006 Version 5.0(4) or later
Release 1.1(x) April 2007 Version 5.1(2b) or later
Release 1.2(x) November 2007 Version 6.0(1) or later

Version 6.1(2) or later recommended
Release 1.3(x) April 2008 Version 6.0(1) or later

Version 6.1(2) or later recommended
Release 1.4(x) August 2008 Version 6.0(1) or later

Version 7.0(2)or later recommended
Release 1.5(x) December 2008 Version 6.1(3)

Version 7.0(2) MIDlets
Dedicated Cisco Unified
Communications Manager
 Question: Why do I need to have a dedicated Cisco Unified
Communications Manager cluster for Cisco TelePresence?
 Answer: You can put Cisco TelePresence on an existing Cisco
Unified Communications Manager cluster, provided you meet the
three criteria explained in the next figure. Otherwise, you should
install a separate Cisco Unified Communications Manager cluster
for Cisco TelePresence.
 Question: How many Cisco Unified Communications Manager
servers do I need?
 Answer: One publisher and one subscriber are sufficient.
 Question: Which server platform should I use for Cisco Unified
Communications Manager? Do I need to use Cisco MCS 7845
Series?
 Answer: The answer depends on the amount of hardware-level
redundancy that you want.
You should ask the following questions about choosing a Cisco Unified Communications
Manager deployment:
 Question: Why do I need to install a dedicated Cisco Unified Communications Manager
cluster for a telepresence environment.
 Answer: You can support telepresence on your existing Cisco Unified Communications
Manager cluster, if you meet three criteria that are explained later in this topic. If you do
not meet these criteria, then you should put in a separate Cisco Unified Communications
Manager cluster to support telepresence.
 Question: How many Cisco Unified Communications Manager servers do I need?

 Answer: One publisher and one subscriber are sufficient.
 Question: Do I need to install Cisco Unified Communications Manager on a Cisco MCS

7845 Series system?
 Answer: The answer depends on the amount of hardware-level redundancy that you
require.

Cisco Unified Communications
Manager: Shared vs. Standalone
 Cisco TelePresence requires Cisco Unified Communications Manager
Version 7.0(2) or later.
 Cisco TelePresence has unique bandwidth and QoS requirements, but
Cisco Unified Communications Manager cannot differentiate between a
Cisco TelePresence call and a regular video-telephony call—both are
viewed as video calls.
 All Cisco TelePresence systems should register to the same Cisco
Unified Communications Manager cluster because Cisco TelePresence
Manager can integrate with only one Cisco Unified Communications
Manager cluster.
Conditions Recommendation
Cisco Unified Communications Manager 7.0(2) or You can use an existing Cisc o Unified
later Communications Manager cluster.
Cisco Unified Communications Manager 7.0(2) or You can pick one of your Cisco Unified
later and more than one Cisco Unified Communications Manager clusters and use it
Communications Manager cluster globally for all Cis co TelePresence systems.
Video-telephony endpoints on this cluster You must deploy a separate Cisco Unified
Communications Manager cluster for Cisc o
TelePresence.
Cisco TelePresence has unique bandwidth and QoS requirements. However, Cisco Unified
Communications Manager cannot differentiate between a Cisco TelePresence call and a regular
video-telephony call. To Cisco Unified Communications Manager, both are video calls. All
Cisco TelePresence systems should also register with the same Cisco Unified Communications
Manager cluster because Cisco TelePresence Manager can integrate with only one Cisco
Unified Communications Manager cluster.
The following table lists the fields on the Cisco Unified Communications Manager
Recommendations screen:
Cisco Unified Communications Manager Recommendations
Conditions: Recommendation:
Cisco Unified Communications You can use an existing Cisco Unified Communications
Manager Version 7.0(2) or later Manager cluster.
Cisco Unified Communications You can pick one of your Cisco Unified Communications
Manager Version 7.0(2) or later and Manager clusters and globally use it for all Cisco TelePresence
more than one Cisco Unified systems.
Communications Manager cluster
Video Telephony endpoints on this You must deploy a separate Cisco Unified Communications
cluster Manager cluster to support telepresence.
Codec-to-Cisco Unified Communications
Manager Registration
This topic describes the registration process between the codec and the Cisco Unified
Communications Manager.
Codec-to-Cisco Unified Communications

Manager Registration
 Cisco Unified Communications Manager sees the primary codec
as a SIP endpoint.
 Secondary codecs are invisible to the network.
 The Cisco Unified IP Phone 797xG runs SIP, not SCCP.
 The primary codec and IP phone share the line appearance.
Ethernet
Ethernet and PoE
SIP
Cisco Unified Communications Manager sees the Cisco TelePresence primary codec as a SIP
endpoint. Each endpoint is assigned a directory number and is configured for all device-level
settings, such as video resolution and bandwidth, access privileges for the local web
administration interface, firmware version, and other attributes.
The secondary codecs are invisible to the network. The primary codec in each room manages
all of the local elements of the Cisco TelePresence meeting room solution, including the
following:
 Plasma displays
 Cameras
 Speakers
 Microphones
 The Cisco IP Phone 797xG (where users initiate Cisco TelePresence calls)
The Cisco IP Phone 797xG runs SIP, not Skinny Client Control Protocol (SCCP). Also, the
primary codec and IP phone share a line appearance.

Cisco TelePresence System
Network Protocol Interaction
Cisco Unified
Cisco Unified Access-Edge Communications Cisco TelePresence
Primary Codec Switch Manager Manager
IP Phone 797xG
LAN/
WAN
802.3af
Cisco Discovery Cisco Discovery Protocol
Protocol Cisco Discovery Protocol
DHCP
DHCP
TFTP
HTTP on port 6970
SIP
Shared Line
SIP
XML/HTTP XML/HTTP
No 802.1Q VLAN Tag

Tagged with 802.1Q ID of Voice VLAN
Protocol Interaction
The figure shows the Cisco TelePresence network protocol interaction:
 The 802.3af protocol negotiates PoE.
 Cisco Discovery Protocol finds the voice VLAN.
 DHCP obtains the IP address for the IP phone. Optionally, DHCP can obtain the IP address
for the codec.
 The IP phone uses TFTP to download the configuration files.
 HTTP on port 6970 is used for firmware upgrades and to download configuration files on
the codec.
 SIP manages the call setup. The IP phone and codec use a shared line.
 XML/HTTP is used to download the user interface for the endpoint.
Cisco TelePresence System Media Path
Cisco Unified
Cisco Unified Primary Communications Primary Cisco Unified
IP Phone 797xG Codec Manager Codec IP Phone 797xG
1
2 3
XML/HTTP
SIP INVITE 4
SIP INVITE
XML RING
5
7 6
XML ANSWER
SIP 200 OK
SIP 200 OK
RTP Medi a
(Audio and Video)
Note: Signaling has been simplified for the purpose of this slide.
Signaling Many other XML and SIP mes sages are not shown.
Media
Cisco TelePresence System Media Path

The figure traces the media path progression when initiating a Cisco TelePresence system
session:
Step 1 The local IP phone sends an XML/HTTP message to the local primary codec.
Step 2 The local primary codec sends a SIP INVITE to Cisco Unified Communications
Manager.
Step 3 Cisco Unified Communications Manager sends a SIP INVITE to the remote primary
codec.
Step 4 The remote primary codec sends an XML RING to the remote IP phone.
Step 5 The remote IP phone sends an XML ANSWER back to the remote primary codec.
Step 6 The remote primary codec sends a SIP 200 OK to Cisco Unified Communications
Manager.
Step 7 Cisco Unified Communications Manager sends a SIP 200 OK to the local primary
codec.
Step 8 RTP media streams begin for both audio and video between the Cisco TelePresence
endpoints.
Note Signaling has been simplified for the example. The figure does not show many other XML
and SIP messages that occur.

Video Quality Negotiation
 Resolution changes from 1080p to 720p because of:
– Insufficient bandwidth between Cisco Unified
Communications Manager regions
– 720p-only Cisco TelePresence endpoint joining a 1080p
multipoint meeting
 Meeting participants experience a glitch or call drop.
 A SIP re-invite with new H.264 parameters handles the change.
On-Screen Notification
Best Better Good Lite

1080p 4 Mb/s 3.5 Mb/s 3 Mb/s
720p 2.25 Mb/s 1.5 Mb/s 1 Mb/s 936 Kb/s
During a session, the resolution on the Cisco TelePresence displays can change from 1080p to
720p because of the following situations:
 Insufficient bandwidth exists between the Cisco Unified Communications Manager
regions.
 A Cisco TelePresence endpoint that supports only 720p joins a 1080p multipoint meeting.
When the resolution change occurs, meeting participants experience a glitch or call drop. A SIP
reinvite with the new H.264 parameters manages this change and the following on-screen
notification appears:
The quality has been reduced due to the network configuration.
The following table lists the display-resolution options:
Display Resolution
Video Region Bandwidth Per Best Better Good

Segment
1080p 4 Mb/s 3.5 Mb/s 3 Mb/s
720p 2.25 Mb/s 1.5 Mb/s 1 Mb/s
Configuration for Cisco TelePresence
This topic describes the configurations that you make in Cisco Unified Communications
Manager to support a Cisco TelePresence system.

Configuration for Cisco TelePresence
 Cisco TelePresence systems are configured in Cisco Unified
Communications Manager, just like IP phones are.
 Cisco TelePresence systems download their configuration and firmware
updates from Cisco Unified Communications Manager, via HTTP.
You configure Cisco TelePresence systems in Cisco Unified Communications Manager just as
you do an IP phone. You can manually add Cisco TelePresence endpoints in Cisco Unified
Communications Manager Administration by using the Phone Configuration windows. The
Cisco TelePresence systems download their configurations and firmware updates from Cisco
Unified Communications Manager via HTTP.
Perform the following steps to add a Cisco TelePresence system to Cisco Unified
Communications Manager:
Step 1 Open a web browser and enter https://x.x.x.x/ccmadmin, where x.x.x.x is the IP
address of the Cisco Unified Communications Manager.
Step 2 Enter the username admin and its password.
Step 3 Choose Device > Phone.
Step 4 Click the Add New button.
Step 5 From the Phone Type drop-down list box, choose the appropriate Cisco
TelePresence type or device, and then click Next.
Step 6 Enter the appropriate settings. Only those settings that are appropriate to the chosen
type are displayed in the window.
Step 7 Click Save.

Device Information
Set the Location field for audio
and video bandwidth to “Unlimited.”
Specify the firmware image

to use if different from
preconfigured “Device
Unlimited Default.”
Image names are in the

format
SIPTS.<release>.sbn.
Allow audio-only
call if video is
Allow control of unavailable.
device from CTI.
When configuring the device information for a Cisco TelePresence endpoint, set the Location
field for audio and video bandwidth to Unlimited. Be sure to specify the firmware image to use
if that image is different from the preconfigured Default Device. The phone load image names
are in the format SIPTS.release.sbn, where release is the codec firmware version.
The following two check boxes at the bottom of the Device Information section must remain
checked:
 Retry Video Call as Audio (allows an audio-only call if video is unavailable)
 Allow Control of Device from CTI
The Ignore Presentation Indicators check box should remain unchecked.
The following table lists the fields on the Device Information screen:
Device Information Fields
Field Required Setting
MAC Address Yes MAC address for the Cisco TelePresence device
Description No Short description of the device
Device Pool Yes Default

Common Device Configuration No <None>
Phone Button Template Yes Standard_Cisco_TelePresence
Common Phone Profile Yes Standard Common Phone Profile
Calling Search Space No <None>
Media Resource Group List No <None>
Location Yes Unlimited
User Locale No <None>
Network Locale No <None>
Device Mobility Mode No Default
Owner User ID No <None>
Phone Load Name No Empty field
Retry Video Call as Audio Yes Checked
Ignore Presentation Indicators No Unchecked

(internal calls only)
Allow Control of Device from CTI Yes Checked
Logged Into Hunt Group No Checked by default
Remote Device No Unchecked

Protocol Specific Information
The SIP connection between
the Cisco TelePresence system
and the Cisco Unified
Cisco TelePresence supports
TCP or UDP.
SIP specific call control

parameters:
timers and media port
range, etc.; defaults are
recommended.
Do not use MTPs with

Cisco TelePresence.
For the SIP connection between the Cisco TelePresence system and Cisco Unified
Communications Manager, the Cisco TelePresence system supports TCP or UDP. For the SIP-
specific call control parameters, the defaults are recommended. Do not use Media Termination
Points (MTPs) with Cisco TelePresence.
Do not check the following two check boxes:
 Media Termination Point Required
 Unattended Port
Protocol Specific Information
Packet Capture Mode Yes None

Packet Capture Duration No 0
Presence Group Yes Standard Presence group
SIP Dial Rules No Leave field as <None>
MTP Preferred Originating Yes 711ulaw
Codec
Device Security Profile Yes Cisco TelePresence–Standard SIP Non-Secure Profile
Rerouting Calling Search No Leave field as <None>
Space
SUBSCRIBE Calling Search No Leave field as <None>
Space
SIP Profile Yes Standard SIP Profile
Digest User No Leave field as <None>
Media Termination Point No Leave unchecked
Required
Unattended Port No Leave unchecked
Product Specific Configuration Layout
Enable or disable
web access.
Email address of Cisco

TelePresence system
mailbox in Exchange
(e.g., room1@cisco.com)
Put plasma displays to

sleep to conserve
power.
Video quality
Default idle phone
display
Address of Cisco
TelePresence
Recording Server
The following table lists the fields on the Product Specific Configuration Layout screen:
Product Specific Configuration Layout
Cisco TelePresence Type Yes Cisco TelePresence system choices:

■ Cisco TelePresence 500
Admin Web Access Yes This field is Enabled by default and allows access to the
Cisco TelePresence Web Administration interface.
Room Name (from No If you have the Cisco TelePresence Manager
Exchange(R)) application, then the name of the conference room is
required. The name must exactly match the room name
(including domain name) as it is entered in the Exchange
Server database. The name is used to schedule
conference calls.
This field accepts a text string with a maximum of
64 characters.
Maximum Call Duration (in Yes This is the maximum number of minutes that are allowed
minutes) for a call.
■ Default: 0 (no call duration set)
■ Maximum: 10,080 (7 days)
The call ends at the number of minutes that you
configure. The default setting means that the call never
ends automatically.
Quality (per Display) Yes This field configures the bandwidth that the system uses.
Higher bandwidth increases video quality but can also
cause packets to be dropped and video to be interrupted.

The default is Highest Detail, Best Motion: 4 Mb/s 1080p.

The choices include the following:
■ Highest Detail, Best Motion: 4 Mb/s 1080p
■ Highest Detail, Better Motion: 3.5 Mb/s, 1080p
■ Highest Detail, Good Motion: 3 Mb/s, 1080p
■ High Detail, Best Motion: 2.25 Mb/s, 720p
■ High Detail, Better Motion: 1.5 Mb/s, 720p
■ High Detail, Good Motion: 1 Mb/s, 720p
Days Display Not Active No This field specifies the days of the week that the Cisco
TelePresence system display remains off by default. The
available choices are Monday through Sunday. The
default is Sunday and Saturday.
Display On Time No This field configures the time each day that the display
turns on automatically (except on the days that are
specified in the Days Display Not Active field).
Display On Duration No This field configures the length of time that the display
remains on after turning on at the time that is specified in
the Display On Time field.
Presentation Input Device Yes From this list, choose the Auto Collaboration input
option.
Presentation Output Device Yes From this list, choose the Auto Collaboration output
option
Lights Yes This field defines how the lights operate in a Cisco
TelePresence room:
■ On with calls only
■ On with display settings
■ On all the time
The default is On with calls only.
Idle Display Yes This field determines which screen displays on the IP
phone interface when the Cisco TelePresence system is
idle:
■ Default
■ Manual
■ Directory
■ Favorites
The default is Default.
CTS Auto Answer No You can set the primary codec to automatically answer
the incoming call or to send an incoming call alert to the
Cisco IP Phone 7975G.
Alternate CUCM for No Use an alternate Cisco Unified Communications
Directory Lookup Manager for directory lookup.
Note The primary codec learns its own Cisco TelePresence Type from Cisco Unified
Product Specific Configuration
Layout (Cont.)
Enable additional
hardware if installed.
Configure auxiliary
control unit
when lighting shroud
Login and password is turned on.
for SSH access
SNMP
configuration
parameters
The following table lists additional fields on the Product Specific Configuration Layout screen:
Product Specific Configuration Layout (Optional Hardware and Auxiliary Control

Unit)
Optional Hardware
Presentation Codec No Check whether an HFR codec is used.
A/V Expansion Box No Check whether an audio/video (A/V) expansion box is
used.
Auxiliary Control Unit Specify if an auxiliary control unit is used.
Auxiliary Control Unit – (If Installed)
Power Control Yes The On with calls only option enables the auxiliary
control unit when you turn on the lighting shroud.

Product Specific Configuration Layout (SSH)
Secure Shell User Yes Username for the SSH account that is used for SSH
access and to access the Cisco TelePresence Web
Administration page. Usernames must be at least 5 but
no more than 64 characters in length and can contain
uppercase and lowercase alphanumeric characters as
well as the underscore and dash characters.
The default username is “admin.” The following
usernames are not allowed: apache, daemon, nobody,
operator, and shutdown.
Secure Shell Password Yes This password is used for the SSH account that is used
for SSH access and to access the Cisco TelePresence
Web Administration page. The default password is
“cisco.”
Passwords must be at least 5 but no more than 64
characters in length and can contain uppercase and
lowercase alphanumeric characters as well as the
underscore and dash characters.
Product Specific Configuration Layout (SNMP)
Enable SNMP Yes SNMP is disabled by default, but must be enabled for the
Cisco TelePresence system to support SNMP.
SNMP(v3) Password Yes This password is used to gain access to the SNMP
server that is associated with the Cisco TelePresence
system. This field accepts a string with a maximum of
32 characters. The password must contain at least 8
characters. The default password is “snmppassword.”
SNMP System Location Yes This value is the physical location of the SNMP system
that is associated with this Cisco TelePresence system.
This field accepts a text string with a maximum of
64 characters. The default is “location.”
SNMP System Contact Yes This value is the name of the SNMP system contact that
is associated with this Cisco TelePresence system. This
field accepts a text string with a maximum of
64 characters. The default is “contact.”
SNMP(v2c) Community Yes This value is the SNMPv2c Read Only string.
Read Only
SNMP(v2c) Community Yes This value is the SNMPv2c Read Write string.
Read Write
Product Specific Configuration Layout (SNMP Trap)
SNMP Trap Receiver Yes This value is the IP address or hostname of the SNMP
Address trap receiver (the remote SNMP system). This field
accepts a text string with a maximum of 64 characters.
The default IP address is 192.168.1.1.
SNMP Trap Username Yes This username is used to access the system on which
SNMP traps are received. This field accepts a text string
with a maximum of 64 characters. The username must
begin with a letter. The default username is “trapuser.”
SNMP Security Level Yes This field indicates the password authentication type that
should be set for the trap receiver:
■ No Authentication, No Privacy
■ Authentication, No Privacy
■ Authentication, Privacy
The default security level is No Authentication, No
Privacy.
SNMP Trap Password Yes This password is used to access the system on which
SNMP traps are received. This field accepts a string with
a maximum of 32 characters. The default password is
“trappassword.”
SNMP Auth. Algorithm Yes This value should be MD5.
SNMP Privacy Password Yes This field indicates the SNMP privacy password that is
used to access the system on which traps will be
received. This field accepts a string with a maximum of
32 characters. The default privacy password is
“privacypassword.”

Cisco Unified IP Phone 797xG
This topic describes the Cisco Unified IP Phone 797xG.

 The phone provides the end-user interface for the Cisco
TelePresence system.
 The phone provides directory and one-button access information
for meetings scheduled through Microsoft Outlook and Exchange
Server.
 The meeting information from Exchange Server comes through
the integration with Cisco TelePresence Manager.
The Cisco TelePresence room solutions use a Cisco IP Phone 797xG, which is conveniently
located on the table, to launch, control, and conclude meetings. This feature makes Cisco
TelePresence as easy to use as an ordinary telephone.
The user uses the high-resolution touchscreen display of the Cisco IP Phone 797xG to dial the
telephone number of the Cisco TelePresence room with which they wish to establish a meeting,
and the call is connected. This menu is an XML service that the phone subscribes to on its
primary codec.
Softkey menu buttons on the phone allow the user to place the call on hold or to conference in
another party. When used with Cisco TelePresence Manager, the phone displays the schedule
of meetings for the day. The user simply touches the appropriate location on the screen to
launch that scheduled meeting.
Cisco Unified Communications Manager:
Device > Phone
 Choose Device > Phone.
 Click Add New.
 Choose SIP as device protocol.
Product Type: Cisco 7970

Device Protocol: SIP
Device > Phone

You use the Cisco Unified Communications Manager Administration tool to add the Cisco IP
Phone 797xG.
Follow these steps to add the Cisco IP Phone 797xG as a SIP phone to the Cisco Unified
Step 1 Access the Cisco Unified Communications Manager Administration tool by going to
https://cm-server-name, where cm-server-name is the name or IP address of the
server.
Step 3 Click the Add New button at the bottom of the window to display the Add a New
Phone window.
Step 4 In the Phone Type drop-down list, choose Cisco 7970, and then click Next.
Step 5 In the Device protocol drop-down list, choose SIP.
Step 6 Click Next to display the Phone Configuration window.

Disable Speakerphone and Headset
 If speakerphone and headset are not disabled and the system is
set to auto answer, the phone might answer with voice only.
Ensure that the following parameters at the bottom of the Product Specific Configuration
Layout section are checked:
 Disable Speakerphone
 Disable Speakerphone and Headset
Shared DN
 Configure the same DN (shared line appearance) on the Cisco
TelePresence primary codec and Cisco IP Phone 797xG.
 Set Max Calls to 4 and Busy Trigger to 2.
 (Optional) Configure Call Forward to a customer voice-mail
greeting such as, “The Cisco TelePresence system you have
called is {busy | not answering}. Please consult your Microsoft
Outlook calendar for room availability or try your call again later.”
Cisco DN 1000
Unified
Communications
Manager
DN 1000
Gigabit Ethernet
Ethernet and PoE
SIP
Use the following guidelines when configuring the Cisco IP Phone 797xG:
 When you configure the dial numbers, use the same directory number on the Cisco
TelePresence primary codec and Cisco IP Phone 797xG. This configuration creates a
shared line appearance.
 Set Max Calls to 4 and Busy Trigger to 2.
 You can optionally use call forwarding to a customer voice-mail greeting. The following is
an example of a call forwarding message:
“The Cisco TelePresence system you have called is {busy | not
answering}. Please consult your Microsoft Outlook calendar for
room availability or try your call again later.”

Enhanced Phone User Interface:
Download MIDlets
http://www.cisco.com/kobayashi/sw-center/index.shtml
 Click TelePresence Software.

 Choose the endpoint type.
 Choose a software release.
 Download MIDlet phone application.
Requires a phone firmware load of 8.4(3)
or later
MIDlet is a Java application framework. Typically, MIDlets are used for the Mobile
Information Device Profile (MIDP) that a Java-enabled cell phone or other embedded device or
emulator commonly use. MIDlets are applications, such as games, applications on a Cisco IP
phone, and so on.
To support MIDlets, you must use Cisco Unified Communications Manager Version 7.0(2). To
enable MIDlet-based phone services, you must first download the Cisco TelePresence MIDlet
Phone Application software. Follow these steps to download the software:
Step 1 Go to http://www.cisco.com/kobayashi/sw-center/index.shtml.
Step 2 Click TelePresence Software.
Step 3 Expand the following folders, in order: Cisco TelePresence System folder,
TelePresence System folder, and the folder that corresponds with your Cisco
TelePresence System (for example, Cisco TelePresence System 3200).
Step 4 The Select a Release window opens. From this window, click the link for the version
of Cisco TelePresence Software that you have (you might need to expand the All
Releases folder).
Step 5 A list of files that you can download appears in the right side of the Download
Software window. Click the link for the Cisco TelePresence MIDlet Phone
Application software that you want to download.
Caution Do not change the name of the downloaded files.
TFTP Directory: Upload Files
Upload the desired .jad and .jar files to the Cisco Unified
Communications Manager TFTP directory:
 From Navigation drop-down menu, choose Cisco Unified OS
Administration and click Go.
 Log into Cisco Unified OS Administration.
 From Software Upgrades, choose TFTP File Management and click
Upload File.
 Browse to find the appropriate file and upload it.
Restart Cisco Unified CM TFTP server:
 From the Navigation drop-down menu, choose
Cisco Unified Serviceability and click Go.
 Log into Cisco Unified Serviceability.
 From Tools, choose Control Center – Feature Services.
 From Select Server, choose the TFTP server and click Go.
 From CM Services, click the Cisco TFTP radio button and click Restart.
After you have downloaded the appropriate files, upload them to the Cisco Unified
Communications Manager TFTP directory.
Follow these steps to upload the desired .jad and .jar files to the TFTP directory:
Step 1 From the Navigation drop-down menu in Cisco Unified Communications Manager,
choose Cisco Unified OS Administration, and then click Go.
Step 2 Log into Cisco Unified OS Administration.
Step 3 From Software Upgrades, choose TFTP File Management, and then click the
Upload File button. A dialog box appears.
Step 4 Browse to find the appropriate file and upload it.
When the files have been uploaded to the TFTP directory, follow these steps to restart the Cisco
Unified TFTP server:
Step 1 From the Navigation drop-down menu, choose Cisco Unified Serviceability, and
then click Go.
Step 2 Log into Cisco Unified Serviceability.
Step 3 From the Tools menu, choose Control Center - Feature Services.
Step 4 From Select Server, choose the TFTP server and click Go.
Step 5 From CM Services, click the Cisco TFTP radio button.
Step 6 Click Restart.
Step 7 Repeat steps 1 to 6 for all of the TFTP servers.

Cisco Unified Communications Manager:
Device Settings > Phone Services
Click Add
New.
Set up the new

MIDlets
services and
click Save.
Follow these steps to create the IP Phone Service in Cisco Unified Communications Manager:
Step 1 From the Navigation drop-down menu in Cisco Unified Communications Manager,
choose Cisco Unified CM Administration, and then click Go.
Step 2 From the Device menu, choose Device Settings > Phone Services.
Step 3 Click the Add New button and fill in the following fields:
 Service Name: The service name must match the filename of the .jad file. Your
filename must not contain the .jad extension. The .jad extension is appended
automatically when you name the file.
 ASCII Service Name: The ASCII service name must match the configured
service name.
 Service Description: Java MIDlet
 Service URL: The Service URL should be in the following format:
http://xx.xx.xx.xx:6970/TSPM.y-y-y-YY.jad, where the following is true:
— xx.xx.xx.xx is the IP address of the Cisco Unified Communications
Manager server (172.28.71.59 in the example in the figure)
— y-y-y is the version of the MIDlet application that is being added to Cisco
Unified Communications Manager (1-5-0 in the example in the figure)
— YY is the build version of the MIDlet application that is being added to
Cisco Unified Communications Manager (15DEV in the example in the
figure)
 Service Category: Java MIDlet
 Service Type: Standard IP Phone Service
 Service Vendor: Cisco
Step 4 Check the Enable check box.
Step 5 Click Save.
Configure IP Phone to Run New Service
 Subscribe the Cisco

TelePresence phone to
the new MIDlets service
that you created.
 This is similar to
subscribing a regular IP
phone to a service.
To configure each Cisco IP Phone 797xG to run the new IP phone service, follow these steps:
Step 1 From the Navigation drop-down menu, choose Cisco Unified CM Administration,
and then click Go.
Step 2 From the Device menu, choose Phone.
Step 3 From the Phone Device page, configure the Authentication URL.
Step 4 From the Related Links drop-down list (top right corner of the page), choose
Subscribe/Unsubscribe Services.
Step 5 Click Go.
Step 6 Choose the new IP phone service from the Select a Service drop-down list. If the
phone is already subscribed to an older MIDlet version, follow these steps:
 Unsubscribe the phone from the older service.
 Subscribe the phone to the new IP phone service that you created.

IP Phone Subscribed to MIDlets Service
 The Cisco TelePresence system phone is now subscribed to the
MIDlets service.
 This service is more user friendly and enables easier conference
controls.
The Cisco TelePresence phone is now subscribed to the MIDlets service that you created. The
MIDlets service is more user-friendly and enables easier conference controls. When starting the
MIDlets interface for the first time, you must press the Service button on the Cisco
TelePresence Phone user interface to start the application.
For Upgrades to Enhanced Interface:
Remove External Data Locations URL
Remove the previously configured URLs.
If you are changing the Cisco Unified IP phone interface from the existing Cisco TelePresence
system interface to the new enhanced interface, follow these steps from the Phone Device page:
 Remove the Service URL from the phone configuration.
 Remove the Idle URL from the phone configuration.
 Set the Idle Timer to 0 in the phone configuration.
Cisco Unified IP Phone 797xG External Data Location Settings
Information No Leave blank.
Directory No Leave blank.
Messages No Leave blank.
Services No Clear the previously configured URL.
Authentication Server No Clear the previously configured URL.
Proxy Server No Leave blank.
Idle No Clear the previously configured URL.
Idle Timer (Seconds) No Set to 0.

CAC Considerations
This topic describes CAC considerations.
CAC Considerations
 Currently, Cisco Unified Communications Manager locations-
based CAC cannot distinguish between a Cisco TelePresence
call and other types of video-telephony or video-conferencing
calls.
– Video-telephony calls could absorb all available bandwidth,
leaving none available for telepresence calls.
 RSVP is not yet supported for Cisco TelePresence.
– Because there is only one application ID (video), there is no
way to distinguish between an RSVP reservation for a Cisco
TelePresence call and other types of video-telephony or video-
conferencing calls.
– The Cisco IOS RSVP Agent does not currently support
telepresence video streams.
For the initial release of the Cisco TelePresence suite of virtual meeting solutions, you should
use a single Cisco Unified Communications Manager server or cluster to support all Cisco
TelePresence devices within a deployment. Currently, the Cisco TelePresence Manager
scheduling server can schedule Cisco TelePresence meetings only across a single cluster.
Although devices can register across multiple Cisco Unified Communications Manager clusters
and ad hoc and permanent meetings can be established between clusters, this design is not
currently recommended.
Similarly, in an integrated deployment in which you deploy Cisco TelePresence along with
other desktop video devices on the same cluster, Cisco Unified Communications Manager
cannot instruct desktop video and telepresence to use different QoS markings. The marking of
audio and video traffic by Cisco Unified Communications Manager is managed at the cluster
level, not at the device level. Cisco TelePresence also requires Cisco Unified Communications
Manager Version 7.0(2) or later. If a customer has a single Cisco Unified Communications
Manager cluster running Version 7.0(2) or later deployed for IP telephony and has no desktop
video devices, then integrating Cisco TelePresence devices onto that cluster might be
acceptable. However, most initial deployments are not expected to meet these criteria, so a
separate Cisco Unified Communications Manager cluster should be deployed to support Cisco
TelePresence.
CAC Recommendations
 Option 1—Create separate locations for Cisco TelePresence.
 Option 2—Use a dedicated Cisco Communications Manager
cluster for Cisco TelePresence.
Cisco Unified
Locations Bandwidth Communications
Manager
Location Bandwidth
Location A—Cisco 12000
TelePresence
Location A 3000
Location B—Cisco 12000
TelePresence
Location B 3000
Location C—Cisco 12000
TelePresence
Location C 3000
Location A Location A Location B Location B
Cisco TelePresenc e Cisco TelePresence
You can use Cisco Unified Communications Manager static location-based CAC for hub-and-
spoke network topologies. In this scenario, you should configure each remote site as a separate
location within the Cisco Unified Communications Manager configuration. You should then set
the video bandwidth settings for each location to match the amount of bandwidth that is
allocated for telepresence traffic (audio and video) across the WAN circuits, minus the protocol
overhead. Cisco Unified Communications Manager does not take into account the protocol
overhead for video traffic.
If video fails and you want the Cisco TelePresence meeting to proceed with audio only, then set
the audio bandwidth settings for each location. Remember that audio bandwidth is not deducted
from the audio bandwidth pool for the location when the call is set up as a video call.

Troubleshooting
This topic describes how to troubleshoot the Cisco TelePresence system.
Troubleshooting: Call Pixilation Issues

 Symptom:
– All or some endpoints in the call are experiencing pixilation.
 Diagnosis:
– Call statistics show packet loss, jitter, or latency above warning
thresholds.
– The network might be experiencing congestion.
 Solution/Workaround:
– Press the Hold/Resume button or reinitiate the call.
– Re-examine network QoS settings and retest.
 Verification:
– Call other Cisco TelePresence system endpoints to verify that other
systems are not experiencing the same problems.
– Test the network QoS configuration.
 Escalation:
– Gather audio and video logs from all units involved in the call,
including Cisco TelePresence Multipoint Switch logs if the call was a
multipoint call.
If some of the Cisco TelePresence endpoints in a call experience pixilation, then packet loss,
jitter, or latency above the warning threshold could be causing the problem. he network might
be experiencing congestion.
A workaround to this congestion is to press the Hold/Resume button or to reinstate the Cisco
TelePresence call. However, you should re-examine the network QoS settings and retest the
call.
To verify the network, call other Cisco TelePresence systems and verify that they are not
experiencing the same problems. You should always test your network QoS configuration to
verify services from end to end.
To escalate the problem to Cisco, be sure to gather audio and video logs from all of the Cisco
TelePresence endpoints that were involved in the call, including the Cisco TelePresence
Multipoint Switch logs if the call was multipoint.
Viewing the Call Statistics
admin:
show call statistics all detail
 Displays the call statistics of the current call
Example:
(output omitted)
admin:show call statistics
-- Video --
IP Addr Src : 172.16.2.206:30316 Dst : 172.16.2.201:16386
Latency Avg : 1 Period : 1
Statistics Left Center Right 0

Pkts % Call 0.0000 0.0000 0.0000 0.0000
Pkts % Period 0.0000 0.0000 0.0000 0.0000
Rx Pkts OOO 0 0 0 0
Rx Pkts Dup'd 0 0 0 0
Rx Pkts Late 0 0 0 0
Rx Pkts AuthFail 0 0 0 0
Rx Jitter/Call 0 1 0 0
Rx Jitter/Period 0 1 0 0
Enter the show call statistics all detail command to display the call statistics of the current call
to check the latency, loss, and jitter.
The figure shows the output of a Cisco TelePresence System 3000 or 3200 and displays the
packet statistics for the left, center, and right displays.

Troubleshooting: Call Echo Issue
 Symptom:
– Audio echo is heard in some or all endpoints.
 Diagnosis:
– Call statistics show packet loss, jitter, or latency above warning
thresholds.
– The physical design of the room is causing excessive reverberation
and might not be to RRA specifications.
– Press the Hold/Resume button or reinitiate the call.
– Re-examine network QoS configuration.
– Test the Cisco TelePresence room reverberation by using RT60 test.
 Verification:
– Call other Cisco TelePresence system endpoints to verify that other
systems are not experiencing the same problems.
– Test the network QoS configuration.
If an audio echo is heard in some or all of the Cisco TelePresence system endpoints, the
following could be causing the problem:
 Packet loss, jitter, or latency above the warning threshold
 The physical design of the room, which can cause excessive reverberation and might not be
up to room readiness assessment (RRA) specifications
A workaround to the audio echo problem is to press the Hold/Resume button or to reinitiate the
call. You should also re-examine the network QoS configuration to verify end-to-end service.
In addition, test the Cisco TelePresence room reverberation by conducting the RT60 test.
To verify network congestion issues, call other Cisco TelePresence system endpoints to
determine whether they are experiencing the same problem. See if you can isolate the echo
problem to one room. Finally, you should test your network QoS configuration.
Troubleshooting: Call Failures
 Symptom:
– You are unable to place or receive calls.
 Diagnosis:
– The Region/Locations settings do not have enough bandwidth
allocated in Cisco Unified Communications Manager.
– The route pattern is not correctly configured in Cisco Unified
– Try calling other endpoints to isolate the problem.
– Call by using the codec CLI.
– Check the Region/Location settings in Cisco Unified Communications
Manager.
 Verification:
– Examine the SIP messages from the codec and the Cisco Unified
Communications Manager for proper call negotiation.
 Escalation:
– Download logs from all affected endpoints.
Problems placing or receiving Cisco TelePresence calls could be caused by the following:
 The region and location settings do not have enough bandwidth allocated in Cisco Unified
 There is a call routing problem in which the route pattern was incorrectly configured in
To isolate the problem, try calling other Cisco TelePresence endpoints. When you make the
calls, use the CLI of the codec. Also, check the region and location settings in Cisco Unified
Communications Manager. Examine the SIP messages from both the codec and Cisco Unified
Communications Manager, to determine whether there is proper call negotiation. When
escalating the problem to Cisco, download the logs from all of the affected endpoints.

Viewing the Call Status
admin:
show call status
 Displays the status of the current call
Example:
admin :cal l st art 1000
admin :sho w ca ll status
Cal l Status
Regis tere d to Cisco Uni fied Communica tions Mana ger : Yes
Call in P rogr ess : Yes
Call Type : A udio/ Video Cal l Call Star t Tim e: Jul 22 18:56:56
2011
Durat ion (sec ) : 34 Direc tion : Outgoin g
Local Num ber : 6 000 Remot e Nu mber : 1000
State : A nswer ed Bit R ate : 4000000
bps,1 080p
Secur ity Leve l : N on-Se cure
To initiate a call from the CLI to an endpoint with a dial number of 1000, issue the call start
1000 command.
To verify the call status of the call from the Cisco TelePresence system codec, issue the show
call status command.
Troubleshooting: Upgrade Problems
 Symptom:
– The plasma display or secondary codec was not upgraded correctly.
 Diagnosis:
– The plasma display or secondary codec displays a failure status from
the web interface.
– The plasma display or secondary codec does not function during a
call.
– The firmware or application code version is mismatched between
codecs.
– Restart the upgrade by restarting the codec from the CLI or web
interface.
– Force an upgrade from the CLI.
 Verification:
– Examine the application code version from the CLI or web interface.
 Escalation:
– Download the logs from all affected endpoints.
If the plasma display or secondary codec was not upgraded correctly, then the display or
secondary codec might display a failure status from the web interface. The codec might not
even function during a call. This behavior is because the firmware or application code version
does not match between codecs.
To solve this problem, restart the upgrade process by restarting the codec from the CLI or web
interface, or force an upgrade from the CLI. You can examine the application code version
from both the CLI and the web interface. When escalating the problem to Cisco, be sure to
download the logs from all of the affected endpoints.

Viewing the Firmware Version
admin:
show version
 Displays the version of codec firmware
Example:
admin :sho w ve rsion
prima ry
*Fa ctor y /dev/hda20 CTS 1.5.1 (208 2)
Sl ot 1 CTS LB(381 9)
Sl ot 2 CTS 1.6.0( 3585) “*” = active image
left
Sl ot 2 CTS 1.6.0( 3585)
right
Sl ot 2 CTS 1.6.0( 3585)
syst em u nava ilable
Enter the show version command at the CLI to examine the firmware.
Forcing a Manual Firmware Upgrade

admin:
set upgrade [camera|audio|auxilary-ctrl|display|firmware]
 Forces a manual upgrade of component firmware
Example:
admin:set upgrade display
Setting forced display upgrade
Enter the set upgrade display command at the CLI to manually force an upgrade of firmware.
Summary
Summary
 Cisco TelePresence provides an end-to-end solution by
multiplexing video and audio streams over the network.
 The Cisco TelePresence codec is responsible for multiplexing
video and audio streams on the network.
 Cisco provides a web interface for administration of the Cisco
TelePresence codec.
 In Cisco Unified Communications Manager, the Cisco
TelePresence endpoints are configured like an IP phone.
 The Cisco TelePresence codec registers with the Cisco Unified
 You configure Cisco TelePresence systems in Cisco Unified
Communications Manager just as you would an IP phone.
 The Cisco Unified IP Phone 797xG has an enhanced user
interface for the Cisco TelePresence endpoint.
Summary (Cont.)
 You must think about certain CAC considerations when deploying
Cisco TelePresence along with other desktop video that uses
QoS markings.
 Verify Cisco TelePresence by troubleshooting the system
integration.

Lesson 2
Examining the Cisco

TelePresence User Interface
Overview
The Cisco TelePresence user interface of the Cisco Unified IP Phone 797xG is designed with
touchscreen items and softkeys to help you connect to another Cisco TelePresence phone and
start a video teleconference. You can also make audio-only calls by using the Cisco
TelePresence phone and conferencing in audio-only calls during a meeting. Starting a Cisco
TelePresence meeting is as easy as touching a phone or directory icon or, if you have Cisco
TelePresence Manager, touching a highlighted scheduled meeting notice on the Cisco
TelePresence phone user interface. Software launches the meeting components and determines
the best settings for the call. The Cisco TelePresence phone user interface displays details about
active calls and meetings.
Objectives
Upon completing this lesson, you will be able to use the Cisco TelePresence phone user
interface. This ability includes being able to meet these objectives:
 Describe the Cisco Unified IP phone that the Cisco TelePresence system uses
 Describe the One-Button-to-Push features of the Cisco Unified IP phone
 Conference an audio-only call into a Cisco TelePresence session
 Describe the multiple audio and video call support features
 Describe the meeting control options
 Control the document camera from the IP phone
 Describe the Cisco Auto Collaborate Presentation Privacy alert
 Describe the Cisco TelePresence in-call icons
 Describe the user interface on phone alerts, status, and messages
Cisco TelePresence Phone User Interface
This topic describes the Cisco Unified IP phone that comes with the Cisco TelePresence
system.
Cisco TelePresence Phone

User Interface
A Cisco Unified IP Phone 797xG is
provided with the Cisco TelePresence
system. It provides a user interface to
the Cisco TelePresence system via a
touch screen.
 The Cisco TelePresence user interface is
shown on the Cisco IP Phone 797xG LCD
as Cisco IP Phone Service, for all Cisco
TelePresence user interactions.
 The service page overwrites the original
phone user interface.
– The page is pushed from the primary
codec to the Cisco IP Phone 797xG in
XML over HTTP.
 The input to the Cisco TelePresence user
interface is forwarded to the primary codec
in XML.
The Cisco Unified IP Phone 797xG is the control center for the Cisco TelePresence system.
You perform all of the Cisco TelePresence call functions while the Cisco Unified IP Phone
79xG is on hook. These call functions include placing a Cisco TelePresence call, answering a
Cisco TelePresence call, and conferencing in an audio call. You can also use the Cisco
TelePresence phone off-hook to perform standard telephone functions. The Cisco IP Phone
797xG is conveniently located on the table, to launch, control, and conclude meetings. This
interface makes Cisco TelePresence as easy to use as an IP phone.
The user uses the high-resolution touchscreen display of the Cisco IP Phone 797xG to dial the
telephone number of the Cisco TelePresence room with which the user wants to have a
meeting, and the call is connected. The menu on the phone is an XML service that the phone
subscribes to on its primary coder-decoder (codec). The service page content overwrites the
original phone interface. Softkey menu buttons on the phone allow the user to place the call on
hold or to conference in another party. The IP phone forwards the user input in XML to the
primary codec.
When the phone is used with Cisco TelePresence Manager, the meeting schedule for the day
displays on the phone. The user simply touches the appropriate location on the screen to launch
that scheduled meeting.
Supported Cisco Unified
Communications Manager Versions
The IP phone and primary codec register with Cisco Unified
Communication Manager as SIP devices and share the same line
appearance. The following Cisco Unified Communications Manager
versions are supported:
 Cisco Unified Communications Manager Version 5.1(X)
– cmterm-devicepack5.1.2.3111-1.cop.sgn
– No device pack required
– cmterm--devicepack6.0.1.2111-1.cop.sgn
– No device pack required
 Cisco Unified Communications Manager Version 7.0(2)
– cmterm-devicepack7.0.2.21009-1.cop.sgn
The Cisco IP Phone 797xG includes the Cisco IP Phone Service. The primary codec pushes the
contents of this service in XML format over HTTP. The service provides the user interface for
interacting with the primary codec for call control and other functions. The IP phone and
primary codec register with Cisco Unified Communication Manager as Session Initiation
Protocol (SIP) devices and share the same line appearance.
Cisco TelePresence supports the following Cisco Unified Communication Manager versions:
 Cisco Unified Communications Manager Version 5.1(X)
— cmterm-devicepack5.1.2.3111-1.cop.sgn
— No device pack required
— cmterm--devicepack6.0.1.2111-1.cop.sgn
— No device pack required
 Cisco Unified Communications Manager Version 7.0(2)
— cmterm-devicepack7.0.2.21009-1.cop.sgn
Note Check Cisco.com for the most recent supported versions of software.

Cisco TelePresence Phone Features
 Ad hoc (manual) calls
 System speed dials
 Preview of future scheduled meetings
 One-Button-to-Push dialing for
scheduled meetings
 Ability to add audio-only participants to
a Cisco TelePresence meeting
XML
The Cisco TelePresence system ships with either a Cisco Unified IP Phone 7970G, 7971G, or
7975G, depending on when the system was purchased. The IP phone provides a touchscreen
user interface to the Cisco TelePresence system. The Cisco TelePresence phone displays
touchscreen icons and softkeys to help you connect to other Cisco TelePresence conference
rooms. You can also make audio-only calls by using the Cisco TelePresence phone or
conference in an audio call during a meeting.
Starting a Cisco TelePresence meeting is as simple as touching the New Call or Directory
icons. If Cisco TelePresence Manager is installed, then you can also use the One-Button-to-
Push feature, by touching a scheduled meeting notice on the phone. Cisco TelePresence
Manager launches the meeting components and determines the best settings for the call. The
Cisco TelePresence phone displays details about active calls and meetings.
The following are the Cisco IP Phone 797xG features:
 Ad hoc (manual) calls
 System speed dials
 Preview of future scheduled meetings
 One-Button-to-Push dialing for scheduled meetings
 Ability to add audio-only participants to a Cisco TelePresence meeting
User Interface Improvements—
Java MIDlets
 MIDlets allow better use and control of the Cisco TelePresence phone:
– Dialing of DTMF digits without using the Tones softkey
– Instant telepresence dialing without using the Manual softkey
– Volume rocker button on the phone to support the telepresence call
– Easier conference controls with support for multiple active calls
– Faster response when using the interface
 MIDlets require Cisco Unified Communications Manager Version 7.0(2)
or later.
The enhanced phone user interface of Cisco TelePresence System Release 1.5, also known as
Java MIDlets, allows better use and control of the IP phone that is associated with the endpoint.
You can enter dual tone multifrequency (DTMF) digits without using the Tones softkey. You
can also initiate instant Cisco TelePresence dialing without pressing the Manual softkey. The
volume rocker button on the IP phone now works for telepresence calls. The MIDlets provide
easier conference controls with support for multiple active calls at one time. Finally, there is
much faster response when using the MIDlets interface. Cisco Unified Communications
Manager Version 7.0(2) or later is required to benefit from these new features.

Cisco TelePresence Phone
User Interface—Manual Screen
 Deploying Cisco TelePresence Manager provides scheduled
meetings.
 New Cisco IP Phone 797xG firmware changes color scheme.
Cisco TelePresence Cisco TelePresence

Manager Deployed Manager is not Deployed
Cisco TelePresence Manager is an optional network application that is installed on a Cisco

Media Convergence Server (MCS) 7845 Series. Cisco TelePresence Manager makes it easy for
you to set up and launch calls and eliminates the complexity for administrators who manage
Cisco TelePresence deployments. The Cisco TelePresence Manager software provides the
functionality for scheduling meetings. The One-Button-to-Push meeting launch and automatic
display of meetings on the in-room IP phone makes the in-room experience for users as natural
and simple as possible.
If Cisco TelePresence Manager is installed on the corporate network, then you can schedule a
Cisco TelePresence meeting by using Microsoft Outlook. When you create a meeting request,
Outlook sends an email announcement to notify each person that is invited to the meeting.
Outlook also reserves the Cisco TelePresence rooms that you schedule for the meeting.
Cisco TelePresence Manager and Outlook work together to manage scheduled meetings
between Cisco TelePresence meeting rooms. The only action that you must take to start the
meeting is to find and press the One-Button-to-Push meeting notice on the Cisco TelePresence
phone.
Note In a deployment that does not have Cisco TelePresence Manager installed, the Meetings
icon does not display.
Idle Screen Display Options
Manual
Screen
Scheduled
Meetings
(Default)
Directory
Favorites
(Speed
Dials)
You can specify the idle display that appears on the IP phone screen from within Cisco Unified
Communications Manager. The idle display is an XML service that Cisco IP Phone invokes
when it has been idle (not in use) for a designated period and no feature menu is open.
You can choose between the following three displays as the idle display:
 Manual Screen: This display has the following options:
— New call
— Directory
— Favorites
— Meetings
 Scheduled Meetings: This display is the default idle display and it lists the meetings that
are currently scheduled in Cisco TelePresence Manager.
 Directory Speed Dials: This display lists the speed dials that are configured.

Configuring the Idle Display in Cisco
Unified Communications Manager
Device configuration for Cisco TelePresence endpoint:
 Under Product Specific Configuration Layout section
 Drop-down choices are Default, Manual, and Directory
You configure the Idle Display by using the Cisco Unified Communications Manager
Administration tool.
Follow these steps to configure the Idle Display:
Step 1 Access the Cisco Unified Communications Manager Administration tool by going to
https://cm-server-name, where cm-server-name is the name or IP address of the
server.
Step 3 Click the Add New button at the bottom of the window. The Add a New Phone
window appears.
Step 4 Choose Cisco 7970 from the Phone Type drop-down list, and then click Next.
Step 5 Choose SIP in the Device Protocol drop-down list.
Step 6 Click Next to display the Phone Configuration window. You will find the Idle
Display device configuration under the Product Specific Configuration Layout
section.
Step 7 Use the drop-down menu and choose one of the following:
 Default (Scheduled Meetings)
 Manual
 Directory
Directory
Choose the site from the Directory list on the Cisco
TelePresence phone user interface.
The Cisco TelePresence Manager scheduling and management software facilitates call
scheduling and setup from common enterprise groupware software such as Microsoft Exchange
Server and IBM Lotus Notes. Users can continue to use their existing email and calendaring
applications for scheduling meetings and rooms. When the users enter the Cisco TelePresence
room to start their meeting, they simply select the site from the speed-dial list.
Follow these steps to use the directory to place a call and initiate a meeting:
Step 1 Press the Directory softkey or touch the Directory icon from the Idle screen to
display a searchable directory of all available Cisco TelePresence phone numbers.
Step 2 Use the Up and Down arrow keys on the Cisco TelePresence phone to scroll through
the directory until the endpoint or person that you want to dial is highlighted.
 Each screen displays 31 phone numbers.
 To see the next set of phone numbers, press the Next softkey.
Step 3 After you highlight the desired number, press the Dial softkey to dial the Cisco
TelePresence system. The Cisco TelePresence software takes care of making the
connections between endpoints.

Favorites—Speed Dialing
Choose the site from the speed-dial list on the Cisco
Speed Dials
Favorites speed dialing is a standard Cisco Unified Communications Manager function that the
Cisco TelePresence phone supports. The speed-dial list that is associated with the Cisco
TelePresence phone enables you to readily access phone numbers and quickly connect
meetings from the manual call user interface.
However, unlike most Cisco Unified IP phones, which allow you to enter 99 speed-dial phone
numbers, the Cisco TelePresence phone user interface accepts only 40 phone numbers. These
speed-dial numbers can be numbered from 3 to 42 in the Cisco Unified Communications
Manager Speed Dial and Abbreviated Dial Configuration windows.
The system administrator adds speed-dial phone numbers to the directory. Follow these steps to
use the speed-dial phone numbers:
Step 1 Press the Favorites softkey or touch the Favorites icon from the Cisco
TelePresence phone Idle screen.
Step 2 Use the Up and Down arrow keys on the Cisco TelePresence phone to scroll through
the directory until the Cisco TelePresence room or person that you want to call is
highlighted.
Step 3 Press the Dial softkey. The Cisco TelePresence software makes the connections
between endpoints.
One-Button-to-Push Meeting
This topic describes the One-Button-to-Push features of the Cisco Unified IP phone.
One-Button-to-Push Meeting
If Cisco TelePresence Manager is installed on the corporate network, then you can schedule
meetings by using Outlook or Lotus Notes. You can then start scheduled meetings by using the
One-Button-to-Push feature. Cisco TelePresence Manager launches the meeting components
and determines the best settings for the call.
The Cisco TelePresence Manager administrator configures the number of days of One-Button-
to-Push meetings that the Cisco TelePresence phone stores and displays. The phone is refreshed
with new meetings at the following times:
 Each time the Cisco TelePresence system receives a meeting notice from the Cisco
TelePresence Manager
 At the end of each meeting
 Each night at midnight
To prevent interruption, the Cisco TelePresence Manager waits until there are no active calls or
meetings before updating the schedule.
Follow these steps to display the list of scheduled One-Button-to-Push meetings:
Step 1 Touch the Meetings icon or press the Meetings softkey.
Step 2 When you have located your meeting, touch the entry or highlight the meeting and
press the StartMtg softkey to initiate the call.

Placing a Call
Redial
New Call 11564
 Dial
 End Call
Use one of the following methods to place a call from the Cisco TelePresence phone:
 Press the Redial softkey to dial the last-dialed number.
 Press the New Call softkey or use the dial keypad to start a new call.
— Enter the number to dial on the Dial Page, and then press the Dial softkey.
— Press the End Call softkey to end the Cisco TelePresence call.
Answering a Call
If you receive a call from a remote Cisco TelePresence conference room, you can configure the
Cisco TelePresence conference room to auto-answer the call. If you do not configure auto-
answer, then the Cisco TelePresence phone on the receiving end displays the phone number of
the incoming call, allowing you to do one of the following:
 Touch the highlighted meeting or press the Answer softkey to connect the call
 Press the iDivert softkey to decline the call, which is diverted to voice mail

Placing a Call on Hold
 Hold
 Resume
 Status
If the call is a Cisco TelePresence call, then placing the a call on hold suspends the operation of
the phone, cameras, and microphones on your end of the connection. Plasma display icons
remind you that the call is active but on hold.
To place a Cisco TelePresence call or an audio-only call or to place a conference call on hold,
highlight the call and press the Hold softkey.
If the call is a conference call, the Cisco TelePresence call and the audio-only call are both
placed on hold. Plasma display icons remind you that the call is active but on hold. Press the
Status softkey to display network information about the call.
Do one of the following to resume a call:
 Press the Resume softkey to resume the call.
 If more than one call is on hold, use the Up and Down arrow keys on the Cisco
TelePresence phone to select which call to resume.
Note You cannot conference Cisco TelePresence calls together.
Ending a Call
The phone number that you are dialing displays while the call is being connected. Press the
End Call softkey if you need to hang up.

Calling the Live Desk Agent
The Live Desk agent can provide the following
information:
 System information
 System status
 Support
 Troubleshooting Dials the Live
Desk phone
number
The Live Desk agent is a person that is assigned to a Cisco TelePresence conference room to
assist you with problems that can occur during a meeting. The Live Desk agent is someone who
must understand how to perform the following tasks:
 Schedule meetings
 Use the Cisco Unified IP Phone in a meeting room that is enabled for Cisco TelePresence
 Use the tools that are supplied by the Cisco TelePresence Manager to monitor the system
and the schedule of upcoming meetings and to update meeting requests
 Gather data to supply to the administrator when a problem cannot be easily solved
When the Live Desk agent logs into the Cisco TelePresence Manager, the following selections
and information are available:
 System information
 System status
 Support
 Troubleshooting
When a Live Desk agent is assigned to a Cisco TelePresence conference room, you can press
the Live Desk softkey to display the phone number, connect the call, or both.
Conferencing an Audio Call
This topic describes how to conference an audio-only call into a Cisco TelePresence session.
Conferencing an Audio Call

 Cisco TelePresence has the ability to participate in an audio-only
session.
 During a meeting, you can add (conference in) one audio-only call. Each
Cisco TelePresence endpoint that takes part in a meeting may
conference in one audio-only call.
 The security level of the Cisco TelePresence meeting may change to
match the highest security level available for the audio phone number
that is added.
Cisco TelePresence supports the secure add-in of audio-only conference channels to a Cisco
TelePresence session. During a meeting, you can add (conference in) one audio-only call. Each
Cisco TelePresence endpoint that takes part in a meeting can conference in one audio-only call.
Adding (conferencing in) an audio-only phone number is different from placing an audio-only
call.
Prior to Cisco TelePresence Multipoint Switch Release 1.5, calls with an audio add-on were
downgraded to a nonsecure session. When you conferenced an audio phone number into an
ongoing Cisco TelePresence meeting, the security level of the Cisco TelePresence meeting
would change to match the highest security level that was available for the audio phone number
that was being added. Cisco TelePresence Multipoint Switch Release 1.5 added support for the
encryption of remote, audio-only participants.
Follow the steps on the next several pages to initiate an audio add-in conference.

Step 1—Initiate an Audio Conference
 Press the Confrn softkey.
 The request is forwarded to the primary codec.
To start an audio
add-in, press the
Confrn softkey.
Step 1 Press the Confrn softkey to start the audio add-in process.
Step 2—Dial the Phone Number

 The primary codec updates the phone screen and asks for the
conference number to dial.
 Enter the phone number to add and press the Dial softkey.
11615
Step 2 Enter the phone number of the audio add-in conference resource and press the Dial
softkey.
Step 3—New Audio Stream Established
 The primary codec dials the number that you entered.
 The table microphones flash red while the original call is on hold.
Step 3 The codec dials the number that you entered, initiating the audio add-in call
segment.
Step 4—Join the New and Original Calls

 The primary codec mixes in the audio-only segment.
 Press the Confrn softkey to conference the two calls.
Step 4 The original call is placed on hold. When the audio add-in party answers the call,
push the Confrn softkey.

ConfList Softkey
 The primary codec mixes the new audio-only stream into the
same audio channel as Auto Collaborate.
 Press the ConfList softkey to display the individual phone
numbers added to the conference.
The primary codec mixes in the audio-only segment to the existing Cisco TelePresence session.
Press the ConfList softkey to display the individual phone numbers that were added to the
conference.
List of Conference Call Phone Numbers

 The audio add-in stream is locally played out to the virtual
speaker (all local loudspeakers).
 The mixed stream is treated as one regular AUX stream and
played out to all remote loudspeaker(s), if received by another
Cisco TelePresence system.
 Press the Remove softkey to remove a number from the call.
Press the Remove softkey to remove a number from the conference call.
Multiple Audio and Video Call Support
This topic describes the support for multiple video or audio calls.
Multiple Audio and Video Call Support

 Cisco TelePresence Release 1.5 supports multiple video or audio calls.
– You can place one video call on hold and place a second video call.
Note: You cannot bridge video calls.
– The system supports as many as three simultaneous audio calls. You
can conference in only one call with the active video call.
 This feature requires Cisco TelePresence System Release 1.5 with
MIDlets and Cisco Unified Communications Manager Version 7.0(2).
Cisco TelePresence System Release 1.5 supports simultaneous multiple video or audio calls.
You now can have as many as four Cisco TelePresence calls, or three Cisco TelePresence calls
and one audio call. You can switch between Cisco TelePresence meetings by placing the active
call on hold and resuming a different call. The Cisco TelePresence system supports as many as
three audio calls; however, you can conference in only one audio call with the active video call.
You must have Cisco TelePresence System Release 1.5 with MIDlets support and Cisco
Unified Communications Manager Version 7.0(2) to support this feature.
Note You cannot bridge video calls.

Meeting Control Options
This topic describes the meeting control options.
Meeting Control—View Control

During Cisco TelePresence meetings, use the View Control
button to choose the way you see speaking participants.
 Speaker (previously called segment): When a participant is speaking,
that participant is displayed.
 Room (previously called site): When a participant is speaking, all
participants from the site of the active speaker are displayed.
You manage Cisco TelePresence meetings by using the Meeting Control function. The Meeting
Control screen displays two buttons:
 View Control
 Meeting Access
View Control
During Cisco TelePresence meetings, you can select the way that you see speaking participants,
by choosing one of the following View Control options:
 Speaker (previously called segment): When a participant is speaking, that participant is
displayed. Only the screen on which that speaker is displayed changes.
 Room (previously called site): When a participant is speaking, all participants from the
site of the active speaker are displayed.
To change the way that you view participants during a Cisco TelePresence conference, follow
these steps:
Step 1 Press the View Control softkey.
Step 2 Press the Speaker or the Room softkeys to change the view.
Step 3 Press the Exit softkey to exit the Multi-Room View Control screen.
Meeting Control—Meeting Access
 This feature allows users to lock and unlock multipoint meetings without
contacting an administrator.
– Softkey is provided to all rooms in the meeting.
– The meeting can be locked or unlocked from any room in the meeting.
– No configuration is required.
 This feature requires Cisco TelePresence System Release 1.5 and Cisco
TelePresence Multipoint Switch Release 1.5.
Meeting Access
The user interface supports multipoint meeting locking and unlocking, starting with Cisco
TelePresence System Release 1.5 and Cisco TelePresence Multipoint Switch Release 1.5. The
Meeting Access softkey is available to all of the rooms in the meeting, and any room can lock
(Block) or unlock (Allow) the meeting to more rooms joining. No special configuration is
required for this feature.
To change the meeting access during a Cisco TelePresence conference, follow these steps:
Step 1 Press the Meeting Access softkey.
Step 2 Press the Allow or the Block softkeys to change the access.
Step 3 Press the Exit softkey to exit the Meeting Access screen.

Controlling the Document Camera
This topic describes document camera options that are available on the Cisco TelePresence user
interface.
Controlling the Document Camera

Control the document camera from the Cisco TelePresence
phone:
 Power
 Focus
 Light
 Magnification
If you have installed a document camera in the Cisco TelePresence conference room and
configured the camera with Cisco Unified Communications Manager, then you can use the
Cisco TelePresence phone to do the following:
 Touch the Power icon to turn the document camera on or off.
 Touch the Focus icon to reset the camera auto focus.
 Touch the Light bulb icon to turn the camera lamp on or off.
 Touch either of the Magnification icons to zoom the camera lens in or out.
Cisco Auto Collaborate Privacy Alert
This topic describes the Cisco Auto Collaborate Presentation Privacy alert feature.
Cisco Auto Collaborate Privacy Alert

 The Privacy Alert feature disables autocollaboration content
sharing when someone dials into a meeting.
 When this happens, an icon displays on the screen, and a
Dismiss or Share option displays on the phone. Choose one of
the options to continue.
Icon on Cisco TelePresence Screen Buttons on the Phone

Because you can use the Cisco TelePresence Systems 500 and 1000 as data displays when they
are not in use by a Cisco TelePresence call, data that you do not want to share might be
displayed before the start of a call. To prevent the input from your presentation device from
being automatically shared, a Presentation Privacy alert is displayed and you can choose
whether to share or dismiss the presentation.
You can use the Dismiss softkey on the IP Phone 797xG to disable the presentation from a
presenter laptop. To resume the presentation, press the Share softkey. An icon displays on the
remote conferences, indicating that the presentation has been suspended.
Note The presentation device input is automatically shared if you plug a presentation device in
during an active call.

Cisco TelePresence User Interface—In-Call Icons
This topic describes the Cisco TelePresence in-call icons.
Cisco TelePresence User Interface

In-Call Icons
Encrypted Telepresence Call
Telepresence
Authenticated Telepresence Call

(Not encrypted)
Unsecure Telepresence Call
(Not encrypted/authenticated)
Telepresence Call On-Hold
(Initiated locally)
Encrypted Audio Only Call
Authenticated Audio Only Call

Audio Only
(Not encrypted)
Unsecure Audio Only Call

(Not encrypted/authenticated)
Audio Only Call On-Hold
(Initiated locally)
The figure describes the in-call icons that might display on the Cisco TelePresence phone user
interface.
In-Call Security On-Screen Display
Call encrypted
 Media encrypted
 Authenticated with Cisco Unified
Call authenticated
 Authenticated with Cisco Unified
 Media not encrypted
Call unsecure
 Not encrypted
 Not authenticated
The figure describes the in-call security icons that might display on the Cisco TelePresence
user interface.
On-Screen Quality Displays
Indication Quality Metrics

5 bars • The lowest resolution of all received HD streams is 1080p with no loss above the 1%
warning threshold.
and
• The received presentation has no loss above 2%, if active.
4 bars • The lowest resolution of all received HD streams is 720p with no loss abov e the 1%
warning threshold.
and
3 bars • The lowest resolution of all received HD streams is CIF with no loss above the 1%
warning threshold.
and
2 bars • The highest percentage packet loss of all received HD streams is above the 1%
warning threshold and less than the 10% error threshold.
or
• The received presentation has loss between 2% and 10%, if active.
1 bar • The highest percentage packet loss of all received HD streams is above the 10%
error thres hold.
or
• The received presentation has loss above 10%, if active.
The figure shows the in-call icons that might display on the Cisco TelePresence phone user
interface, for call quality. The figure also describes their meanings and possible causes.

On-Screen Hold and Mute Displays
Microphone muted
 Local microphone(s) are muted.
Remote call on-hold/resume in-progress

 Call hold is initiated remotely.
 Call is being resumed.
Local call on-hold

 Call hold is initiated locally.
The figure describes the in-call icons for the hold and mute functions that might display on the
Cisco TelePresence phone user interface.
Miscellaneous On-Screen Displays

Phone handset
 Audio-only call
Projector and bulb

 Projector bulb warming up
The figure describes some miscellaneous in-call icons that might display on the Cisco
On Phone Alerts, Status, and Messages
This topic describes the user interface for Cisco TelePresence phone alerts, status, and
messages.
Alert—Upcoming Meeting
Alert—Upcoming Meeting
The figure shows an example of an upcoming meeting alert that the Cisco TelePresence phone
displays to help participants end their meeting on time. Press the Dismiss softkey to close the
alert screen.

Alert—Meeting Ends in 10 Minutes
Alert—Meeting Is Scheduled to End in 10 Minutes

The figure shows an example of the message that the Cisco TelePresence phone displays when
a meeting is scheduled to end in 10 minutes. Press the Dismiss softkey to close the alert screen.
Error—No Dial Number Provided
Error—No Dial Number Provided

a meeting is scheduled without the phone number of the meeting room. Press the Back softkey
to return to the previous screen. Contact the concierge or system administrator to reschedule the
meeting with the required information.

Error—Meeting Outside Start Window
Error—Meeting Is Outside the Start Window

you try to initiate a meeting outside of the start window. Ask the concierge or Cisco
TelePresence Manager administrator how far in advance of a scheduled meeting you can
initiate a meeting connection.
Network Congestion
Network Congestion
The Cisco TelePresence software monitors the network connection. When Cisco TelePresence
detects network congestion, a message might appear on the Cisco TelePresence phone, warning
that the call cannot proceed. Press the End Call softkey to end the call and try the call again. If
the network congestion message reappears, contact the concierge or system administrator.

System Information
System Information
If you press the Info softkey when the Cisco TelePresence system is idle, the System Info
screen displays. The Maximum Security Setting field displays the highest level of security that
is available from that Cisco TelePresence room.
Error—System Is Not Registered
Error—This System is Not Currently Registered

the Cisco TelePresence system is not registered with Cisco Unified Communications Manager.
If you see this system error screen, press the Update softkey to re-establish a connection with
Cisco Unified Communications Manager, or call the concierge or Cisco TelePresence system
administrator.

Call Status
Call Status
The Status softkey is available while you are in a call. Press this softkey to see a report that
summarizes the quality of the call connection. The Cisco TelePresence software monitors the
connection quality. The Status display shows the following fields:
 Security Level: Secure/Non-Secure
 Latency
 Jitter
 Packet Loss
The following are the possible connection-quality ratings for latency, jitter, and packet loss:
 Good
 Marginal
 Poor
Peripheral Status
Peripheral Status
The Periph softkey is available on the Status screen and the System Info screen. The peripheral
status includes information about cameras, plasma displays, the projector, and the document
camera.
The Peripheral Status display shows the following fields:
 Cameras
 Displays
 Document Camera
 Projector
 Room Phone
 Unified CM
 In a Call
Note The Cisco TelePresence Systems 3000 and 3200 will show the status for left, center, and
right displays.

Alert—Resolution Not Supported
Alert—Resolution Not Supported

Any peripheral, such as a laptop, must be set to display in a resolution of 1024 x 768. The Alert
screen that is shown in the figure appears if you connect a peripheral device to the Video
Graphics Array (VGA) cable with a resolution other than 1024 x 768. Follow these steps if you
see this alert appear on the Cisco TelePresence phone screen:
Step 1 Unplug the peripheral from the VGA cable.
Step 2 Click the Dismiss button.
Step 3 Reset the resolution on the peripheral device.
Step 4 Reconnect the peripheral device.
Alert—Troubleshooting in Progress
Alert—Troubleshooting in Progress
If a Cisco TelePresence administrator is troubleshooting the Cisco TelePresence system, the
screen in the figure appears on the Cisco TelePresence phone screen. You can press the
Override softkey to stop any troubleshooting operation. When you press the Override softkey,
your Cisco TelePresence phone operates in normal mode. You can start a conference call and
remote participants can initiate a call.

Peripheral Upgrade
Peripheral Upgrade
You perform a peripheral upgrade when you apply a new software load to the
Cisco TelePresence system. While the Cisco TelePresence peripherals, such as the camera or
display, are upgrading, you will see a message like the one in the figure on the Cisco
TelePresence phone screen.
Summary
Summary
 The Cisco IP phone user interface provides the input for the Cisco
TelePresence room.
 The user interface has a series of One-Button-to-Push options.
 You can conference in an audio-only call into a Cisco TelePresence
session.
 Cisco TelePresence supports multiple video or audio calls.
 You can control meeting view preferences and restrict meeting access.
 You can use the user interface on the IP phone to control the document
camera.
 You can disable the presentation from a presenter laptop, by using the
Dismiss softkey.
 The Cisco TelePresence user interface displays in-call icons about the
session.
 The Cisco TelePresence user interface also displays phone alerts,
statuses, and messages.

Module Summary
Module Summary
 Cisco TelePresence endpoints have a primary codec and an IP
phone that share the same line characteristics in Cisco Unified
 The Cisco Unified IP Phone 797xG user interface subscribes to
the primary codec, for an XML menu that overwrites the original
phone interface, providing softkey menu buttons that help you
manage Cisco TelePresence sessions.
All Cisco TelePresence endpoints have a primary coder-decoder (codec) device that
communicates as a telephony endpoint. The codec shares line characteristics with a Cisco
Unified IP Phone 797xG, which is on the table and which serves as a convenient user interface.
The endpoints work with Cisco TelePresence Manager software, which provides easy call
scheduling and setup, and with the Cisco TelePresence Multipoint Switch, for multipoint calls.
The menu on the phone is an XML service that the Cisco TelePresence phone subscribes to on
its primary codec. The service-page content overwrites the original phone interface. Softkey
menu buttons on the phone allow the user to place the call on hold or to conference in another
party.

References
 Cisco Systems, Inc. Cisco TelePresence System Release 1.5 Administrator. Guide
http://www.cisco.com/en/US/docs/telepresence/cts_admin/1_5/admin/guide/CTS_Rel_1_5.
html
 Cisco Systems, Inc. Cisco TelePresence System 1.5 Phone User Guide
http://www.cisco.com/en/US/docs/telepresence/cts_admin/1_5/PUG/cts_1_5_PUG.html
 Cisco Systems, Inc. Cisco Unified Communications Manager Administration Guide,
Release 7.1(2)
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/7_1_2/ccmcfg/bccm-712-
cm.html
 Cisco Systems, Inc. Cisco TelePresence Multipoint Switch Release 1.5 Administration
Guide
http://www.cisco.com/en/US/docs/telepresence/multipoint_switch/1_5/admin/CTMS_Rel_
1_5.html
Module Self-Check
Q1) Which one of these statements about Cisco TelePresence endpoints is true? (Source:
Integrating Endpoints with Cisco Unified Communications Manager)
A) From the perspective of the Cisco Unified Communications Manager, Cisco
TelePresence codec devices communicate as SCCP telephony endpoints.
B) The Cisco TelePresence Systems 3000 and 3200 configuration delivers
multiple RTP streams for each audio and video channel to the far end codec, to
complete the Cisco TelePresence call.
C) The Cisco Unified IP Phone 797xG connects to the primary codec, which
supplies 802.3af PoE to the IP phone.
D) The primary codec on Cisco TelePresence Systems 3000 and 3200 is
responsible for multiplexing audio and video inputs from its secondary codecs
into one RTP stream.
Q2) Which one of these statements about the Cisco TelePresence codec is false? (Source:
A) A private network is used for internal communications between the primary
and secondary codecs, as well as between codecs and cameras.
B) By default, the internal address range is 192.168.0.0/24 through
192.168.4.0/24.
C) If the primary codec receives a 192.168.x.x address from the network, then the
internal private network will switch to 172.16.1.0/24 through 172.16.4.0/24.
D) The private IP address block that the codec uses will cause routing issues if
these addresses are used by other devices that communicate with Cisco
TelePresence.
Q3) The Cisco TelePresence System Administration tool, which you access via a web-
based interface, allows you to configure, troubleshoot, and monitor the codec. (Source:
A) true
B) false
Q4) Which one of these statements about the Cisco TelePresence System Administration
tool is true? (Source: Integrating Endpoints with Cisco Unified Communications
Manager)
A) The IP Settings pane allows you to configure a static IP assigned address for
the primary codec; dynamic IP addresses are not allowed.
B) The IP Settings pane allows you to configure a static IP address for the
secondary codecs.
C) You must configure private IP addresses for the secondary codecs in the IP
Settings pane.
D) The IP Settings pane displays the MAC address that you will need to register
the device in Cisco Unified Communications Manager.

Q5) The CallManager Settings pane in the Cisco TelePresence System Administration tool
allows you to configure the FTP server settings. (Source: Integrating Endpoints with
Cisco Unified Communications Manager)
A) true
B) false
Q6) The CallManager Settings pane in the Cisco TelePresence System Administration tool
allows you to configure the settings of the TFTP servers. (Source: Integrating
Endpoints with Cisco Unified Communications Manager)
A) true
B) false
Q7) You can use the Telephony Settings pane to modify the default settings that are
recommended for telepresence communication. However, you should not change the
default settings without specific reason, because modifications can impair system
performance. (Source: Integrating Endpoints with Cisco Unified Communications
Manager)
A) true
B) false
Q8) You can use the System Settings pane in the Cisco TelePresence System
Administration tool to verify and modify values such as administrative username,
administrative password, email, and phone number. (Source: Integrating Endpoints
with Cisco Unified Communications Manager)
A) true
B) false
Q9) Which one of these statements about the Cisco TelePresence System Administration
tool is true? (Source: Integrating Endpoints with Cisco Unified Communications
Manager)
A) You use the Hardware Setup pane—from which you can adjust settings for
displays, cameras, speakers, and microphones—only when you perform the
initial setup.
B) You use the Hardware Setup pane any time that there is a significant change,
such as a change in lighting or acoustics, in the Cisco TelePresence
environment.
C) When using the Hardware Setup pane, you must test the microphones before
testing the speakers because the speaker test depends on the correct functioning
of the microphones.
D) If the displays are not working, you can still use the Hardware Setup pane to
test the cameras and speakers.
Q10) Which release of Cisco Unified Communications Manager must you use with Cisco
TelePresence Manager Release 1.5(x)? (Source: Integrating Endpoints with Cisco
Unified Communications Manager)
A) Cisco Unified Communications Manager Version 6.0(1)
B) Cisco Unified Communications Manager Version 6.1(2)
C) Cisco Unified Communications Manager Version 6.1(3)
D) Cisco Unified Communications Manager Version 7.1(4)
Q11) Which one of these recommendations is true when using video telephony endpoints on
the same cluster? (Source: Integrating Endpoints with Cisco Unified Communications
Manager)
A) You must deploy a separate Cisco Unified Communications Manager cluster
for Cisco TelePresence.
B) You can choose to deploy a separate Cisco Unified Communications Manager
cluster for Cisco TelePresence.
C) You can pick one of your Cisco Unified Communications Manager clusters
and use it globally for all Cisco TelePresence systems.
D) You can pick two of your Cisco Unified Communications Manager clusters
and use them separately for all Cisco TelePresence systems.
Q12) Place these Cisco TelePresence system media path steps in the correct order. (Source:
A) RTP media streams for both audio and video begin between the Cisco
TelePresence endpoints.
B) A SIP INVITE from the local primary codec is sent to the Cisco Unified
C) An XML ANSWER is sent from the remote IP phone back to the remote
primary codec.
D) A SIP INVITE is sent from Cisco Unified Communications Manager to the
remote primary codec.
E) An XML RING is sent from the remote primary codec to the remote IP phone.
F) A SIP 200 OK is sent from the remote primary codec to the Cisco Unified
G) An XML DIAL is sent from the local IP phone to the local primary codec.
H) A SIP 200 OK is sent from the Cisco Unified Communications Manager to the
local primary codec.
_____ 1. first
_____ 2. second
_____ 3. third
_____ 4. fourth
_____ 5. fifth
_____ 6. sixth
_____ 7. seventh
_____ 8. eighth
Q13) Cisco TelePresence systems are configured in Cisco Unified Communications

Manager, just as IP phones are. You can manually add Cisco TelePresence endpoints in
Cisco Unified Communications Manager Administration by using the Phone
Configuration windows. (Source: Integrating Endpoints with Cisco Unified
Communications Manager)
A) true
B) false

Q14) Which one of these steps is invalid when deploying the enhanced phone user interface
(MIDlets)? (Source: Integrating Endpoints with Cisco Unified Communications
Manager)
A) Obtain the appropriate .jad and .jar files from the Cisco TelePresence
download area in Cisco.com.
B) Upload the desired .jad and .jar files from the Cisco Unified Communications
Manager Operating System Administration page to the Cisco Unified FTP
directory.
C) Create a new service named “IP Phone Service” in Cisco Unified
Communication Manager.
D) Configure each Cisco Unified IP Phone 797xG to run the new IP Phone
Service.
Q15) Which one of these is not a valid IP Phone 797xG feature? (Source: Examining the
Cisco TelePresence User Interface)
A) ad hoc (manual) calls
B) system speed dials
C) past scheduled meetings archive
D) One-Button-to-Push dialing for schedule meetings
E) Conference/Join used to add audio participants to a Cisco TelePresence
meeting
Q16) Which one of the following features is a an improvement that Java MIDlets provide to
the Cisco TelePresence phone? (Source: Examining the Cisco TelePresence User
Interface)
A) the Tones softkey to enter DTMF digits
B) the Manual softkey for instant telepresence dialing
C) easier conference controls with support for one active call
D) volume rocker button that works for telepresence
Q17) Which one of these is not an option on the Manual screen of the Cisco TelePresence
phone? (Source: Examining the Cisco TelePresence User Interface)
A) New Call
B) Directory
C) Favorites
D) Meetings
E) Conference
Q18) Which one of these is not an option for configuring the IP phone Idle Display in Cisco
Unified Communications Manager? (Source: Examining the Cisco TelePresence User
Interface)
A) Default (Scheduled Meetings)
B) Speed Dial
C) Manual
D) Directory
Q19) Which one of these is false when conferencing an audio call? (Source: Examining the
A) Cisco TelePresence has the ability to participate in an audio-only session.
B) During a meeting, you can add (conference in) one audio-only call.
C) Each endpoint that takes part in a meeting can conference in one audio-only
call.
D) The security level of the Cisco TelePresence meeting may change to match the
lowest security level that is available for the audio phone number that is being
added.
Q20) Cisco TelePresence System Release 1.5 supports simultaneous multiple video or audio
calls. This system allows you to have as many as four Cisco TelePresence calls or three
Cisco TelePresence calls and one audio call. (Source: Examining the Cisco
TelePresence User Interface)
A) true
B) false
Q21) Which two options are valid Meeting Control options? (Choose two.) (Source:
Examining the Cisco TelePresence User Interface)
A) View Control: Choose the way that you see speaking participants.
B) Number of Rooms: Choose the number of rooms participating.
C) Speaker Control: Choose which speaker is displayed.
D) Segment Control: Choose which table segment is displayed.
E) Meeting Access: Lock and unlock access to a meeting.
F) Time Control: Choose to extend an existing meeting.
Q22) Which one of these is not an option when controlling the document camera on the
Cisco TelePresence phone user interface? (Source: Examining the Cisco TelePresence
User Interface)
A) power
B) exposure
C) focus
D) light bulb
E) magnification icons
Q23) Which one of these is not a valid description of an in-call icon? (Source: Examining the
A) encrypted Cisco TelePresence call
B) authenticated Cisco TelePresence call
C) unsecured Cisco TelePresence call
D) authorized Cisco TelePresence call

Q1) C
Q2) C
Q3) A
Q4) D
Q5) B
Q6) A
Q7) A
Q8) B
Q9) B
Q10) C
Q11) A
Q12) 1-G
2-B
3-D
4-E
5-C
6-F
7-H
8-A
Q13) A
Q14) B
Q15) C
Q16) D
Q17) E
Q18) B
Q19) D
Q20) A
Q21) A, E
Q22) B
Q23) D
Module 3
Cisco TelePresence Network

Architecture
Overview
The various Cisco TelePresence meeting solutions can run on the existing converged network
of a company enterprise and does not require a dedicated and separately managed
infrastructure. It uses an intelligent network, allowing it to coexist with other applications,
which means real savings of capital and operating expenses to a business. To take advantage of
this architecture, a company needs to make sure that its infrastructures are capable of
processing the demands of Cisco TelePresence and the demands of other next-generation
applications.
Module Objectives
Upon completing this module, you will be able to describe the Cisco TelePresence network
architecture. This ability includes being able to meet these objectives:
 Deploy Cisco TelePresence in a business
 Describe traffic-policing and traffic-shaping QoS mechanisms
 Establish a QoS policy
 Design a WAN and branch QoS policy
 Perform an NPA
 Configure VSAA and collect network statistics
Lesson 1
Deploying a Cisco
TelePresence Network
Overview
The Cisco TelePresence meeting solution comprises several endpoint models that can meet
many types of meeting needs. Each of these endpoints has a primary coder-decoder (codec)
device that communicates as a telephony endpoint from the perspective of Cisco Unified
Communications Manager. Cisco TelePresence is an end-to-end solution that was developed by
Cisco and uses the existing network and service provider connection of a customer to extend
Cisco TelePresence meetings beyond their enterprise boundary. This structure enables the
company to meet “in person” with customers, suppliers, and partners as easily as they can
internally. Organizations that regularly need to meet with third parties can benefit from this
solution.
Because Cisco TelePresence can reside on a converged network, it must coexist with other
applications on your network. The growing rise of recreational applications and peer-to-peer
traffic can affect the delivery of critical applications. To address this issue, you can equip
switches and routers to inspect and prioritize traffic at the packet level.
Objectives
Upon completing this lesson, you will be able to deploy Cisco TelePresence in a business
environment. This ability includes being able to meet these objectives:
 Describe the functionality of multiplexing RTP video and audio streams with the Cisco
TelePresence codec
 Describe the various Cisco TelePresence deployment models
 Configure Cisco devices for use with Cisco TelePresence
Codec Communication
This topic describes the point-to-point communication between two primary codecs.
Codec Communication
LAN/WAN
Audio Streams
Video Streams
Primary Codec
The Cisco Unified IP Phone 797xG connects to the primary codec. The primary codec supplies
802.3af Power over Ethernet (PoE) to the phone. In Cisco TelePresence Systems 3000 and
3200 configurations, the primary codec is responsible for multiplexing audio and video inputs
from the secondary codecs and then delivering a single Real-Time Transport Protocol (RTP)
stream for audio and video to the “far end” codec to complete the Cisco TelePresence call. On
the receiving side, the primary codec is responsible for demultiplexing the respective streams
and delivering them to the appropriate video display or audio speaker channel.
From the perspective of the Cisco Unified Communications Manager, codec devices
communicate, and are controlled, as telephony endpoints in much the same way that any IP
phone communicates to another IP phone using Session Initiation Protocol (SIP). In other
words, calls are point-to-point, or IP address-to-IP address. Cisco Unified Communications
Manager generates the SIP commands that are necessary to manage the devices for events such
as call setup and teardown. Audio and video streams also communicate in much the same way
as IP phones or Cisco Unified Video devices, namely using RTP over User Datagram Protocol
(UDP). Therefore, you must properly configure the underlying IP network for the end-to-end
service and dependability of Cisco TelePresence endpoints.
Deployment Models
This topic describes the different Cisco TelePresence deployment models.
Intracampus Deployment Model
Campus Building A Campus Building B
Campus
Core
Cisco TelePresence
Cisco TelePresence
System 3000 System 3000
Campus Campus Campus
Access Distribution Access
The intracampus network deployment model has Cisco TelePresence

systems limited to a single enterprise campus.
Intracampus Deployment Model

The intracampus network deployment model limits Cisco TelePresence systems to a single
enterprise campus. This deployment model is applicable for enterprises that have many
buildings within a given campus and employees who frequently drive to different buildings to
attend meetings during the course of the day. Deploying multiple intracampus Cisco
TelePresence systems can reduce time that is lost by employees driving between buildings to
attend meetings, without sacrificing meeting effectiveness and thus improving overall
productivity.
The network infrastructure of an intracampus deployment model consists of predominantly

Cisco Catalyst switches connecting Gigabit Ethernet or 10-Gb Ethernet links.
© 2011 Cisco Systems, Inc. Cisco TelePresence Network Architecture 3-5

Intra-Enterprise Deployment Model
Campus B
Campus A
Private WAN
MPLS VPN Cisco TelePresenc e

System 3000
Cisco
Metro
TelePresence Ethernet
System 3000 Campus WAN/MAN
Block
Branch C
The intra-enterprise model Cisco TelePresence
expands on the intracampus model System 1000
to span the WAN and MAN.
Intra-Enterprise Deployment Model

The intra-enterprise network deployment model for Cisco TelePresence systems connects
buildings within a campus and geographically separated campus sites and branch offices. The
intra-enterprise model expands on the intracampus model to span the WAN and metropolitan-
area network (MAN).
The intra-enterprise deployment model is suitable for businesses that often require employees
to travel extensively for internal meetings. Deploying Cisco TelePresence systems within the
enterprise improves productivity by saving travel time, and it reduces travel expenses. Also, the
overall quality of work and life often improves when employees travel less.
The network infrastructure of an intra-enterprise deployment model is a combination of Cisco

Catalyst switches within the campus and Cisco routers over the WAN or MAN. The WAN or
MAN can include private WANs, Multiprotocol Label Switching Virtual Private Networks
(MPLS VPNs), or Metro Ethernet networks. WAN speeds can range from 45-Mb/s digital
signal level 3 (DS-3) circuits to 155-Mb/s optical carrier 3 (OC-3) circuits or higher.
Intercompany Deployment Model
Enterprise A Enterprise B
Shared Servic es
VRF
Sess ion
Border Controller
MPLS VPN
Cisco Cisco
TelePresence System TelePresence Sys tem
3000 PE Routers PE Routers 3000
The intercompany network deployment model enables Cisco TelePresence

systems within one enterprise to call systems within another enterprise.
Intercompany Network Deployment Model

The intercompany network deployment model connects Cisco TelePresence systems within an
enterprise and enables Cisco TelePresence systems within one enterprise to call systems within
another enterprise. This model is sometimes referred to as the inter-enterprise or business-to-
business (B2B) deployment model.
The intercompany model offers the most flexibility and is suitable for businesses that often
require employees to travel extensively for both internal and external meetings. In addition to
the business advantages of the intra-enterprise model, the B2B deployment model lets
employees maintain high-quality customer relations without the associated travel costs.
The network infrastructure of the intercompany deployment model builds on the intra-
enterprise model and requires the enterprises to share a common MPLS VPN service provider.
Additionally, the MPLS VPN service provider must have a “shared services” virtual routing
and forwarding (VRF) instance that is provisioned with a Cisco IOS XR Session Border
Controller.
The Cisco Session Border Controller bridges a connection between two separate MPLS VPNs
to perform secure inter-VPN communication, which the intercompany deployment model
requires. Additionally, the Session Border Controller provides services:
 Topology and address-hiding services
 Network Address Translation (NAT) and firewall traversal
 Fraud and theft-of-service prevention
 Distributed denial-of-service (DDoS) detection and prevention
 Call Admission Control (CAC) policy enforcement
 Guaranteed quality of service (QoS)

Multipoint Network Deployment Model
Cisco TelePresence
Multipoint Solution
Cisco TelePresence
System 3000
Each endpoint has to mix the audio and video from every other endpoint in
order to determine which video stream to display at any given time.
Multipoint
This form of multipoint video conferencing has limited scalability. Each endpoint has to mix
the audio and video from every other endpoint in order to determine which video stream to
display at any given time. Alternatively, the endpoints may display video from each of the other
endpoints in a small section of the display, for example, four or eight boxes of video. Audio
must still be mixed at the video endpoint and played on the speakers. The addition of each new
video endpoint results in every other endpoint having to both send and receive a new video and
audio stream. For a conference with N video endpoints, each endpoint has to both send and
receive N – 1 unicast video and audio streams. For this reason, you must be careful with
bandwidth utilization for multipoint configurations.
Cisco Device Configuration
This topic describes the configuration of Cisco switches, firewalls, and access control lists for
use with Cisco TelePresence.
Switch Configuration
 The phone and primary codec reside on the voice VLAN. The voice
VLAN should be different from the data VLAN.
 The primary codec passes Cisco Discovery Protocol and 802.1Q/p
between the phone and network.
 The switch sees two Cisco Discovery Protocol neighbors. The QoS trust
is extended through the codec to the phone.
 The phone and cameras receive PoE (802.3af) from the codec.
IP Phone 797xG Codec Switch
Cisco Discovery Cisco Discovery
Protocol Protocol
802.1Q/p 802.1Q/p
POE
A/C
Example:
Console(config)#interface Gigabit 0/16
Console(config-if)#switchport mode access
Console(config-if)#switchport access vlan 261
Console(config-if)#switchport voice vlan 262
Console(config-if)#spanning-tree portfast
Console(config-if)#mls qos trust {dscp | . }
The Cisco TelePresence phone and cameras receive PoE (802.3af) from the primary codec. The
phone and primary codec both reside on the voice VLAN. The voice VLAN should be different
from the data VLAN. The primary codec passes the Cisco Discovery Protocol and 802.1Q/p
information between the phone and network. The switch then sees two Cisco Discovery
Protocol neighbors.
The following is an example of the configuration on the switch:

Console(config)#interface Gigabit 0/16
Console(config-if)#switchport mode access
Console(config-if)#switchport access vlan 261
Console(config-if)#switchport voice vlan 262
Console(config-if)#spanning-tree portfast
Console(config-if)#mls qos trust {dscp | cos}

Firewalls and ACLs
 Customers rely on firewalls, ACLs, or both to protect their
Cisco Unified Communications network.
 ACLs also help enforce QoS settings.
 The Cisco Unified Communications suite already fully
supports a proven security framework that applies directly to
Cisco TelePresence as well.
 There are three key considerations for Cisco TelePresence:
– The TCP and UDP ports used by Cisco TelePresence
must be allowed through the firewall.
– The bandwidth required is significantly higher and far
less tolerant than a typical voice call.
– Firewalls that use application layer inspection to
dynamically open and close UDP ports may not support
the SIP implementation of Cisco TelePresence.
 Testing is still pending. Proceed with caution when deploying
firewalls or access control lists with Cisco TelePresence.
Many enterprise customers rely on firewalls and access control lists to protect their Cisco
Unified Communications network from various sorts of malicious threats. Companies also
frequently use access control lists to enforce QoS settings, including marking, shaping, and
policing traffic at various places in the network.
The Cisco Unified Communications suite already supports a proven security framework, which
is one component of the Cisco SAFE Blueprint for Cisco Unified Communications. As a SIP-
based end-user device of Cisco Unified Communications Manager, Cisco TelePresence fits into
this framework. Therefore, all of the existing concepts, methodologies, and best practices for
deploying firewalls and access control lists with Cisco Unified Communications apply to Cisco
TelePresence.
There are three key considerations for Cisco TelePresence:

 You must allow the specific TCP and UDP ports that the Cisco TelePresence systems and
the Cisco TelePresence Manager use, through the firewall and access control lists.
 The bandwidth required for the audio and video media streams of a Cisco TelePresence
meeting is significantly higher and far less tolerant of latency, jitter, and loss than a typical
voice call. You must consider this requirement when choosing specific router and firewall
platforms and their performance characteristics.
 Firewalls that rely on application layer inspection to dynamically open and close certain
UDP ports may not support the SIP protocol implementation of Cisco TelePresence. Also,
the firewalls may not be able to inspect the contents of the application layer protocol
because it is encrypted.
Note Testing firewalls and access control lists with Cisco TelePresence is still pending. Until test
results and best-practice deployment guidance are available, it is recommended that
customers proceed with caution when deploying firewalls or access control lists with Cisco
TelePresence.
Cisco TelePresence TCP and UDP Port
Usage
 The tables on the following slides provide a list of TCP and UDP
ports used by the:
– Cisco TelePresence System
– Cisco Unified IP Phone 797xG
– Cisco TelePresence Manager
– Cisco TelePresence Multipoint Switch
 The term “ephemeral” refers to a random range of ports that are
dynamically assigned. Many protocols use ephemeral source
ports.
Audio Video
Codecs Codecs
SIP SIP CAPF
RT P/RTCP
UDP TCP
IP
The following sections provide the list of TCP and UDP ports that are used by the Cisco
TelePresence system, the Cisco IP Phone 797xG, the Cisco TelePresence Manager, and the
Cisco TelePresence Multipoint Switch. In the following tables, these abbreviations are used:
 CTS: Refers to the Cisco TelePresence system primary codec
 CTSMGR: Refers to Cisco TelePresence Manager
 CTMS: Refers to the Cisco TelePresence Multipoint Switch
 CUCM: Refers to Cisco Unified Communications Manager
The term “ephemeral” refers to a random range of ports that is dynamically assigned. Many
protocols use ephemeral source ports.
Note The tables include only the ports relevant to a firewall or access control lists administrator.
Ports that are used for internal communications, such as the communication between the
Cisco TelePresence primary and secondary codecs, are intentionally omitted. Furthermore,
the tables include only ports that are used by Cisco TelePresence.

Cisco TelePresence Primary Codec
TCP and UDP Port Usage
 Cisco Discovery Protocol
 Dynamic Host Configuration Protocol (DHCP)
 Internet Control Message Protocol (ICMP)
 Network Time Protocol (NTP)
 Domain Name System (DNS)
 HTTP
 Secure Shell (SSH)
 Simple Network Management Protocol (SNMP)
 Certificate Authority Proxy Function (CAPF)
 Certificate Trust List (CTL)
 Session Initiation Protocol (SIP)
 Real Time Transport Protocol (RTP)
 XML- remote procedure call (RPC)
Cisco TelePresence Primary Codec Release 1.5(X) TCP and UDP Port Usage
TCP Source Destination
Protocol or Device: Device: Description
UDP Port Port
Advertises the existence of the primary codec to
the attached upstream Cisco Catalyst Ethernet
Cisco Discovery switch and learns with which VLAN it should tag its
N/A CTS: N/A Switch: N/A
Protocol packets. Cisco Discovery Protocol is a Layer 2
protocol, so it does not use TCP or UDP for
transport.
Requests an IP address from the DHCP server. It
0.0.0.0: 68 Broadcast:
UDP is recommended to use static IP addressing
CTS: 68 67
DHCP instead of DHCP.
0.0.0.0: 67 Broadcast: The DHCP server sends this port in response to a
UDP
DHCP: 67 68 request for an IP address.
ICMP can determine whether a device is reachable
(for example, ICMP echo request/response). ICMP
Internet Control
unreachables can indicate that a device or port is
Message Protocol N/A Any: N/A Any: N/A
no longer reachable. ICMP time-exceeded may be
(ICMP)
sent by a device to indicate that the Time to Live
(TTL) of a packet was exceeded.
Network Time NTP synchronizes the hardware clock on the Cisco
UDP CTS: 123 NTP: 123
Protocol (NTP) TelePresence primary codec with an NTP Server.
Domain Name CTS:
UDP DNS: 53 DNS resolves hostnames to IP addresses.
System (DNS) Ephemeral
TCP Source Destination
Protocol or Device: Device: Description
UDP Port Port
HTTP downloads configuration and firmware files
from the Cisco Unified Communications Manager
CTS: CUCM: TFTP service.
TCP
Ephemeral 6970
Note: The Cisco TelePresence system uses HTTP
instead of TFTP for accessing these files.
The Directories feature uses HTTP on the Cisco
CTS: TelePresence phone user interface to search the
CUCM:
TCP Ephemeral Lightweight Directory Access Protocol (LDAP)
8080
directory of the Cisco Unified Communications
Manager.
XML/Simple Object Access Protocol (XML/SOAP)
is used to coordinate the meeting schedule and
system operational status with Cisco TelePresence
Manager. When security is enabled, the Cisco
HTTP TelePresence system uses port 8443 on Cisco
CTS: CTS-MAN:
TelePresence Manager, and Cisco TelePresence
Ephemeral 8080, 8443
TCP Manager uses port 9501 on the Cisco
CTS-MAN: CTS: 8081,
TelePresence system. When security is not
Ephemeral 9501
enabled, Cisco TelePresence system uses port
8080 on Cisco TelePresence Manager, and Cisco
TelePresence Manager uses port 8081 on the
Cisco TelePresence system. Secure mode is
recommended.
HTTP provides access to the administrative web
Any: CTS: 80,
TCP interface of the primary Cisco TelePresence codec;
Ephemeral 443
port 80 is automatically redirected to port 443.
XML is used between each Cisco TelePresence
CTS: CTMS: system and the Cisco TelePresence Multipoint
TCP
Ephemeral 9501 Switch for in-meeting controls, such as site and
segment switching and meeting Lock/Unlock.
SSH provides secure access to the administrative
Secure Shell Any:
TCP CTS: 22 command-line interface (CLI) of the Cisco
(SSH) Ephemeral
TelePresence codec.
Any: The Cisco TelePresence primary codec receives
Simple Network UDP CTS: 161
Ephemeral SNMP queries from a management station.
Management
Protocol (SNMP) CTS: The Cisco TelePresence primary codec sends
UDP SNMP: 162
Ephemeral SNMP traps to a management station.
The Cisco TelePresence primary codec registers
Certificate Authority its manufacturing installed certificate (MIC), or
CTS: CUCM:
Proxy Function TCP obtains a locally significant certificate (LSC) from
Ephemeral 3804
(CAPF) the Cisco Unified Communications Manager CAPF
service.
The Cisco TelePresence primary codec downloads
Certificate Trust List CTS: CUCM:
TCP the CTL from the Cisco Unified Communications
(CTL) Ephemeral 2444
Manager CTLProvider service.
CUCM: SIP provides registration and call signaling with
UDP
5060 Cisco Unified Communications Manager. It can be
CTS:
SIP UDP port 5060, TCP port 5060, or TCP port 5061 if
Ephemeral CUCM:
TCP SIP over Transparent LAN Services (TLS) is
5060, 5061 enabled. SIP over TLS is recommended.
CTS:
RTP UDP 16384 – Any: Any
RTP sends and receives audio and video media.
32768
CTS: Phone: The Cisco TelePresence primary codec auto starts
TCP
Ephemeral 61456 the MIDlet phone user interface.
XML-remote Phone: The Cisco TelePresence primary codec sends
TCP CTS: 61457
procedure call (RPC) Ephemeral notifications to the MIDlet phone user interface.
Phone: The Cisco TelePresence primary codec receives
TCP CTS: 61458
Ephemeral notifications from the MIDlet phone user interface.

 DHCP
 ICMP
 NTP
 DNS
 TFTP
 HTTP
 SSH
 CAPF
 CTL
 SIP
 RTP
 XML-RPC
Cisco Unified IP Phone 797xG Release 8.4(3) TCP and UDP Port Usage
TCP Destination
Source
Protocol or Device: Description
Device: Port
UDP Port
Cisco Discovery Protocol advertises the existence
of the IP Phone 797xG to the Cisco TelePresence
system and the attached upstream Cisco Catalyst
Cisco
Ethernet switch. Cisco Discovery Protocol is used
Discovery N/A Phone: N/A Switch: N/A
to learn what VLAN it should tag its packets with
Protocol
and to negotiate PoE. Cisco Discovery Protocol is
a Layer 2 protocol, so it does not use TCP or
UDP.
0.0.0.0: 68 Broadcast: The IP Phone 797xG requests an IP address from
UDP
Phone: 68 67 the DHCP server.
DHCP
UDP
ICMP can determine whether a device is
reachable (for example, ICMP echo
request/response). ICMP unreachables can
ICMP N/A Any: N/A Any: N/A indicate that a device or port is no longer
reachable. ICMP time-exceeded may be sent by a
device to indicate that the TTL of a packet was
exceeded.
NTP synchronizes the hardware clock on the IP
NTP UDP Phone: 123 NTP: 123
Phone 797xG with an NTP server.
Phone:
DNS UDP DNS: 53 DNS resolves hostnames to IP addresses.
Ephemeral
The IP Phone 797xG initiates the request to
Phone: download configuration and firmware files from
UDP TFTP: 69
Ephemeral the Cisco Unified Communications Manager
TFTP service.
TFTP
The initial TFTP request spawns unique sessions
TFTP: Phone: for each configuration and firmware file
UDP
Ephemeral Ephemeral downloaded; these sessions are established
using ephemeral source and destination ports.
TCP Destination
Source
Protocol or Device: Description
Device: Port
UDP Port
Any:
HTTP TCP Phone: 80 interface of the IP Phone 797xG (for
Ephemeral
troubleshooting purposes only).
SSH provides secure access to the administrative
Any:
SSH TCP Phone: 22 CLI of the IP Phone 797xG (for troubleshooting
Ephemeral
purposes only).
The IP Phone 797xG registers its MIC or obtains
Phone: CUCM:
CAPF TCP an LSC from the Cisco Unified Communications
Ephemeral 3804
Manager CAPF service.
The IP Phone 797xG downloads the CTL from the
Phone: CUCM:
CTL TCP Cisco Unified Communications Manager CTL
Ephemeral 2444
Provider service.
CUCM: SIP provides registration and call signaling with
UDP
5060 Cisco Unified Communications Manager. Can be
Phone:
SIP UDP port 5060, TCP port 5060, or TCP port 5061
Ephemeral CUCM:
TCP if SIP over TLS is enabled. SIP over TLS is
5060, 5061 recommended.
Phone:
RTP UDP 16384 – Any: Any RTP sends and receives audio media.
32768
The Cisco TelePresence primary codec
CTS: Phone:
TCP automatically starts the MIDlet phone user
Ephemeral 61456
interface.
XML-
Phone: The Cisco TelePresence primary codec sends
RPC TCP CTS: 61457
Ephemeral notifications to the MIDlet phone user interface.
Phone: The Cisco TelePresence primary codec receives
TCP CTS: 61458
Ephemeral notifications from the MIDlet phone user interface.

Cisco TelePresence Manager TCP and
UDP Port Usage—Microsoft Exchange
 DHCP
 ICMP
 NTP
 DNS
 HTTP
 SSH
 SNMP
 CAPF
 CTL
 Java Telephony Application Programming Interface (JTAPI)
 Lightweight Directory Access Protocol (LDAP)
 Web-based Distributed Authoring and Versioning (WebDAV)
– The WebDAV protocol is used to subscribe to the Microsoft
Exchange mailboxes.
Note Cisco TelePresence Manager uses the Web-based Distributed Authoring and Versioning
(WebDAV) protocol to subscribe to the Microsoft Exchange mailbox of each Cisco
TelePresence endpoint.
Cisco TelePresence Manager Release 1.5(X) for Microsoft Exchange

TCP
Source Destination
Protocol or Description
Device:Port Device:Port
UDP
Cisco Discovery Protocol advertises the
existence of the Cisco TelePresence Manager
Cisco
to the upstream Cisco Catalyst Ethernet switch
Discovery N/A N/A N/A
to which it is attached. Cisco Discovery
Protocol
Protocol is a Layer 2 management protocol, so
it does not use TCP or UDP.
The Cisco TelePresence manager requests an
0.0.0.0: 68
Broadcast: IP address from the DHCP server. It is
UDP CTSMGR:
67 recommended that you use static IP addressing
DHCP 68
instead of DHCP.
0.0.0.0: 67 Broadcast: DHCP servers send this port in response to a
UDP
reachable. ICMP time-exceeded may be sent
by a device to indicate that the TTL of a packet
was exceeded.
NTP synchronizes the hardware clock on the
CTSMGR:
NTP UDP NTP: 123 Cisco TelePresence Manager with an NTP
123
server.
CTSMGR:
Ephemeral
TCP
Source Destination
UDP
XML/SOAP is used to coordinate the meeting
schedule and system operational status with
Cisco TelePresence Manager. When security is
enabled, the Cisco TelePresence system uses
CTS: CTS-MAN: port 8443 on Cisco TelePresence Manager,
Ephemeral 8080, 8443 and Cisco TelePresence Manager uses port
TCP
CTSMGR: CTS: 8081, 9501 on the Cisco TelePresence system. When
Ephemeral 9501 security is not enabled, Cisco TelePresence
system uses port 8080 on Cisco TelePresence
Manager, and Cisco TelePresence Manager
uses port 8081 on the Cisco TelePresence
system. Secure mode is recommended.
XML/SOAP is used over HTTP or HTTPS to
HTTP CTMS: CTS-MAN:
coordinate the meeting schedule and system
TCP operational status between the Cisco
CTS-MAN: CTMS: 8080,
TelePresence Manager and the Cisco
Ephemeral 8443
TelePresence Multipoint Switch.
XML/SOAP is used over HTTPS to the
Administrative XML Layer (AXL) Web Services
CTSMGR:
TCP CUCM: 8443 and Cisco Unified Communications Manager to
Ephemeral
interrogate the database and discover the
existence of Cisco TelePresence systems.
HTTP provides access to the administrative
Any: CTSMGR: web interface of the Cisco TelePresence
TCP
Ephemeral 80,443 Manager; port 80 is automatically redirected to
port 443.
SSH provides secure access to the
Any:
SSH TCP CTSMGR: 22 administrative CLI of the Cisco TelePresence
Ephemeral
Manager.
Any: CTSMGR: Cisco TelePresence Manager receives SNMP
UDP
Ephemeral 161 queries from a management station.
SNMP
CTSMGR: Cisco TelePresence Manager sends SNMP
UDP SNMP: 162
Ephemeral traps to a management station.
Cisco TelePresence Manager obtains an LSC
CTS-MAN: from the Cisco Unified Communications
CAPF TCP CUCM: 3804
Ephemeral Manager Certificate Authority Proxy Function
(CAPF) service.
Cisco TelePresence Manager downloads the
CTS-MAN:
CTL TCP CUCM: 2444 CTL from the Cisco Unified Communications
Ephemeral
Manager CTL Provider service.
Cisco TelePresence Manager uses JTAPI to
register with the Cisco Unified Communications
Java
Manager CTI Manager service to receive
Telephony
device event status of Cisco TelePresence
Application CTSMGR: CUCM: 2748,
TCP System endpoints. When security is enabled,
Programming Ephemeral 2749
Cisco TelePresence Manager uses port 2749
Interface
on Cisco Unified Communications Manager.
(JTAPI)
Otherwise, port 2748 is used. Secure mode is
recommended.
Cisco TelePresence Manager searches the
Microsoft Active Directory to discover the
Microsoft Exchange mailbox name of Cisco
TelePresence rooms; port 389 is used for
Active
CTSMGR: single Active Directory server deployments. If
LDAP TCP Directory:
Ephemeral Active Directory deployment uses a Global
389,3268,636
Catalogue Server, then port 3268 is used. If
Active Directory uses LDAP over Secure
Sockets Layer (LDAP/SSL), then port 636 is
used (LDAP/SSL is recommended).

TCP
Source Destination
UDP
Cisco TelePresence Manager uses WebDAV to
subscribe to the Microsoft Exchange mailbox of
CTSMGR: Exchange: each Cisco TelePresence room to process
TCP
Ephemeral 80,443 meeting requests. If Exchange is set up to
support SSL, then port 443 is used. Otherwise,
WebDAV port 80 is used. SSL is recommended.
Exchange uses WebDAV to notify the Cisco
Exchange: CTSMGR: TelePresence Manager of any events in the
UDP
Ephemeral 3621 mailboxes to which it is subscribed. These
notify messages are sent on UDP port 3621.
Cisco TelePresence Manager TCP and
UDP Port Usage—IBM Domino
 DHCP
 ICMP
 NTP
 DNS
 HTTP
 SSH
 SNMP
 CAPF
 CTL
 JTAPI
 LDAP
 Internet Inter-Orb Protocol (IIOP)
– The IIOP protocol is used to subscribe to the IBM Domino
mailboxes.
Note Cisco TelePresence Manager uses the Domino Internet Inter-Orb Protocol (IIOP) to
negotiate sessions with the IBM Domino mailbox of each Cisco TelePresence endpoint.
Cisco TelePresence Manager Release 1.5(X) for IBM Domino

TCP
Source Destination
UDP
of the Cisco TelePresence Manager to the
Cisco
upstream Cisco Catalyst Ethernet switch to which
it is attached. Cisco Discovery Protocol is a Layer
Protocol
2 management protocol, so it does not use TCP
or UDP.
The Cisco TelePresence Manager requests an IP
0.0.0.0: 68
Broadcast: address from the DHCP server. It is
UDP CTSMGR:
67 recommended that you use static IP addressing
DHCP 68
instead of DHCP.
0.0.0.0: 67 Broadcast: DHCP servers send this port in response to a
UDP
reachable. ICMP time-exceeded may be sent by
a device to indicate that the TTL of a packet was
exceeded.
CTSMGR:
NTP UDP NTP: 123 Cisco TelePresence Manager with an NTP
123
server.
CTSMGR:
Ephemeral

TCP
Source Destination
UDP
XML/SOAP is used to coordinate the meeting
schedule and system operational status with
Cisco TelePresence Manager. When security is
enabled, the CTS uses port 8443 on Cisco
CTS: CTS-MAN: TelePresence Manager, and Cisco TelePresence
Ephemeral 8080, 8443 Manager uses port 9501 on the Cisco
TCP
CTSMGR: CTS: 8081, TelePresence system. When security is not
Ephemeral 9501 enabled, Cisco TelePresence system uses port
8080 on Cisco TelePresence Manager, and Cisco
TelePresence Manager uses port 8081 on the
Cisco TelePresence system. Secure mode is
recommended.
operational status between Cisco TelePresence
Manager and the Cisco TelePresence Multipoint
Switch. When security is enabled, the Cisco
HTTP TelePresence Multipoint Switch uses port 8443
CTMS: CTS-MAN:
on Cisco TelePresence Manager, and Cisco
TCP TelePresence Manager uses port 8443 on the
CTS-MAN: CTMS: 8080,
Cisco TelePresence Multipoint Switch. When
Ephemeral 8443
security is not enabled, Cisco TelePresence
Multipoint Switch uses port 8080 on Cisco
TelePresence Manager, and Cisco TelePresence
Manager uses port 8080 on the Cisco
TelePresence Multipoint Switch. Secure mode is
recommended.
XML/SOAP is used to interrogate the Cisco
CTSMGR: Unified Communications Manager database and
TCP CUCM: 8443
Ephemeral discover the existence of Cisco TelePresence
systems.
Any: CTSMGR:
TCP interface of Cisco TelePresence Manager; port 80
Ephemeral 80,443
is automatically redirected to port 443.
Any: SSH provides secure access to the administrative
SSH TCP CTSMGR: 22
Ephemeral CLI of Cisco TelePresence Manager.
Any: CTSMGR: Cisco TelePresence Manager receives SNMP
UDP
Ephemeral 161 queries from a management station.
SNMP
CTSMGR: Cisco TelePresence Manager sends SNMP traps
UDP SNMP: 162
Ephemeral to a management station.
Cisco TelePresence Manager obtains an LSC
CTS-MAN:
CAPF TCP CUCM: 3804 from the Cisco Unified Communications Manager
Ephemeral
CAPF service.
Cisco TelePresence Manager downloads the CTL
CTS-MAN:
CTL TCP CUCM: 2444 from the Cisco Unified Communications Manager
Ephemeral
CTL Provider service.
Cisco TelePresence Manager uses JTAPI to
register with Cisco Unified Communications
Manager CTI Manager service to receive device
CTSMGR: CUCM: 2748, event status of Cisco TelePresence systems.
JTAPI TCP
Ephemeral 2749 When security is enabled, Cisco TelePresence
Manager uses port 2749 on Cisco Unified
Communications Manager. Otherwise, port 2748
is used. Secure mode is recommended.
Cisco TelePresence Manager searches Active
Directory to discover the Domino mailbox name of
each Cisco TelePresence system and for
CTSMGR: Domino: 389,
LDAP TCP authentication of users logging into Cisco
Ephemeral 636
TelePresence Manager. If Domino uses
LDAP/SSL, then port 636 is used. Otherwise, port
389 is used. SSL is recommended.
TCP
Source Destination
UDP
Cisco TelePresence Manager negotiates an IIOP
session to the Domino mailbox of each CTS
CTS-MAN: Domino:
TCP endpoint to process meeting requests. If Domino
Ephemeral 80,443
is set up to support SSL, then port 443 is used.
IIOP Otherwise, port 80 is used. SSL is recommended.
Cisco TelePresence Manager queries and
CTS-MAN: Domino:
UDP synchronizes the Domino mailboxes to which it is
Ephemeral 63148
subscribed.

Cisco TelePresence Multipoint Switch
 DHCP
 ICMP
 NTP
 DNS
 HTTP
 SSH
 SNMP
 SIP
 RTP
Cisco TelePresence Multipoint Switch Release 1.5(X)

TCP
Source Destination
UDP
of the Cisco TelePresence Multipoint Switch to
Cisco
the attached upstream Cisco Catalyst Ethernet
switch. Cisco Discovery Protocol is a Layer 2
Protocol
management protocol, so it does not use TCP or
UDP.
The Cisco TelePresence Multipoint Switch
0.0.0.0: 68 Broadcast: requests an IP address from the DHCP server. It
UDP
CTMS: 68 67 is recommended that you use static IP addressing
DHCP instead of DHCP.
UDP
reachable. ICMP time-exceeded may be sent by a
device to indicate that the TTL of a packet was
exceeded.
NTP UDP CTMS: 123 NTP: 123 Cisco TelePresence Multipoint Switch with an
NTP server.
CTMS:
Ephemeral
TCP
Source Destination
UDP
operational status between the Cisco
TelePresence Manager and the Cisco
TelePresence Multipoint Switch. When security is
enabled, the Cisco TelePresence Multipoint
CTMS: CTS-MAN:
Switch uses port 8443 on the Cisco TelePresence
TCP Manager, and the Cisco TelePresence Manager
CTS-MAN: CTMS:
uses port 8443 on the Cisco TelePresence
Multipoint Switch. When security is not enabled,
Cisco TelePresence Multipoint Switch uses port
8080 on the Cisco TelePresence Manager, and
HTTP the Cisco TelePresence Manager uses port 8080
on the Cisco TelePresence Multipoint Switch.
Secure mode is recommended.
Any: CTMS: interface of the Cisco TelePresence Multipoint
TCP
Ephemeral 80,443 Switch. Port 80 is automatically redirected to port
443.
XML is used between each Cisco TelePresence
system and the Cisco TelePresence Multipoint
CTS: CTMS: Switch for in-meeting controls, such as site and
TCP
Ephemeral 9501 segment switching and Meeting Lock/Unlock. This
port is the same for both secure and nonsecure
modes.
SSH TCP CTMS: 22
Ephemeral CLI of Cisco TelePresence Multipoint Switch.
Any: Cisco TelePresence Manager receives SNMP
UDP CTMS: 161
Ephemeral queries from a management station.
SNMP
CTMS: Cisco TelePresence Manager sends SNMP traps
UDP Any: 162
Ephemeral to a management station.
CTMS: CUCM: SIP provides call signaling with Cisco Unified
Ephemeral 5060 Communications Manager. Can be UDP port
UDP 5060 or TCP port 5060.
CUCM: CTMS:
Ephemeral 5060
SIP Note: Unlike the Cisco TelePresence systems,
CTMS: CUCM:
which always initiate the SIP TCP socket to Cisco
Ephemeral 5060
TCP Unified Communications Manager, with the Cisco
CUCM: CTMS: TelePresence Multipoint Switch either side can
Ephemeral 5060 initiate the connection.
CTMS:
RTP UDP 16384 – Any: Any RTP sends and receives audio and video media.
32768

Cisco IOS IP SLA
 Cisco Discovery Protocol  IP SLA is used to measure
 ICMP and assess the network path.
 NTP  Agent refers to the router that
generates the IP SLA test
 DNS packets.
 SSH  Responder refers to the
 SNMP router that replies to those
requests.
 IP SLA
 Both means that the Agent or
 RTP
the Responder could
generate such a packet.
Agent Responder
Cisco IOS IP Service Level Agreements (IP SLAs) are commonly used to measure and assess
the network path before the installation of Cisco TelePresence. The Cisco IOS IP SLA table
lists the ports that the IP SLA Agent and IP SLA Responder routers most commonly use. The
table lists only the ports relevant for the IP SLA UDP Jitter probe operation that is used to
conduct Cisco TelePresence network path assessment (NPA) testing.
The term “Agent” refers to the router that generates the IP SLA test packets, and the term
“Responder” refers to the router that replies to those requests. “Both” means that either the
Agent or the Responder can generate such a packet.
Cisco IOS IPSLA

TCP
Source Destination
UDP
Cisco Discovery Protocol advertises the
existence of the Cisco IOS IP SLA router to the
Cisco
upstream Cisco Catalyst Ethernet Switch to
which it is attached. Cisco Discovery Protocol is a
Protocol
Layer 2 management protocol, so it does not use
TCP or UDP.
reachable. ICMP time-exceeded may be sent by
a device to indicate that the TTL of a packet was
exceeded.
NTP UDP Both: 123 NTP: 123
Cisco IOS IP SLA router with an NTP server.
Both:
Ephemeral
SSH TCP Both: 22
Ephemeral CLI of the Cisco IOS IP SLA router.
TCP
Source Destination
UDP
Any: SNMP queries are received on this port from a
UDP Both: 161
Ephemeral management station.
SNMP
Both: SNMP traps are sent on this port to a
UDP Any: 162
Ephemeral management station.
Agent: Responder: This port is used to signal a new IPSLA operation
IPSLA UDP
Ephemeral 1967 between the Agent and the Responder.
RTP sends and receives audio and video media
Responder:
from the Agent to the Responder. The Responder
Agent: 16384 –
RTP UDP then returns these packets to the Agent. You can
Ephemeral 32768
define the specific destination UDP ports in the IP
(configurable)
SLA Agent configuration.

Summary
Summary
 RTP video and audio streams are multiplexed by the Cisco
TelePresence codec for transmission on the network.
 Cisco TelePresence deployment models include these:
– Intracampus network
– Intra-enterprise network
– Intercompany network
 You must configure Cisco devices to accommodate Cisco
TelePresence on the network; however, caution should be used
when deploying firewalls and access control lists.
Lesson 2
Shaping and Policing

Overview
You can use traffic policing to control the maximum rate of traffic that is sent or received on an
interface. Traffic policing is often configured on interfaces at the edge of a network to limit
traffic into or out of the network. You can use traffic shaping to match the flow of traffic going
out of an interface to the speed of the remote target interface. You can also use traffic shaping
to ensure that the traffic conforms to policies contracted for it. Traffic policing and traffic
shaping differ in the way in which they respond to traffic violations. Policing typically drops
traffic, while shaping typically queues excess traffic. This lesson describes the traffic-policing
and traffic-shaping quality of service (QoS) mechanisms that you can use to limit the available
bandwidth to traffic classes. Because both traffic policing and traffic shaping use the token
bucket metering mechanism, this lesson also describes how a token bucket works.
Objectives
Upon completing this lesson, you will be able to describe traffic-policing and traffic-shaping
QoS mechanisms. This ability includes being able to meet these objectives:
 Describe recommendations for provisioning a network with Cisco TelePresence
 Describe bursty traffic in the network
 Describe traffic policing and shaping of network traffic
 Describe traffic characteristics for Cisco TelePresence
 Provision for bursts in the network
Recommendations for Provisioning
This topic describes recommendations for provisioning the network for Cisco TelePresence.
Recommendations for Provisioning

Bursts must be accommodated at every port along the
end-to-end path:
 LAN—Use a Cisco Catalyst Ethernet Switch that has enough buffer
capacity per port and can provide guaranteed QoS.
 WAN—There are three areas of concern:
– Policing—Service providers can police in different ways and use
different time intervals depending on the circuit type and service
class.
 They may police the aggregate of all traffic classes, police per
traffic class, or both.
 Engage your service provider to understand the network
configuration before deploying Cisco TelePresence on the
WAN.
– Queuing—You can place Cisco TelePresence into the real-time
PQ or
you can use CBWFQ. The queue must be provisioned for the
correct amount of burst to avoid drop or significant packet delay.
– Shaping—Implement shaping on the W AN interfaces to shape the
bursts to conform to the policing policy of the service provider.
QoS for any application is only as good as the QoS of the weakest link. You must
accommodate bursts at every port along the end-to-end path. Creating the high levels of service
that Cisco TelePresence needs depends on designing them into your network coherently from
end to end, rather than one device at a time.
Within the campus LAN, you must use a Cisco Catalyst Ethernet switch that has enough buffer
capacity per port and can provide guaranteed QoS. Ethernet interfaces that carry Cisco
TelePresence traffic must be at least 1 GB in capacity. In addition, you should assign Cisco
TelePresence to a dedicated priority queue on all interfaces that it traverses. Addressing the
transmission bursts and preventing dropped packets require adequate transmit buffer memory.
Within the WAN, policing, queuing, and shaping are three areas of concern. Service providers
can manage policing in different ways and use different time intervals, depending on the circuit
type and service class. They can police the aggregate of all traffic classes, or police per traffic
class, or both. It is critical that you engage your service provider to understand their network
configuration before attempting to deploy Cisco TelePresence on the WAN. When queuing
traffic, you can place Cisco TelePresence into the real-time priority queue (PQ) or into a class-
based weighted fair queue (CBWFQ). In either case, you must provision the queue for the
correct amount of burst. Otherwise, the queue could drop or significantly delay the excess
packets. You can implement shaping on the WAN interfaces to shape the bursts down to
conform to the policer policy of the service provider.
Understanding Bursts
This topic describes bursty traffic in the network and how it affects Cisco TelePresence.
Understanding Bursts
15 Mb/s
Megabits (Mb/s)
11 Mb/s
66 ms
1 Second
Most LANs today carry traffic that is “bursty” in nature. Bursty traffic can affect the perceived
QoS of all traffic on the network by introducing inconsistent latency, also known as “jitter.”
This behavior can cause problems for Cisco TelePresence, which requires a high degree of
predictability from a network. Bursts of packets that exceed the buffer (queue) limit or policer
configurations on network interfaces along the path can also cause packet loss that results in
noticeable pixelization of the video. Jitter is invisible to the user, but loss (including packets
that arrive but exceed the 165-ms jitter buffer and manifest into late packets) is immediately
apparent.

Bursts—Time Constant (Tc)
 Routers and switches measure burst in bytes. The mean rate is
the number of bytes a router expects to receive over some time
interval (Tc), which is a number of milliseconds for a given bit rate.
 To obtain the mean rate in bytes per millisecond, use the
following formula:
– Mb/s x 1000 (converts Mb/s to kb/s) x 1000 (converts kb/s to
b/s) / 8 (converts b/s to B/s) / 1000 (converts B/s to B/ms)
– For example, using a Cisco TelePresence System 3000
running at 1080p-Best (15.3 Mb/s), the mean rate the router
expects is 1.913 KB/ms
Routers and switches measure burst in bytes. The mean rate is the number of bytes a router
expects to receive over some time interval (Tc), which is a number of milliseconds for a given
bit rate. To obtain the mean rate in bytes per millisecond, use the following formula:
 Megabits per second x 1000 (converts megabits per second to kilobits per second) x 1000
(converts kilobits per second to bits per second) / 8 (converts bits per second to bytes per
second) / 1000 (converts bytes per second to bytes per millisecond)
 For example, using a Cisco TelePresence System 3000 running at 1080-Best (15.3 Mb/s),
the mean rate that the router expects is 1.913 KB per millisecond.
Bursts Tc
1080p 1080p 1080p 720p 720p 720p 720p
Motion handling Best Better Good Best Better Good Lite
Cisco TelePresence Systems 500, 1000, 1100, and 1300
5.5 Mb/s 4.9 Mb/s 4.3 Mb/s 3.4 Mb/s 2.5 Mb/s 1.9 Mb/s 936 kb/s
Maximum bandwidth Tx Tx Tx Tx Tx Tx Tx
over one sec (Mb/s) 5.7 Mb/s 5.1 Mb/s 4.5 Mb/s 3.6 Mb/s 2.7 Mb/s 2.1 Mb/s 1000 kb/s
Rx Rx Rx Rx Rx Rx Rx
Mean rate per 117 Tx

688 Tx 613 Tx 538 Tx 425 Tx 313 Tx 238 Tx
millisecond the router
713 Rx 638 Rx 563 Rx 450 Rx 338 Rx 263 Rx 125 Rx
expects (bytes)
Cisco TelePresence Systems 3000 and 3200
Maximum bandwidth 15.3 13.5 11.7

9 Mb/s 6.3 Mb/s 4.5 Mb/s 3.2 Mb/s
over one sec (Mb/s) Mb/s Mb/s Mb/s
Mean rate per

millisecond the router 1913 1688 1463 1125 788 563 396
expects (bytes)
Committed Burst (Bc)
 Cisco TelePresence System 3000 running at 1080-Best (15.3 Mb/s)
– Routers expect a mean rate of 1.913 KB/ms. Traffic above the yellow line is
considered “burst.” Routers (queues and policers) allow some Bc over some
Tc, as long as it does not exceed the Bc provisioned for Tc.
 Cameras and codecs
– They operate at 30 f/s and produce a frame every 33 ms, with a frame size up
to 65 KB per codec, regardless of resolution. Packets are “paced” so a 65-KB
video frame is smoothly transmitted over a 33-ms interval. Better traffic
shaping reduces the chances of exceeding the Bc.
 Cisco TelePresence Release 1.2
– The largest burst measured is about 5 KB in one millisecond, per codec. This
is a significant improvement over previous releases.
Bytes per millisecond 65 KB
5 KB
1.913 KB
33 ms 33 ms
Two 33-ms Video Frame Intervals
The figure shows an example of using a Cisco TelePresence System 3000 running at 1080-Best
(15.3 Mb/s). In the example, the mean rate the router expects is 1.913 KB per millisecond.
Everything above the yellow line in the figure is considered “burst” by the router. Routers
(queues and policers) allow some amount of burst (Bc) over some time interval (Tc). As long as
the burst does not exceed the Bc that is provisioned for that Tc, the bursts are permitted
Cisco TelePresence cameras and coder-decoders (codecs) run at 30 frames per second (f/s),
which means that a video frame is produced every 33 ms. Each video frame can be as large as
65,000 B (65 KB) per codec (including overhead), regardless of the resolution. Packets are
“paced” so that each 65-KB video frame is smoothly transmitted over each 33-ms frame
interval. The better you shape the traffic, the less likely you are to exceed the Bc.
In Cisco TelePresence System Release 1.2, the largest burst that is measured is about 5 KB in 1
ms per codec. This measurement is a significant improvement over previous releases of Cisco
TelePresence.

Traffic Policing and Shaping
This topic describes traffic policing and shaping for Cisco TelePresence.
Traffic Policing and Shaping

 You must classify packets before policing or shaping the
traffic rate.
 Traffic policing typically drops or marks excess traffic to stay
within a traffic rate limit.
 Traffic shaping queues excess packets to stay within the
desired traffic rate.
Both traffic shaping and policing mechanisms are traffic-conditioning mechanisms that you use
in a network to control the traffic rate. Both mechanisms use classification to differentiate
traffic. They both measure the rate of traffic and compare that rate to the configured traffic-
shaping or traffic-policing policy.
You can describe the difference between traffic shaping and policing in terms of their
implementation:
 Traffic shaping buffers excessive traffic so that the traffic stays within the desired rate.
With traffic shaping, traffic bursts are smoothed out by queuing the excess traffic to
produce a steadier flow of data. Reducing traffic bursts helps reduce congestion in the
network.
 Traffic policing drops excess traffic to control traffic flow within specified rate limits.
Traffic policing does not introduce any delay to traffic that conforms to traffic policies.
Traffic policing can cause more TCP retransmissions because traffic in excess of specified
limits is dropped.
Traffic-policing mechanisms, such as class-based policing or committed access rate (CAR),
also have marking capabilities in addition to rate-limiting capabilities. Instead of dropping the
excess traffic, traffic policing can alternatively mark and then send the excess traffic. This
option allows the excess traffic to be re-marked with a lower priority before the excess traffic is
sent out. Traffic shapers, on the other hand, do not re-mark traffic; they only delay excess
traffic bursts to conform to a specified rate.
Why Use Policing?
 To limit access to resources when high-speed access is used but
not desired (sub-rate access)
 To limit the traffic rate of certain applications or traffic classes
 To mark down (re-color) exceeding traffic at Layer 2 or Layer 3
CIR
Bc
No No
B>Tc
Packet of size B
Yes
Exceed Conform
Action Action
Action Action
Exceed
You typically use traffic policing to do one of the following:

 You can limit the access rate on an interface when a high-speed physical infrastructure is
used in transport. Service providers typically use rate limiting to offer customers subrate
access. For example, a customer may have an optical carrier 3 (OC-3) connection to the
service provider but pay only for a T1 access rate. The service provider can rate-limit the
customer traffic to the T1 speed.
 You can engineer bandwidth so that traffic rates of certain applications or classes of traffic
follow a specified traffic-rate policy. For example, you can rate-limit traffic from file-
sharing applications to a maximum of 64 kb/s.
 You can re-mark excess traffic with a lower priority at Layer 2 or Layer 3, or both, before
sending the excess traffic out. You can configure Cisco class-based traffic policing to mark
packets at both Layer 2 and Layer 3. For example, excess traffic can be re-marked to a
lower differentiated services code point (DSCP) value and have the Frame Relay discard-
eligible (DE) bit set before the packet is sent out.

Why Use Shaping?
 To prevent and manage congestion in ATM and Frame Relay
networks in which asymmetric bandwidths are used along the
traffic path
 To regulate the sending traffic rate to match the subscribed
(committed) rate in Frame Relay or ATM networks
Enough
Token Bucket tokens in
Yes
the token
bucket?
Match
Outgoing packets
Incoming Packets transmitted
Enough
tokens in
Classify
the token
Configured bucket?
Traffic-Shaping Rate Outgoing packets
placed in shapi ng queue
(transmitted later)
Packet Classification Token Bucket
Cri teria Applied Shaping
No
You typically use traffic shaping for the following reasons:

 To prevent and manage congestion in Asynchronous Transfer Mode (ATM) and Frame
Relay networks, where asymmetric bandwidths are used along the traffic path. If shaping is
not used, buffering can occur at the slow (usually the remote) end. Buffering can lead to
queuing, causing delays, and overflow, causing drops.
 To prevent the dropping of noncompliant traffic by the ATM or Frame Relay service
provider by not allowing the traffic to burst above the subscribed (committed) rate. This
shaping allows the customer to keep local control of traffic regulation.
Policing vs. Shaping
Policing Shaping
 Incoming and outgoing directions  Outgoing direction only
 Out-of-profile packets are dropped  Out-of-profile packets are queued
 Dropping causes TCP retransmits until a buffer is full
 Support for packet marking or  Buffering minimizes TCP retransmits
re-marking  No support for marking or re-marking
 Less buffer usage (shaping requires  Support for shaping interaction with
an additional shaping queuing Frame Relay congestion indication
system)
Traffic shaping queues excess traffic by holding packets inside a shaping queue. Use traffic
shaping to shape the outbound traffic flow when the outbound traffic rate is higher than a
configured shape rate. Traffic shaping smoothes traffic by storing traffic that is above the
configured rate in a shaping queue. Therefore, shaping increases buffer utilization on a router
and causes unpredictable packet delays. Traffic shaping can also interact with a Frame Relay
network, adapting to indications of Layer 2 congestion in the WAN. For example, if the
backward explicit congestion notification (BECN) bit is received, the router can lower the rate
limit to help reduce congestion in the Frame Relay network.
You can apply policing to either the inbound or the outbound direction, while you can apply
shaping only in the outbound direction. Policing drops nonconforming traffic instead of
queuing the traffic, which shaping does. Policing also supports the marking of traffic. Traffic
policing is more efficient than traffic shaping in terms of memory utilization because no
additional packet queuing is needed.
Both traffic policing and traffic shaping ensure that traffic does not exceed a bandwidth limit,
but each mechanism affects traffic differently:
 Policing drops packets more often, generally causing more retransmissions of connection-
oriented protocols, such as TCP.
 Shaping adds variable delay to traffic, possibly causing jitter.

Single Token Bucket
 Bc is normal burst size
 Tc is the time interval
 CIR is the committed information rate
– CIR = Bc / Tc
The token bucket is a mathematical model that routers and switches use to regulate traffic flow.
The model has two basic components:
 Token: Each token represents permission to send a fixed number of bits into the network.
The Cisco IOS Software puts tokens into a token bucket at a certain rate.
 Token bucket: A token bucket has the capacity to hold a specified number of tokens. Each
incoming packet, if forwarded, takes tokens from the bucket that represents the packet size.
If the bucket fills to capacity, newly arriving tokens are discarded. Discarded tokens are not
available to future packets. If there are not enough tokens in the token bucket to send the
packet, the traffic conditioning mechanisms can take these actions:
— Wait for enough tokens to accumulate in the bucket (traffic shaping)
— Discard the packet (traffic policing)
The traffic policing feature works with this token bucket mechanism. A token bucket relies on
the following parameters:
 Committed burst (Bc): Bc is the normal burst size (also called the committed burst). It
specifies in bits (or bytes) per burst how much traffic can be sent within a given unit of
time to not create scheduling concerns.
 Committed time window (Tc): Tc is the time interval (also called the measurement
interval). It specifies the time quantum in seconds per burst.
 Committed information rate (CIR): CIR is the committed information rate (also called
the mean rate). It specifies how much data can be sent or forwarded per unit time on
average. CIR is calculated by the formula CIR = Bc / Tc.
Tokens are put into the bucket at a certain rate. The bucket itself has a specified capacity. If the
bucket fills to capacity, newly arriving tokens are discarded. Each token is permission for the
source to send a certain number of bits into the network. To send a packet, the regulator must
remove from the bucket a number of tokens equal in representation to the packet size.
If not enough tokens are in the bucket to send a packet, the packet either waits until the bucket
has enough tokens or the packet is discarded or marked down. If the bucket is already full of
tokens, incoming tokens overflow and are not available to future packets. Thus, at any time, the
largest burst a source can send into the network is roughly proportional to the size of the
bucket.
Example: Token Bucket as a Piggy Bank

You can also think of a token bucket as a piggy bank. Every day you can insert a dollar into the
piggy bank (the token bucket). At any given time, you can spend only what you have saved in
the piggy bank. On average, if your saving rate is one dollar per day, your long-term average
spending rate will be one dollar per day if you constantly spend what you have saved.
However, if you do not spend any money on a given day, you can build up your savings in the
piggy bank to the maximum limit that the piggy bank can hold. For example, if the size of the
piggy bank is limited to hold five dollars, and if you save and do not spend for five straight
days, the piggy bank will contain five dollars. When the piggy bank fills to its capacity, you
will not be able to put any more money into it. Then, at any time, you can spend up to five
dollars (bursting above the long-term average rate of one dollar per day).

Dual Token Bucket
 Be—Excess burst size
 Tc—Tokens in Bc bucket
 Te—Tokens in Be bucket
 The return value is conform, exceed, or violate
With a dual-token bucket mechanism, you can configure class-based traffic policing to support
excess bursting capability. The dual token bucket has four additional components:
 Be: The excess burst size
 Tc: The tokens in Bc bucket
 Te: The tokens in Be bucket
 Return value: Provides users with three categories for each packet:
— Conforming: There are enough tokens in the first token bucket with a maximum
size of Bc.
— Exceeding: There are not enough tokens in the first token bucket, but there are
enough tokens in the second token bucket with a maximum size of Be.
— Violating: There are not enough tokens in the first or second token bucket.
With excess bursting, after the first token bucket is filled to Bc, extra (excess) tokens can be
accumulated in a second token bucket. Excess burst (Be) is the maximum amount of excess
traffic, over and above Bc that can be sent during the time interval after a period of inactivity.
With a single rate-metering mechanism, the second token bucket—with a maximum size of
Be—fills at the same rate (CIR) as the first token bucket. If the second token bucket fills up to
capacity, no more tokens can be accumulated and the excess tokens are discarded.
With dual token bucket traffic policing, the typical actions that are performed are sending all
conforming traffic, re-marking (to a lower priority), sending all exceeding traffic, and dropping
all violating traffic. The main benefit of using a dual token bucket method is the ability to
distinguish between traffic that exceeds the Bc but not the Be. This approach enables a different
policy to be applied to packets in the Be category. Using the piggy bank example, think of the
CIR as the savings rate of $1 per day. Bc is how much you can save in the piggy bank per day
($1). Tc is the interval at which you put money into the piggy bank (one day). Be ($5) allows
you to burst over the average spending rate of one dollar per day if you do not spend a dollar
per day.
Traffic Characteristics of Cisco TelePresence
This topic describes the traffic characteristics of Cisco TelePresence.
Traffic Characteristics of
Cisco TelePresence
1920 Lines of Vertical Resolution (Widescreen Aspect Ratio is 16:9)
1080 Lines of Horizontal Resolution
2,073,600 pixels per frame

x 3 colors per pixel
x 1 Byte (8 bits) per color
x 30 f/s
Compressed to 4 Mb/s per screen = 1.5 Gb/s per screen
> 99% compression ratio uncompressed
Each 65-inch plasma display supports 1920 lines of vertical resolution and 1080 lines of
horizontal resolution, with a widescreen aspect ratio of 16:9. One 65-inch plasma display
contains 2,073,600 pixels per frame. With three colors per pixel, 1 byte (8 b) per color, and 30
f/s, that is 1.5 Gb/s of bandwidth per screen if the image is not compressed.
The Cisco TelePresence systems use a codec to compress this bandwidth down to 4 Mb/s per
screen, which represents a compression ratio of more than 99 percent. Therefore, each packet
represents a large amount of video data, and hence a very small amount of packet loss can be
extremely damaging to the video quality.
Cisco TelePresence System Release 1.5 implements a new technique that is known as Long-
Term Reference Frames. This technique allows the system to recover from packet loss
significantly faster by retransmitting the differences in the current frame relative to the original
reference frame, instead of transmitting an entirely new reference frame. You implement Long-
Term Reference Frames only for point-to-point meetings between two Cisco TelePresence
systems. The Cisco TelePresence Multipoint Switch does not implement this feature in this
release, but it is planned for a future release of Cisco TelePresence Multipoint Switch software.
Given the intense compression ratio and extremely high-definition of the video, even a small
amount of packet loss or jitter can cause noticeable disruptions in the user experience. Also,
because you are trying to maintain the real-time interaction of human conversations, latency
must be kept to an absolute minimum.

Requirements for Cisco TelePresence
 Service level requirements: Measured end-to-end in each
– Latency ≤ 150 ms direction (not round-trip)
– Jitter ≤ 50 ms
– Loss ≤ 0.05%
 Maximum bandwidth per second
Cisco
– Cisco TelePresence Systems 500, 1000, 1100, TelePresence
and 1300 = 5.5 Mb/s (at 1080p) Traffic Profile
– Cisco TelePresence Systems 3000 and 3200 =
15.3 Mb/s (at 1080p)
bytes
– Cisco TelePresence Multipoint Switch =
198 Mb/s (5.5 Mb/s * 36 sites)
 Average packet size/packets per second 33-ms Frame Intervals
– Average 1100 bytes/packet
 Cisco TelePresence Systems 500, 1000,  30 f/s
1100, and 1300 at 5.5 Mb/s = average 625  Variable bit rate
p/s
 Cisco TelePresence Systems 3000 and  Large packet sizes
3200 at14.6 Mb/s = average 1740 p/s
 High packets/second
The Cisco TelePresence profile uses 30 f/s, a variable bit rate, large packet sizes, and high
packets/second. While the details of the service level requirements of Cisco TelePresence are
still being defined with testing, initial tests have produced the following requirements:
 Service level requirements
— Latency ≤ 150 ms
— Jitter ≤ 50 ms
— Loss ≤ 0.05 percent
 Maximum bandwidth per second
— Cisco TelePresence Systems 500, 1000, 1100, and 1300 = 5.5 Mb/s (at 1080p)
— Cisco TelePresence Systems 3000 and 3200 = 15.3 Mb/s (at 1080p)
— Cisco TelePresence Multipoint Switch = 198 Mb/s (5.5 Mb/s * 36 sites)
 Average packet size/packets per second
— Average 1100 B per packet
— Cisco TelePresence Systems 500, 1000, 1100, and 1300 at 5.5 Mb/s = average 625
p/s
— Cisco TelePresence Systems 3000 and 3200 at 14.6 Mb/s = average 1740 p/s
Note These values are measured end-to-end in each direction, not round trip, and do not include
a high frame rate (HFR) codec or interoperability.
Video Frame Jitter vs. Packet Jitter
 Packet jitter is the variation in latency of received packets. Jitter results
when a packet gets queued or delayed somewhere in the circuit, where
there was no delay or queuing for other packets.
 Frame jitter is also referred to as delay variation. Frame delay greatly
affects the performance of real-time applications such as IP telephony or
IP video.
 Cisco TelePresence measures jitter by comparing the arrival time of the
current video frame to the expected arrival time of that frame based on a
running clock of fixed 33-ms intervals.
 The primary contributor to video frame jitter is the clock rate of every
interface along the path (i.e., how long it takes to serialize a video frame
onto the wire as compared to the 33-ms expected frame arrival time).
10 Mbps
Per Screen T1 E1 4 x T1 4 x E1 E3 T3 OC-3 OC-12
Ethernet
Max Jitter
304 ms 221 ms 51 ms 31 ms 19 ms 0 ms 0 ms 0 ms 0 ms
(MFSR vs . 33ms)
Packet Jitter
Packet jitter is a variation in the latency of received packets. At the sending side, packets are
sent—spaced evenly apart—in a continuous stream. Jitter results when a packet gets queued or
delayed somewhere in the circuit, where there was no delay or queuing for other packets. Due
to network congestion, improper queuing, or configuration errors, the delay between each
packet can vary instead of remaining constant.
Frame Jitter
Frame jitter is also referred to as delay variation. Frame delay greatly affects the performance
of real-time applications such as IP telephony or IP video. To function as intended, these
applications require a low and bounded frame jitter.
Cisco TelePresence measures jitter by comparing the arrival time of the current video frame to
the expected arrival time of that frame, based on a running clock of fixed 33-ms intervals.
Unlike most other video-conferencing and telepresence products on the market that use variable
frame rate codecs, Cisco TelePresence operates at a consistent 30 f/s. Therefore, the sending
codec generates a video frame every 33 ms, and the receiving codec expects those video frames
to arrive every 33 ms.
The primary contributor to video frame jitter is the clock rate of every interface along the path
(for example, how long it takes to serialize a video frame onto the wire as compared to the 33
ms expected frame arrival time).
Video frames vary in size, based on how much motion a given video frame represents. When
there is a low amount of motion within the encoded video, the video frame is relatively small.
When there is a large amount of motion within the encoded video, the video frame is large.

Video Frame Statistics
Per Screen T1 E1 4xT1 4xE1
Circuit Bit Rate (kb/s) 1 1544 2048 6176 8192
Max Frame Size 65 KB 65 KB 65 KB 65 KB
Average Frame Size 16 KB 16 KB 16 KB 16 KB
Min Frame Size 1 KB 1 KB 1 KB 1 KB

2
Max Frame Serialization Rate 337 ms 254 ms 84 ms 64 ms
2
Average Frame Serialization Rate 83 ms 63 ms 21 ms 16 ms
2
Min Frame Serialization Rate 5 ms 4 ms 1 ms < 1 ms
Max Jitter (MFSR vs. 33 ms) 304 ms 221 ms 51 ms 31 ms
Video Frame Statistics
10 Mb
Per Screen E3 T3 OC-3 OC-12
Ethernet
Circuit Bit Rate

10,000 34,368 44,736 155,520 622.080
(kb/s) 1
Max Frame Size 65 KB 65 KB 65 KB 65 KB 65 KB
Average Frame Size 16 KB 16 KB 16 KB 16 KB 16 KB
Min Frame Size 1 KB 1 KB 1 KB 1 KB 1 KB
Max Frame
2 52 ms 15 ms 12 ms 4 ms < 1 ms
Serialization Rate
Average Frame
2 13 ms 4 ms 3 ms < 1 ms < 1 ms
Serialization Rate
Min Frame
2 < 1 ms < 1 ms < 1 ms < 1 ms < 1 ms
Serialization Rate
Max Jitter
19 ms 0 ms 0 ms 0 ms 0 ms
(MFSR vs. 33 ms)
1. Circuit Bit Rate values do not take into consideration any Layer 2 framing overhead, such
as Multilink PPP (MLP), Inverse Multiplexing over ATM (IMA), Multilink Frame Relay
(FRF.16), Multiprotocol Label Switching (MPLS), and IEEE 802.1Q. The Layer 2 framing
overhead will cause the Circuit Bit Rate to be reduced by some number of kilobits per
second, so the serialization rate of the frame would be slightly longer in real life.
2. These values are calculated for just a single screen of video. It does not include all the other
audio, video, and data packets that could simultaneously be sitting in the queue waiting to
transmit. Therefore, the serialization rates in the table are really the “best case” given no
other traffic in queue. Real world serialization rates would be higher.
Average vs. Maximum Bandwidth
 You must provision the network to support the maximum
bandwidth. However, under normal conditions, average
bandwidth utilization is generally 60%-80%.
– For example, a Cisco TelePresence System 3000 running at
1080p-Best averages 10–12 Mb/s. A Cisco TelePresence
System 1000 running at 1080p-Best averages 3–4 Mb/s.
 On a converged network, data applications can take advantage of
the unused bandwidth (white space will be filled in by data traffic).
15 Mb/s
Megabits (Mb/s)
11 Mb/s
1 Second
When participants are sitting, talking, and gesturing normally, average bandwidth utilization is
generally 60 to 80 percent of the numbers that are provided in the figure. For example, a Cisco
TelePresence System 3000, running at 1080p, has a best average of 10 to 12 Mb/s. However,
from a bandwidth provisioning and network engineering perspective, the network must be
engineered to accommodate the peak rate. Peak rates generally occur at the following times:
 The beginning of the call, or when you resume a call on hold
 When the codecs are reconverging, such as recovering from severe packet loss due to a
midcall network outage
 During periods of high motion in the video, such as when participants all stand up or walk
around the room
Ninety percent of the time, Cisco TelePresence will use far less than what the network is
provisioned for. During these times, data traffic can flow at higher rates, taking advantage of
the unused bandwidth.

Maximum Bandwidth per Second
Network must be provisioned for the values in the table, but average
bandwidth utilization is 60%-80% of these numbers.
1080p 1080p 1080p 720p 720p 720p 720p
Motion handling Best Bett er Good Best Better Good Lite
Video per screen (kb/s) 4000 3500 3000 2250 1500 1000 800
Audio per microphone (kb/ s) 64 64 64 64 64 64 64
Auto-Collaborate video channel

500 500 500 500 500 500 100
(i.e., data projector (kb/s)
Auto-Collaborate audio channel

(i.e., audio add-in) (kb/s) 64 64 64 64 64 64 64
Cisco TelePresence System 500, 1000, 1100, or 4628 Tx 4128 Tx 3628 Tx 2878 Tx 2128 Tx 1628 Tx 1628 Tx
1300 total audio and video (kb/s) 4756 Rx 4256 Rx 3756 Rx 3006 Rx 2256 Rx 1756 Rx 1756 Rx
Cisco TelePresence Systems 3000 or 3200 total

12,756 11,256 9756 7506 5256 3756 3756
audio and video (kb/s)
+ 20% for Layer 2-4 overhead
Cisco TelePresence Systems 500, 1000, 1100, or

1300 total bandwidth (kb/s) (includes Layer 2–4 5554 Tx 4954 Tx 4354 Tx 3454 Tx 2554 Tx 1954 Tx 1330 Tx
5707 Rx 5107 Rx 4507 Rx 3607 Rx 2707 Rx 2107 Rx 1483 Rx
overhead)
Cisco TelePresence System 3000 or 3200 total

bandwidth (kb/s) (includes Layer 2–4 overhead) 15,307 13,507 11,707 9007 6307 4507 3907
The Cisco TelePresence System 1000 transmits up to 128 kb/s of audio, but can receive up to
256 kb/s when participating in a meeting with a Cisco TelePresence System 3000 or 3200.
The actual Layer 2 to Layer 4 required overhead varies by the encapsulation method and
whether IP Security (IPsec) tunneling and encryption are used. To make it easier for customers
to determine how much overhead that they should provision, the numbers in the figure include
a very conservative 20 percent for Layer 2 to Layer 4. This overhead accounts for all possible
encapsulation and encryption overhead.
Max Bandwidth
Resolution 1080p 1080p 1080p 720p 720p 720p 720p
Motion handling Best Better Good Best Better Good Lite
Video per screen (kb/s) 4000 3500 3000 2250 1500 1000 936
Audio per microphone

64 64 64 64 64 64 64
(kb/s)
Auto Collaborate video

channel 500 500 500 500 500 500 100
(i.e., data projector) kb/s)
Auto Collaborate audio

channel 64 64 64 64 64 64 64
(i.e., audio add-in) (kb/s)
Cisco TelePresence 4628 4128 3628 2878 2128 1628 1164

System 500, 1000, 1100, Tx Tx Tx Tx Tx Tx Tx
or 1300 total audio and 4756 4256 3756 3006 2256 1756 1292
video (kb/s) Rx Rx Rx Rx Rx Rx Rx
Cisco TelePresence
System 3000 or 3200 12,756 11,256 9756 7506 5256 3756 3164
total audio and video (kb/s)
+ 20% for Layer 2–4 Overhead
Cisco TelePresence
System 500, 1000, 1100, 5554 4954 4354 3454 2554 1954 1397
or 1300 total bandwidth Tx Tx Tx Tx Tx Tx Tx
(kb/s) 5707 5107 4507 3607 2707 2107 1550
(Includes Layer 2–4 Rx Rx Rx Rx Rx Rx Rx
overhead)
Cisco TelePresence
System 3000 or 3200 total
bandwidth (kb/s) 15,307 13,507 11,707 9007 6307 4507 3797
(Includes Layer 2–4
overhead)

Relation of Video Frames to Packets
1 Second
33-ms Frame Intervals
15 Mb/s
11 Mb/s
33 ms 33 ms 33 ms 33 ms
#5 RX Buffer
16 KB #3
#1
#4 65 KB
25 KB #2 16 KB
6 KB
Application Layer
Network Layer
The Cisco TelePresence cameras run at a 30-Hz clock rate (displays are progressive scan and
clocked at 60 Hz). Therefore, the Cisco TelePresence codecs produce a video frame every 33
ms (30 f/s in 33-ms frame intervals).
The figure zooms in to take a closer look at the actual behavior of Cisco TelePresence video
frames. The figure illustrates four 33-ms frame intervals. The video frames vary in size, based
on the amount of motion within the encoded video for a given 33-ms frame interval. The
maximum frame size is 65 KB (including Layer 3 to Layer 4 overhead). The average frame size
is 16 KB. The minimum frame size is as small as 1 KB.
These frames are then broken down into 1100 B packets and transported across the network.
While the frame sizes vary, the frame intervals do not. The Cisco TelePresence codec runs at a
consistent 30 f/s. The Cisco TelePresence codec does not reduce the frame rate (as other video
codecs do) during periods of severe motion in the encoded video. The Cisco TelePresence
codec continues sending 30 f/s but increases the frame size to accommodate the additional
motion. You implement a maximum in the encoder so that you never exceed the maximum
bandwidth over a one-second period.
Video Frames to Packets
 Video frame size can range from 1 KB to 65 KB.
 Use the average of 16 KB per frame to calculate packets per
second.
 16 KB per frame / 1100 Bytes per video packet gives you about
15 packets per video frame.
 30 video f/s equals 450 video p/s per video channel.
Resolution 1080p 1080p 1080p 720p 720p 720p
Motion handling Best Better Good Best Better Good
Average video frame si ze includes Layer
16 KB 16 KB 16 KB 9.5 KB 9.5 KB 9.5 KB
3-4 overhead
Average bytes per video packet includes
1100 1100 1100 1100 1100 1100
Layer 3-4 overhead
average video p/s 900 p/s 900 p/s 900 p/s 540 p/s 540 p/s 540 p/s
(2 video channels)
(4 video channels)
Because some video frames are 65 KB and some are as small as 1 KB, you must use the
average of 16 KB per frame to calculate packets per second.
The average bytes per video packet is 1100, therefore 16 KB per frame/1100 B per video
packet gives you about 15 packets per video frame. 15 packets per video frame * 30 video
frames per second equals 450 video packets per second per channel. You multiply this number
by the number of video channels per system to determine the average video packets per second
of the Cisco TelePresence system.
Note The table in the figure shows only video packets. Add four channels of audio at 50 packets
per second (p/s) per channel (200 p/s of audio) in addition to what is given in the table.
Video Frames to Packets
Average video frame size includes

16 KB 16 KB 16 KB 9.5 KB 9.5 KB 9.5 KB
Layer 3–4 overhead
Average bytes per video packet

1100 1100 1100 1100 1100 1100
includes Layer 3–4 overhead

(2 video channels)

1800 1800 1800 1080 1080 1080
average video p/s
p/s p/s p/s p/s p/s p/s
(4 video channels)

Relation of Video Frames to
Bytes per Millisecond
 To obtain the mean rate in bytes per millisecond, use the
following formula:
– Megabits per second x 1000 (converts megabits per second to
kilobits per second) x 1000 (converts kilobits per second to bits
per second) / 8 (converts bits per second to bytes per second)
/ 1000 (converts bytes per second to bytes per millisecond)
Motion handli ng Best Better Good Best Better Good
5554 TX 4954 TX 4354 TX 3454 TX 2554 TX 1954 TX
max bandwidth over one second
5707 RX 5107 RX 4507 RX 3607 RX 2707 RX 2107 RX
(Mb/s)
max bandwidth over one second 15,307 13,507 11,707 9007 6307 4507
(Mb/s)
688 TX 613 TX 538 TX 425 TX 313 TX 238 TX
mean rate per millisecond the
713 RX 638 RX 563 RX 450 RX 338 RX 263 RX
router expects (bytes)
mean rate per millisecond the 1913 1688 1463 1125 788 563
router expects (bytes)
You tend to think of bandwidth in seconds (for example 15 Mb/s). However, queuing, shaping,
and policing algorithms in routers and switches measure bandwidth in much smaller intervals
of time (milliseconds). Cisco TelePresence never exceeds the maximum bandwidth over one
second, but you have to analyze the traffic per millisecond to understand how policer and
shaper algorithms measure it. Routers and switches measure traffic in bytes over some time
interval. The mean rate (R) is the amount of bytes a router expects to receive over some
number of milliseconds (Tc) for a given bit rate. To obtain the mean rate in bytes per
millisecond, use the following formula:
Megabits per second x 1000 (converts megabits per second to kilobits per second) x 1000
(converts kilobits per second to bits per second) / 8 (converts bits per second to bytes per
second) / 1000 (converts bytes per second to bytes per millisecond)
Relation of Video Frames to Bytes Per Millisecond

5553 Tx 4953 Tx 4353 Tx 3454 Tx 2554 Tx 1954TX

5707 5107 4507 3607 2707 2107
max bandwidth over one sec (Mb/s)
Rx Rx Rx Rx Rx Rx

15,307 13,507 11,707 9007 6307 4507
max bandwidth over one sec (Mb/s)

688 Tx 613 Tx 538 Tx 425 Tx 313 Tx 238 Tx
mean rate per millisecond the router
713 Rx 638 Rx 563 Rx 450 Rx 338 Rx 263 Rx
expects (bytes)

mean rate per millisecond the router 1913 1688 1463 1125 788 563
expects (bytes)
Provisioning for Bursts
This topic describes how to provision for bursts in the network.
Provisioning for Bursts

 Provision 20 Mb/s for a Cisco TelePresence System 3000 or 3200 running at
1080p-best because the traffic is bursty and very intolerant of jitter.
 A 15 Mb/s call can require 20 Mb/s to accommodate bursts without being policed.
 Provision end-to-end queuing policies to provide adequate queue depth.
 Policing traffic varies by provider and types of circuit.
 Consider the entire provider path (e.g., ingress traffic coming in the left side is OK,
but may be policed in egress coming out the right side of the cloud).
 Implement shaping at the CE WAN edge to shape the traffic to conform to service
providers policers.
Service
Provider
PE
CE
CE PE
Leased-Line DS-3 Metro-Ethernet circ uit

Queuing circuit with generous with tight policer
Policing polic er policy (200- policy (20-ms Tc)
ms Tc)
Shaping
Because Cisco TelePresence traffic is bursty and intolerant of jitter, you should provision a 20-
Mb/s circuit for a Cisco TelePresence System 3000 or 3200 running at 1080p-best. This is
because a 15-Mb/s call actually requires 20 Mb/s to accommodate the bursts without being
policed. You should also be aware that providers may only offer bandwidth in increments of
10, 20, 30, or 45 Mb/s.
Cisco TelePresence System Release 1.5 increases the jitter tolerance, allowing you to
implement shaping to reduce the necessary bandwidth. However, you must account for all
traffic on the circuit (such as data, voice, video, routing protocols, and Operation,
Administration, Maintenance, and Provisioning [OAM&P] traffic). Using priority queuing with
a 33 percent ratio, you would need a 45-Mb/s circuit to allow 33 percent of the circuit (15
Mb/s) to be allocated to telepresence traffic in a strict PQ. Using weighted fair queuing (WFQ)
with a 50 percent ratio, you would need a 30-Mb/s circuit. If your circuit is dedicated to
telepresence traffic, then plan on 80 to 85 percent of the bandwidth being used for the
telepresence traffic. 15 to 20 percent of the bandwidth is reserved for routing protocols and
OAM&P overhead. This allocation would require a 20-Mb/s circuit to achieve the 15 Mb/s that
the Cisco TelePresence System 3000 or 3200 call requires.
To achieve the high levels of service that Cisco TelePresence requires, you must enable
queuing policies on every node along the path to provide service guarantees, regardless of how
infrequently congestion might occur on certain nodes.
Having the service provider police traffic varies by provider and can even vary within a given
provider, based on the types of circuits. You must consider the entire provider path when
policing traffic. For example, in the figure, ingress traffic coming in the left side of the cloud is
OK, but can be policed in egress coming out the right side of the cloud. You should implement
shaping at the customer edge (CE) WAN to shape the traffic to conform to the policers of the
service provider.

Cisco TelePresence Burst Comparison
 For a 15 Mb/s-call, the router policer algorithm
expects to receive a mean rate of 1.913 KB per 65 KB
millisecond. Everything above the yellow line is
considered burst and will be policed. Release 1.1.1(365)
August 2007
 In Cisco TelePresence Release 1.0, the entire 65-
Per Screen
KB payload is sent in one millisecond (34x the 20 KB
mean rate).
 Cisco TelePresence Release 1.1 began shaping
traffic across the 33-ms frame interval, lowering
max burst to 20 KB in one millisecond (still 10x the 1.913 KB
mean rate).
 Cisco TelePresence Releases 1.2 and later One 33-ms Video Frame Interval
shaped traffic even more, reducing max burst to 13
KB (still 7x the mean rate).
65 KB 65 KB
Release 1.2.0(991)
Release 1.0.1(616) November 2007
Per Screen
Per Screen
November 2006
13 KB
1.913 KB 1.913 KB
One 33-ms Video Frame Interval One 33-ms Video Frame Interval
The mean rate for a 15-Mb/s call is 1913 B per millisecond. The figure illustrates how many
bytes a single codec (per screen) can transmit on a per-millisecond basis. The router considers
everything above the yellow line to be burst.
Cisco TelePresence System Release 1.1 and 1.2 have dramatically improved the burst behavior.
Cisco TelePresence System Release 1.3, 1.4, and 1.5 have the same burst characteristics as
Cisco TelePresence System Release 1.2.
In Cisco TelePresence System Release 1.0, the largest burst that is measured is 65 KB in 1 ms
per codec. The entire payload is sent within the first millisecond of the 33-ms interval.
and 65 KB spread over 16 ms per codec. The average is 16 KB over 16 ms per codec. Cisco
TelePresence System Release 1.1 still tends to burst at the beginning of the frame interval, but
tries to smooth the burst over the entire interval. Because most of the payload is sent within
about the first 16 ms of the frame, with a lot of unused white space towards the end, the
spreading leaves room for improvement.
and 65 KB spread over 32 ms per codec. The average is 16 KB over 33 ms per codec. The
traffic is spread out evenly over the 33-ms video frame interval. Also, the bursts tend to be
weighted towards the end of the frame interval, rather than at the beginning.
In all three releases, a maximum of 65 KB is sent over each 33-ms interval (with the average
being 16 KB over each 33-ms interval). The difference in releases is whether that 65 KB is
spread over the entire interval or sent all at once, leaving many unused milliseconds of space in
between.
All of the examples in the figure are per screen. The likelihood of all four screens bursting in
the same millisecond is very low because the screens run on independent clocks and switch
independently so they are loosely staggered. The worst case would be site switching in a
multipoint meeting, in which all four screens could switch at once. However, even in this
situation, the screens will not line up on the same millisecond boundary, but will be more
tightly staggered.
Also, none of the examples in the figure include any bandwidth for audio. So while the Cisco
TelePresence System Release 1.2 example shows a 13-KB burst, testing shows that you will
need a Bc of about 14,250 B. This equates to a Tc of 20 ms worth of burst.
The following is an example of calculating the amount of traffic that is associated with the
audio traffic:
There is 160 B of audio payload per packet and 40 B overhead for the IP, UDP, and RTP
headers per packet, which equals 200 B per packet. With a possibility of 50 p/s, this equals
10,000 B/s. Multiply this value by the number of audio channels (4) and divide by 1000 to
calculate milliseconds, and you have 40 B per millisecond of audio traffic:
((160 B + 40 B) * 50 p/s) * 4/1000 = 40 B/ms

Internal Codec Policer Comparison
 In Cisco TelePresence Release 1.0, the policer Tc
had to be set to 200 ms to accommodate bursts. 65 KB

 In Cisco TelePresence Release 1.1, the policer Tc Release 1.1.1(365)
had to be set to 100 ms to accommodate the August 2007
bursts.
20 KB
 In Cisco TelePresence Release 1.2 and later, the
policer Tc only needs to be 10 ms.
– This is a major improvement and should
eliminate concern over bursts. 1.912 KB
 Note: All of the competitors that were tested to
date behave like Release 1.0. One 33-ms Video Frame Interval
65 KB 65 KB

Release 1.0.1(616) Release 1.2, and later

November 2006 November 2007 – and later
5 KB
1.912 KB 1.912 KB
One 33-ms Video Frame Interval One 33-ms Video Frame Interval
Because of improvements to the shaping smoother inside of the Cisco TelePresence codec,
there is less need to modify the traffic externally to allow an average over a long Tc. Take, for
example, driving 60 miles in 60 minutes. Although the average speed is 60 miles per hour, the
actual speed may vary greatly over the hour, allowing for a high variability of burst. However,
a drive during which the car is going an average of 60 miles per hour and is checked every 10
miles does not allow for as much flexibility of bursting.
In November 2006, Cisco TelePresence System Release 1.0 required the policer Tc to be set to
200 ms to accommodate bursts. In August 2007, Cisco TelePresence System Release 1.1
required the policer Tc to be set to 100 ms to accommodate the bursts. As of November 2007,
Cisco TelePresence System Release 1.2 and later only need the policer Tc to be set to 10 ms.
This improvement should eliminate the concern about burst.
Switch Port Recommendations for
the LAN
The 400-KB recommendation shown here is based on the burst behavior of 1.0 and 1.1.
No solution testing has been performed with emphasis on relaxing the standard for 1.2 through 1.6.
Access Distribution Core WAN Handoff

Cisco
TelePresence
Multipoint
Switch
Cisco
TelePresence
System 3000
Any Ethernet port that carries a single Cisco TelePresence call must
offer > 400 KB of Tx memory, be > 1 Gb/s, and provide PQ.
Any Ethernet port which carries two or more Cisco TelePresence calls must
offer > 1 MB of Tx memory, be > 1 Gb/s, and provide PQ.
Router interfaces should be > 1 Gb/s and provide Cisco IOS LLQ with the
appropriate burst value provisioned on the Cisco TelePresence queue.
The following are recommendations for how to provision for bursts on the LAN:
 Any Ethernet port that carries a single Cisco TelePresence call must offer more than 400
KB of Tx memory, be greater than 1 Gb/s, and provide PQ.
 Any Ethernet port that carries two or more Cisco TelePresence calls must offer more than 1
MB of Tx memory, be greater than 1 Gb/s, and provide PQ.
 Router interfaces should be more than 1 Gb/s and provide Cisco IOS Software low latency
queuing (LLQ) with the appropriate burst value provisioned on the Cisco TelePresence
queue.
Note The 400-KB recommendation is based on the burst behavior of Cisco TelePresence System
Release 1.0 and 1.1. No solution testing has been performed with emphasis on relaxing the
previous standard for Cisco TelePresence System Releases 1.2 through 1.6.

WAN Port Recommendation
Service
Provider
CE PE CE
PE
The interface must provide LLQ or CBWFQ with appropriate burst

value provisioned on the Cisco TelePresence queue.
Policing may be done on the aggregate of all traffic classes or on a
per-class basis. Service providers must provision the correct Bc and
Tc values for TelePresence bursts. Talk with the service provider to
determine how their Bc, Be, and Tc values are configured.
Implement shaping on the WAN interfaces to shape the bursts down
to conform to the policer policy of the service provider.
When the telepresence traffic from the LAN reaches the WAN router, it is queued with other
network traffic according to the local QoS policy. This queuing can result in rapid queue
buildup, both in the telepresence class and in the other classes. These queuing events can
introduce from tens to hundreds of milliseconds of delay or packet loss and can result in
significant degradation for Cisco TelePresence and other applications.
The following are recommendations for how to provision for bursts on the WAN:
 The interface must provide LLQ or CBWFQ with the appropriate burst value provisioned
on the Cisco TelePresence queue.
 You can do policing on the aggregate of all traffic classes or on a per-class basis. Policers
measure bursts (Bc and Be) based on some interval of time (Tc). Service providers must
provision the correct Bc and Tc values to allow for Cisco TelePresence bursts. In some
situations, this provisioning is not possible. You must talk with your service provider to
find out how their Bc, Be, and Tc values are configured.
 Implement shaping on the WAN interfaces to shape the bursts down to conform to the
policer policy of the service provider.
WAN Port Recommendation (Cont.)
 Ask the service provider to increase the Bc and Tc of their
policers to accommodate bursts. This is not an option on certain
types of carrier circuits.
 Buy 20% more bandwidth so that bursts are invisible to the
provider. This is a more expensive solution.
 Implement shaping on the WAN interfaces to shape the bursts to
conform to the policer policy of the service provider.
– Shaping introduces jitter into the video stream. Prior to Cisco
TelePresence Release 1.5, this was not recommended.
– Cisco TelePresence Release 1.5 introduces a dynamic jitter
buffer that allows the jitter buffer to grow to up to 165 ms,
making shaping a viable option.
There are three options for dealing with bursts on the WAN:
 Ask your provider to increase the Bc and Tc of their policers to accommodate the bursts.
This is often not an option on certain types of carrier circuits.
 Buy 20 percent more bandwidth than required so that the bursts are invisible to the
provider. This is the more expensive solution.
 Implement shaping on the WAN interfaces to shape the bursts down to conform to the
policer policy of the service provider.
— Shaping introduces jitter into the video stream. Before Cisco TelePresence System
Release 1.5, this was not recommended because the jitter buffer was too tight.
— Cisco TelePresence System Release 1.5 introduces a dynamic jitter buffer, allowing
the jitter buffer to grow up to 165 ms, meaning that shaping is now a very viable
option in Cisco TelePresence System Release 1.5 and above, and is the new
recommended method for dealing with bursts.

Modifying Policer Configuration
 Obtain burst parameter using the following formula:
– Tc = Bc/R
 Where:
– Tc = Time (1000th of second)
– R = Rate (bytes per second)
– Bc = Burst (bytes)
 Example burst calculations for post 1.2 firmware assuming 20-ms Tc:
– Cisco TelePresence System 1000 running 1080p-Best
 R=5.7 Mb/s, Tc = 20 ms, Bc = 14,250 B
– Cisco TelePresence System 3000 running at 1080p-Best
 R = 15.3 Mb/s, Tc = 20 ms, Bc = 38,250 B
– Cisco TelePresence Multipoint Switch maximum loading at 1080p
Best
 R = 264 Mb/s, Tc = 200 ms, Bc = 6,850,000 B
 Maximum load = 48 TelePresence System 1000 rooms at 1080p
The following is a long-hand explanation of the Bc formula:

 Bc = R (in Mb/s) * 1000 (converts Mb/s to kb/s) * 1000 (converts kb/s to b/s) / 8 (converts
b/s to bytes/sec) x Tc (in milliseconds)
— Bc = [15.3 * 1000 *1000 / 8] * 0.02 = 1,912,500 * 0.02 = 38,250 B
To reverse the math (where Tc is automatically calculated given R and Bc), use the following
formula:
 Tc = Bc / R
— Tc = 38250 / [15.3 / 1000 / 1000 / 8] = 38,250 / 1,912,500 = 0.02 sec = 20 ms
Obtain the burst parameter using the following formula:
 Bc = R(Tc)
— R = Rate (bytes ⁄seconds)
— Tc = Time in seconds (It is recommended that you use 20 ms for Tc.)
— Bc = Burst (bytes)
Note Bc = R (in Mb/s) * 1000 (converts Mb/s to kb/s) * 1000 (converts kb/s to b/s) / 8 (converts b/s
to bytes/sec) * T (in milliseconds)
Example Burst Calculations

 Cisco TelePresence System 1000 running at 1080p-Best
— R = 5.7 Mb/s, Tc = 20 ms, Bc = 14,250 B
 Cisco TelePresence System 3000 running at 1080p-Best
— R = 15.3 Mb/s, Tc = 20 ms, Bc = 38,250 B
 Cisco TelePresence Multipoint Switch maximum load running at 1080p-Best
— R = 264 Mb/s, T = 200 ms, Bc = 6,850,000 Maximum load is 48 Cisco TelePresence
System 1000 rooms at 1080p
Note A circuit with multipoint (multiple point-to-point calls) requires a larger Tc to accommodate
burst. Alternatively, you can accommodate burst by increasing burst (Bc) or by implementing
a shaper on the customer edge to smooth burst.

Policer Configurations
router(config-pmap-c)#
police bps [burst-max] conform-action action exceed-action action
 Single-rate policer
 Use the bit-per-second rate and increase the burst-max parameter to
accommodate the subsecond bursts
Example for a 20-ms Tc:
police 15300000 38250 conform-action transmit exceed-action drop
router(config-pmap-c)#
priority {bandwidth-kbps | percent percentage} [burst]
 Configures LLQ
Example for a 20-ms Tc:

priority 15300 38250
To configure policing and shaping on a Cisco IOS device, use the following commands:
 Single-rate policer
police b/s [burst-max] conform-action action exceed-action action
Example: police 15300000 38250 conform-action transmit exceed-action drop
 Shaper
shape [average | peak] mean-rate [burst-size] [excess-burst-size]
Example: shape average 15300000 1520000
Note This command expresses burst-size in bits, not bytes.
 LLQ
priority {bandwidth-kb/s | percent percentage} [burst]
Example: priority 15300 38250
Summary
Summary
 Cisco provides recommendations for provisioning a network with
Cisco TelePresence.
 Bursty traffic can cause problems for Cisco TelePresence, which
requires a high degree of predictability from a network.
 Traffic policing and shaping are mechanisms you can use in a
network to control the traffic rate.
 Cisco TelePresence has specific requirements for service level,
bandwidth, and packet size.
 Options to provision for bursts in the network include queuing,
policing, and shaping.

Lesson 3
Setting a QoS Policy

Overview
To run an infrastructure that supports Cisco TelePresence, it is necessary to implement an
appropriate quality of service (QoS) policy. It is fundamental to manage network delays,
bandwidth requirements, and packet loss parameters, while maintaining simplicity, scalability,
and manageability is fundamental to creating a proper QoS policy.
Objectives
Upon completing this lesson, you will be able to describe how to establish a QoS policy. This
 Explain the effect that latency, jitter, and loss have on Cisco TelePresence
 Describe the various IP packet classification and marking methods
 Describe the Cisco Catalyst queuing model for telepresence traffic
 Provide an overview of campus QoS policies
Latency, Jitter, and Loss
This topic describes the effect that latency, jitter, and loss have on Cisco TelePresence.
Latency, Jitter, and Loss

 From PE-PE, the primary concern is latency (caused by distance) and packet loss
(caused by policing).
 On the CE-PE links, the primary concern is jitter caused by queuing, serialization,
and shaping.
 In the campus, the primary concern is packet loss.
Humans perceive round-trip latency at 250–350 ms.
Service
CE PE Provider PE CE
Codec Campus CE-PE PE-PE PE-CE Codec
Encodi ng, Serialization, Seri alization, De-Ji tter Buffer,

Queuing, Shaping Queuing, Policing, Queuing, Queui ng,
Packeti zati on Propagation Decoding
Shaping Shaping
At the human experience level, latency is defined and measured as the time that it takes for the
speech or gestures of one individual (the speaker) to reach the ears and eyes of another (the
listener) and for the audible or visual reaction of that listener to come all the way back to the
speaker. Hence, the human experience is round trip in nature, which is referred to as
“conversational latency” or “experience-level latency.” It takes between 250 and 350 ms for the
human mind to begin to perceive this round-trip latency and be annoyed by it.
The control of network latency, jitter, and packet loss is a vital ingredient in delivering
maximum performance for Cisco TelePresence, which requires consistent delivery of
controlled latency with low jitter and packet loss in the network.
 Latency: From provider edge (PE) to PE, the primary concern is latency (caused by
distance) and packet loss (caused by policing). Latency is a complex phenomenon because
it has many sources at different layers in the information systems stack: propagation delay,
queuing delay, middleware delay, and application delay.
 Jitter: On the customer edge (CE) to PE links, the primary concern is jitter caused by
queuing, serialization, and shaping introduced on link speeds less than 30 Mb/s.
 Packet Loss: In the campus, the primary concern is packet loss. Packet loss is caused by
queuing. During periods of congestion, QoS configuration can drop packets that exceed the
subscribed rate of the queue. Packet loss is also caused by policing, when the network
drops packets that exceed the allocated rate.
Note Cisco TelePresence Extended Reach runs at 720p resolution over lower bandwidth
connections available in two modes. The two modes are T1/E1 networks with QoS, or high-
bandwidth premium broadband connections, such as Verizon Fiber Optic Service (FiOS) or
Data-over-Cable Service Interface Specifications (DOCSIS).
Latency, Jitter, and Loss Measurement
 Latency, jitter, and loss are measured:
– End-to-end (codec Ethernet port-to-codec Ethernet port)
– Unidirectionally (each codec measures incoming RTP traffic)
 Latency and loss are measured at a packet level, based on RTP
header sequence numbers and timestamps.
 Jitter is measured at a video frame level, not a packet level.
 In order to understand jitter, you must first understand the
difference between packets and video frames.
Latency 95 ms Latency 90 ms
Jitter 6 ms Ji tter 9 ms
Loss .04% Loss .01%
With the emergence of new applications on data networks, it is becoming increasingly

important for customers to accurately predict the impact of new application introductions. Not
long ago, it was easy to allocate bandwidth to applications and let the applications adapt to the
exploding nature of traffic flows through the timeout and retransmission functions of the upper-
layer protocols. However, Cisco TelePresence is more susceptible to changes in the
transmission characteristics of data networks. It is imperative to understand the traffic
characteristics of the network before deploying Cisco TelePresence to ensure a successful
implementation.
Latency, jitter, and loss are measured end-to-end in the network from the source coder-decoder
(codec) Ethernet port to the destination codec Ethernet port. Unidirectionally, each codec
independently measures incoming Real-Time Transport Protocol (RTP) traffic. The one-way
latency and loss are measured at a packet level, based on RTP header sequence numbers and
time stamps. Jitter, however, is different because it is measured at a video frame level, not a
packet level. Understanding where the bottleneck occurs is necessary to effectively tune any
system.
Note To understand jitter in a Cisco TelePresence world, you must first understand the difference
between packets and video frames.

Video Frame vs. Jitter
33 ms 33 ms 33 ms 33 ms
Jitter Buffer
Frame
#5 Frame #3 Frame
Frame Frame # 1
#4 #2
Transport Layer
Network Layer
Variation in serialization Variation in serialization delay between
delay between frames packets (0 ms because our packets are
(41 ms in this example) 2 ms 43 ms
all the same size)
In the figure, the camera on the left is sending to a display on the right. The camera is operating
at 30 Hz (30 frames per second [f/s] or 1 frame every 33 ms). The codec takes the video that is
sent from the camera and encodes the video into H.264 compressed data. Every 33 ms a video
frame is produced. The video frame becomes the payload that is wrapped in RTP packets. Each
video frame can be as large as 65,000 B (65 KB) and as small as 1,000 B (1 KB). The size
depends on the number of pixels that must be transmitted in that frame interval. 720p is the
same as 1080p, except that the average frame size is much smaller.
With an average packet size of 1100 B, the codec must break this payload into approximately
60 packets. The packets are then transported across the network. Because they are
predominantly of equal size (1100 B each), there is typically very little packet jitter (assuming
that QoS is configured properly). However, the total size of the frame, and hence the number of
packets that are needed to transport that frame, is highly variable.
The routers and switches along the path must serialize all of the bytes of each frame onto the
wire for transmission. How long this serialization takes varies for large frames as compared to
small frames. For example:
 An Optical Carrier 3 (OC-3) circuit can serialize a 65-KB video frame in about 2 ms.
 A T1 circuit would take about 336 ms to serialize this same frame.
 An 8xT1 Multilink PPP (MLP) bundle would require about 42 ms.
 A 10-Mb/s Ethernet circuit would take about 52 ms; however, the small video frames
would go through much faster.
The variation in serialization delay between large frames and small frames equals jitter at a
video frame level, even though there is 0 ms jitter at a packet level. To keep video frame jitter
below 20 ms, the best practice requires the link speed to be greater than 30 Mb/s.
On the receiving codec, a jitter buffer is capable of managing about 75 ms of jitter.
The second threshold is set at 40 ms because, first, 33 ms is removed for the frame interval
itself, so that leaves roughly 42 ms of buffer remaining to accommodate jitter. You generally
will not see any negative manifestations of jitter in the actual video until you start to exceed 40
ms. As you begin to exceed 40 ms, the jitter buffer cannot wait anymore and it moves on to the
next frame. Even if the system ultimately receives all of the packets of a frame, the packets that
came too late are discarded and marked as “late” packets. Therefore, packet loss can also be a
function of excessive jitter that results in late packets. A late packet is just as detrimental as a
lost packet. You can have zero packet loss on the network, but if you have frame jitter that
exceeds 40 ms, you will experience the same negative effect.
The receiving codec measures the interarrival time of each frame to calculate the jitter.
Therefore, the jitter statistics that are calculated by the codec are really a combination of both
packet jitter and frame jitter, because packet jitter also manifests itself as frame jitter. You can
have 0-ms packet jitter but still have large amounts of frame jitter if the clock rate of any
interface in the path is less than 30 Mb/s, because not all video frames are 65 KB. Some are
much smaller (< 1 KB) if there is no motion in the video for that 33-ms interval.
The time that it takes to serialize all of the packets of a 65-KB frame compared to all of the
packets of a 1-KB frame is significant on link speeds less than 30 Mb/s. For link speeds greater
than 30 Mb/s, the difference is small enough to stay below the 20-ms threshold. But as the link
speed goes down, the frame jitter goes up. The following are a couple of relevant examples:
 A 10-Mb/s Ethernet circuit exhibits frame jitter greater than 20 ms.
 An 8xT1 MLP bundle exhibits frame jitter greater than 40 ms because the clock rate of
each T1 circuit member of the bundle is only 1.544 Mb/s, even though the aggregate
bandwidth of the bundle is 12.4 Mb/s. Therefore, the variation in serialization delay
between 65-KB frames and 1-KB frames is dramatic.
Shaping also introduces frame jitter because it has to buffer the packets that constitute a frame
and transmit them in a smoother pattern. Therefore, the worst case scenario is a 10-Mb/s Metro
Ethernet circuit on which the provider polices using a low committed burst size (Bc)/
committed rate measurement interval (Tc) value. The service provider performs this policing
because it is a shared service, and the service provider is unwilling to increase the burst values
in their policers. This configuration will force you to shape. This results in the combination of
jitter that is caused by shaping, and jitter that is caused by variation in the serialization delay of
large frames, resulting in extremely high frame jitter as measured by the receiving codec.

One Way Latency
Targets and Thresholds
 There is an 80/20 split between the service provider and the enterprise.
– The service provider is from demarc to demarc, including the CE-PE link.
– 20% is allocated to the enterprise.
– These splits are just guidelines.
 The service provider should engineer its network to the target, but the SLAs may
be much higher due to legal ramifications.
 Threshold behavior:
– Threshold #1—Sysop/SNMP alarm and on-screen message
– Threshold #2—As of Cisco TelePresence System Release 1.5, no action is
taken.
 Satellite mode adjusts threshold 1 to two seconds and displays a message.
 Endpoints measure only latency to the Cisco TelePresence Multipoint Switch.
Threshold Threshold Threshold #1 Threshold #2

Metric Target
#1 #2 Action Action
Sysop/SNMP Alarm,
Latency 150 ms 250 ms None No action
On-Screen Message
When you design a network that transports voice over packet, frame, or cell infrastructures, it is
important to understand and account for the predictable delay components in the network. You
must also correctly account for all potential delays to ensure that the overall network
performance is acceptable. Overall voice quality is a function of many factors, including the
compression algorithm, errors and frame loss, echo cancellation, and delay. There are two
distinct types of delay:
 Fixed delay: Fixed-delay components are predictable and add directly to the overall delay
on the connection. The following are fixed-delay components:
— Coding: The time that it takes to translate the audio signal into a digital signal
— Serialization: The insertion of bits onto a link
— Propagation: The time that it takes a packet to traverse a link
 Variable delay: Variable delay arises from queuing delays in the egress trunk buffers that
are located on the serial port that is connected to the WAN. These buffers create variable
delays, called jitter, across the network.
Latency in Cisco TelePresence is defined and measured as the time that it takes for an audio or
video packet containing speech or motion to travel from the Ethernet network interface of the
Cisco TelePresence system of the speaker to the Ethernet network interface of the Cisco
TelePresence system of the listener, in one direction. The listener Cisco TelePresence system
processes the incoming packets and computes a running average of the latency, based on time
stamps within the RTP packets. Therefore, latency is measured only at the network level from
one Cisco TelePresence system to another, not at the “experience level.” It is measured
unidirectionally by each Cisco TelePresence system; it is not measured round trip, and does not
take into account the processing time (encoding and decoding) of the packets.
Latency Target
In order to maintain acceptable experience-level latency, it is recommended that customers
engineer their networks with a target of 150 ms or less of network-level latency between any
two Cisco TelePresence systems, in each direction. Given the circumference of the earth, the
speed of light, and the cabling paths that light travels on between cities, it is not always possible
to achieve 150 ms between any two points on the globe.
Latency Threshold No. 1

When network-level latency exceeds 250 ms, averaged over any 10-second period, the Cisco
TelePresence system receiving those packets generates an alarm and displays an on-screen
message to the user. The alarm is written to the sysop log file of that Cisco TelePresence
system, and a Simple Network Management Protocol (SNMP) system generates a trap
message. The on-screen message displays for 15 seconds, after which it is removed. The system
does not display the on-screen message again for the duration of the meeting, unless the media
is interrupted or restarted. The media can be interrupted or restarted when the user places the
meeting on hold and then resumes it (using the Hold/Resume softkeys), or the user terminates
the meeting and then re-establishes it (using the End Call/Redial softkeys).
Latency Threshold No. 2

In previous releases, when latency exceeded 400 ms averaged over any 10-second period, the
Cisco TelePresence system receiving those packets would generate a second alarm and on-
screen message. Cisco TelePresence Release System 1.5 removes this threshold entirely.
Satellite Mode—Latency Thresholds

Cisco TelePresence System Release 1.5 implements support for satellite networks. This feature
requires a software license to activate. When the feature is activated, whenever a satellite
endpoint joins a meeting, all other Cisco TelePresence systems in that meeting adjust their
latency threshold No. 1 from 250 ms to 2 seconds and display a satellite mode message and
icon on the display for 15 seconds. This change in latency threshold No. 1 persists for the
duration of the meeting, even if the original satellite endpoint drops off.
Understanding Latency Measurements in Multipoint Meetings

As audio and video packets traverse a Cisco TelePresence Multipoint Switch, the RTP header
that contains the original time-stamp information is overwritten and the Cisco TelePresence
Multipoint Switch applies a new time-stamp value. Therefore, the latency that is measured by
each participating Cisco TelePresence system is only a measurement of the latency from the
Cisco TelePresence Multipoint Switch to that endpoint. It is possible for the end-to-end latency
from one Cisco TelePresence system, through the Cisco TelePresence Multipoint Switch to
another Cisco TelePresence system, to exceed the 250-ms latency threshold. However, the
Cisco TelePresence system will not realize it.
For example, assume the following latencies:
 The latency from a Cisco TelePresence system in Hong Kong to the Cisco TelePresence
Multipoint Switch in London is 125 ms.
 The latency from the Cisco TelePresence Multipoint Switch in London to the other
TelePresence system in San Francisco is 125 ms.

The end-to-end latency from the Ethernet network interface of the Hong Kong system to the
Ethernet network interface of the San Francisco system would be 250 ms, plus approximately
10 ms added by the Cisco TelePresence Multipoint Switch. These values result in a total of 260
ms latency. The Cisco TelePresence system in San Francisco does not realize this and thinks
that the latency for that meeting is only 125 ms.
Therefore, be careful when designing the network and the location of the Cisco TelePresence
Multipoint Switch in order to reduce the probability of this situation occurring. The Cisco
TelePresence Multipoint Switch is the only device in the network that is aware of the end-to-
end latency between any two Cisco TelePresence systems in a multipoint meeting. Network
administrators can view the end-to-end statistics (the sum of any two legs in that meeting) via
the Cisco TelePresence Multipoint Switch Administration interface.
One Way Jitter
 There is a 50/50 split between the service provider and the enterprise.
– The 50% allocated to the service provider is from demarc to demarc, including
the CE-PE link.
– Threshold #1—Sysop/SNMP alarm
– Threshold #2—Packets are discarded.
 Satellite mode forces all system jitter buffers to 165 ms and displays a message.
Threshold Threshold Threshold #1 Threshold #2

Metric Target
#1 #2 Action Ac tion
50 ms of video 125 ms of 165 ms of

Sysop/SNMP Packets are
Jitter frame jitter (10 ms video frame video frame
Alarm dis carded
of packet jitter) jitter jitter
Jitter is defined as a variation in the delay of received packets. On the sending side, packets are
sent in a continuous stream with the packets spaced evenly. Because of network congestion,
improper queuing, or configuration errors, this steady stream can become uneven because the
delay between each packet varies instead of remaining constant, as displayed in the figure.
When a router receives an audio stream for VoIP or IP video, it must compensate for the jitter
that is encountered. The mechanism that manages this function is the playout delay buffer or
dejitter buffer. The playout delay buffer buffers these packets and then plays them out in a
steady stream to the digital signal processors (DSPs), which converts them back to an analog
audio stream. The playout delay buffer, however, affects the overall absolute delay.
Cisco TelePresence systems implement jitter buffers to manage variations in video frame
arrival times. Upon receipt at the destination, the packets are buffered until an adequate portion
of the video frame has arrived, and then the packets are removed from the buffer and decoded.
The size (depth) of the jitter buffer dictates how much jitter can be managed before it begins to
be noticeable to the user. The receiving codec drops packets that exceed the jitter buffer
because they arrived too late to be decoded. The depth of the jitter buffer has an important
consequence to the round-trip, experience-level latency; every millisecond spent waiting in the
jitter buffer increases the end-to-end latency between the participants. Therefore, jitter buffers
must be kept as small as reasonably possible to accommodate network-level jitter without
adding an unacceptable amount of experience-level latency.
Jitter Target
In order to maintain acceptable experience-level latency, it is recommended that customers
engineer their networks with a target of 50 ms or less of video frame jitter, in each direction,
between any two Cisco TelePresence systems. Given the following situations, it is not always
possible to accomplish video frame-level jitter that is 50 ms or less:
 The desire to deploy telepresence over the smallest, and hence least expensive amount of
bandwidth possible
 The need in some circumstances to implement shaping within the routers along the path to
conform to service provider contractual rates and policing enforcements

Therefore, Cisco TelePresence System Release 1.5 implements the following thresholds and
jitter buffer behavior to alert the network administrator when video frame-level jitter exceeds
acceptable levels.
 Jitter Threshold No. 1: Cisco TelePresence System Release 1.5 introduces an adaptive
jitter buffer. At the beginning of every new meeting, the jitter buffer starts at a depth of 85
ms. If at any time during the meeting the incoming jitter exceeds 85 ms, the system
dynamically adjusts the jitter buffer up to 125 ms. If at any time during the meeting the
jitter exceeds 125 ms, the system dynamically adjusts the jitter buffer up to 165 ms. Every
time the system adjusts the jitter buffer, an alarm is written to the sysop log file of the
Cisco TelePresence system that is receiving the packet. From the Cisco TelePresence
system web interface, choose Log Files to view system operation (sysop) log files. If
configured, an SNMP trap message is also generated and sent to a network management
station (NMS). No on-screen message is displayed to the user.
 Jitter Threshold No. 2: The receiving Cisco TelePresence system discards any packets
that exceed the 165-ms jitter buffer depth and logs these packets as “late packets” in the
call statistics. This threshold does not trigger any alarms or on-screen messages. However,
late packets are just as bad as lost packets because they cause a noticeable effect on the
video quality. Therefore, take care to design the network so that the video frame jitter never
exceeds 165 ms.
Satellite Mode—Jitter Thresholds

Cisco TelePresence System Release 1.5 implements support for satellite networks. Activating
this feature requires a software license. When activated, the jitter buffer behavior that was
described previously is effectively reversed. Whenever a satellite endpoint joins a meeting, all
other Cisco TelePresence systems in that meeting reset their jitter buffers to 165 ms. The
systems also display a satellite mode message and an icon on the display for 15 seconds. A
message indicating that the system has entered satellite mode is also written to the sysop log
file of each system. If the incoming jitter is low after monitoring the arrival jitter of video
frames for the first few seconds of the meeting, the receiving codec dynamically adjusts its
jitter buffer down to 125 ms and then to 85 ms. This change in the jitter thresholds persists for
the duration of the meeting, even if the original satellite endpoint drops off.
One Way Loss
 There is a 50/50 split between the service provider and the enterprise.
– The 50% allocated to the service provider is from demarc to demarc, including
the CE-PE link.
– Threshold # 1—Sysop/SNMP alarm, on-screen message
– Threshold # 2—Sysop/SNMP alarm, on-screen message, quality (motion) is
reduced
 Satellite mode does not change the loss thresholds.
Threshold Threshold Thres hold #1 Threshold #2

Metric Target
#1 #2 Action Action
Sysop/SNMP Alarm,
Sysop/SNMP Alarm,
Loss 0.05% 1% 10% On-Screen Message,
On-Screen Message
Quality (motion) is reduced
VoIP has been traditionally viewed as one of the most loss-sensitive applications on converged
networks, tolerating the loss of only a single packet in a row (or 1 percent). However, Cisco
TelePresence is even more sensitive to loss than VoIP because of multiple factors:
 The high quality of the video images being transmitted (up to 1080p, full high-definition
TV [HDTV])
 The significant compression of the video stream
 The (potential) multiplexing of multiple primary and auxiliary video and audio
Given these factors, the initial loss target for Cisco TelePresence is set in-line with the ITU-T
G.1050 specification of 0.05 percent loss.
Loss is defined as packets that did not arrive (dropped somewhere along the network path).
Each Cisco TelePresence system measures loss by comparing the sequence numbers of the RTP
packets that it receives to the sequence numbers that it expected to receive. Packet loss can
occur anywhere along the path for various reasons. The following are the three most common
reasons:
 Layer 1 errors on the physical interfaces and cables along the path, such as a
malfunctioning optical interface
 Misconfigured network interfaces along the path, such as Ethernet speed or duplex
mismatches between two devices
 Bursts of packets exceeding the buffer (queue) limit or policer configurations on network
interfaces along the path, such as:
— Ethernet switches with insufficient queue depth
— Oversubscribed backplane architectures
— WAN router interfaces that police traffic to conform to the contractual rates of a
service provider

A closely related metric to loss is “late packets.” Late packets are packets that arrived, but
exceeded the jitter buffer (arrived too late to be decoded) and were therefore discarded
(dropped) by the receiving Cisco TelePresence system. Cisco TelePresence systems track lost
packets and late packets independently, but they both result in the same outcome: noticeable
pixelization of the video.
Loss is by far the most stringent of the three metrics that are discussed in this lesson (loss,
latency, and jitter). Latency can be annoying to the users, but their meeting can still proceed.
Jitter is invisible to the users, but loss (including packets that arrived but exceeded the 165 ms
jitter buffer and manifest into late packets) is immediately apparent to users.
Cisco TelePresence System Release 1.5 implements a new technique that is known as Long-
Term Reference Frames. This technique allows the system to recover from packet loss
significantly faster. It can accomplish this faster recovery by retransmitting the differences in
the current frame relative to the original reference frame, as opposed to transmitting an entirely
new reference frame. Long-Term Reference Frames are only implemented for point-to-point
meetings between two Cisco TelePresence systems. Currently, Cisco TelePresence Multipoint
Switches do not implement this feature.
Loss Target
In order to maintain acceptable experience-level video quality, it is recommended that
customers engineer their networks with a target of 0.05 percent or less of packet loss, in each
direction, between any two Cisco TelePresence systems. This packet loss is an incredibly small
amount and, given the complexity of global networks today, 0.05 percent loss is not always
possible to accomplish. Therefore, Cisco TelePresence System Release 1.5 implements the
following thresholds to alert the network administrator when packet loss (or late packets)
exceeds acceptable levels.
 Loss Threshold No. 1: When packet loss (or late packets) exceeds 1 percent averaged over
any 10-second period, the Cisco TelePresence system that receives those packets generates
an alarm and displays an on-screen message. The alarm is written to the sysop log file of
that Cisco TelePresence system, and an SNMP trap message is generated. The on-screen
message is displayed for 15 seconds, after which it is removed, and a 5-minute hold timer is
started. During the 5-minute hold timer, sysop and SNMP alarms continue to be generated,
but no on-screen message is displayed.
 Loss Threshold No. 2: When packet loss (or late packets) exceeds 10 percent averaged
over any 10-second period, the Cisco TelePresence system that receives those packets
generates a second alarm and displays a second on-screen message (unless the hold timer is
already in effect). The alarm is written to the sysop log file of that Cisco TelePresence
system, and an SNMP trap message is generated. The on-screen message is displayed for
15 seconds, after which it is removed, and a 5-minute hold timer is started (if it was not
already started by loss threshold No. 1). During the 5-minute hold timer, sysop and SNMP
alarms continue to be generated, but no on-screen message is displayed.
If loss (or late packets) exceeds 10 percent averaged over any 60-second period, then in
addition to the previous actions, the system downgrades the quality of its outgoing video. When
the video is downgraded, an alarm is generated and an on-screen icon and message are
displayed indicating that the quality has been reduced. The quality is downgraded by reducing
the motion handling (such as applying a higher compression factor to the motion). The
resolution is not affected. For example, if the meeting is running at 1080p-Best, it will
downgrade to 1080-Good. If the meeting is running at 720p-Best, it will downgrade to 720p-
Good.
Satellite Mode—Loss Thresholds
Cisco TelePresence System Release 1.5 implements support for satellite networks. You must
have a software license to activate this feature. The loss thresholds for satellite mode are the
same as for nonsatellite mode.

Latency, Jitter, and Loss Summary
 Cisco TelePresence puts stringent requirements on latency, jitter, and packet loss.
 All network topologies have points where congestion builds and data can be lost.
 All parts of your network infrastructure must collaborate to support QoS policies.
 Cisco TelePresence System Release 1.5 introduces several enhancements in the
ability of systems to accommodate a greater breadth of network topologies.
Service
CE PE Provider PE CE
Campus Branch
Codec Campus CE-PE PE-PE PE-CE Codec

Serialization, Policing, Serialization,
Encoding, Queuing, Shaping Queuing, Queuing, Queuing, De-Jitter Buffer,
Packetization Shaping Propagation Shaping Decoding
SLAs Only Relate to Network Flight Time

Codec Codec
Cisco TelePresence puts stringent requirements on latency, jitter, and packet loss. All parts of
your network infrastructure must collaborate to support intelligent QoS policies that are
compatible across your LAN and WAN. All network topologies have points where congestion
builds and data can be lost.
Cisco TelePresence System Release 1.5 introduces several significant enhancements in the
ability of the systems to accommodate a greater breadth of network topologies:
 New technologies, such as Long-Term Reference Frames and a quasi-adaptive jitter buffer,
were implemented.
 Additional SNMP traps were introduced.
 The threshold behaviors were modified to reduce the possibility of unnecessary on-screen
warning messages annoying the user.
For satellite mode, when any satellite-enabled endpoint is in a point-to-point or multipoint call,
all endpoints participating in that call switch to satellite mode and adopt the satellite mode
latency, jitter, and loss threshold characteristics. These characteristics persist for the duration of
the meeting, resetting back to defaults when the meeting is ended (hung up), even if the satellite
endpoint drops off the multipoint call.
Latency Threshold Changes in Cisco TelePresence System

Release 1.5
 Latency threshold No. 1 was increased from 200 to 250 ms. This range provides the
“breathing room” customers need to deploy Cisco TelePresence between certain points on
the globe without triggering a warning message.
 The on-screen message for latency threshold No. 1 is now displayed for 15 seconds,
compared to 5 seconds in previous releases. This increase in time provides the users
enough time to read the message before it disappears.
 Latency threshold No. 2 was completely removed.
 Satellite mode was introduced.
 SNMP traps were enhanced to include in-meeting network statistics alarms.
 Cisco TelePresence Multipoint Switch Administration now provides real-time statistics to
allow administrators to view the end-to-end latency statistics for multipoint meetings.
Jitter Threshold Changes in Cisco TelePresence System

Release 1.5
 A quasi-adaptive jitter buffer was implemented, ranging from 85 to 165 ms in depth.
 The jitter target was changed from 10 to 50 ms.
 Jitter threshold No. 1 was increased from 20 to 125 ms.
 Jitter threshold No. 2 was increased from 40 to 165 ms.
 The combination of these four changes allows the Cisco TelePresence systems to be more
accommodating of network-based shapers. This behavior introduces frame-level jitter by
virtue of their buffering and shaping algorithms and slower speed circuits (such as 10 Mb/s
or less), which introduce frame-level jitter by virtue of their slow serialization rate (clock
rate).
 On-screen messages are no longer displayed for jitter thresholds No. 1 or No. 2. Sysop and
SNMP trap alarms are generated only for jitter threshold No. 1.
Packet Loss Changes in Cisco TelePresence System

Release 1.5
 The loss target remains unchanged at 0.05 percent.
 Loss threshold No. 1 was increased from 0.1 percent to 1 percent.
 Loss threshold No. 2 was increased from 0.2 percent to 10 percent.
 Long-Term Reference Frames were implemented for point-to-point meetings.

IP Packet Classification and Marking
This topic describes IP packet classification and marking that you use to prioritize Cisco
TelePresence traffic.
IP Packet Classification and Marking

 IPv4—Three most significant bits of ToS byte are called IP
precedence; other bits unused
 DiffServ—Six most significant bits of ToS byte are called DiffServ
Code Point (DSCP)—remaining two bits used for flow control
 DSCP is backward-compatible with IP precedence
Version ToS
Len ID Offset TTL Proto FCS IP SA IP DA Data
Length Byte
IPv4 Packet
7 6 5 4 3 2 1 0
Standard IPv4
IP Precedence Unused
DSCP Flow Ctl DiffServ with Extensions
At the network layer, IP packets are typically classified based on source or destination IP
address, packet length, or the contents of the type of service (ToS) byte. Data link-layer media
often changes as a packet travels from its source to its destination. Because a class of service
(CoS) field does not exist in a standard Ethernet frame, CoS markings at the data link layer that
are not preserved as packets traverse the network. Using marking at the network layer provides
a more permanent marker that is preserved from source to destination. The network layer
markers most typically used are IP precedence and differentiated services code point (DSCP).
The header of an IPv4 packet contains the ToS byte. IP precedence uses three precedence bits
in the ToS field of the IPv4 header to specify CoS for each packet. IP precedence values range
from 0 to 7 and allow network administrators to partition traffic in up to six useable classes of
service. (Settings 6 and 7 are reserved for internal network use.)
Differentiated Services (DiffServ) is a new model that supersedes—and is backward
compatible with—IP precedence. DiffServ redefines the ToS byte and uses six prioritization
bits that permit classification of up to 64 values (0 to 63), of which 32 are commonly used. A
DiffServ value is called a DSCP.
With DiffServ, packet classification partitions network traffic into multiple priority levels or
classes of service. Packet classification uses the DSCP traffic descriptor to categorize a packet
within a specific group to define that packet. After the packet has been defined (classified), the
packet is then accessible for QoS handling on the network.
Video Conferencing vs.
Cisco TelePresence
 Video-conferencing vendors reduce (Generic)
frame rate to compensate for motion. Service Level
Video
Cisco
Cisco TelePresence keeps frame rate Parameter
Conferencing
TelePresence
at 30 f/s regardless of motion.
384 kb/s or 768
 Video-conferencing vendors care little Bandwidth 2–12.5 Mb/s
kb/s
about latency. Cisco TelePresence
considers latency a critical element of Variable Fixed
the user experience. Frame Rate
10–30 f/s 30 f/s
 Video-conferencing vendors
implement huge jitter buffers, which
introduce latency. Cisco Latency 400–450 ms 150–250 ms
TelePresence tries to keep jitter
buffers as low as possible to keep
latency to a minimum. Jitter
30–50 ms 50 ms
Peak-to-Peak Peak-to-Peak
 Cisco TelePresence has a much
higher compression ratio, keeping 1% 0.05%
loss to an absolute minimum. Loss Random Packet Random
Loss Packet loss
Video-conferencing vendors have always taken the approach of sacrificing quality in order to
sell their product to more types of networks. This strategy has caused the vendors to do things
such as make their frame rate variable, accept much higher latency, and implement huge jitter
buffers. Cisco strives not to do that. Cisco TelePresence maintains 30 f/s and keeps latency and
jitter buffers to an absolute minimum. These characteristics mean that the network demands for
Cisco TelePresence are much stricter than demands traditionally followed for video
conferencing.
The high quality of the Cisco TelePresence experience is a distinguishing characteristic.
To avoid blurred or discontinuous pixels in the middle of someone's eye and enable real-life
imaging, the application imposes new requirements on your network. For example, while
most IP applications have one-way latency targets of 400 to 450 ms, Cisco TelePresence
recommends one-way latency end to end of 150 ms or less for best performance. In addition,
jitter for Cisco TelePresence should not exceed 50 ms, and the target for packet loss is 0.05
percent.
The following table displays a Service Level Agreement (SLA) comparison of video
conferencing versus Cisco TelePresence:
Video Conferencing vs. Cisco TelePresence
Service-Level Parameter (Generic) Video Conferencing Cisco TelePresence
384 or 768 kb/s 2.5–12.5 Mb/s

Bandwidth
+ network overhead + network overhead
Variable Fixed
Frame Rate
10–30 f/s 30 f/s
Latency 400–450 ms 150–250 ms
Jitter 30–50 ms peak-to-peak 50 ms peak-to-peak
Loss 1% random packet loss 0.05% random packet loss

Key QoS Recommendations
Best practice guidelines for the network:
 Classify and mark traffic as close to the source as
possible.
 Allow trusted hosts to mark their own traffic.
 Use DSCP whenever possible (more granularity than
IP precedence).
 Follow standards-based DSCP PHBs as specified in
RFC 4594, Configuration Guidelines for DiffServ
Classes.
 Limit the amount of real-time voice and video traffic
to 33% of link capacity.
 Reserve at least 25% of link bandwidth for the
default Best Effort data class.
 Use a 1% scavenger class to ensure unruly
applications do not dominate the default Best Effort
data class.
 Use WRED on all TCP flows, wherever possible,
preferably DSCP-based WRED.
 Refer to the latest SRND guide.
It is recommended that you follow QoS best-practice guidelines for the entire network, not just
for telepresence traffic. You should classify and mark traffic using DSCP because it has more
granularity than IP precedence, and it should be done as close to the source as technically and
administratively feasible. Allow the trusted hosts to mark their own traffic. Follow standards-
based DSCP per-hop behaviors (PHBs) to help ensure interoperation and future expansion as
specified in RFC 4594, Configuration Guidelines for DiffServ Service Classes.
On converged networks, you should limit the amount of real-time voice and video traffic to 33
percent of the link capacity. Otherwise, data will be starved, resulting in very slow and erratic
performance of data applications. Reserve at least 25 percent of the link bandwidth for the
default Best Effort data class. Use a 1-percent Scavenger class to ensure that unruly
applications do not dominate your default Best Effort data class. Also, use weighted random
early detection (WRED) on all TCP flows, wherever possible, preferably DSCP-based. For
current QoS recommendations, refer to the latest Solution Reference Network Design (SRND)
guide.
RFC 4594—12-Class Model
L3 Classification IETF
Application
PHB DSCP RFC
Network Control CS6 48 RFC 2474
VoIP Telephony EF 46 RFC 3246
Broadcast Video CS5 40 RFC 2474
Multimedia Conferencing AF41 34 RFC 2597
Real-Time Interactive/Telepresence CS4 32 RFC 2474
Multimedia Streaming AF31 26 RFC 2597

Call Signaling CS3 24 RFC 2474
Low-Latency/Transactional Data AF21 18 RFC 2597
Operations/Administration/Management CS2 16 RFC 2474
High-Throughput/Bulk Data AF11 10 RFC 2597
Best Effort DF 0 RFC 2474
Low-Priority/Scavenger Data CS1 8 RFC 3662
Cisco uses a separate marking scheme to classify telepresence traffic in order to distinguish it
from other forms of real-time traffic.
Call-signaling traffic was originally marked by Cisco IP Telephony equipment to DSCP AF31.
However, the AF classes, as defined in RFC 2597, were intended for flows that could be
subject to markdown, and then the aggressive dropping of marked-down values. Marking down
and aggressively dropping call signaling could result in noticeable delay-to-dial-tone (DTT)
and lengthy call setup times, both of which generally translate to poor user experiences.
The Cisco QoS baseline changed the marking recommendation for call-signaling traffic to
DSCP CS3. This change was made because Class Selector code points, as defined in RFC
2474, were not subject to markdown or aggressive dropping.
RFC 4594 presents configuration guidelines for DiffServ classes and recommends using a
dedicated class for “Real-Time Interactive” traffic, such as telepresence. RFC 4594 also
recommends using CS4 as a marking value for this class.

Cisco Catalyst Switch Queuing Model for
Telepresence Traffic
This topic describes the Cisco Catalyst 3750 Switch 1P3Q3T Queuing Model for telepresence
traffic. This model supports one strict priority queue (PQ) and three nonpriority queues, each
with three configurable WRED drop thresholds.
Cisco Catalyst Switch Queuing Model for

Telepresence Traffic
Application DSCP 1P3Q3T
Network Control CS7 AF1 Q4T2
CS1 Queue 4 (5%) Q4T1
Internetwork Control CS6
Default Queue
Voice EF DF Queue 3 (35%)
Interactive Video AF4x
CS7 Q2T3
Telepresence CS4
Mission-Critical Data AF3x CS6
Call Signaling CS3 CS3 Queue 2 Q2T2

Transactional Data AF2x AF4 (30%) Q2T1
AF3
Network Management CS2
AF2
Bulk Data AF1x
CS2
Scavenger CS1
EF Q1
Best Effort DF
CS4 Priority Queue
It is highly recommended that all Catalyst switches and line cards within a Cisco TelePresence
campus design support a 1PxQyT queuing model. With such a hardware queuing
configuration, it is recommended that you assign the CoS values as follows:
 CoS values 4 (telepresence) and 5 (voice) to the strict priority queue
 CoS 3 (call signaling) to a nonpriority queue
 CoS 0 (Best Effort) to another nonpriority queue that is used as the default queue
If an optional policer that marks anomalous traffic flows to Scavenger (CS1) is used, then
you should assign these flows, represented as CoS 1, to a Less Than Best Effort nonpriority
queue.
Cisco Catalyst Series Switches
Hardware Considerations
Cisco Catalyst 3560-E, 3560-G, 3750-E, and 3750-G Series
Switches:
 Use shared buffers per ASIC
– 13 ASICs with 750-KB Rx-buffers and 2-MB Tx-buffers for 4 GE ports
– Buffers per queue (per port) may be fixed or borrowed from a
common pool
 Support both ingress and egress queuing
– Ingress queuing is 2Q3T or 1P1Q3T (with Q1 as the PQ)
– Egress queuing is 4Q3T or 1P3Q3T (with Q1 as the PQ)
 Support both CoS-to-Queue or DSCP-to-Queue maps
– Set port trust to trust dscp to enable DSCP-to-Queue mapping
 Do not oversubscribe the ingress PQ when stacking a Cisco Catalyst
3750-E Series Switch
– Dual ring provides a 32-Gb/s “backplane”; 48 GE ports per switch
– When more switches are added, the oversubscription ratio increases.
From a QoS perspective, some of the relevant features of the Cisco Catalyst 3560-E, 3560-G,
3750-E, and 3750-G Series Switches include the following:
 Conditional trust
 Per-port/per-VLAN policers (via hierarchical QoS policies)
 DSCP-to-Queue mapping
 Q3T or 1P1Q3T ingress queuing
 4Q3T or 1P3Q3T egress queuing
Additionally, these platforms provide a minimum of 750 KB of receive buffers and 2 MB of
transmit buffers for each set of four ports. These buffers can be allocated, reserved, or
dynamically borrowed from a common pool—on a per-port, per-queue basis—depending on
the administrative configurations that are chosen.
Because QoS is disabled by default on these switches, the first step that you must take is to
globally enable QoS. You can do this by issuing the global command mls qos.
With QoS enabled, you can configure the access-edge trust boundaries. As discussed
previously, you have three options:
 Trust DSCP
 Trust CoS
It is recommended that you configure ports that are used for data and VoIP traffic to
conditionally trust CoS, while you configure ports that are used for telepresence traffic to trust
either DSCP, CoS, or conditionally trust CoS. Trusting DSCP on these ports is operationally
the simplest. The interface command to configure DSCP trust is mls qos trust dscp.

The Catalyst 3750G Series Switches include support for a stackable configuration, via
Stackwise technology. This configuration allows the 32-Gb/s backplane, which is comprised of
dual counter-rotating 16-Gb/s rings, to be extended over multiple Catalyst 3750G Series
Switches (up to nine). Additionally, the Catalyst 3750G Series Switches provide support for 10-
Gb Ethernet connectivity. However, more switches in the stack and using more 10-Gb Ethernet
connectors increases the oversubscription ratio accordingly. Do not oversubscribe the ingress
PQ.
Catalyst 3750 1P3Q3T Queuing Configuration Example
The following configuration has the PQ set to 30 percent. If there are more than two switches in
the stack, this configuration should be modified. For example, 2 * 48 Gb Ethernet = 96 Gb/s—
PQ is 30 percent (28.8 Gb/s)—Ring/Backplane capacity is 32 Gb/s.
mls qos srr-queue output cos-map queue 1 threshold 3 5
! Maps CoS 5 to Egress Queue 1 Threshold 3 (PQ)
mls qos srr-queue output cos-map queue 2 threshold 1 2 4
! Maps CoS 2 and CoS 4 to Egress Queue 2 Threshold 1 (Q2T1)
! Maps CoS 3 to Egress Queue 2 Threshold 2 (Q3T2)
mls qos srr-queue output cos-map queue 2 threshold 3 6 7
! Maps CoS 6 and CoS 7 to Egress Queue 2 Threshold 3 (Q2T3)

mls qos srr-queue output dscp-map queue 1 threshold 3 32 46
! Maps DSCP CS4 (telepresence) and EF (VoIP) to Egress Queue 1 (PQ)
mls qos srr-queue output dscp-map queue 2 threshold 1 16 18 20 22
! Maps DSCP CS2 and AF2 to Egress Queue 2 Threshold 1 (Q2T1)
mls qos srr-queue output dscp-map queue 2 threshold 1 26 28 30 34 36 38
! Maps DSCP AF3 and AF4 to Egress Queue 2 Threshold 1 (Q2T1)
mls qos srr-queue output dscp-map queue 2 threshold 2 24
! Maps DSCP CS3 to Egress Queue 2 Threshold 2 (Q2T2)
mls qos srr-queue output dscp-map queue 2 threshold 3 48 56
! Maps DSCP CS6 and CS7 to Egress Queue 2 Threshold 3 (Q2T3)
! Maps DSCP DF to Egress Queue 3 Threshold 3 (Q3T3 – Default Queue)
! Maps DSCP CS1 to Egress Queue 4 Threshold 1 (Q4T1)
mls qos srr-queue output dscp-map queue 4 threshold 2 10 12 14
! Maps DSCP AF1 to Egress Queue 4 Threshold 2 (Q4T2)
mls qos queue-set output 1 threshold 2 80 90 100 100
! Sets Egress Queue 2 Threshold 1 (Q2T1) to 80 percent and Threshold 2 (Q2T2) to 90
percent
mls qos queue-set output 1 threshold 4 60 100 100 100
! Sets Egress Queue 4 Threshold 1 (Q4T1) to 60 percent and Threshold 2 (Q4T2) to 100
percent
interface GigabitEthernet1/0/1
description telepresence and/or Uplink port
mls qos trust dscp
! Assigns the telepresence port and uplink port to trust DSCP
queue-set 1
! Assigns interface to Queue-Set 1 (default)

srr-queue bandwidth share 1 30 35 5
! Q2 gets 30 percent of remaining BW (after servicing PQ) Q3 gets 35 percent Q4 gets 5
percent
priority-queue out
! Expedite queue is enabled for telepresence and VoIP
interface GigabitEthernet1/0/2
description IP Telephony and/or Data port
mls qos trust device cisco-phone
! Configures conditional trust on IP Telephony and Data port
queue-set 1
! Assigns interface to Queue-Set 1 (default)
srr-queue bandwidth share 1 30 35 5
! Q2 gets 30 percent of remaining BW (after servicing PQ) Q3 gets 35 percent Q4 gets 5
percent
priority-queue out
! Expedite queue is enabled to for VoIP
Cisco Catalyst 4500 and 4900 Series
Switch Access Layer Considerations
 Oversubscription on some line cards
– 4448 and 4548 line cards have 8:1 oversubscription.
– Cisco Catalyst 4948 Switch has a nonblocking architecture.
 Maps DSCP-to-queues
 Egress queuing structures are 4Q1T or 1P3Q1T (+ DBL)
– Q3 is PQ
 DBL also applies to PQ traffic
– Default, when enabled
The Cisco Catalyst 4500 Series supervisor engines use a shared memory architecture to provide
queuing and scheduling features to the connected line cards. The 4448 and the 4548 line cards
have an 8:1 theoretical oversubscription ratio. While these line cards are suitable at the campus
access edge, you should not use them as uplinks or in the distribution and core layers of a
campus network that is enabled for Cisco TelePresence.
The Cisco Catalyst 4948 Switch is a wire-speed, low-latency, Layer 2 to Layer 4, 1-rack-unit (1
RU), fixed-configuration switch for rack-optimized server switching. It has a completely
nonblocking architecture that would be suitable at any layer (access, distribution, or core)
within a campus network that is enabled for Cisco TelePresence.
From a QoS perspective, the Cisco Catalyst 4500 Series Switches and the Cisco Catalyst 4948
Switch include the following:
 An elegant per-port/per-VLAN policer implementation
 DSCP-to-Queue mapping
 4Q1T or 1P3Q1T queuing support
 An advanced congestion algorithm (Dynamic Buffer Limiting [DBL])
The QoS commands do not include the mls prefix that the Cisco Catalyst 3560G and 3750G/E
Switches or the Cisco Catalyst 6500 Series Switches use. To globally enable QoS (which is
disabled by default), the command is qos.
Configure ports that you will use for data and VoIP telephony to conditionally trust CoS.
Configure ports that you will use for telepresence traffic to trust either DSCP, CoS, or
conditionally trust CoS. Trusting DSCP on these ports is operationally the simplest choice. The
interface command to configure DSCP trust is qos trust dscp.

If you choose to trust CoS or conditionally trust CoS, then you must explicitly map CoS 5 to
DSCP EF (expedited forwarding) before configuring the port to trust CoS. You can leave all
other CoS-to-DSCP mappings at their respective default values. Use the following global and
interface commands:
qos map cos 5 to 46
interface Gigx/y
qos trust cos
To implement conditional trust on the Cisco TelePresence ports, use the following interface
command:
qos trust device cisco-phone
Cisco Catalyst 6500 Series Switch
Access Layer Considerations
 Dedicated per-port buffers
– Buffer sizes (ingress and egress)
vary by line-card family
 Some cards have oversubscription
ratios
– 8:1 oversubscription ratio for 6148A
and 6548 line cards
– 6748 line card is effectively
nonblocking (dual 20 Gb/s
connection to fabric)
 Queuing structures vary by line-card
family
– Line cards only support CoS-to-
queue configurations
– The exception is the WS-X6708-
10GE, which also supports DSCP-
to-queue map, however is not
relevant for access-edge designs
The Cisco Catalyst 6500 Series Switch is widely deployed as the premier switch platform of
choice for small enterprise networks, large multinational companies, and transcontinental
service providers. One of the emerging technologies gaining particular interest across this
platform is the integration of voice and video across a traditional data network.
The queuing and buffering capabilities of the Cisco Catalyst 6500 Series Supervisor Engines
and line cards vary according to model. The Cisco 6148A-GE line cards and the Cisco 6548-
GE line cards are both engineered with 8:1 oversubscription ratios and are suitable at the access
layer. However, it is not recommended that you deploy these line cards as uplinks or within the
distribution and core layers of a campus network that has enabled Cisco TelePresence. In
contrast, the Cisco 6748-GE line card is virtually nonblocking, supporting a dual 20-Gb/s
connection to the switch fabric for its 48 (10/100/1000) ports, which equates to a minimal 6:5
oversubscription ratio.
Queuing structures also vary by line-card family. It is important to note that, at the time of this
writing, all Catalyst 6500 Series line cards support only CoS-to-Queue configurations for both
ingress and egress queuing, except for the Cisco WS-X6708-10GE line-card family. The Cisco
WS-X6708-10GE line-card family can be configured either with CoS-to-Queue mappings or
with DSCP-to-Queue mappings. However, the WS-X6708-10GE is not relevant for access-
edge designs.

Cisco TelePresence Campus Design
Catalyst 6500 Series Line Cards By Egress Queuing

Structures
1P2Q2T 1P3Q8T
1P3Q8T 1P7Q8T 1P7Q4T
CoS-to-Queue CoS-to-Queue CoS-to-Queue DSCP-to-Queue
WS-X6316-GE-TX WS-X6148A-GE-45F WS-X6704-10GE WS-X6708-10G-3C

WS-X6408A-GBIC WS-X6148A-GE-TX WS-X6708-10G-3CXL
WS-X6416-GBIC WS-X6724-SFP
WS-X6416-GE-MT WS-X6748-GE-TX
WS-X6516-GE-TX
WS-X6516A-GBIC
WS-X6816-GBIC
The queuing and buffering capabilities of Catalyst 6500 Series Supervisor Engines and line
cards vary according to type. The following table lists the Catalyst 6500 Series Switches line
cards by the egress queuing structures they support:
C 6500 Line Cards
1P2Q2T 1P3Q8T 1P7Q8T 1P7Q4T

CoS-to-Queue CoS-to-Queue CoS-to-Queue DSCP-to-Queue
WS-X6316-GE-TX WS-X6148A-GE-45F WS-X6704-10GE WS-X6708-10G-3C

WS-X6408A-GBIC WS-X6148A-GE-TX WS-X6708-10G-3CXL
WS-X6416-GE-MT WS-X6748-GE-TX
WS-X6516-GE-TX
WS-X6516A-GBIC
WS-X6816-GBIC
Catalyst 6500 Series Switch
CoS-to-Queue Limitation Workarounds
 Map CoS 4 to PQ and engineer PQ traffic not to exceed 33%
– For example, 128 kb/s for VoIP and 384 kb/s for interactive video per port x 48
ports x 11 line cards + 1 Cisco TelePresence System 3000 = 285 Mb/s PQ
(28% of a Gigabit Ethernet port)
– Simplest to implement and easiest to adapt when DSCP-to-Queue support
becomes available for access line cards
 Configure ingress re-marking and egress DSCP-mutations on Catalyst
6500 Series Switch to links to non-Catalyst 6500 Series Switches and
assign only CoS 5 to PQ
– Re-mark CS4 to CS5 on ingress (from non-Catalyst 6500 Series Switches)
– Perform DSCP mutation for CS5 to CS4 on egress (to non-Catalyst 6500
Series Switches)
– Assign only CoS 5 to PQ
– Is more difficult to configure, manage, and troubleshoot
– Also requires more configuration to reverse-engineer when
DSCP-to-Queue support becomes available
Generic video-conferencing and telepresence traffic share the same CoS value of 4. Therefore,
telepresence and generic video-conferencing traffic are indistinguishable from one another with
a CoS-based queuing scheme, because both applications are always mapped to the same queue.
Two workarounds are available for the Cisco Catalyst 6500 Series Switch CoS-to-Queue
limitation:
 Map CoS 4 to the PQ and engineer PQ traffic not to exceed 33 percent of the bandwidth of
the link. For example, 128 kb/s for VoIP traffic and 384 kb/s for interactive-video traffic
per port * 48 ports * 11 line cards and 1 Cisco TelePresence System 3000 = 285 Mb/s PQ.
This number is 28 percent of a Gigabit Ethernet port. This method is the simplest
workaround to implement and the easiest to adapt when DSCP-to-Queue support becomes
available for access line cards sometime in the future.
 Configure ingress re-marking and egress DSCP mutations on links that connect a Catalyst
6500 Series Switch to a switch that is not a Catalyst 6500 Series Switch. Also, assign only
CS5 to the PQ. You accomplish this configuration by re-marking CS4 to CS5 on the
ingress from switches that are not Catalyst 6500 Series Switches. Then perform the DSCP
mutation for CS5 to CS4 on the egress to the switches that are not Catalyst 6500 Series
Switches. Finally, assign only CS5 to the PQ. This configuration is more difficult to
configure, manage, and troubleshoot. It also requires more configuration to reverse-
engineer when DSCP-to-Queue support becomes available.

Catalyst 6500 1P&Q4T Configuration Example
interface range TenGigabitEthernet4/1 – 8
wrr-queue queue-limit 5 25 10 10 10 10 10
! Allocates 5 percent to Q1, 25 percent to Q2, 10 percent to Q3, 10 percent to Q4
! Allocates 5 percent to Q5, 5 percent to Q6 and 10 percent to Q7
wrr-queue bandwidth 5 25 10 10 10 10 10
! Sets the WRR weights for 5:25:10:10:10:10:10 (Q1 through Q7)
priority-queue queue-limit 20 ! Limits PQ to 20 percent
wrr-queue random-detect 1 ! Enables WRED on Q1

wrr-queue random-detect min-threshold 1 60 70 80 90 100 100 100 100

! Sets Min WRED Thresholds for Q1T1 to 60 percent, Q1T2 to 70 percent, Q1T3 to 80
percent, Q1T4 to 90 percent
wrr-queue random-detect max-threshold 1 70 80 90 100 100 100 100 100
! Sets Max WRED Thresholds for Q1T1 to 70 percent, Q1T2 to 80 percent, Q1T3 to 90
! Sets Min WRED Threshold for Q2T1 to 80 percent and all others to 100 percent
! Sets all Max WRED Thresholds for Q2 to 100 percent
! Sets Max WRED Thresholds for Q3T1 to 80 percent, Q3T2 to 90 percent, Q3T3 & Q3T4
to 100 percent
to 100 percent
to 100 percent
! Sets Max WRED Thresholds for Q6T1 to 70 percent, Q6T2 to 80 percent, Q6T3 to 90
! Sets all Min WRED Thresholds for Q7 to 100 (Disables WRED)
! Sets all Max WRED Thresholds for Q7 to 100 (Disables WRED)
! WRED is disabled on telepresence Queue (Q7); Tail-drop only
mls qos trust dscp ! Sets interface to trust DSCP

mls qos queue-mode mode-dscp ! Enables DSCP-to-Queue mapping mode
wrr-queue dscp-map 1 1 8 ! Maps Scavenger (CS1) to Q1T1

wrr-queue dscp-map 1 2 14 ! Maps Bulk Data (AF13) to Q1T2
wrr-queue dscp-map 2 1 0 ! Maps Best Effort to Q2T1
wrr-queue dscp-map 3 1 22 ! Maps Transactional Data (AF23) to Q3T1

wrr-queue dscp-map 4 1 30 ! Maps Multimedia Streaming (AF33) to Q4T1

wrr-queue dscp-map 5 1 38 ! Maps Multimedia Conferencing (AF43) to Q5T1

wrr-queue dscp-map 5 2 36 ! Maps Multimedia Conferencing (AF42) to Q5T2
wrr-queue dscp-map 5 3 34 ! Maps Multimedia Conferencing (AF41) to Q5T3.
wrr-queue dscp-map 6 1 16 ! Maps Net-Mgmt (CS2) to Q6T1

wrr-queue dscp-map 6 2 24 ! Maps Call-Signaling (CS3) to Q6T2
wrr-queue dscp-map 6 3 48 ! Maps IP Routing (CS6) to Q6T3
wrr-queue dscp-map 6 4 56 ! Maps Spanning-Tree (CS7) to Q6T4
wrr-queue dscp-map 7 1 32 ! Maps telepresence (CS4) to Q7T1
priority-queue dscp-map 1 46 ! Maps Voice (EF) to the PQ (Q8)

Note You can also map nonstandard DSCP values to their respective queues; however, for the
sake of simplicity, this configuration example does not show nonstandard DSCP-to-Queue
mappings. Because of WRED defaults and settings, you may need to change the order of
the WRED minimum and maximum threshold commands for some queues.
Campus QoS Policies Overview
This topic provides an overview of campus QoS policies.
Trust Boundary
1. Codec and IP phone Trust
both run Cisco Successful “Condition” Met
Boundary
(i.e., Cisco Discovery Protocol
Discovery Protocol, Negotiation Successful)
and the trust 1
Trust Is Dynamically Extended to
boundary is extended Cisco Unified IP Phone 797xG
to the IP phone. 2
2. The IP phone marks IP Phone 797xG: Voice  CoS 5 and DSCP EF
Call Signaling  CoS 3 and DSCP CS3
the packets at both
Layer 2 (802.1p CoS)
and Layer 3 (DSCP). 3
3. The codec marks the Cisco TelePresence Primary Codec: Voice + Video 
packets at both layer CoS 4 and DSCP CS4
2 (802.1p CoS) and Call Signaling  CoS 3 and DSCP CS3
Layer 3 (DSCP).
4
4. Switch port can be
CoS-to-DSCP Map:
set to trust CoS and
CoS 5  DSCP EF (46)
then map CoS-to-
CoS 4  DSCP CS4 (32)
DSCP or trust DSCP.
CoS 3  DSCP CS3 (24)
Access Edge Switch Port QoS Policies

The first QoS operation that you must perform is to define the trust boundary. The network
infrastructure can do one of the following:
 Trust the endpoints
 Not trust the endpoints
 Conditionally trust the endpoints
Cisco IP Telephony devices, including the Cisco Unified IP Phone 797xG, have the ability to
identify themselves to the network infrastructure via Cisco Discovery Protocol. Upon
successful identification, such as a condition being met successfully, the network infrastructure
begins to dynamically trust the endpoint. Both the Cisco Unified IP Phone 797xG and the Cisco
TelePresence primary codec are then assigned to the trusted voice VLAN. Once in the voice
VLAN, both the Cisco Unified IP Phone 797xG and the Cisco TelePresence codec can tag their
traffic with 802.1Q/p CoS values, as well as Layer 3 IP DSCP values.
The Cisco Unified IP Phone 797xG marks CoS values for voice and call signaling to CoS 5 and
CoS 3, respectively. It also marks DSCP values for voice and call signaling to DSCP EF/46 and
CS3/24, respectively. The Cisco TelePresence primary codec marks video traffic to CoS 4 and
DSCP 32.
Note Because two to six data ports are available for PC connections (as part of the Cisco
TelePresence tables), it is recommended that you disable the PC port on the back of the
IP Phone 797xG. You can disable this port from within Cisco Unified Communications
Manager.

Implementing Telepresence
Classification and Marking
 Cisco Unified Communications Manager is currently unable to
distinguish video-conferencing traffic from telepresence traffic and
marks both to AF41 by default.
 Use a policy map applied to the Cisco TelePresence system port
to re-mark telepresence traffic at the access-edge to CS4.
 Optionally, deploy policers at the access-edge switch ports to
prevent physical access and trust abuse of Cisco TelePresence
ports.
 Cisco TelePresence traffic can now be distinguished from video-
conferencing traffic (which will remain AF41) in downstream
DiffServ policies.
Cisco Unified Communications Manager currently controls the setting for how voice and video
packets are marked from the source nodes. The Cisco Unified Communications Manager
Release has no separate marking for Cisco TelePresence calls. You must mark telepresence
traffic at the switch port or first trustpoint of the network. Use a policy map to set Cisco
TelePresence video and audio RTP streams to a DSCP of CS4. Additionally, to properly
support IP telephony traffic, you should modify the global CoS-to-DSCP mapping table so that
CoS 5 is mapped to a DSCP value of 46 (EF). This configuration is not the default; the default
setting is for CoS 5 to map to a DSCP value of 40. These settings are achieved via the
following global and interface commands:
mls qos map cos-dscp 0 8 16 24 32 46 48 56
interface Gigx/y
mls qos trust cos
You can apply an optional access-edge ingress policer to the switch port to which the Cisco
TelePresence station is connected, and you can configure it to permit up to 15 Mb/s of traffic
from the port. You can mark excess traffic to CS1 (Scavenger) or drop it, depending on the
administrative preference and policy. Such a policy prevents network abuse in case a rogue
device is inserted or should the Cisco TelePresence unit itself somehow become compromised.
Note Policers are discussed in more detail with configuration examples in the “Designing WAN
and Branch QoS Policies” lesson of this course.
Campus QoS Policies Overview
Cisco
TelePresence
System 3000
 Set all interswitch Trust DSCP or

links to trust DSCP. Trust CoS + Map CoS 4  DSCP CS4 and CoS 5  DSCP EF
+ Optional Ingress Policing
 Marking granularity is + Queuing (DSCP CS4 and EF  PQ)
lost every time a + Queuing (DSCP CS3  Non PQ)
device trusts COS. Trust DSCP
+ Queuing (DSCP CS4 and EF  PQ)
+ Queuing (DSCP CS3  Non PQ)
Campus Interswitch Link QoS Policies

When the trust boundary has been established and optimal access-edge policers have been
enabled, then the DSCP values on all interswitch links can be trusted. Therefore, it is
recommended that you set all interswitch links to trust DSCP (not CoS), whether these are
uplinks or downlinks to or from the distribution layer, uplinks or downlinks to or from the core
layer, intracore links, or links to WAN aggregation routers.
The reason that you should trust DSCP and not CoS is that marking granularity is lost every
time that a node is set to trust CoS. For example, if Cisco TelePresence endpoints mark traffic
as CS4, Cisco Unified Video Advantage (or other video-conferencing endpoints) marks traffic
as AF41 and the distribution layer trusts CoS from the access layer, then both flows appear the
same (as CoS 4) to the distribution layer switch and are indistinguishable from each other from
that node forward.
Likewise, it is recommended that you enable queuing on every node along the path. Queuing
policies can be more complex than previously described, because now they may have to
accommodate additional data or video applications.

Summary
Summary
 Cisco TelePresence requires consistent delivery of controlled
latency, low jitter, and low packet loss in the network.
 QoS uses IP packet classification and marking. IPv4 uses the
three most significant bits of the ToS byte, called the IP
precedence. DiffServ uses the six most significant bits of the ToS
byte, called DSCP.
 All Catalyst switches and line cards within a Cisco TelePresence
campus design support a 1PxQyT queuing model.
 You should enable queuing on every node along the path.
Lesson 4
Designing WAN and Branch

QoS Policies
Overview
You will not fully realize the primary business advantages of the Cisco TelePresence systems if
the systems are connected solely via an intracampus deployment model. To maximize the
complete potential of Cisco TelePresence requires that you deploy Cisco TelePresence systems
across WANs, whether these are private WANs or virtual private networks (VPNs). You can
use WANs or VPNs to interconnect large campuses to each other or to connect one or more
large campuses with smaller branch offices. For an optimal Cisco TelePresence experience, you
must design quality of service (QoS) policies for the WAN and the branch offices.
Objectives
Upon completing this lesson, you will be able to design a WAN and branch QoS policy. This
 Describe the difference between a converged network and an overlay WAN network
 Provide an overview of the WAN and branch QoS polices
 Describe considerations and recommendations for LLQ and CBWFQ
 Describe the various WAN edge models
 Provide an overview of MPLS VPN policies
 Provide an overview of subline rate issues
 Describe the Cisco Certified TelePresence Connection program for service providers
WAN—Converged vs. Overlay
This topic describes a converged network versus an overlay network as they relate to Cisco
TelePresence.
WAN—Converged vs. Overlay
Converged Overlay
Network Network
 Maximum ROI, lowest TCO  Quicker, tactical option

in the long run  Easier, cheaper in the short run
 Must follow network design  Less concern of impact on
guidelines current network
- Switch platforms, line cards  Relaxed network design
- Router platforms guidelines
- WAN bandwidth and queuing  Overlay now, converge when
policies you are ready
- Shaping, queuing policies
A converged network uses your existing network and service provider connection to extend
Cisco TelePresence meetings beyond your enterprise boundary, enabling you to meet with
customers, suppliers, and partners. An overlay network requires you to build and manage a
separate network for Cisco TelePresence meetings at additional cost.
In a converged network, Cisco TelePresence runs on the existing intelligent network, allowing
it to coexist with other applications. When Cisco TelePresence calls are not active, this
bandwidth can be devoted to other enterprise applications. When Cisco TelePresence calls are
made, QoS and bandwidth reservation capabilities in the network allocate the bandwidth that is
needed, which means a company saves capital and operating expenses. The customer gets a
maximum return on investment (ROI) and has an overall lower total cost of ownership (TCO)
in the end. To fully benefit from a converged network, you must follow network design
guidelines when choosing switch platforms, line cards, and router platforms. You must follow
WAN bandwidth and queuing policies, as well as shaping queuing policies.
Using an overlay network is the quickest tactical option. It is easier and cheaper in the short run
to deploy, because there is less concern for the effect that Cisco TelePresence will have on
other network applications. There is no need to upgrade the existing network infrastructure
because you are isolating the Cisco TelePresence traffic on a dedicated network. As a result,
you can use relaxed design guidelines, however, you lose the benefits that are achieved from a
converged network design. For some customers the choice may be to use the overlay network
design now and converge when they are ready.
WAN—Converged vs. Overlay (Cont.)
Internetwork Control
Limit the amount of real-time voice and and OAM
video traffic to 33% of the link capacity. 2% Call Signaling
1%
Best Effort/ Real

Scavenger Default
1% Time
= 25% = 33%
Real Time/Default
= 97%
Critical
Critical Data Class Data
Includes Call 41%
Signaling,
Internetwork
Control, and OAM
Converged Overlay
Queuing policies may not be necessary on a properly provisioned overlay network

because this link would never congest, so it would never engage queuing policies.
Converged networks are recommended for a Cisco TelePresence deployment to maximize the
ROI. One of the benefits of a converged network is that when Cisco TelePresence is not using
the increased bandwidth, data applications can use the extra bandwidth. This capability allows
customers to leverage the network upgrades that were made for Cisco TelePresence to roll out
new applications.
However, on a converged network, follow some guidelines to allow the transparent
convergence of voice, video, and data:
1. Limit the amount of real-time voice and video traffic to 33 percent of the link capacity or
data will be starved out. This behavior results in very slow and erratic performance of
data applications.
2. Reserve at least 1 percent of the link capacity for signaling.
3. Reserve at least 2 percent of the link capacity for routing protocols and management
(Operations, Administration, and Maintenance [OAM]) traffic.
4. Reserve at least 25 percent of the link bandwidth for the default Best Effort data class.
5. Utilize a 1 percent scavenger class to ensure that unruly applications do not dominate
your default best effort data class.
Overlay (dedicated) networks do not need to follow guidelines 1, 4, or 5. However, you should
still reserve a small percentage (2 to 3 percent) of the link for routing protocols, OAM traffic,
and signaling, with the remaining 97 percent allocated for telepresence traffic.

Overlay Circuit Considerations
Assuming the customer is using an overlay network:
 Question 1: For a single Cisco TelePresence System 1000 at a branch office, can
a 10-Mb/s circuit be used?
 Answer: This is correct from a bandwidth perspective, but you must also consider
jitter.
 Question 2: Can a single E3 circuit be used for two Cisco TelePresence Systems
3000 at the regional campus?
 Answer: This would work for an overlay network. If a converged network is used,
only one Cisco TelePresence System 3000 would be supported.
The customer is using an overlay network and has the following two questions:
 Question 1: We are deploying a single Cisco TelePresence System 1000 at a branch office
location. Based on the guidelines, can we use a 10-Mb/s circuit?
Answer: From a bandwidth throughput perspective, a 10-Mb/s circuit would suffice,
but you must also consider jitter.
 Question 2: We are deploying two Cisco TelePresence Systems 3000 at the regional
campus. Can we use a single E3 circuit?
Answer: A single E3 circuit would suffice for an overlay network; however, if
customers are going to use a converged network, they could have only one Cisco
TelePresence System 3000.
WAN and Branch Policies Overview
This topic provides an overview of WAN and branch QoS policies.
WAN and Branch Policies Overview

Distribution
Layer Switches
WAN/VPN
Aggregators C B A D
A B C
C Branch Office 1
A A B C Dedicated, Separate Switch and Router
A A B C
C Branch Office 2
A B Cisc o ISR
C
with Cisco
C D
EtherSwitch Network
Module
A Interswitch Link Policies C WAN/VPN Edge QoS Policies
B Router LAN Edge Policies D Branch Access Edge Policies
For the scenario in the figure, branch office 1 has a Cisco TelePresence 3000 with a separate
dedicated switch and router. Branch office 2 has a Cisco TelePresence 1000 with a Cisco
Integrated Services Router with an EtherSwitch network module. The following are the
suggested best practices for this scenario:
 A: Interswitch Link Policies
— Trust differentiated services code point (DSCP)
— Queue class of service (CoS) 4 and CoS 5 to priority queue (PQ)
— Queue CoS 3 to non-PQ
 B: Router LAN Edge Policies
— Trust DSCP default
— (Optional) Low latency queuing (LLQ) for VoIP (Expedited Forwarding [EF])
— (Optional) LLQ for telepresence (CS4)
— (Optional) Class-based weighted fair queuing (CBWFQ) for call signaling (CS3)
 C: WAN/VPN Edge QoS Policies
— LLQ for VoIP (EF)
— LLQ or CBWFQ for telepresence (CS4)
— CBWFQ for call signaling (CS3)

 D: Branch Access Edge Policies
— Trust DSCP or trust CoS
— Map CoS 4 to DSCP CS4
— Map CoS 5 to DSCP EF and CoS 3 to DSCP CS3
— (Optional) Ingress policing
— Queue CoS 4 and CoS 5 to PQ
— Queue CoS 3 to non-PQ
Provisioning for Bursts on the WAN
 Line rate: The service provider is typically capable of modifying Bc and Tc values
in their queues and policers to accommodate telepresence traffic.
– Example: Full-line rate leased-line T3, E3, OC-3, OC-12, OC-48
 Subline rate or shared service: The service provider is typically unable to modify
their Bc and Tc values to accommodate telepresence traffic, and the enterprise
must use shaping to ensure traffic conforms to the Bc and Tc values of the policer.
– Example:
 Subline rate leased-line T3, E3, OC-3, OC-12, OC-48
 Metro Ethernet where link speed is 100 Mb/s or 1000 Mb/s, but only paying
for 20 Mb/s of bandwidth
When provisioning for bursts on the WAN to accommodate Cisco TelePresence, it is important
to understand the capabilities of the service provider. For line rate, the service provider is
typically capable of modifying committed burst size (Bc) and committed rate measurement
interval (Tc) values in their queues and policers for full-line rate leased-line T3, E3, Optical
Carrier 3 (OC-3), Optical Carrier 12 (OC-12), and Optical Carrier 48 (OC-48).
However, when it comes to subline rate or shared service, the service provider is typically
unable to modify their Bc and Tc values to accommodate Cisco TelePresence traffic. In this
case, the enterprise must use shaping to ensure that traffic conforms to the Bc and Tc values of
the service provider policer. An example of when you would need to use shaping is when there
is a subline rate leased-line T3, E3, OC-3, OC-12, OC-48, or Metro Ethernet with a possible
link speed of 100 or 1000 Mb/s, but the customer is only paying for 20 Mb/s of bandwidth.
Note Consider the end-to-end path. If the leased line is to Metro Ethernet, the leased-line side
must shape to conform to the Metro Ethernet side policers because service providers
typically police ingress and egress.

LLQ vs. CBWFQ Considerations and
Recommendations
This topic describes considerations and recommendations when provisioning LLQ versus
CBWFQ.
LLQ vs. CBWFQ Considerations

and Recommendations
 CBWFQ extends the standard WFQ functionality to provide support for user-
defined traffic classes.
 LLQ brings strict priority queuing to CBWFQ.
 Best-practice recommendations:
– Telepresence traffic receives best service when provisioned with LLQ
 May be cost-prohibitive
 Dedicated CBWFQ is the “next-best” solution
– If telepresence traffic is to be provisioned with LLQ: LLQ
 Keep to the “33% LLQ” rule for transparent
convergence of voice, video, and data PQ Voice
 Use dual-LLQ policy to eliminate PQ Video Police

potential interference with voice Conf
 Considerations: Class = X
– The cost of real-time services Packets
In Class = Y CBWFQ
– The “33% LLQ” rule
– Impact of Cisco TelePresence policies on voice WFQ Default
CBWFQ extends the standard weighted fair queuing (WFQ) functionality to provide support
for user-defined traffic classes. For CBWFQ, you define traffic classes that are based on match
criteria including protocols, access control lists (ACLs), and input interfaces. CBWFQ adds a
level of administrator control to the WFQ process, but the same WFQ dispatch process is
followed. However, CBWFQ allows you to define the various flows that are needed to classify
traffic into unique conversations. In addition to this separation of traffic, you can use CBWFQ
to guarantee that flows receive adequate bandwidth (as defined by you).
The LLQ feature brings strict priority queuing to CBWFQ. LLQ combines the use of a PQ with
a CBWFQ scheme. Classes are defined with classification admission schemes. Traffic flows
have access to either the PQ, one of the class-based queues, or a default weighted fair queue.
When deciding whether to provision telepresence traffic with LLQ or CBWFQ, consider the
cost of subscribing to real-time services. Also, consider the “33 percent” LLQ rule and examine
the potential effect that telepresence policies will have on voice traffic.
Cisco TelePresence receives the best service when provisioned with LLQ. However, this
approach can be cost-prohibitive at times. In this case, provisioning Cisco TelePresence in a
dedicated CBWFQ is the “next-best” solution. If you are going to provision Cisco TelePresence
with LLQ, then keep to the “33 percent” LLQ rule to allow for the transparent convergence of
voice, video, and data traffic. It is recommended that you use a dual-LLQ policy to eliminate
any potential interference with voice traffic.
Dual-LLQ Operation
po licy -map WAN-EDGE
 The implicit LLQ policers allows “multiple” low-latency c lass VOI P
queues to be configured, even though all LLQ traffic is prio rity 100
serviced by a single strict-priority queue. c lass VID EO
prio rity 400
 This PQ is serviced on a FIFO basis between c lass CAL L-SIG NALING
the VOIP and VIDEO classes, until the implicit LLQ band widt h x
policing limits of each class is reached. c lass TRA NSACTIONAL
 In this manner, both VoIP and VIDEO receive an EF band widt h y
PHB, but VIDEO cannot interfere with VoIP. c lass BUL K-DAT A
band widt h z
c lass cla ss-default
fair -que ue
100 kb/s
VOIP
Policer
Packets 500 kb/s PQ (FIFO Between VOIP and VIDEO)
In 400 kb/s TX
VIDEO
Policer
Ring
Call-Signaling CBW FQ Packets

Transactional CBWFQ CBW FQ Out
Bulk Data CBWFQ Scheduler
FQ Default Queue
The LLQ feature brings strict priority queuing to the CBWFQ scheduling algorithm. Strict
priority queuing allows delay-sensitive data, such as voice or video, to be transmitted before
packets in other queues are dequeued. This behavior gives delay-sensitive data strict-priority
treatment, as defined in RFC 3246, an EF per-hop behavior (PHB).
You can provision more than one low-latency queue, one for voice and another for telepresence
traffic. Each queue is serviced on a FIFO basis until an implicit policer for each class engages
and drops excess packets. This should occur only if Call Admission Control (CAC) and
bandwidth provisions were not set properly.
To achieve the goal of convergence, namely allowing voice, video, and data applications to
transparently share a single network, it is important not to assign the dominant share of the
bandwidth to real-time applications such as voice and video. Testing has shown that when more
than 33 percent of WAN links are dedicated for voice and video, then data application response
times deteriorate significantly. Therefore, a conservative and successfully deployed
recommendation is to limit the sum of all LLQ traffic to 33 percent.
However, it is important to recognize that this is a best-practice general principle and not a
mandate. When specific objectives and constraints exist that do not allow for this rule, the
administrator must design according to the individual needs of the enterprise.

Cisco TelePresence Traffic
Characteristics
 The queuing and shaping algorithms on every interface along the path are the
secondary contributors to video frame jitter.
 WFQ produces higher jitter than PQ.
 Example: RFC 4594 queuing policy on an OC-3 circuit (fully-congested,
no shaping):
– Observed jitter values for Cisco TelePresence in LLQ: 3–13 ms
– Observed jitter values for Cisco TelePresence in CBWFQ: 5–29 ms
 Slower links need to buffer and queue more, resulting in much higher jitter.
30 30
25 25
20
Jitter (ms)
20
Jitter (ms)
15 15
10 10
5 5
Left
Cisco TelePresence LLQ Center Cisco TelePresence CBWFQ
Right
The figure illustrates the jitter that is introduced by queuing. Shaping introduces even more
jitter, as would lower bit-rate circuit speeds. The target jitter of Cisco TelePresence System
Release 1.5 is less than 50 ms, but the Cisco TelePresence system can sustain jitter up to 165
ms before dropping packets. However, proceed with caution until the Cisco Verified Design
guidance can be updated.
Jitter Comparison for LLQ vs. CBWFQ

Jitter comparison is the most significant service level agreement (SLA) on the WAN-edge.
Using the policies that are established in RFC-4594 on an OC-3 link that was fully congested,
the following jitter values were observed for Cisco TelePresence:
 Observed jitter values for Cisco TelePresence in LLQ: 3 to 13 ms
 Observed jitter values for Cisco TelePresence in CBWFQ: 5 to 29 ms
WAN Edge Models
This topic describes the WAN edge models.
CBWFQ WAN Edge Model

Voice
10%
(LLQ)
Best Effort 25%
Telepresence
Class Supports:
Telepresence 1x Cisco TelePresence
35% System 3000 call at
Scavenger 1% (CBWFQ) 1080p-Best over a
Bulk Data 4% 45-Mb/s DS3 link
Transactional Data 5%
Multimedia Streaming 5%
Multimedia Conferencing 5% Network Control 2%

OAM 1%
Broadcast Video 5% Call Signaling 2%
*Traffic allocations based on a 45-Mb/s DS3 line rate

The following is the portion of the running configuration that applies to the CBWFQ example
in the figure:
class-map match-all VOICE
match ip dscp ef ! Voice marking
class-map match-all TELEPRESENCE
match ip dscp cs4 ! Telepresence marking
class-map match-all NETWORK-CONTROL
match ip dscp cs6 ! Routing and Control marking
class-map match-any CALL-SIGNALING
match ip dscp cs3 ! Call-Signaling (Cisco marking)
class-map match-all OAM
match ip dscp cs2 ! Network Management marking
class-map match-all MULTIMEDIA-CONFERENCING
match ip dscp af41 af42 af43 ! Multimedia Conferencing marking
class-map match-all MULTIMEDIA-STREAMING
match ip dscp af31 af32 af33 ! Multimedia Streaming marking
class-map match-all BROADCAST-VIDEO
match ip dscp cs5 ! Broadcast Video (Cisco marking)
class-map match-all LOW-LATENCY-DATA
match ip dscp af21 af22 af23 ! Transactional Data markings
class-map match-all HIGH-THROUGHPUT-DATA
match ip dscp af11 af12 af13 ! Bulk-Data markings
class-map match-all SCAVENGER
match ip dscp cs1 ! Scavenger marking
class-map match-all VOICE
match ip dscp ef ! Voice marking
class-map match-all TELEPRESENCE
match ip dscp cs4 ! Telepresence marking
class-map match-all NETWORK-CONTROL
match ip dscp cs6 ! Routing and Control marking
class-map match-any CALL-SIGNALING
match ip dscp cs3 ! Call-Signaling (Cisco marking)
class-map match-all OAM

match ip dscp cs2 ! Network Management marking
class-map match-all MULTIMEDIA-CONFERENCING
match ip dscp af41 af42 af43 ! Multimedia Conferencing marking
class-map match-all MULTIMEDIA-STREAMING
match ip dscp af31 af32 af33 ! Multimedia Streaming marking
class-map match-all BROADCAST-VIDEO
match ip dscp cs5 ! Broadcast Video (Cisco marking)
class-map match-all LOW-LATENCY-DATA
match ip dscp af21 af22 af23 ! Transactional Data markings
class-map match-all HIGH-THROUGHPUT-DATA
match ip dscp af11 af12 af13 ! Bulk-Data markings
class-map match-all SCAVENGER
match ip dscp cs1 ! Scavenger marking
interface Serial6/0
description BRANCH-TO-CAMPUS-T3
ip address 192.168.2.9 255.255.255.252
tx-ring-limit 10 ! Tuned T3 Tx-Ring
dsu bandwidth 44210
framing c-bit
cablelength 10
serial restart-delay 0
max-reserved-bandwidth 100 ! LLQ/CBWFQ BW Override
service-policy output WAN-EDGE-T3 ! Attaches policy to T3 int
LLQ WAN Edge Model
Voice
10%
(LLQ)
= 33% of bandwidth
Best Effort 25%
Telepresence Class
Telepresence Supports:
20%
Scavenger 1% (LLQ) 2x Cisco TelePresence
System 3000 call at
Bulk Data 4% 1080p-Best over a
155-Mb/s OC-3 link
Network Control 5%
Transactional Data 10%
OAM 5%
Multimedia Streaming 5% Call Signaling 5%

Broadcast Video 5%
Multimedia Conferencing 5%
*Traffic allocations based on a 155-Mb/s OC-3 line rate

The following is the portion of the running configuration that applies to the LLQ example in
the figure:
policy-map WAN-EDGE-OC3-POS
class VOICE
police cir 1550000 bc 20000 conform-action transmit exceed-action drop
! Voice is policed to 15.5 Mb/s; Bc is (Rate/100) 20 KB
priority ! LLQ command for OC3-POS
class TELEPRESENCE
! TP is policed to 31 Mb/s; Bc is (8x 64 KB segments)
priority
class NETWORK-CONTROL
bandwidth percent 5 ! CBWFQ for Network Control
class OAM
bandwidth percent 5 ! CBWFQ for OAM
class CALL-SIGNALING
bandwidth percent 5 ! CBWFQ for Call-Signaling
class BROADCAST-VIDEO
bandwidth percent 5 ! CBWFQ for Broadcast Video
class MULTIMEDIA-CONFERENCING
bandwidth percent 5 ! CBWFQ Multimedia Conferencing
random-detect dscp-based ! DSCP-WRED for Multimedia Conferencing
class MULTIMEDIA-STREAMING
bandwidth percent 5 ! CBWFQ for Multimedia Streaming
random-detect dscp-based ! DSCP-WRED for Multimedia Streaming
class TRANSACTIONAL-DATA
bandwidth percent 10 ! CBWFQ for Transactional Data
random-detect dscp-based ! DSCP-WRED for Transactional Data
class BULK-DATA
bandwidth percent 4 ! CBWFQ for Bulk Data
random-detect dscp-based ! DSCP-WRED for Bulk Data
class SCAVENGER
bandwidth percent 1 ! Minimum CBWFQ for Scavenger
class class-default
bandwidth percent 25 ! CBWFQ for Best Effort
random-detect ! WRED for Best Effort

LLQ WAN Edge Sample Configuration
LLQ for Cisco TelePresence System 3000 at 1080p-Best with
auxiliary video:
 Requires 15-Mb/s LLQ
 Requires burst for three segments of 64 KB (max) each
 Additionally requires burst provisioning for auxiliary video at 64 KB (max)
Main Cisco IOS configuration: OC-3-POS Cisco IOS configuration:

policy-map WAN-EDGE policy-map WAN-EDGE-OC3-POS
class TELEPRESENCE class TELEPRESENCE
priority 15000 256 police cir 15000000 bc 256000
conform-action transmit
… exceed-action drop
priority
...
Note: OC-3-POS does not have an implicit policer or an implicit burst; you must
explicitly configure them.
The LLQ bandwidth is typically limited by either implicit policing or a configured explicit
policer. In either case, the policed rate (CIR) must be sufficient for the number of Cisco
TelePresence system endpoints that are supported across the converged WAN circuit.
The following is a portion of the running configuration that applies to the LLQ example in the
figure.
Main Cisco IOS configuration:
policy-map WAN-EDGE
class TELEPRESENCE
priority 15000 256
OC-3-POS Cisco IOS configuration:
police cir 15000000 bc 256000
conform-action transmit
exceed-action drop
priority
The commands were configured for a Cisco TelePresence System 3000 running at 1080p-Best
with auxiliary video to meet the following requirements:
 15-Mb/s LLQ
 A maximum burst of 64 KB each for three segments
 Burst provisioning for auxiliary video at a maximum of 64 KB
Note OC-3-Packet over SONET (OC-3-POS) does not have an implicit policer or an implicit burst;
you must explicitly configure them.
LLQ WAN Burst Provisioning
 The LLQ priority command has an implicit burst parameter on
most platforms.
– priority {bandwidth-kb/s | percent percentage} [burst]
 Adequate burst should be provisioned for the largest frame.
– An Instantaneous Decode Refresh frame is 64 KB for 1080p-Best.
 Multiple segments can send IDR frames simultaneously.
– Provision up to 64 KB of burst per segment.
 Additionally, add a burst allowance for auxiliary video.
– Add 64 KB of burst for the auxiliary video.
 LLQ syntax can vary across platforms and interfaces.
The LLQ priority command has an implicit burst parameter:

priority {bandwidth-kbps | percent percentage} [burst]
You should provision adequate burst for the largest frame: an Instantaneous Decode Refresh
frame is 64 KB for 1080p-Best. Multiple segments can send Instantaneous Decode Refresh
frames simultaneously, therefore, you should provision up to 64 KB of burst per segment.
Additionally, you should add a 64-Kb burst allowance for auxiliary video.
Note LLQ syntax can vary across platforms and interfaces.

MPLS VPN Policies Overview
This topic provides an overview of Multiprotocol Label Switching (MPLS) VPN policies.
MPLS VPN Policies Overview

Branch 1
F
E F E
MPLS
E
F
VPN F
E
Campus
VPN Block CE Routers PE Routers CE Routers Branch 2
Enterprise Subscriber (unmanaged CE routers) Service Provider:

E Outbound policies: F Outbound policies:
 HQoS Shaper (if required)  LLQ for real-time
= 33%  LLQ for VoIP (EF)  CBWFQ for critical data
of BW  LLQ or CBWFQ for Telepresence (CS4) Inbound policies:
 Re-mark telepresence (if necessary)  Trust DSCP
 CBWFQ for call signaling (CS3)  Police on a per-class basis
 Re-mark call signaling (if necessary)
 Restore call signaling to CS3 (if necessary)
Inbound policies:
 Trust DSCP
 Restore Telepresence to CS4 (if necessary)
Network architects must take into account additional QoS design considerations when an
enterprise is subscribing to an MPLS VPN service provider. In this scenario, the enterprise and
the service provider jointly manage QoS policies. Specifically, the enterprise controls the QoS
policies on the Customer Edge (CE) routers to the Provider Edge (PE) routers, but the service
provider controls the QoS policies on the PE routers towards the CE routers. Therefore,
enterprise subscribers of MPLS VPN services must fully understand the QoS policies that their
provider offers and design their own QoS policies to be consistent with, and complement, the
policies of their service providers.
Currently, most service providers offer between three and six classes of service to
enterprise subscribers. These classes of service typically include one real-time service class
(which corresponds to the RFC 3246 EF PHB) and several other (nonpriority) guaranteed
service classes. The limited number of classes of service that are offered by the service
provider often requires enterprises to collapse the number of service classes that they are
using before handing off their traffic to their MPLS VPN service provider.
MPLS Four-Class Model
Voice 10%
Best
Effort 25% Telepresence 20%
SP–Best SP–Real
Telepresence class supports:
Effort Time 30%
30% 2x Cisco TelePresence
System 3000 call at
Scavenger 1% 1080p-Best over a
SP– SP– 155-Mb/s OC-3 link
Bulk Data 4%
Critical 2 Critical 1
20% 20% Network
OAM 5% Control 5%
Multimedia Streaming 5% Call Signaling 5%
Multimedia Conferencing 5%
Transactional
Broadcast Video 5% Data 10%
Traffic allocations are based on a 155-Mb/s OC-3 line rate

MPLS Four-Class Model Configuration Example

The following is the portion of the running configuration that applies to the MPLS four-class
example in the figure:
policy-map CE-EDGE-4CLASS-OC3-POS
class VOICE
! Voice is policed to 15.5 Mb/s (10%), Bc is 20 KB (Rate / 100), conforming

action is “transmit”, single-rate policing action

class TELEPRESENCE
! TP policed to 31 Mb/s (2x Cisco TS-3000 calls), Bc is 512 KB (8x 64-KB

segments)
! Conforming action is “transmit”, single-rate policing action

set ip dscp cs5 ! Re-mark Telepresence to CS5
class NETWORK-CONTROL
bandwidth percent 5 ! CBWFQ for Routing
bandwidth percent 5 ! CBWFQ for Call-Signaling
class TRANSACTIONAL-DATA
bandwidth percent 10 ! CBWFQ for Transactional Data
random-detect dscp-based ! DSCP-WRED for Transactional Data
set ip dscp af31 ! Re-mark Transactional Data to
AF31
class BROADCAST-VIDEO
bandwidth percent 5 ! CBWFQ for Broadcast Video
set ip dscp cs2 ! Re-mark Broadcast Video to CS2
class MULTIMEDIA-CONFERENCING
bandwidth percent 5 ! CBWFQ Multimedia-Conferencing
random-detect dscp-based ! DSCP-WRED for Multimedia-
Conferencing

set ip dscp af21 ! Re-mark Multimedia-Conferencing
to AF21
class MULTIMEDIA-STREAMING
bandwidth percent 5 ! CBWFQ for Multimedia-Streaming
random-detect dscp-based ! DSCP-WRED for Multimedia-
Streaming
set ip dscp af21 ! Re-mark Multimedia-Streaming to
AF21
class OAM
bandwidth percent 5 ! CBWFQ for Network Management
class BULK-DATA
bandwidth percent 4 ! CBWFQ for Bulk Data
random-detect dscp-based ! DSCP-WRED for Bulk Data
class SCAVENGER
bandwidth percent 1 ! Minimum CBWFQ for Scavenger
class class-default
bandwidth percent 25 ! CBWFQ for Best Effort
random-detect ! WRED for Best Effort
Subline Rate Access Overview
This topic provides an overview of subline rate access.
Subline Rate Access Overview
Metro
Ethernet
Network
Network-Facing
Subline Rate
Ethernet PE
HQoS-Capable
Switch or Router Access Circuit
Trust DSCP Trust DSCP

 HQoS shaping to subline access rate  Queuing (CoS 4 and 5 to PQ)
= 33% of  PQ for CoS 5 (VoIP) within shaped rate
shaped
rate  PQ for CoS 4 (Telepresence) within
shaped rate
 Non-PQ for CoS 3 (call signaling)
Metro Ethernet Subline Rate QoS Policies

Many of the QoS considerations that are required for Metro Ethernet networks are the same as
the considerations for MPLS VPN and campus configurations. These considerations include
fully understanding the QoS models that the Metro Ethernet provider offers, including the
number of classes and the admission criteria per class, and designing your network accordingly.
However, Metro Ethernet networks also have some unique considerations. For example, unlike
MPLS VPNs, the admission criteria for Metro Ethernet networks are usually based on 802.1Q/p
CoS values, not Layer 3 DSCP.
Another difference for Metro Ethernet services is that they are usually offered in 1-Mb/s
increments and are typically at subline access rates. Subline access rates present a unique QoS
design requirement that applies to Metro Ethernet networks, Ethernet-over-MPLS (EoMPLS),
and other Transparent LAN Services (TLS). This unique design requirement is necessary
because queuing policies do not engage unless the physical interface is congested. If circuit
speeds are subline rate, then traffic is not queued by ordinary queuing policies and thus service
levels cannot be guaranteed. Enabling hierarchical QoS (HQoS) policies that shape traffic
within a given rate and force queuing to occur within the shaped rate provides a solution to this
problem.

For example, consider a 50-Mb/s Metro Ethernet service that is offered by a provider over a
Gigabit Ethernet link. Assume that the enterprise subscriber has deployed Cisco TelePresence
and wants to guarantee the strict SLAs required by Cisco TelePresence over the metropolitan-
area network (MAN). The queuing policies that are deployed, whether done in hardware or in
software, do not engage unless the Gigabit Ethernet link is physically congested. Furthermore,
the MAN provider may be policing to drop traffic above the 50-Mb/s rate. In this case, the only
way that the enterprise subscriber can guarantee that telepresence traffic gets strict priority
servicing within this scenario is by doing the following:
 Configure a shaper to shape all traffic to 50 Mb/s
 Embed a queuing policy to force queuing (including strict priority queuing for telepresence
traffic) to engage within the 50-Mb/s subline rate
HQoS policies can be implemented in hardware, such as in the Cisco Catalyst 3750-Metro
switch with Enhanced Services ports or the Shared Port Adaptors (SPAs) on Cisco Catalyst
6500 Series Switches and Cisco 7600 Series Routers. Alternatively, you can implement HQoS
policies in software, such as in Cisco IOS Modular QoS command-line interface (MQC). One
of the primary QoS design principles is to always deploy QoS in hardware, rather than
software, whenever there is a choice. This recommendation is due to the efficiency of enforcing
QoS policies in hardware over software. On higher-speed circuits, hardware HQoS is highly
recommended. Obviously, the speeds of the circuits and the available platforms, as well as the
associated costs, factor into the decision of deploying HQoS policies within hardware or
software for Metro Ethernet or any other subline rate access circuit.
Subline Rate Access—
Shaping Configuration
 Queuing policies do not engage unless the interface is congested.
 A shaper guarantees that traffic does not exceed the contracted rate.
 A nested queuing policy forces queuing to engage at the contracted
subline rate to prioritize packets prior to shaping.
GE interface
with a subline rate
access service
2 Mb/s (for example, 50
VoIP Mb/s)
Packets Policer
In 17 Mb/s PQ (FIFO Between VoIP and VIDEO)
15 Mb/s
Class-
Based TX
VIDEO Ring
Policer Call-Signaling CBWFQ Shaper
Trans actional CBWFQ CBWFQ Packets
Bulk Data CBWFQ Scheduler Out
FQ Default Queue
Queuing policies do not engage unless the interface is congested. A shaper guarantees that
traffic will not exceed the contracted rate and a nested queuing policy forces queuing to engage
at the contracted subline rate to prioritize packets before shaping. The following is the portion
of the running configuration that applies to the subline rate access configuration shown in the
figure:
policy-map ACCESS-EDGE
class VOIP
priority 2000
class VIDEO
priority 15000
bandwidth 1000
class TRANSACTIONAL
bandwidth 2500
class BULK-DATA
bandwidth 2000
class class-default
fair-queue
policy-map HQoS-50MBPS
class class-default
shape average 50000000 1000000
service-policy ACCESS-EDGE

Subline Rate Access Hierarchical
QoS Policy
 By default, queuing policies do not engage at subline rates.
 Use shaper to ensure transmission rates do not exceed
contracted rate.
 Cisco IOS Software allows for HQoS policies.
– One QoS policy may be “nested” within another.
 Queuing policy nested within a shaping policy
 Packets prioritized within a subline (shaped) rate
 Cisco IOS shapers operate on a token bucket principle:
Burst (Bc) = Shaped Rate * Shaping Time Interval (Tc)
By default, queuing policies do not engage at subline rates. You can achieve queuing only by
introducing a two-part policy, sometimes referred to as an HQoS policy or nested QoS policy.
The HQoS policy shapes traffic to the subline rate and queues traffic according to the LLQ and
CBWFQ policies within the subline rate. With this type of HQoS policy, the class-based shaper
triggers software queuing, not the Tx-Ring, when the shaped rate has been reached.
One QoS policy can be “nested” within another. For example, you can nest a queuing policy
within a shaping policy. In this case, packets are prioritized within a subline (shaped) rate.
As with policers, Cisco IOS shapers operate on a token bucket principle using the following
formula:
Bc = Shaped Rate * Tc
Subline Rate Access Hierarchical
QoS Policy (Cont.)
 Optimal shaping interval for Cisco TelePresence is 20 ms:
– The shaping interval (Tc) cannot be directly set within Cisco IOS Software.
– You can indirectly set it by configuring the corresponding value for Bc.
 Bc = Shaped Rate * Shaping Time Interval (Tc)
 Example:
– Gigabit Ethernet interface configured to support a subline rate of 50 Mb/s
 The optimal Tc value is 20 ms.
 The value for shaping burst is:
– Bc = Shaped Rate * Tc (20 ms)
– Bc = 50,000,000 * 0.20
– Bc = 1,000,000 (or 1 Mb/s)
Sample configuration:
class class-default
shape average 50000000 1000000 ! Average shaping (not peak)
service-policy ACCESS-EDGE ! Nested queuing policy
Testing has shown that the optimal shaping interval for Cisco TelePresence is 20 ms. Although
you cannot directly set the Tc within the Cisco IOS configuration, you can indirectly set it by
configuring the corresponding value for Bc:
Bc = Shaped Rate * Tc
Take, for example, a Gigabit Ethernet interface that is configured to support a subline rate of 50
Mb/s:
 The optimal Tc value is 20 ms.
 The value or shaping burst is:
— Bc = Shaped Rate * Tc (20 ms)
— Bc = 50,000,000 * 0.20
— Bc = 1,000,000 (or 1 Mb/s)
The following is the resulting configuration:
class class-default
shape average 50000000 1000000 ! Average shaping (not peak)
service-policy ACCESS-EDGE ! Nested queuing policy

Service Provider Recommendations
This topic describes recommendations for choosing the appropriate service provider for
deploying Cisco TelePresence.
Which Service Provider?

Cisco Certified TelePresence Connection program for service
providers:
 Cisco Certified TelePresence Connection service providers have tested Cisco
TelePresence on their network and defined the mean Bc and Tc values for their
offerings, along with recommended QoS and bandwidth configurations.
 Customers can use a provider who is not a Cisco Certified TelePresence
Connection member as long as the network guarantees to provide the required
bandwidth, burst throughput, and meet service level requirements (one-way
latency, jitter, and loss).
 Providers should have well established SLAs that are typically conservative and
much higher than Cisco TelePresence requirements.
– Do not get diverted by legal verbiage of the SLA if the network performs to
requirements.
– Talk with providers about stated SLA vs. actual measured performance
metrics and if they meet end-to-end latency, jitter, and loss requirements for
Cisco TelePresence.
To ensure customer success, Cisco has created the Cisco Certified TelePresence Connection
program for service providers.
 The service providers in the Cisco Certified TelePresence Connection program have tested
Cisco TelePresence on their network and have defined the mean Bc and Tc values for each
of their network offerings, along with the recommended QoS and bandwidth
configurations.
 For various business reasons, customers may want to use a provider who is not a member
of the Cisco Certified TelePresence Connection program. They can use this type of
provider as long as the network can be guaranteed to provide the required bandwidth and
burst throughput and meet the other service level requirements for one-way latency, jitter,
and loss.
 Most service providers have well established SLAs that they are unwilling to modify. They
are typically very conservative and are much higher than the requirements for Cisco
TelePresence.
— Do not become diverted by the legal verbiage of the SLA, as long as the network
performs to the requirements.
— Talk with your service provider about their stated SLA compared to their actual
measured performance metrics and how capable they are of meeting the end-to-end
latency, jitter, and loss requirements for Cisco TelePresence.
What Type of Circuit?
 The raw bandwidth (throughput) required is a function of how many calls you must
support and whether you use a converged network or build out a dedicated
overlay.
 The clock-rate of the interface dictates the serialization delay. You may experience
unacceptable levels of jitter even if the aggregate throughput is sufficient.
 The following are recommendations for maximum ROI by providing increased
bandwidth for other data applications:
– 33% of the link should be allocated to telepresence traffic.
 Cisco TelePresence System 500 or 1000 = 5.5 Mb/s, minimum speed =
16.5 Mb/s
 Cisco TelePresence System 3000 or 3200 = 15.3 Mb/s, minimum speed =
46.5 Mb/s
 Overlay (dedicated) networks are also supported:
– 33% rule does not apply. Reserve 2% of the link for routing protocol and
management traffic overhead.
 Cisco TelePresence System 1000 = 5.5 Mb/s + 2% = 5.6 Mb/s
(round up to 6 Mb/s) + burst
 Cisco TelePresence System 3000 = 15.3 Mb/s + 2% = 15.6 Mb/s
(round up to 16 Mb/s) + burst
When you are determining the type of circuit to purchase for Cisco TelePresence, consider the
following:
 The raw bandwidth (throughput) required: This requirement is a function of how many
calls that you need to support and whether you are running on a converged network or
building a dedicated overlay network for Cisco TelePresence. Before you can decide how
much bandwidth to provision the WAN for, you must first consider the converged and
overlay deployment models.
 The clock-rate of the interface: This setting dictates the serialization delay. Even if the
aggregate throughput is sufficient, if the clock rate of the interface is less than 30 Mb/s you
will experience unacceptable levels of jitter.
 Converged networks: This model is recommended for maximum ROI. You can use the
increased bandwidth for data applications when telepresence traffic is not using it, allowing
you to leverage bandwidth upgrades that are made for telepresence traffic to roll out new
applications. Assuming the priority queue reserves one third of the WAN, the provisioned
circuit must be three times larger than the priority queue.
— Following are best-practice WAN recommendations:
 Do not allocate more than 33 percent of the link to telepresence traffic.
– If, for example, a Cisco TelePresence System 500 or 1000 is generating 5.5
Mb/s of traffic and the priority queue is configured for 5.5 Mb, the
minimum recommended circuit speed should be 16.5 Mb/s. (33 percent of
16.5 Mb is 5.5 Mb.)
– If, for example, a Cisco TelePresence System 3000 or 3200 is generating
15.3 Mb/s of traffic and the priority queue is configured for 15.3 Mb, the
minimum recommended circuit speed would be 46.5 Mb/s. (33 percent of
46.5 Mb is 15.3 Mb.)
 Overlay (dedicated) networks: This model is the quicker tactical model to implement.
— Following are the WAN recommendations for this model:

 The 33 percent rule does not apply in this case.
 Reserve 2 percent of the link for routing protocol and management traffic
overhead. Round this value up to the nearest whole megabytes per second to be
safe.
 If, for example, a Cisco TelePresence System 500 or 1000 is generating 5.5
Mb/s of traffic plus a 2 percent overhead for routing protocol and
management traffic, that would be a total of 5.6 Mb/s plus burst for the
recommended WAN circuit speed.
 If, for example, a Cisco TelePresence System 3000 or 3200 is generating
15.3 Mb/s of data, plus a 2 percent overhead for routing protocol and
management traffic, that would be a total of 15.6 Mb/s plus burst for the
recommended WAN circuit speed.
WAN Interface Recommendations
 Avoid bundled interfaces (for example, MLP, IMA)
– Fragmentation and reassembly cause jitter and high CPU utilization
on the router
 Use fractional DS-3 or higher when possible
– T1/E1 circuits are not a viable option
 Use Metro Ethernet as an alternative to leased circuits where available
 Broadband (for example, DSL, cable) is not recommended, pending
solution testing
– Shared bandwidth
– Asynchronous upstream and downstream speeds
– No QoS guarantees
The following are additional WAN interface recommendations:

 Avoid bundled interfaces (such as Multilink PPP [MLP] and Inverse Multiplexing over
ATM [IMA]).
— Fragmentation and reassembly cause jitter and high CPU utilization on the router.
 Fractional DS-3 or higher recommended
— T1/E1 circuits are not a viable option.
 Metro Ethernet recommended as an alternative to leased circuits, where available.
 Broadband (such as DSL and Cable) is not recommended, pending solution testing.
— Shared bandwidth
— Asynchronous upstream and downstream speeds
— No QoS guaranties

Summary
Summary
 For maximum ROI, converged WAN networks are recommended
instead of overlay WAN networks.
 Cisco has WAN and branch policies for the links, router LAN
edge, QoS, branch access edge, and provisioning for bursts.
 Cisco TelePresence receives the best service when provisioned
with LLQ. Dedicated CBWFQ is the next-best solution.
 There are specific WAN edge models for LLQ and CBWFQ.
 The enterprise and service provider jointly manage MPLS VPN
QoS policies.
 Subline access rates present a unique QoS design requirement
and apply to Metro Ethernet networks.
 Cisco Certified TelePresence Connection service providers have
tested Cisco TelePresence on their network and defined the
mean Bc and Tc values for their offerings, along with
recommended QoS and bandwidth configurations.
Lesson 5
Understanding the NPA

Overview
The planning and design phase of a Cisco TelePresence network deployment is critical. Device
and network issues must be proactively determined to assure the expected rich quality and
experience of Cisco TelePresence after the deployment. It is necessary to perform an
assessment of the network paths in an enterprise in order to properly support the Cisco
TelePresence system.
Objectives
Upon completing this lesson, you will be able to perform a network path assessment (NPA).
 Describe the NPA process
 Describe the tools that are used to perform an NPA
 Use the VSAA to collect network statistics
 Describe the Cisco TelePresence Manager PreQualification Assistant 1.5
What Is the NPA?
This topic describes the NPA process.
What Is the NPA?

Customer Wants Implementation
Cisco TelePresence Success
Network
Remediation
Network Discovery Gap Analysis Remediation and

Phase Recommendation
 Infrastructure assessment Data analysis based on Final remediation and
– QoS strategies Advanced Services best recommendation
practices and design aspects
– Hardware for Cisco TelePresence:
– Campus LAN, WAN  Survey
– Software  Site analysis
– Bandwidth (high-level)
 Path measurement
– Latency, jitter, packet loss
measurement
The NPA is a consultative process that prepares a customer network for broadband
deployments of Cisco TelePresence both on the LAN and WAN. It is necessary to perform an
NPA before the deployment of Cisco TelePresence systems to proactively detect common
problems and to help ensure the expected TelePresence experience. The NPA will lead to
higher customer satisfaction. It has three major steps:
 Network discovery phase
— Infrastructure assessment
 Quality of service (QoS) strategies
 Hardware
 Campus LAN, WAN
 Software
 Bandwidth (high-level)
— Path measurement
 Latency, jitter, and packet loss measurement
 Gap analysis
— Data analysis that is based on Advanced Services best practices and design aspects
for Cisco TelePresence
 Survey
 Site analysis
 Remediation and recommendations
NPA
 NPA purpose:
– Evaluates the readiness of a customer network infrastructure path
between Cisco TelePresence endpoints and evaluates any gaps
– Provides detailed Cisco TelePresence network path assessment,
validates prequalification report, and provides detailed remediation
steps
 NPA methodology:
– Interview customer to gather and review network path information
between Cisco TelePresence sites
– Review customer service provider SLA offerings to ensure they meet
the Cisco TelePresence requirements
– Gather and evaluate end-to-end SLA data (latency, jitter, and packet
loss) across the network path that the Cisco TelePresence traffic will
traverse
The purpose of the NPA is to evaluate the readiness of a customer network infrastructure path
between Cisco TelePresence endpoints and assess the gaps. The NPA provides detailed Cisco
TelePresence network path assessment, validates the prequalification report, and provides
detailed remediation steps before the installation can occur.
The methodology is to interview the customer to gather and review network path information
between proposed Cisco TelePresence sites. It is important to review the customer service
provider service level agreement (SLA) offerings to ensure that they meet the Cisco
TelePresence requirements.
Finally, validate the network infrastructure by gathering and evaluating end-to-end SLA data
(latency, jitter, and packet loss) across the network path that the Cisco TelePresence traffic will
be traversing.

The Cisco Experience and Order
Assurance Tool
http://tools.cisco.com/tsbu/oa/index.html
As part of the go-to-market strategy for Cisco TelePresence, Cisco opened the Cisco
TelePresence Experience and Order Assurance Program Office to manage a controlled release
process for all Cisco TelePresence systems products.
An NPA must be completed before an order can be released from product hold. The data that is
collected during the NPA process is entered using the Experience and Order Assurance tool,
which is located at http://tools.cisco.com/tsbu/oa/index.html.
Start a New Preinstallation
A preinstallation is the only requirement for Cisco TelePresence
System 500 deployments of 1 to 15 endpoints.
The preinstallation process is the only requirement for Cisco TelePresence System 500
deployments of 1 to 15 endpoints; an NPA is not required. Do not confuse the preinstallation
with the prequalification questionnaire, which is part of the prequalification and is required for
all installations.
The preinstallation contains the following four steps:
 Contacts
 Site Info
 Pre-Install Info
 Pre-Install Summary
Note If the customer has more than 15 Cisco TelePresence System 500 endpoints, then you must
complete an NPA.

Start a New NPA
All other deployments of Cisco TelePresence require an
NPA.
For all other deployments of Cisco TelePresence systems, you must complete an NPA. In order
to successfully conduct an NPA, you must have a thorough understanding of all Cisco
TelePresence solution components, how each component works, and the networking
requirements for Cisco TelePresence. Also, you must have a solid background in IP networking
design and performance, Cisco IOS routing, switching, and QoS. And finally, you need a solid
background in Cisco Unified Communications, specifically in Cisco Unified Communications
Manager design and configuration, Cisco Unified IP phones, dial plans, and signaling
protocols. If applicable, you must have a good understanding of Domain Name System (DNS),
Microsoft Active Directory, Microsoft Exchange Server, and Lotus Domino Unified
Communication Services (DUCS).
Caution Engineers who do not meet these requirements are not qualified to conduct NPAs for Cisco
TelePresence.
Contact and Site
 First step of an NPA:
– Contact information
 Customer and partner information
– Overview
 Does the customer have Cisco TelePresence deployed?
– General solution information
 The number and types of endpoints for this NPA
 The endpoint locations and details
The first step of the NPA consists of entering contact and site information. You must complete
all of the fields that are marked with an asterisk (*) in order to continue. The following
information is entered on this page:
 Contact information
— Customer company and contact information
— NPA submitter
— Partner information
 Overview
— Does the customer have existing Cisco TelePresence systems deployed?
 General solution information
— Choose the number and type of endpoints for this NPA.
— Populate the endpoint locations and details using a grid at the bottom of the screen.
Note When you have completed the contact and site information, click Next to continue to the
assessment survey.

Part 1
NPA Survey
 Version compatibility check
 General Cisco TelePresence solution design information
 Cisco Unified Communications Manager
 LAN design
 WAN design
 QoS
 Security
 Network infrastructure hardware readiness
 Network infrastructure software readiness
 Customer remediation agreements
The Network Path Assessment Survey question categories represent a subset of network and
application design and configuration considerations that are taken from the Cisco TelePresence
Network and Application design guides. You must complete all of the fields that are marked
with an “*” in order to continue.
 Version compatibility check (contains a link to a software compatibility matrix)
 General Cisco TelePresence solution design information
 Intercompany exchange
 Auto collaboration
 Interoperability (Cisco Unified Videoconferencing)
 Cisco Unified Communications Manager (Contains a link to the Cisco TelePresence
Network Systems 2.0 design guide)
 LAN design (Contains a link to the Enterprise Campus 3.0 Architecture design guide)
 WAN design (Contains a link to the Enterprise Campus 3.0 Architecture design guide)
 QoS (Contains a link to the Cisco TelePresence Network Systems 2.0 design guide)
 Security (Contains a link to the Cisco TelePresence Network Systems 2.0 design guide)
 Network infrastructure hardware readiness
 Network infrastructure software readiness
 Customer remediation agreements
Note When you have completed the assessment survey, click Proceed to Part 2 to continue to
the site analysis.
Part 2
NPA Site Analysis
 Site analysis
– Complete for each Cisco TelePresence system endpoint
 Service-level compliance
– Service-level matrix
 Assign locations to columns and rows in the table
 Enter the latency, jitter, and loss between sites
 Network design documents
– Attach network design documents
The Network Path Assessment Site Analysis is where you enter the details of the information
that you collect about the customer’s network. You must complete all of the fields that are
marked with an asterisk in order to continue.
 Site analysis
— Complete for each Cisco TelePresence system endpoint
 Bandwidth utilization
 LAN link utilization
 WAN link utilization
 Device utilization
 Service level compliance
— Enter the collected data into the Service Level Matrix.
 Assign sites to columns and rows in the table.
 Enter the latency, jitter, and loss between all sites.
 Network design documents (attachments)
— At least one file is required for each attachment section.
— There is a three-attachment maximum for each section.
— Please use a .zip file for multiple pictures or files when possible.
— Label the files accordingly.
— The maximum file size is 10 MB.

Site Analysis: Service Level Matrix
Complete this table to document network latency, jitter, and loss between sites.
The figure shows the Service Level Matrix, which is part of the site analysis. You enter the
latency, jitter, and loss information on this matrix. The matrix is designed to provide a visual
picture of the network, to help you enter the statistics that you gathered for multiple sites.
From the drop-down lists, choose the following:
 The NPA tool that was used to gather the service-level compliance data
 The software version that will be running on the coder-decoders (codecs)
After you have assigned the sites to the desired rows and columns, you can enter the data that
was collected during the NPA. When you are finished, save the changes.
Note When you have completed all of the steps in the site analysis, click Submit to continue to
the summary.
Summary
 The culmination of
the NPA process
 Summarizes the
findings of the NPA
(Part-1 and Part-2)
 Should be
presented to the
customer and to
the Cisco Account
Manager, along
with other
supporting
documents
The NPA summary report is the final step of the NPA process, which qualifies the customer’s
network readiness and summarizes the findings of the NPA. You should present this document
to the customer and to the Cisco Account Manager, along with the supporting documents
obtained using the NPA tools.
For each step of the NPA, a color indicates the status that determines the remediation necessary
to support an optimal Cisco TelePresence experience:
 Red: Significant remediation is needed.
 Yellow: Moderate remediation is needed.
 Green: No remediation is needed.

NPA Tools
This topic describes the tools that are used to assist in performing an NPA.
NPA Tools
 Tools used to gather statistics for the NPA:
– Cisco TelePresence codec call statistics
 Detailed latency, jitter, and loss statistics IP SL A
– Cisco IOS IP SLA

 Cisco IOS feature for path measurement
– Video SLA Assessment Agent
 Generates actual Cisco TelePresence video streams
The following tools are available to assist with the NPA process:
 Cisco TelePresence codec call statistics
— Provides detailed latency, jitter, and loss statistics on a per-call basis
 Cisco IOS IP Service Level Agreement (IP SLA)
— IP SLA is a tool in Cisco IOS Software that measures the end-to-end latency, jitter,
and loss between any two devices. Results are entered in the NPA Latency, Jitter,
and Loss Matrix and the NPA Summary Report Template.
— To access the Cisco IOS IP SLAs Configuration Guide, go to
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/12_4t/sla_12_4t_bo
ok.html.
 Video SLA Assessment Agent (VSAA)
— The VSAA provides the path characteristics, such as latency, jitter, and packet loss
measurements, before the deployment of Cisco TelePresence systems and before site
extensions or Cisco TelePresence model upgrades.
— The VSAA generates actual Cisco TelePresence video streams.
Cisco TelePresence Codec Call Statistics
This subtopic describes how to view the Cisco TelePresence codec call statistics.

CLI Interface show call statistics video detail
Every Cisco TelePresence codec offers detailed latency, jitter, and loss statistics on a per call
basis. This data is accessible via the command-line interface (CLI) on the primary codec. You
can use the command show call statistics video detail to gather the NPA data necessary for the
Experience and Order Assurance tool.

Web Interface
You can also use the web administrator interface on the primary codec to view detailed latency,
jitter, and loss statistics on a per call basis.
Step 1 Choose Call Statistics to view audio and video statistics that were collected from
the codecs. The reports include descriptions to help you understand the type of
information that is being collected. The window provides two immediate reports:
 Real Time Call Statistics: Lists whether a call is in progress
 Historical Call Statistics: Lists historical information about the calls, including
the configured bit rate
Step 2 Check the check boxes for the following items to see more specific audio and video
statistics. Bold text highlights significant statistics in the reports that follow:
 Audio/Video Call: Audio Stream Statistics
 Audio/Video Call: Video Stream Statistics
 Audio-Only Call: Stream Statistics
Note Statistics are listed in columns that are labeled as if you were looking at the back of the
system. For example, on a Cisco TelePresence System 3000, the labels would indicate
statistics from the left, center, and right codecs and from an auxiliary device if one is
connected. Set an interval for updating these reports by choosing the time in minutes from
the Refresh drop-down list.
Step 3 Click Refresh to update the statistics immediately.
Cisco IOS IP Service Level Agreement
This subtopic describes how to use the Cisco IOS IP SLA feature in the Cisco IOS Software to
collect network statistics.
Cisco IOS IP Service Level Agreement

 Can be deployed on stand-alone routers
Cisco provided by partner or on customer network
Unified Cisco TelePresence
devices
Communications Multipoint Switch
Manager  Should be deployed as close as possible to the
Cisco TelePresence devices, preferably using
the same IP address or addresses that the
Cisco TelePresence devices use
IP WAN
IP SL A
I P SLA
 Use active monitoring to generate

traffic and measure network
performance
Cisco IOS IP SLAs is a feature that is built into the software on Cisco IOS routers. It enables
customers to assure that new business-critical IP applications, as well as IP Services that utilize
data, voice, and video, function as expected in an IP network. Cisco has augmented traditional
service level monitoring and advanced the IP infrastructure to become IP application-aware by
measuring network performance and network health both end-to-end and at the IP layer.
With Cisco IOS IP SLAs, users can verify service guarantees, increase network reliability by
validating network performance, proactively identify network issues, and increase return on
investment (ROI) by easing the deployment of new IP Services.
 Cisco IOS IP SLAs use active monitoring to generate traffic in a continuous, reliable, and
predictable manner, thus enabling the measurement of network performance and health.
 You can deploy Cisco IOS IP SLAs on stand-alone routers that are provided by the Partner
or on the existing network devices of the customer.
 You should deploy Cisco IOS IP SLAs as close to the Cisco TelePresence devices as
possible, preferably using the same IP addresses that the Cisco TelePresence devices will
use.
Note Cisco IOS IP SLA was originally named Response Time Reporter (RTR). Older releases of
the Cisco IOS Software still use rtr as part of the commands to activate the feature. In more
recent Cisco IOS Releases, the rtr keyword has been changed to ip sla monitor. At one
time, the RTR process was also referred to as Service Assurance Agent (SAA).

Cisco IOS IP SLA UDP Test Operations
 DNS/DHCP
 Echo  DNS/DHCP test
 Jitter  UDP Echo test:
– Measures round-trip delay
UDP
– Optionally, uses a Cisco IOS IP SLA Responder as a
target device to remove processing delay at the
destination
 Jitter test: (requires Cisco IOS IP SLA Responder for target)
– Measures the variance of the test packet and packet loss
delay
– Measures round-trip delay statistics
UDP Echo
The UDP Echo operation calculates User Datagram Protocol (UDP) response times between a
Cisco router and any IP-enabled device. Response time is computed by measuring the time that
it takes to send a datagram and receive a response from the destination device. If the target is a
Cisco router, you have an option to enable the Cisco IOS IP SLA Responder in the target
router. The responder would either listen to the default UDP echo port (port 7) or to the port
that the user specifies. Using the Cisco IOS IP SLA Responder can increase accuracy as the
process delay in the target router is assessed. If the destination is a regular IP host, the user
must use UDP port 7 as the destination port.
Note Almost all of the IP devices provide a UDP echo service that listens on port 7 and responds
to client requests (echo server). Cisco routers have this service, but it is disabled by default.
If the echo server is enabled on the target Cisco router and the administrator starts a UDP
operation that tries to communicate with a responder on port 7, the responder fails due to a
socket bind problem (port 7 is already used by the echo server). If you plan to use a
responder, you should not specify a port that might already be in use by other services on
the router.
Note In order for a Cisco router to respond to UDP ports above 1023, the router must support
Cisco IOS IP SLA and have the Cisco IOS IP SLA Responder feature enabled.
UDP Jitter (Enhanced UDP)
With the addition of real-time traffic in the network, such as VoIP, the focus is no longer just
on the reliability of the network, but also on the delays that are involved in transmitting data.
Real-time traffic is delay-sensitive. With voice data, some packet loss is manageable, but
frequent losses impair communication between endpoints.
The UDP Jitter operation was designed to measure the delay, delay variance, and packet loss in
IP networks by generating UDP test traffic. The UDP Jitter operation sends N packets, each of
size S, from the source router to a target router, which requires the Cisco IOS IP SLA
Responder to be enabled. Each packet is sent T milliseconds apart. All of these parameters are
user-configurable. In the encoding implementation of Cisco, if a G.729 codec is used, frames
are generated every 10 ms with a Real-Time Transport Protocol (RTP) payload size of 10
bytes. Cisco voice gateway combines two such frames and transmits them every 20 ms.
Because of this behavior, the UDP Jitter operation default values are set to simulate voice
traffic. By default, 10 packets are sent for each operation.
The UDP Jitter operation measures the following network performance statistics:
 Round-trip network latency
 Per direction packet loss
 Per direction interpacket delay variance (jitter)
 Network availability and errors
You can also configure UDP Jitter operation with the following parameters on Cisco IOS IP
SLA routers that have a Cisco IOS Software Release greater than 12.3 (7):
 MOS: Mean opinion score (MOS) provides a numerical measure of the voice quality in the
network. It is expressed as a single number in the range of 1 to 5; 1 is the lowest perceived
quality, and 5 is the highest perceived quality.
 ICPIF: The Calculated Planning Impairment Factor (ICPIF) numbers represent predefined
combinations of loss and delay. Packet loss and delay determine the threshold for initiating
the busyout state. The ICPIF range is from 0 to 55; 5 is very good, and 55 is very bad.
Default Enhanced UDP Operations Settings
Request Packet Number Jitter

Packet Payload Interval of Threshold Target
Enhanced UDP Priority (Bytes) (ms) Packets (ms) Port
Operation (Default: (Default: (Default: (Default: (Default: (Default:
0) 64) 20) 10) 250) 2000)
Default160ByteVoice 5 160 20 10 250 16,400
Default60ByteVoice 5 60 20 10 250 16,400
DefaultVPN 0 1024 20 20 250 2000
DefaultVideo 0 1024 20 50 250 50,505

Cisco IOS IP SLA Delay Computation
Cisco IOS
IP SLA Source Target Device
Cisco Device
Network with Cisco
IOS IP SLA
Time Time Responder
TS1
TS2
TS3
Processing
TS4 Time
Calculating the round-trip delay:

 With the Cisco IOS IP SLA Responder, the processing time of the target device
is eliminated.
– (TS4 – TS1) – (TS3 – TS2)
 Without the Cisco IOS IP SLA Responder, the delay includes the processing time
of the target.
– TS4 – TS1
Round-Trip Delay Computations

The figure shows how the round-trip latency values are computed. As illustrated, when the
Cisco IOS IP SLA Responder is used as the target device, processing delays can be minimized
by computing the processing delay time of the target and subtracting it from the total round-trip
time.
Routers sometimes take tens of milliseconds to process incoming Cisco IOS IP SLA packets
due to other high-priority processes. This delay affects the response times that the Cisco IOS IP
SLA computes, because the reply to test packets might be sitting in the queue while waiting to
be processed by Cisco IOS IP SLA. Therefore, the response times would not accurately
represent true network delays.
If a Cisco IOS IP SLA Responder is used, Cisco IOS IP SLA minimizes these processing
delays on the source router as well as on the target router in order to compute true round-trip
times. It minimizes the delays by time-stamping the test packets for Cisco IOS IP SLA
operations.
Cisco IOS IP SLA Responder Command for Target Cisco IOS Router
When the Cisco IOS IP SLA responder command is enabled on the target router, the device
takes two time stamps, one when the packet arrives on the interface at an interrupt level and
one just as the packet is leaving. This method eliminates the processing time. At times of high-
network activity, an Internet Control Message Protocol (ICMP) ping test often shows a long
and inaccurate response time, while a Cisco IOS IP SLA test shows an accurate response time
due to the time stamping on the responder.
Configuring Cisco IOS IP SLA
The IP SLA embedded in
Cisco IOS devices can
generate synthetic traffic
for measuring latency,
jitter, and packet loss.
Test Packets
IP SLA
Network IP SLA
Source
Router Target Device:
 Cisco IOS Router
 Cisco TelePresence
System Endpoint
Configure using an
Configure from CLI SNMP application
Cisco IOS IP SLA uses generated traffic to measure network performance between two
networking devices, such as routers, or between a router and a Cisco TelePresence System
codec. A Cisco IOS IP SLA starts when the Cisco IOS IP SLA device sends a generated packet
to the destination device. After the destination device receives the packet, and depending on the
type of Cisco IOS IP SLA operation, the device responds with time-stamp information for the
source to make the calculation on performance metrics. A Cisco IOS IP SLA operation
performs a network measurement from the source device to a destination in the network using a
specific protocol such as User Datagram Protocol (UDP).
The following are capabilities of the Cisco IOS IP SLAs:
 VoIP, video, and virtual private network (VPN) monitoring
 SLA monitoring
 Network performance monitoring and network performance visibility
 IP Service network health readiness or assessment
 Edge-to-edge network availability monitoring
 Network operation troubleshooting
 Multiprotocol Label Switching (MPLS) network monitoring
You can configure Cisco IOS IP SLA from the CLI of a Cisco router. To access the Cisco IOS
IP Service Level Agreements User Guide, go to
http://www.cisco.com/en/US/technologies/tk648/tk362/tk920/technologies_white_paper09186a
00802d5efe.html.
You can configure Cisco IOS IP SLA from an application that uses Simple Network
Management Protocol (SNMP) to configure the router. Cisco Internetwork Performance
Monitor is an example of an SNMP application that is part of the CiscoWorks LAN
Management Solution (LMS) bundle.

Configuring Cisco IOS IP SLA from
the CLI
 To use the UDP jitter operation, you must enable the Cisco IOS IP
SLA Responder on the target Cisco IOS device.
 Time synchronization, such as NTP, is required between the
source and target device to provide accurate one-way delay
(latency) measurements.
 Before configuring any Cisco IOS IP SLA applications, enter the
following command on the Cisco IOS device to verify that the
operation type is supported on the software image.
– Router# show ip sla application
 To enable the Cisco IOS IP SLA Responder, enter the following
command in the global configuration mode of the target Cisco IOS
device:
– Router(config)# ip sla responder
IP SLA
Using the UDP jitter operation requires that the Cisco IOS IP SLA Responder be enabled on
the target Cisco IOS device. Time synchronization, such as that provided by Network Time
Protocol (NTP), is required between the source and the target device in order to provide
accurate one-way delay (latency) measurements. However, time synchronization is not required
for the one-way jitter and packet loss measurements. If the time is not synchronized between
the source and target devices, one-way jitter and packet loss data will be returned. However,
values of “0” will be returned for the one-way delay measurements that are provided by the
UDP jitter operation.
Before configuring any IP SLA applications, enter the following command in the EXEC mode
of the Cisco IOS device to verify that the operation type is supported on the software image:
Router# show ip sla application
To configure the Cisco IOS IP SLA Responder, enter the following command in the global
configuration mode of the target Cisco IOS device:
Router(config)# ip sla responder
Configuring and Scheduling Basic
UDP Jitter
 To configure and schedule a basic UDP Jitter operation on the
source Cisco IOS device, enter the following commands:
Router# configure terminal
Router(config)# ip sla operation-number
Router(config-ip-sla)# udp-jitter {destination-ip-address
| destination-hostname} destination-port [source-ip {ip-
address | hostname}] [source-port port-number] [control
{enable | disable}] [num-packets number-of-packets]
[interval interpacket-interval]
Router(config-ip-sla)# frequency seconds
Router(config-ip-sla)# exit
Router (config)# ip sla schedule operation-number [life
{forever | seconds}] [start-time {hh:mm[:ss] [month day |
day month] | pending | now | after hh:mm:ss}] [ageout
seconds] [recurring]
Router (config)# exit
Router# show ip sla configuration [operation-number]
The following command configures the operation number and enters the IP SLA configuration
submode:
Router(config)# ip sla operation-number
The following command configures the Cisco IOS IP SLA operation as UDP jitter and
specifies optional characteristics of the operation:
Router(config-ip-sla)# udp-jitter {destination-ip-address |
destination-hostname} destination-port [source-ip {ip-address
| hostname}] [source-port port-number] [control {enable |
disable}] [num-packets number-of-packets] [interval
interpacket-interval]
The following command sets the rate at which a specified IP SLA operation repeats:
Router(config-ip-sla)# frequency seconds
The following command exits the configuration submode:
Router(config-ip-sla)# exit
The following command is used to enter scheduling parameters for the operation:
Router (config)# ip sla schedule operation-number [life
{forever | seconds}] [start-time {hh:mm[:ss] [month day | day
month] | pending | now | after hh:mm:ss}] [ageout seconds]
[recurring]
After the operation has been scheduled, you can view the configuration from the EXEC mode:
Router (config)# exit
Router# show ip sla configuration [operation-number]

Sample UDP Jitter Configuration
ip sla 1
u dp-jitter 192. 168. 200.111 163 86
n um-packets 150 0 in terval 30 Time
f requency 1 between
r equest-data-si ze 2 56 How often to
t os 136 repeat the packets
o wner Dan operation
t ag TelePresenc e_sm all
ip sla 2
u dp-jitter 192. 168. 200.111 163 88 num-packet s 300 0 interval 15
r equest-data-si ze 9 60
t os 136 Bytes per Packets
o wner Dan request per
t ag TelePresenc e_me dium packet frequency
ip sla 3
u dp-jitter 192. 168. 200.111 163 90 num-packet s 450 interval 4
r equest-data-si ze 7 652
f requency 1
t os 136
owner Dan
t ag TelePresenc e_la rge
... Output omitte d .. .
The following is an example of commands for a basic UDP jitter configuration on a source
Cisco IOS device supporting Cisco IOS IP SLA. The IP address of the target device that is used
in the example is 192.168.200.111. Five separate operations are created using different
destination ports, numbers of packets, and packet intervals. When the operations are created,
they are scheduled, which starts the data collectors on the device.
ip sla 1
udp-jitter 192.168.200.111 16386 num-packets 1500 interval 30
request-data-size 256
tos 136
owner Dan
tag TelePresence_small
ip sla 2
tos 136
owner Dan
tag TelePresence_medium
ip sla 3
tos 136
owner Dan
tag TelePresence_large
ip sla 4
udp-jitter 192.168.200.111 16392 num-packets 1000
tos 136
owner Dan
tag TelePresence_audio
ip sla 10
udp-jitter 192.168.200.111 17000 num-packets 1000
tos 184
owner Dan
tag voice-only-calls
ip sla group schedule 1 10,1-4 schedule-period 1 frequency 60 start-time now
Cisco TelePresence Traffic Profile by
Millisecond
 Cisco TelePresence System 3000
– Mean bytes per ms: 1913
– Average packets per second: 1800 (1.8 packets per ms)
 Cisco TelePresence System 1000
– Mean bytes per ms: 713
– Average packets per second: 900 (0.9 packets per ms)
 IP SLA can generate packets every 4–6000 ms
– Build operations for 4-ms packet distributions and 1-second frequency
by multiplying the 1-ms Cisco TelePresence mean rate by 4 and
average p/s by 250
– Example for a Cisco TelePresence System 3000:
ip sla 3
udp- jitt er 192.168.200. 111 1 6390 num- packets 450 in terva l 4
requ est- data-size 7652
freq uenc y 1
tos 136 Packet fragmentation will
own er D an occur.
tag Tele Presence_large
The Cisco IOS IP SLA is limited to the rate at which it can generate traffic. The traffic rate for
a Cisco TelePresence System 3000 is 1913 B/ms, with packets being created every 1.8
milliseconds. The traffic rate for a Cisco TelePresence System 1000 is 713 B/mm with packets
created every 0.9 ms.
To simulate Cisco TelePresence traffic using Cisco IOS IP SLA, you must identify the
constraints of Cisco IOS IP SLA.
 Cisco IOS IP SLA can only push one packet every 4 ms.
 Cisco TelePresence generates roughly one to two packets every millisecond. Because of
this traffic rate, you must increase the packet size to compensate.
Increasing packet size causes the packet to exceed the normal Ethernet maximum transmission
unit (MTU), causing the packet to be fragmented. Although this example will simulate similar
traffic volume, it may not accurately represent jitter because delay will occur through packet
serialization. It is recommended that you also create another profile with a request-data-size of
1500 B and average the results between the two.

show ip sla statistics
router# sho w ip sla statis tics 1
Round Tri p Tim e (RTT) fo r Ind ex 5 5
Late st RT T: 1 ms
Lates t op erati on start t ime: *23: 43:3 1.845 UTC Thu F eb 3 2005
Lates t op erati on return code: OK
RTT V alue s:
Numb er Of RTT : 10 R TT M in/Av g/Max: 1/1/1 m illis econds
Laten cy o ne-wa y time:
Numb er of Lat ency one-way Sa mples : 0
Sour ce to Des tinat ion Latenc y one way Min /Avg/M ax: 0/0/0 mill isec onds
Dest inati on t o Sou rce Latenc y one way Min /Avg/M ax: 0/0/0 mill isec onds
Jitte r ti me:
Numb er of Jit ter S amples: 9
Sour ce to Des tinat ion Jitter Min/ Avg/ Max: 0/0/0 mil lisec onds
Dest inati on t o Sou rce Jitter Min/ Avg/ Max: 1/1/1 mil lisec onds
Packe t Lo ss Va lues:
Loss Sour ce t o Des tination: 0 Loss Dest inat ion to Sou rce: 0
Out Of Se quen ce: 0 T ail Drop: 0 Pack et La te A rrival: 0
Voice Sco re Va lues
Calc ulate d Pl annin g Impairme nt Fa ctor (IC PIF): 0
Mean Opin ion Score (MOS): 0
Numbe r of succ esses: 1
Numbe r of fail ures: 0
Opera tion time to live: 3591 sec
After the jitter operation has run and enough data has been collected on the source device, you
can display the results with the show ip sla statistics EXEC command. This command shows
the instantaneous results for the measurement operation. The following example shows sample
output from the show ip sla statistics command:
router# show ip sla statistics 1
Round Trip Time (RTT) for Index 55
Latest RTT: 1 ms
Latest operation start time: *23:43:31.845 UTC Thu Feb 3 2005
Latest operation return code: OK
RTT Values:
Number Of RTT: 10 RTT Min/Avg/Max: 1/1/1 milliseconds
Latency one-way time:
Number of Latency one-way Samples: 0
Source to Destination Latency one way Min/Avg/Max: 0/0/0
milliseconds
Destination to Source Latency one way Min/Avg/Max: 0/0/0
milliseconds
Jitter time:
Number of Jitter Samples: 9
Source to Destination Jitter Min/Avg/Max: 0/0/0 milliseconds
Destination to Source Jitter Min/Avg/Max: 1/1/1 milliseconds
Packet Loss Values:
Loss Source to Destination: 0 Loss Destination to
Source: 0
Out Of Sequence: 0 Tail Drop: 0 Packet Late Arrival: 0
Voice Score Values
Calculated Planning Impairment Factor (ICPIF): 0
Mean Opinion Score (MOS): 0
Number of successes: 1
Number of failures: 0
Operation time to live: 3591 sec
Configuring Cisco IOS IP SLA
Using SNMP
 IPM is an example of an SNMP application in
the CiscoWorks LMS bundle.
 IPM can be used to configure collectors on the
source Cisco IOS IP SLA device.
 IPM uses SNMP to configure collectors.
 IPM retrieves data from collectors and stores it
in a database.
 You can run reports and graphs from results in
the IPM database.
CiscoWorks Internetwork Performance Monitor (IPM) is an example of an SNMP network

management application that is part of the CiscoWorks LMS bundle. CiscoWorks LMS is a
suite of powerful management tools that simplify the configuration, administration, monitoring,
and troubleshooting of Cisco networks.
CiscoWorks IPM is an easy-to-use application that enables you to do the following:
 Configure Cisco IOS IP SLA on the source router
 Collect the data and store it in a database
 Run reports to view the performance results

IPM Jitter Report and Graph
Report contains data on

latency, jitter, and loss.
Graph
The figure shows an example of jitter data that was gathered by CiscoWorks IPM from its UDP
Jitter collectors. The reports and graphs are generated from the data that was collected from the
source router and stored in the IPM database. It displays the delay between any two data
packets or the interpacket delay between the source and the target device. The target device
must be responder-enabled. This report also contains latency and packet loss information. To
view the jitter report in a graphical format, click the Graph link on the Jitter Report window.
Video SLA Assessment Agent
This topic describes how to use the VSAA to collect network statistics.
VSAA
 Benefits of using the VSAA:
– Avoids costs of shipping network equipment to customer sites
– Improves productivity
– Is easy to use, run tests, and generate reports
 Technical benefits
– Central management software, which runs on a Linux server
– A VSAA (Linux-based) runs on the laptop platform
– Sends actual Cisco TelePresence video traffic between agents
– Encrypts the data generated
– Supports 16 test profiles
 Automation for consistency and productivity
– Numerical results provided for each source-destination pair for
latency, jitter, and packet loss
– Easy-to-read green, yellow, and red results against design thresholds
– Modular components for ease of integration into NPA report
The VSAA provides the path characteristics, such as latency, jitter, and packet loss
measurements, before the deployment of the Cisco TelePresence systems and before site
extensions or Cisco TelePresence model upgrades. Using the VSAA, you can proactively
determine device and network issues to help facilitate the expected rich quality and experience
of a Cisco TelePresence system after its deployment.
The VSAA is composed of central management software, which runs on a Linux server, and a
VSAA (Linux-based) that runs on the laptop platform. The VSAA sends actual Cisco
TelePresence video traffic between agents and it encrypts the data that it generates. There are
16 different profiles by default, each with different resolutions and different durations. Based
on the requirements, you can choose the appropriate profiles to run the tests.
The entire VSAA process has been automated for consistency and productivity. The VSAA
provides numerical results for each source-destination pair that shows latency, jitter, and packet
loss information. The results are easy to read and display in green, yellow, and red against
design thresholds. Modular components are designed for ease of integration into the NPA
report.

VSAA Technical Goals
 Sends actual Cisco TelePresence video streams between agents
– Same bandwidth
– Same burstiness
– Same packet distribution
 Calculates RTP/UDP statistics for
– Jitter
– Packet loss
– Latency
 Is a Client/Server model
– Software on bootable USB drive
The technical goal of the VSAA is to send actual Cisco TelePresence video streams between
agents in the network. These tests are actually conducted between the sites where the Cisco
TelePresence endpoints are to be installed. The VSAA uses the same bandwidth, burst
characteristics, and packet distribution that an actual call would create. The VSAA tool gathers
SLA measurements on jitter, packet loss, and latency to be included in the NPA report, which is
submitted to the customer. The VSAA works on a client/server model using software that is
loaded on a bootable Universal Serial Bus (USB) drive.
VSAA Architecture
 Collects latency, jitter, and packet and frame loss statistics for
Cisco TelePresence streams
 Exports data from the VSAAs to VSAA Central Management
Servers to generate results
Location 1 Location 2
Laptop with Bootable Laptop with Bootabl e

USB VSAA USB VSAA
VSAA Server
Located at
Laptop with Location 3 Cisco
Bootable
USB VSAA Encrypted data to be
uploaded on to the backend
server for results generation
Laptop computers with a 2-GHz CPU or greater and 2 GB of RAM are used with the bootable
USB to run the VSAA tests between endpoints. The VSAA tool creates endpoints on the agents
that launch bidirectional traffic streams. The agents collect actual latency, jitter, and packet and
frame loss statistics for the Cisco TelePresence streams between locations. The VSAAs then
export the data to the VSAA central management servers to generate the results.

VSAA Process Overview
Partner Activities
Analysis and Reporting
Site A Site B
SLA
Si te C Site D Compliance
Collection
Report
 USB collector for
each source-
destination pair
 Traffic data is
encrypted
Network Path Assessment Report
Advanced Services Cisco Web

Portal
 Provides agent software
 Collects data
 Evaluates results and documents
recommendations
 Creates report
Advanced Services provides a VSAA install guide that lists the guidelines for downloading the
software that is required to prepare the bootable USB flash drive. When you log into the partner
portal, you download the software to your laptop, from which you create the bootable USB
flash image. When the USB flash drive preparation is complete, you can reboot the laptop using
the USB and configure the agents and endpoints to run the tests.
The tests collect data, evaluate the results, and document the recommendations. All of the test
results are copied to the laptop where they are uploaded to the Partner Portal. Then Cisco
compiles the SLA compliance report and adds it to the NPA report.
VSAA Sample Summary Report
The figure displays a sample of the VSAA report. The RTP Packet Summary Analysis provides
a summary of the Real-Time Transport Protocol (RTP) statistics for the video RTP stream and
audio RTP stream. The statistics are gathered from sending a “real” Cisco TelePresence stream
across the planned network paths. These statistics are measuring RTP packet to RTP packet and
indicate the latency, jitter, and packet loss at Layer 3 and Layer 4 (IP/UDP).
The tables are color-coded green, yellow, or red to indicate if the specific path characteristics
meet the recommended Cisco TelePresence requirements, fall within an acceptable range, or
exceed the requirements. In the figure, the color-coded tables are shown for end-to-end one-
way latency (ms) for both video and audio RTP streams as well as peak-to-peak jitter (ms).

VSAA Sample Detailed Report
SiteA to SiteB:
 Latency Video Traffic
 Jitter Video Traffic
 Packet Loss
The sample detailed report output in the figure is from the VSAA analysis. It displays the
following three graphs:
 Latency Video Traffic: SiteA to SiteB
 Jitter Video Traffic: SiteA to SiteB
 Packet Loss SiteA to SiteB
VSAA Process Flow Chart for Partners
 Partner Portal: https://ciscotelepresence.webexone.com/
 VSAA Install and User Guide available on Partner Portal
1 2 3 4
Cu sto m er Acc ou nt
Preparation Do wnl oad C ustom er
Sub mi t th e
co m ple ted C PF to
created with in 12 h ou rs;
Pro cu re 4-. 8-, or 16-
GB USB drives
Pro file F orm (CPF ) em ail con fi rm ation sent to
t p-webo ff ice@ b ased on th e
Phase fro m Partne r Po rtal .
c isco .com .
pa rtn er with fu rth er
i nstructio ns.
nu mb er of sites .
5 6 7
Up lo ad te st d ata to Pa rtne r
Data Collection D own lo ad lates t so ftware
on to th e PC/lap top an d
Shi p USB d rives to the cu stom er Po rtal an d em ail to
loca tio n. Co nfig ure ag ents, tp -web o ffice@ci sco. com ;
p rep are b o otab le U SB F lash
Phase Drive.
en d po in ts; run an d ve ri fy tes ts. su bj ect “Cu sto mer VSAA
C aptu re C om pl ete”.
8 9 10 11
C isco verifies files, run s Do wnlo ad VSAA Do wnlo ad fe edb ack form En su re
Report Collection resu lts , p repa res rep o rt, su mm ary repo rt from availab le in the CT S USB flash
a nd u p loa ds to Partn er Po rtal. Rev iew resu lts. Au to m atio n Services d riv es are
Phase Po rtal with em ail F or an y clarifi catio n s, fo ld er; fil l i n an d sen d to shi pp ed
con f irm ation t o Partn er. co ntact C isco . tp-webo ffice@ cisco.co m . back.
LEGEND
Cisco Pa rtn er
The flow chart in the figure shows the VSAA process that partners should follow.
 Preparation Phase
1. Download the Customer Profile Form (CPF) from the Partner portal.
2. Submit the completed CPF to tpweboffice@cisco.com.
3. The Customer Account is created within 12 hours with an email confirmation sent to
the Partner with further instructions.
4. Procure the 8- or 16-GB USB drives based on the number of sites.
 Data Collection Phase

5. Download the latest software to the PC or laptop and prepare the bootable USB flash
drive.
6. Ship the USB drives to the customer location. Configure the agents, endpoints, and run
and verify the tests.
7. Upload the test data to the Partner Portal and send an email to tp-weboffice@cisco.com
with “Customer VSAA Capture Complete” as the subject.
 Report Collection Phase

8. Cisco verifies the files, runs the results, prepares the VSAA Summary report, and
uploads the reports to the Partner Portal with an email confirmation to the Partner.
9. Download the VSAA Summary Report from the portal. Review the results. For any
clarifications, please contact Cisco.
10. Download the feedback form that is available in the CTS Automation Services folder,
complete it, and send it to tpweboffice@cisco.com.
11. Ensure that the USB flash drives are shipped back.

Cisco TelePresence Manager PreQualification
Assistant 1.5
This topic describes the Cisco TelePresence Manager PreQualification Assistant.

PreQualification Assistant 1.5
 The PreQualification Assistant
Release 1.5. is designed to work with
Cisco TelePresence System Manager  LDAP Server
Release 1.5.  Calendar Server
 It performs a series of tests to  Cisco Unified CM
determine if network resources and
services meet the requirements.
 The three network devices being
prequalified are the:
– LDAP server
– Calendar server (IBM Domino, MS
Exchange, or None) configuration
– Cisco Unified Communications
Manager configuration
 Once the tests are run, the results
contain the information needed to
either change the existing
configurations or to configure Cisco
TelePresence System Manager.
The Cisco TelePresence Manager Prequalification Assistant Release 1.5 is designed to work
with Cisco TelePresence Manager Release 1.5. It performs a series of tests to determine if
network resources and services meet Cisco TelePresence System Manager requirements. The
three network devices being prequalified are:
 The LDAP server
 The calendar server (IBM Domino, Microsoft Exchange, or None) configuration
 Cisco Unified Communications Manager configuration
Once the tests are run, the results contain the information that you need either to change the
existing configurations or to configure Cisco TelePresence Manager.
The Test Configuration Forms window presents three areas, selected by individual tabs, for the
LDAP server, Calendar server, and Cisco Unified Communications Manager. The Test
Configuration forms are used to collect the data that is required to run the relevant tests for each
network environment.
The data you enter into the Tool Test Configuration form is used to verify connections to the
servers and retrieve data from them to be used in configuring Cisco TelePresence System
Manager. Each test has a corresponding test results window that displays detailed information
about the test results and a list of recommended actions to fix any problems.
Summary
Summary
 The NPA is a methodology, checklist, and tool set for measuring
the network path between every Cisco TelePresence device and
for validating the required infrastructure services in order to obtain
a release from New Product Hold.
 These tools are used to gather statistics for an NPA: Cisco
TelePresence Codec Call Statistics, Cisco IOS IP SLA, and Cisco
TelePresence Readiness Assessment Manager.
 The VSAA sends actual Cisco TelePresence video traffic between
agents, and it encrypts the data that it generates.
 The Cisco TelePresence Manager PreQualification Assistant
Release 1.5 performs a series of tests to determine if network
resources and services meet Cisco TelePresence System
Manager requirements.

Lesson 6
Using the VSAA

Overview
The success of a Cisco TelePresence system deployment depends on many factors. One of
these factors is the network path assessment (NPA). The best way to ensure that the network
performs up to expectations under real-life network traffic conditions is to monitor actual Cisco
TelePresence traffic. The Video Service Level Agreement Assessment Agent (VSAA) was
developed to run tests by generating actual Cisco TelePresence traffic streams for a proposed
network path and collect data on actual performance characteristics for latency, jitter, and
packet loss.
Objectives
Upon completing this lesson, you will be able to gather traffic statistics between VSAAs. This
 Describe the VSAA
 Configure VSAA bootable flash drives
 Configure VSAAs, run tests on the network, collect the data, and upload the results to the
Cisco Partner portal
What Is the VSAA?
This topic describes how you use the VSAA to measure actual Cisco TelePresence traffic.
What Is the VSAA?

 Provides the proposed Cisco
TelePresence path characteristics
 Provides latency, jitter, and packet
loss measurements prior to
deployment of Cisco TelePresence
 Creates actual Cisco TelePresence
video traffic between agents
 Is an automated process to test for
consistency and productivity
The VSAA provides the characteristics of the proposed Cisco TelePresence system path. It
measures latency, jitter, and packet loss before the deployment of the Cisco TelePresence
endpoints. There are other methods to measure the performance of the network path, but the
data that they collect is not as accurate as the VSAA. The VSAA creates actual Cisco
TelePresence video traffic streams between the agents that are installed on bootable Universal
Serial Bus (USB) flash drives on PCs. The VSAA automates the data collection process for
consistency and efficient productivity. The goal is to perform a network path analysis under
real-life network traffic conditions.
Configuring VSAA Bootable USB Drives
This topic describes how to prepare the bootable USB flash drives that VSAA uses.
Configuring VSAA Bootable USB Drives

 Log into the partner portal.
– https://ciscotelepresence.webexone.com
 Download the file Fedora-10-i686-Live.iso.
 Download the file liveusb-creator-2.7.15.zip.
 Change to the directory in which you expanded the zip file.
Directory of C:\TEMP\liveusb-creator-2.7
08/02/2008 04:39 PM <dir> .
08/02/2008 04:39 PM <dir> ..
07/16/2008 12:19 AM 21,636,661 liveusb-creator.exe
08/02/2008 04:39 PM 59 liveusb-creator.exe.log
05/24/2008 01:36 AM 449,712 MSVCP71.DLL
02/21/2003 04:42 AM 348,160 MSVCR71.dll
08/02/2008 04:31 PM <DIR> tools
02/21/2008 01:11 PM 4,608 w9xpopen.exe
5 File(s) 22,489,200 bytes
3 Dir(s) 47,129,968,640 bytes free
The following instructions describe how to download the software from the Cisco Partner
portal that you will need for the VSAA process. The instructions also describe how to create the
bootable USB flash drive. After you are finished, you will then be able to boot your laptop from
the USB flash drive to collect data.
Follow these steps to create a bootable USB flash drive that is based on Fedora 10 with built-in
persistence.
Step 1 Log into the Partner portal at https://ciscotelepresence.webexone.com/.
Step 2 Use the following path to download the file named Fedora-10-i686-live.iso to your
laptop:
Group Documents > CTS Automation Services > Network Path
Assessment > VSAA Software Images
Note The Fedora-10-i686-live.iso file is 690 MB.
Step 3 Download the file named liveusb-creator-2.7.15.zip to your laptop and unzip the file.
Note You can place both files in the same directory.
Step 4 Open a command prompt window and change to the directory where you expanded
the zip file.

Fedora Live USB Creator
 Insert the flash drive into
the USB port.
 Change to the Tools
directory and execute
HPUSBFW.EXE.
 From the File System list
box, choose FAT32 and
enter KNOPPIX in the
Volume Label field.
 Change to the liveusb-
creator-2.7 directory and
execute liveusb- Fedora10(i686)
creator.exe.
 Browse to the location of
the saved file
(Fedora-10-i686-Live.iso).
 Move the Persistent
Storage slider to 2047 Mb.
Step 5 Insert your flash drive into a USB socket on your laptop.
Note Currently, Cisco supports only 8- and 16-GB flash drives. Although 32-GB drives should
work, 2- and 4-GB drives will probably not have sufficient storage.
Step 6 Change to the Tools directory and execute HPUSBFW.EXE. To execute this
command, you need administrative access to the laptop.
Caution The next step erases the entire contents of the flash drive.
Step 7 Choose FAT32 from the File System list box, and enter KNOPPIX as the volume
label. Ensure that the device shown makes sense, is the correct flash drive, and click
Start. When it has finished, click the Close button to exit the formatter.
Note It takes only a few seconds for the process to finish formatting the flash drive.
Step 8 Change to the liveusb-creator-2.7 directory (up one level from the tools directory)
and execute the liveusb-creator.exe file.
Step 9 Browse to the location where you saved the file (Fedora-10-i686-Live.iso).
Step 10 Move the Persistent Storage slider so it reads exactly 2047 Mb. You can use the
arrow keys to fine-tune the slider until it shows exactly 2047 Mb.
Caution Any value greater or less than 2047 Mb will not work.
Fedora Live USB Creator (Cont.)
 Ensure the proper target
device matches your USB
device and click Create
Live USB.
 After creating the live USB,
close the window and click F edora10(i686 )
OK when you see the error

message.
Step 11 Ensure that the proper target device is shown and that it matches the drive letter of
your USB device and click Create Live USB. You will see a status message like the
following:
Fedora-10-i686-Live.iso selected
Verifying filesystem…
Extracting live image to USB device…
Creating 2047 Mb persistent overlay…
Configuring and installing bootloader…
Complete! (0:06:14)
Note It should take a few minutes to complete.
Step 12 When you have successfully created the live USB, close the Fedora LiveUSB
Creator window. When you close the window, an error message appears. You can
simply ignore the message and click OK.

Completing USB Flash Drive Preparation
 Change back to the tools directory and enter
live-overlayinstaller.exe --out E:
 This completes the USB flash drive preparation.
 Eject the drive.
C:\TEMP\l iveu sb-cr eator-2.7\ tools > li ve-o verlay-installe r.exe –-o ut E:
USB Drive sel ected is drive E:
Found ove rlay file E:/LiveOS /over lay- KNOP PIX-COEB-608D. Size = 21 46435 072
Starting repl aceme nt of live overl ay. This will take a fe w min utes
rawwrite dd f or wi ndows vers ion 0 .5.
Written b y Jo hn Ne wgibin <jn @it.s win. edu. au>
This prog ram is co vered by t he GP L. S ee c opying.txt for detai ls
2,146,435 ,072 100%
2047+0 re cord s in
2047+0 re cord s out
C:\TEMP\l iveu sb-cr eator-2.7\ tools >
Step 13 Change back to the tools directory and enter live-overlay-installer.exe --out E:
(where E: is the target USB device). For example:
C:\TEMP\liveusb-creator-2.7\tools> live-overlay-installer.exe
–-out E:
USB Drive selected is drive E:
Found overlay file e:/LiveOS/overlay-KNOPPIX-C0EB-608D. Size =
2146435072
Starting replacement of liveoverlay. This will take a few
minutes
rawwrite dd for windows version 0.5.
Written by John Newgibin <jn@it.swin.edu.au>
This program is covered by the GPL. See copying.txt for
details
2,146,435,072 100%
2047+0 records in
2047+0 records out
At this point, the USB flash drive preparation is complete. You can eject the USB device or
reboot it. When you reboot, press F12 (this depends on the platform), and check the BIOS
settings for boot options to get a list of boot devices. From here, choose the USB device and
press Enter. The Fedora operating system should then boot.
Caution While booting from the USB flash, you will get a series of pop-up windows. Do not do, or
click, anything until the final blue window with six icons on the left displays. The USB has a
live file system on it and, and like all file systems, it is susceptible to corruption in the case of
a nongraceful shutdown, removal, or power failure. Anything that would normally corrupt a
Linux (or Windows) file system can affect the USB drive.
The VSAA Reporting Process
This topic describes the VSAA reporting process.
The VSAA Reporting Process

 Minimum PC requirements:
– 2 GHz
– 2-GB RAM
– USB Slot
– 1-GB Ethernet port
 VSAA procedure steps:
– VSAA configuration
– IP address configuration
– VSAA endpoints configuration
– Profile ToS configuration
– Sample tests
– Running the tests
– Data collection
Note: Test VSAA on your laptop prior to the customer visit.

The following are the hardware requirements for running VSAA:

 A PC with a 2-GHz CPU or greater
 2 GB of RAM, a USB slot
 A 1-GB Ethernet port to run the tests between endpoints
After the laptop has booted with the USB drive, the VSAA reporting process consists of the
following tasks:
 VSAA configuration
 IP address configuration
 VSAA endpoints configuration
 Profile type of service (ToS) configuration
 Sample tests
 Running the tests
 Data collection
Note Test VSAA for compatibility on your laptop or PC before going out to the customer site.

IP Address Configuration
 DHCP IP addresses
– IP addresses are obtained automatically.
– Use the ifconfig command to view IP addresses.
 Static IP addresses (configured from the Systems menu from Linux GUI)
– Choose Systems > Administration > Network
 Configure eth0 through eth7 with the same static IP address.
 Laptops use different interfaces while booting, so one should be active.
[root@sbigs -lnx5 ~]# ifco nfig

eth0 L ink e ncap :Ethe rnet HWad dr 0 0:C0: F0:7 7:FD:A D
i net a ddr: 172.1 6.2.103 B cast :172. 16.2 .255 Mask: 255. 255. 255.0
i net6 addr : fe8 0::2c0:f0f f:fe 77:fd ad/6 4 Scop e:Lin k
U P BRO ADCA ST RU NNING MULT ICAS T MT U:15 00 Me tric: 1
R X pac kets :9132 40 errors: 230 dropp ed:0 overr uns:0 fra me:2 30
T X pac kets :6639 90 errors: 7 dr opped :0 o verrun s:0 c arri er:1 2
c ollis ions :0 tx queuelen:1 000
There are two ways to configure the IP address of the endpoints.

 DHCP IP address
— The IP address is obtained automatically.
— Use the command ifconfig to see the IP address of the endpoints and to verify that
all of the interfaces are configured correctly.
 Static IP address (configured from the Systems menu from the Linux GUI):
— Choose Systems > Administration > Network.
There are eight interfaces named eth0 through eth7 listed in the dialog box. Configure all of the
interfaces with the same IP address information. You must configure all eight interfaces
because various laptops use different Ethernet interfaces while booting. When the configuration
is completed, shipped to a different location, and started, at least one of the interfaces should be
active.
VSAA Configuration
 After the PC has booted with the USB drive, configure the agents:
– Open the terminal window.
 Become root (su –) and enter password tcp1sc0.
 If accessing remotely, use SSH to log in to the USB drive.
– Configure the NTP Server using the vi editor.
 Enter vi /etc/ntp.conf and comment out existing
servers using hash (#).
 Add server x.x.x.x (where x.x.x.x is the IP address
of an NTP server on the internal network).
 Enter i to start making changes to the file.
 Press Esc, enter :wq, and press Enter.
 Restart the NTP daemon using the service ntpd restart command.
 Enter the command ps -ef | grep ntpd to verify the NTP service is
running.
 Enter ntpdc -s -n and ntpstat to check the status of NTP server
synchronization.
Follow these steps to configure the VSAAs:

Step 1 After opening the terminal window, become root (su-), and enter the password
tpc1sc0. If you are accessing the system remotely, use Secure Shell (SSH) to log
into the USB drive.
Step 2 Configure the Network Time Protocol (NTP) server using the vi editor:
 Enter vi /etc/ntp.conf. Comment out the existing servers using the hash (#) sign
and add ‘server x.x.x.x’, where x.x.x.x is the NTP server on the internal network.
 Enter i to start making changes to the file.
 To save the file, press ESC, enter :wq, and press Enter.
Step 3 Restart the NTP daemon using the service ntpd restart command.
Step 4 Issue the command ps –ef | grep ntpd to verify that the NTP service is running.
Step 5 Use the commands ntpdc –s –n and ntpstat to check the status of the NTP server
synchronization. Ensure that ntpstat shows the synchronized time before you start
the tests.

VSAA Endpoint Configuration
 Vsaa.pl is a tool designed to simplify the creation of endpoints
and launch bidirectional traffic streams.
– /usr/local/mtaa/bin/vsaa.pl
 With no parameters, the following help screen displays:
[root@sbigs-lnx5 ~]# /usr/local/mtaa/bin/vsaa.pl

Adapter eth0 selected for use with MTAA
All mtaa process are up and running
You must provide a -ep1 parameter
/usr/local/mtaa/bin/vsaa.pl –-ep1 endpoint1|ip_address1 -ep2
endpoint2|ip_address2 –tos tos_value –profile profile_name
[-createep][root@sbiggs-lnx5~]#
Vsaa.pl is a tool that is designed to simplify the creation of the endpoints and to launch the
bidirectional Cisco TelePresence traffic streams using the following command:
/usr/local/mtaa/bin/vsaa.pl
Entering the command with no parameters displays the following help screen:
Adapter eth0 selected for use with MTAA
All mtaa process are up and running
You must provide a –-ep1 parameter
/usr/local/mtaa/bin/vsaa.pl –-ep1 endpoint1|ip_address1 --ep2
endpoint2|ip_address2 –tos tos_value –-profile profile_name
[--createep][root@sbiggs-lnx5~]#
VSAA Endpoint Configuration (Cont.)
 Method 1—Use existing endpoint files.
– cd /usr/local/mtaa/etc/endpoints
– There are two sample files:
 Chicago.sample
 NewYork.sample
– cp Chicago.sample <name of new endpoint file>
– Use the ifconfig command to find the ip address of each endpoint.
– Use a file editor to change the IP address and description in the new
endpoint file.
– Repeat these steps for additional endpoints.
 Method 2—No endpoints created.
– Enter the IP address of endpoints followed by –createep.
– /usr/local/mtaa/bin/vsaa.pl -ep1 agent_A_ipaddress -ep2
agent_B_ipaddress -tos tos_value -profile profile_name -createep
There are two methods of operation for vsaa.pl.
Method 1
The first mode uses existing endpoint files, which must exist in the
/usr/local/mtaa/etc/endpoints directory. Follow these steps to create new endpoints.
Step 1 Enter the command cd /usr/local/mtaa/etc/endpoints.
 By default, there are two sample files in this directory: Chicago.sample and
NewYork.sample.
Step 2 Enter the command cp Chicago.sample <name of the new endpoint file> to copy the
example file to a file for a new endpoint.
 Example: cp Chicago.sample SiteA
 Example: cp NewYork.sample SiteB
Note You must create both endpoints on the laptops in both sites.
Step 3 Use the ifconfig command to find the local IP address on each endpoint.
Step 4 Use a file editor to change the IP address and description in the new endpoint file
and save the file. Do not change anything else in the file.
Note You must configure at least two endpoints on the source agent to run a test, one for the
source and one for the destination. The source endpoint is your laptop and the destination is
the remote laptop with which you would like to perform the test.
Step 5 The newly created endpoint should appear in /usr/local/mtaa/etc/endpoints directory.

Ensure that the IP addresses are correct.

Method 2
In this method, there is no need to create the endpoints. You can input the IP address of the
endpoints, followed by the –createep parameter, which will create bidirectional traffic. The
following is an example of the syntax to use when creating endpoints:
 /usr/local/mtaa/bin/vsaa.pl –ep1 agent_A_ipaddress –ep2 agent_B_ipaddress –tos
tos_value -profile profile_name -createep
Profile (ToS) Configuration
 By default, there are 16 profiles with different resolutions and durations.
 Choose appropriate profiles for the tests based on requirements.
[root@localhost ~]# cd /usr/local/mtaa/etc/profiles/
[root@localhost profiles]# ls
cts1000-1080p-best-1hr.txt cts3000-1080p-best-1hr.txt
 View ToS values for a file:
– cd /usr/local/mtaa
– grep Tos etc/profiles/cts3000-1080p-best-1hr.txt
 Configure ToS values during test: (default ToS is 128 if not defined)
– ./bin/vsaa.pl -ep1 agent_A_ipaddress -ep2 agent_B_ipaddress
-createep -tos 123 -profile profile_name [-createep]
By default, there are 16 profiles with different resolutions and different durations. Based on
your requirements, you can choose the appropriate profiles for running the tests on the
customer network. You can also configure the ToS values for the Cisco TelePresence audio and
video traffic by using the following steps:
Step 1 Go to /usr/local/mtaa/etc/profiles to see the files.
[root@localhost ~]# cd /usr/local/mtaa/etc/profiles/
[root@localhost profiles]# ls
Step 2 Follow these steps to see the ToS values for a file:
 cd /usr/local/mtaa
 grep Tos etc/profiles/cts3000-1080p-best-1hr.txt
Step 3 To change the ToS values, you can input the ToS values when you execute the test
using the following command:
• ./bin/vsaa.pl –ep1 agent_A_ipaddress –ep2 agent_B_ipaddress –createep –tos
123 –profile profile_name [-createep]
Note By default, if you do not specify the –tos parameter, it is 128.

Sample Test
 You can run a sample 10-minute test before the actual test.
– ./bin/vsaa.pl -ep1 endpoint_1|ipaddress1 -ep2
endpoint_2|ipaddress2 -tos tos_value -profile cts1000-
1080p-best-10min.txt [-createep]
 Check the size of the file at the end of the test.
– ls -l /usr/local/mtaa/data/crypt_results
– File should be greater than 40 KB after 10-minute test.
 Check whether the set ToS value is what you see at receiver end.
– more log/vsaa-* (where vsaa-* is the latest log file)
– “Getting from sender” should be equal to “Getting from
receiver.”
Before you run an actual test, you can run a sample test using the 10-minute test profile to
ensure that the tests are working properly. Follow these steps to run the sample test:
Step 1 Enter the following commands:
 ./bin/vsaa.pl –ep1 endpoint_1|ip_address1 –ep2 endpoint_2|ipaddress2 –tos
tos_value –profile cts1000-1080p-best-10min.txt [-createep]
Step 2 Check the size of the file at the end of the 10-minute test by entering the command
ls –l /usr/local/mtaa/data/crypt_results.
Note The file size should be greater than 40 KB.
Step 3 Check to make sure the ToS value that you set is what the receiver sees. To check
this, enter the following commands:
 more log/vsaa-*
Note The vsaa-* parameter is the name of the latest log file. The ToS values under “Getting from
sender” should be equal to “Getting from receiver.”
Running the Tests
 Disable the Linux GUI:
– Open the terminal window, become root (su -), and enter the
password tpc1sc0.
– Enter init 3 at the prompt to disable the GUI.
– Verify that the second number of the runlevel command is 3.
– Enter init 5 to re-enable the GUI after the test.
 Execute the actual tests:
– ./bin/vsaa.pl -ep1 endpoint_1|ip_address1 -ep2
endpoint_2|ipaddress2
-tos tos-value -profile profile_name [-createep]
– endpoint_1 and endpoint_2 are the endpoints you created.
– Two tests automatically generate bidirectional traffic.
 When the tests complete successfully, you should see four data files with
a non-zero size in the /usr/local/mtaa/data/crypt_results directory.
Before running the actual test, follow these steps to disable the Linux GUI on each VSAA to
ensure that the test generates accurate results:
Step 1 Open the terminal window, become root (su -), and enter the password tpc1sc0. If
you are accessing the PC remotely, use SSH to log into the USB drive.
Step 2 Enter init 3 at the prompt to disable the GUI.
Step 3 Verify that the second number of the runlevel command is 3.
[root@localhost ~]# runlevel
5 3
Step 4 To re-enable the GUI after the tests, enter init 5.
Note Avoid running any other programs on a VSAA while the tests are running, and always view
the test status from another PC.
Step 5 Enter the following commands to execute the test:

 ./bin/vsaa.pl –ep1 endpoint_1|ip_address1 –ep2 endpoint_2|ipaddress2 –tos
tos-value –profile profile_name [-createep]
Note When the test duration is complete, ensure that the tests were successful. For a one-hour
test, after one hour and two minutes have passed, you should see four data files with a
nonzero size in the /usr/local/mtaa/data/crypt_results directory. The approximate size of the
files in this folder should be around 800 to 900 KB. While the tests are running, the size of
the files will be zero.

Data Collection
 Once tests are complete, log into the USB flash drive using
SFTP or FTP.
– ftp <IP address of endpoint where tests were executed>
– Log in with a username of vsaa and a password of tpc1sc0.
 Go to the results directory and set the FTP transfer mode to binary:
– cd /usr/local/mtaa/data/crypt_results
– binary
 Import the text files to your local machine.
– mget *.*
– When asked to copy the file, enter y and then press Enter.
 Upload the completed test files to the Partner portal.
When the tests are complete, follow these steps to collect the data and upload to the Partner
portal:
Step 1 Log into the USB flash drive using Secure FTP (SFTP) or FTP.
 ftp <IP address of endpoints where tests were executed>
 Log in using the username vsaa and password tpc1sc0.
Step 2 Use the following commands to get to the crypt_results directory and set the FTP
transfer mode to binary.
 cd /usr/local/mtaa/data/crypt_results
 binary
Step 3 Import the text files from this directory to your local machine.
 mget *.*
 Enter y when asked to copy the files.
Step 4 When all of the files have copied to your local machine, you can upload the files to
the Partner portal.
Summary
Summary
 The VSAA provides the characteristics of the proposed Cisco
TelePresence system network path.
 The partner downloads software from the Cisco Partner portal and
configures a bootable flash drive.
 The VSAA reporting process consists of configuring VSAAs with
IP addresses for the various endpoints, configuring a ToS profile,
running tests, collecting data, and uploading the results to the
Cisco Partner portal.

Module Summary
Module Summary
 The different Cisco TelePresence system codecs appear as endpoints in
Cisco Unified Communications Manager. They multiplex RTP video and
audio streams over the network.
 QoS provisioning in a network uses traffic policing and traffic shaping to
avoid bursty traffic.
 Cisco TelePresence relies on QoS IP packet classification and marking.
Cisco has established queuing models for the end-to-end configuration of
network devices to support Cisco TelePresence.
 Converged WAN networks provide the maximum ROI. Cisco has
established W AN and branch bursting policies and models using LLQ
and CBWFQ. Special considerations must be made for MPLS VPN
policies and QoS design for subline access rates.
 The NPA validates the required infrastructure services in order to obtain
a release from New Product Hold. Various tools exist to help perform this
mandatory process.
 VSAA uses Cisco TelePresence traffic to test path characteristics prior to
the deployment of endpoints in the network.
The Cisco TelePresence end-to-end solution, which can use your existing network and service
provider, is comprised of several endpoint models to accommodate many types of meeting
needs. Each of these endpoints has a primary codec device that communicates as a telephony
endpoint from the perspective of the Cisco Unified Communications Manager. The coder-
decoders (codecs) multiplex Real-Time Transport Protocol (RTP) video and audio streams
across the network between endpoints. Designing a converged network solution using the
existing infrastructure is a better return on investment (ROI) than an overlay network solution.
Traffic-policing and traffic-shaping quality of service (QoS) mechanisms are used to limit the
available bandwidth to traffic classes in order to achieve the required QoS that supports Cisco
TelePresence. WAN QoS policies need to be designed and configured on the WAN edges and
branch routers. Ultimately, it is necessary to perform an assessment of the network paths in an
enterprise to support the Cisco TelePresence system. There are specific tools that help you
evaluate network preparedness and service quality for a Cisco TelePresence deployment.
The Video SLA Assessment Agent (VSAA) provides a tool to measure jitter, latency, and
packet loss in a network using Cisco TelePresence traffic streams before deploying the Cisco
TelePresence endpoints.

References
 Cisco Systems, Inc. Campus QoS Design for TelePresence.
http://www.cisco.com/en/US/docs/solutions/Enterprise/Video/tpqoscampus.pdf
 Cisco Systems, Inc. Cisco IOS IP SLAs Configuration Guide
http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/12_4t/sla_12_4t_book.html
 Cisco Systems, Inc. Cisco IOS IP Service Level Agreements User Guide.
http://www.cisco.com/en/US/technologies/tk648/tk362/tk920/technologies_white_paper091
86a00802d5efe.html
 Cisco Systems, Inc. Cisco TelePresence Network Systems 2.0 Design Guide
http://www.cisco.com/en/US/docs/solutions/Enterprise/Video/TP-Book.html
Module Self-Check
Q1) Codec devices communicate and are controlled as SCCP telephony endpoints from the
perspective of Cisco Unified Communications Manager. (Source: Deploying a Cisco
TelePresence Network)
A) true
B) false
Q2) Which of the following is not a valid Cisco TelePresence deployment model? (Source:
Deploying a Cisco TelePresence Network)
A) intracampus deployment model
B) intra-enterprise deployment model
C) intercompany deployment model
D) intercampus deployment model
E) multipoint deployment model
Q3) The best practices for deploying firewalls and ACLs with Cisco Unified
Communications Manager apply to Cisco TelePresence as well. (Source: Deploying a
Cisco TelePresence Network)
A) true
B) false
Q4) The “mean rate” is the number of bytes a router expects to receive over some time
interval (Tc), which is a number of seconds for a given bit rate. (Source: Shaping and
Policing)
A) true
B) false
Q5) Which one of the following is a valid statement? (Source: Shaping and Policing)
A) A Cisco TelePresence System 3000 running at 1080-Best requires 25.3Mb/s.
B) Cameras and codecs operate at 24 f/s, and a frame is produced every 25 ms.
C) A frame can be as large as 75,000 bytes (75 KB) per codec, regardless of the
resolution.
D) Better traffic-shaping increases the chances of exceeding the Bc.
E) Routers (queues and policers) allow some Bc over some Tc, as long as the
burst does not exceed the Bc that provisioned for Tc.
Q6) Traffic-shaping smoothes traffic by storing traffic above the configured rate in a
shaping queue. (Source: Shaping and Policing)
A) true
B) false

Q7) Which one of the following is a valid statement about policing? (Source: Shaping and
Policing)
A) Service providers do not typically use rate limiting to offer customers subrate
access.
B) You can engineer bandwidth so that traffic rates of certain applications or
classes of traffic follow a specified traffic-rate policy.
C) Excess traffic cannot be re-marked to a lower DSCP value before the packet is
sent out.
D) You can configure Cisco class-based traffic policing to mark packets at either
Layer 2 or Layer 3, but not both.
Q8) A benefit of a converged network that carries Cisco TelePresence traffic is that 90
percent of the time Cisco TelePresence will use far less bandwidth than the network is
provisioned for. (Source: Shaping and Policing)
A) true
B) false
Q9) Cisco TelePresence uses variable frame rate codecs that operate at 30 f/s. (Source:
Shaping and Policing)
C) true
D) false
Q10) As of Cisco TelePresence System Release 1.5, which one of the following is not a valid
statement about provisioning for bursts? (Source: Shaping and Policing)
A) Shaping introduces significant jitter and should be avoided.
B) The interface must provide LLQ or CBWFQ with the appropriate burst value
provisioned on the Cisco TelePresence queue.
C) Policing may be done on the aggregate of all traffic classes or on a per-class
basis.
D) Service providers must provision the correct Bc and Tc values to allow for
Cisco TelePresence bursts.
Q11) Which one of the following is a true statement about how network latency, jitter, and
loss are measured? (Source: Setting a QoS Policy)
A) Latency and loss are measured at a packet level that is based on RTP header
sequence numbers and timestamps.
B) Each codec measures outgoing RTP traffic unidirectionally.
C) Jitter is measured at a packet level, not a video frame level.
D) As far as jitter is concerned, there is no difference between packet and video
frames.
Q12) Given the circumference of the earth, the speed of light, and the cabling paths that light
travels on between cities, it is not always possible to achieve 150 ms between any two
points on the globe. (Source: Setting a QoS Policy)
A) true
B) false
Q13) Based on Cisco TelePresence System Release 1.5, match the first half of each latency
and jitter statement with the appropriate second half. (Source: Setting a QoS Policy)
A) When network-level latency exceeds 250 ms averaged over any 10-second
period,
B) When latency exceeds 400 ms averaged over any 10-second period,
C) Whenever a satellite endpoint joins a meeting,
D) If incoming jitter exceeds 125 ms,
_____ 1. no action is taken.
_____ 2. the jitter buffer is reset to 165 ms.
_____ 3. an on-screen message is displayed to the user.
_____ 4. the jitter buffer is dynamically adjusted up to 165 ms.
Q14) Based on Cisco TelePresence System Release 1.5, match the first half of each packet
loss statement with the appropriate second half. (Source: Setting a QoS Policy)
A) When packet loss exceeds 1 percent averaged over any 10-second period,
B) When packet loss exceeds 10 percent averaged over any 10-second period,
C) If loss (or late packets) exceeds 10 percent averaged over any 60-second
period,
D) Whenever a satellite endpoint joins a meeting,
_____ 1. an on-screen message is displayed to the user.
_____ 2. no action is taken.
_____ 3. the system will downgrade the quality of its outgoing video.
_____ 4. an on-screen message is displayed to the user unless the hold timer is
already in effect.
Q15) Cisco TelePresence reduces the frame rate to compensate for motion, whereas other
video conference vendors keep the frame rate at 30 f/s regardless of motion. (Source:
Setting a QoS Policy)
A) true
B) false
Q16) You should limit the amount of real-time voice and video traffic to 25 percent of the
link capacity. (Source: Setting a QoS Policy)
A) true
B) false
Q17) Cisco uses a separate marking scheme to classify TelePresence traffic in order to
distinguish it from other forms of real-time traffic. (Source: Setting a QoS Policy)
A) true
B) false
Q18) You should trust DSCP and not CoS because marking granularity is increased every
time that a node is set to trust CoS. (Source: Setting a QoS Policy)
A) true
B) false

Q19) Which one of the following statements is true? (Source: Designing WAN and Branch
QoS Policies)
A) A converged network uses your existing network and service provider
connection to extend Cisco TelePresence meetings beyond your enterprise
boundary.
B) Using a converged network is the quicker tactical option. It is easier and
cheaper in the short run.
C) For some customers, the choice may be to use the converged network design
now and overlay when they are ready.
D) There is less concern for the impact on the current network when using a
converged network, and relaxed network design guidelines can be used.
Q20) Overlay networks are recommended for a Cisco TelePresence deployment to maximize
the ROI. (Source: Designing WAN and Branch QoS Policies)
A) true
B) false
Q21) When it comes to subline rate or shared service, the service provider is typically unable
to modify their Bc and Tc values to accommodate telepresence traffic. (Source:
Designing WAN and Branch QoS Policies)
A) true
B) false
Q22) More than one low-latency queue can be provisioned; one low-latency queue can be
provisioned for voice and another for telepresence traffic. (Source: Designing WAN
and Branch QoS Policies)
A) true
B) false
Q23) By default, queuing policies do not engage at subline rates. To ensure that transmission
rates do not exceed the contracted rate, a shaper must be used. (Source: Designing
WAN and Branch QoS Policies)
A) true
B) false
Q24) Customers are not allowed to use a service provider that is not a member of the Cisco
Certified TelePresence Connection. (Source: Designing WAN and Branch QoS
Policies)
A) true
B) false
Q25) Match the following NPA categories with one or more of the individual tasks. (Source:
Understanding the NPA)
A) NPA discovery phase
B) gap analysis
C) recommendation
_____ 1. remediation
_____ 2. path measurement
_____ 3. detailed NPA questionnaire analysis
_____ 4. infrastructure assessment
_____ 5. path characteristics analysis
Q26) Match the following NPA terms with the appropriate definition. (Source:
Understanding the NPA)
A) Customer Requirements Validation
B) Detailed Design
C) Network Implementation Plan
D) Preimplementation Checklist
E) Acceptance Test Plan
_____ 1. Verify that the room and network have been completed to satisfaction
before implementation.
_____ 2. Verify the implementation of the critical features and functionality of the
Cisco TelePresence system specific to the customer environment.
_____ 3. Document and communicate the Cisco TelePresence feature and
functionality requirements to the customer.
_____ 4. Document interfaces between various Cisco TelePresence solution
components.
_____ 5. Document critical information and steps necessary for the successful
deployment.
Q27) VSAA measures latency, jitter, and packet loss of actual Cisco TelePresence traffic
after the deployment of the endpoints. (Source: Using the VSAA)
A) true
B) false
Q28) The Fedora Live USB Creator will erase the entire contents of your flash drive and
create a bootable Windows image. (Source: Using the VSAA)
A) true
B) false
Q29) Which one of the following does not meet the hardware requirements for a laptop
running VSAA? (Source: Using the VSAA)
A) 2 GHz
B) 2-GB RAM
C) USB slot
D) 100-Mb Ethernet

Q1) B
Q2) D
Q3) A
Q4) B
Q5) E
Q6) A
Q7) B
Q8) A
Q9) B
Q10) A
Q11) A
Q12) A
Q13) 1-B
2-C
3-A
4-D
Q14) 1-A
2-D
3-B
4-C
Q15) B
Q16) B
Q17) A
Q18) B
Q19) A
Q20) B
Q21) A
Q22) A
Q23) A
Q24) B
Q25) 1-C
2-A
3-B
4-A
5-B
Q26) 1-D
2-E
3-A
4-B
5-C
Q27) B
Q28) B
Q29) D


Implementing Cisco TelePresence Vol1

Uploaded by

Copyright:

Available Formats

You might also like

Implementing Cisco TelePresence Vol1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Implementing Cisco TelePresence Vol1

Uploaded by

Copyright:

Available Formats

ITS

Text Part Number: 97-2994-01

Cisco Systems Learning

Learner Skills and Knowledge

Learner Skills and Knowledge

© 2011 Ci sc o Sy s tems, Inc . All rights reserv ed. ITS v1.1—3

“Design, deploy, and support the Cisco

Implementing Cisco TelePresence Solutions

© 2011 Ci sc o Sy s tems, Inc . All rights reserv ed. ITS v1.1—4

© 2011 Ci sc o Sy s tems, Inc . All rights reserv ed. ITS v1.1—5

© 2011 Cisco Systems, Inc. Course Introduction 3

© 2011 Ci sc o Sy s tems, Inc . All rights reserv ed. ITS v1.1—6

Cisco Icons and Symbols

© 2011 Cisco Systems, Inc. Course Introduction 5

© 2011 Ci sc o Sy s tems, Inc . All rights reserv ed. ITS v1.1—8

Prepare to share this information:

Exploring the Cisco

© 2011 Cis co S ys t em s, I nc. A ll rights res erved. IT S v1.1—1-2

The term telepresence is an industry-accepted definition of technologies that allow participants,

Traditional Video Conferencing

© 2011 Cis co S ys t em s, I nc. A ll rights res erved. IT S v1.1—1-3

© 2011 Cisco Systems, Inc. Introduction to Cisco TelePresence 1-5

Primary Attributes of Cisco

© 2011 Cis co S ys t em s, I nc. A ll rights res erved. IT S v1.1—1-4

© 2011 Cis co S ys t em s, I nc. A ll rights res erved. IT S v1.1—1-5

© 2011 Cisco Systems, Inc. Introduction to Cisco TelePresence 1-7

© 2011 Cis co S ys t em s, I nc. A ll rights res erved. IT S v1.1—1-6

By adhering to the original primary attributes of Cisco TelePresence during product

Cisco TelePresence Endpoint

© 2011 Cis co S ys t em s, I nc. A ll rights res erved. IT S v1.1—1-7

© 2011 Cisco Systems, Inc. Introduction to Cisco TelePresence 1-9

© 2011 Cis co S ys t em s, I nc. A ll rights res erved. IT S v1.1—1-8

Advantages of Cisco TelePresence

Cisco supplies the high-end technology, but the room

Customers can create a personalized Cisco

A broad range of aesthetic direction is available

Rooms integrate and blend with the corporate look

© 2011 Cisco Systems, Inc. All rights reserved. ITS v1.1—1-9

© 2011 Cisco Systems, Inc. Introduction to Cisco TelePresence 1-11

Shaping the Future of the Internet

© 2011 Cis co S ys t em s, I nc. A ll rights res erved. I TS v1. 1— 1-10

Requirements for Cisco TelePresence

© 2011 Cisco Systems, Inc. Introduction to Cisco TelePresence 1-13

What Is the NPA?

Network Discovery Gap Analysis Remediation and

© 2011 Cisco Systems, Inc. Introduction to Cisco TelePresence 1-15

Exploring the Cisco

The Cisco TelePresence Solution

• Next-generation multipoint switching

Management • Cisco Unified Communications Manager

As a breakthrough technology for remote meetings, Cisco TelePresence integrates advanced

Cisco TelePresence comes to market with a wide product breadth:

© 2011 Cisco Systems, Inc. Introduction to Cisco TelePresence 1-19

Cisco TelePresence Cisco TelePresence

© 2011 Cis co S ys t em s, I nc. A ll rights res erved. IT S v1.1—1-3

Interoperability with standards-based video conferencing allows Cisco TelePresence endpoints

© 2011 Cisco Systems, Inc. Introduction to Cisco TelePresence 1-21

Cisco TelePresence Endpoint Portfolio

Cisco Cisco Cisco Cisco Cisco