This book is designed to provide information about the CCNA Collaboration CICD exam (). . viii CCNA Collaboration CICD Official Cert Guide. CCNA Collaboration CIVND Official Cert Guide BRIAN MORGAN, the exam is contained in a PDF document on this book's companion website. Research all CCDP, CCNA Routing and Switching, CCNA Security, CCNP Collaboration, CCNP Data Center, CCNP Routing and Switching.
|Language:||English, Spanish, French|
|Genre:||Business & Career|
|ePub File Size:||26.36 MB|
|PDF File Size:||18.53 MB|
|Distribution:||Free* [*Regsitration Required]|
This book is designed to provide information about the CCNA Collaboration Every effort has been made to make this book as complete and as accurate as. CCNA Collaboration CICD Official Cert Guide By Michael Valentine Published Oct 15, by Cisco Press homeranking.info KB. Tags 0. Does Cisco Press make large print books?. CCNA Collaboration CICD Official Cert Guide from Cisco Press enables you to succeed on the exam the first time and is the only self-study resource approved by Cisco. CCNA Collaboration CICD Official Cert Guide is part of a recommended learning path from Cisco that.
The rest of the collaboration solu- tion components are in the provider cloud infrastructure. Regardless of the strategy you use or the background you have, the book is designed to help you get to the point where you can pass the exam with the least amount of time required. To some degree, all three of these venues overlap. Outside of this program, his daughter is getting into software design, and his son is taking courses through North Carolina State University called Young Engineers, offered for children between 12 and 18 years of age, where he is furthering his IT skills. The lack of standards-compliant media was a huge challenge in attempting to make use of this kind of technology. Each server held a different library of content and, therefore, had to be accessed independently.
Material is presented in a concise manner, focusing on increasing readers retention and recall of exam topics. Readers will organize their exam preparation through the use of the consistent features in these chapters, including: This tool allows the reader to quickly review the most important details in each chapter.
Readers will be instructed to review key topics from the chapter, complete tables and lists from memory, and define key terms. SlideShare Explore Search You. Submit Search. Successfully reported this slideshow. We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime. Upcoming SlideShare. Like this presentation? Why not share! An annual anal Embed Size px. Start on. Show related SlideShares at end.
WordPress Shortcode. Published in: Full Name Comment goes here. There is quite a bit more that goes on with CUCM, in particular. From a video architecture perspective, CUCM provides the common platform for voice and video endpoint registration and management.
This includes soft phone, desk phone, desktop video endpoints, and immersive TelePresence endpoints. Cisco has made great strides in consolidating all elements into a single call control entity to ease overall admin- istration tasks. This allows a single pane of glass for call control and for IM, network-based presence, federation, and the use of Cisco Jabber on desktop and mobile devices.
Endpoints There has been a slight shift in nomenclature as it pertains to collaboration architecture. Where the collaboration architecture used to reference phones and calls, it now references endpoints and sessions. An endpoint is no longer necessarily merely a phone. The endpoint may be any phone or video device in the Cisco portfolio, be it a , , DX80, or MX From an administrative perspective, they are all identical in how they are config- ured in CUCM.
That said, a call is no longer necessarily audio only. The term session pro- vides a more generic descriptor while carrying the same essential connotation.
With the diversity of the endpoints available comes a diversity in features that each may access and use. With call control and endpoints in play, the remaining pieces of the archi- tecture provide modularity in functionality. Whereas call control provides a foundation, endpoints provide a means of accessing the wide array of services and applications available within the remaining architectural components.
The endpoint is the face of the system as it provides the user experience. If the endpoint is difficult to use or complicated to deploy, there may be a high potential for adoption and growth problems. Conferencing A conference is loosely defined as three or more people communicating in real time. This is a core capability of legacy voice deployments and video deployments. The ability to communicate only via point-to-point video will have a negative impact on adoption of the technology. If video is the new way, it needs to function in a similar manner to the old way, with very little, if any, learning curve.
Conferencing capabilities build upon the existing infrastructure for point-to-point calls. For multiparty calls, additional resources will be required. The idea, however, is to offer the same ease of use and consistent experience regardless of how many individuals are in attendance.
This is accomplished by positioning the right components within the network. These components are sized based on usage expectations and user habits. As adoption grows, it may well become necessary to expand the resources available for conferencing.
Conferences can be classified into three types: This is a conference that is not scheduled. It begins as a point-to-point call. Once established, one party or the other adds additional participants. Formerly known as a rendezvous bridge, personal meeting rooms are static meeting spaces defined on a per-user basis.
These rooms can be allocated to executives, power users, or anyone else who requires it. Introduction to Video Communications 11 the pilot phone number and entering the meeting number. Other terms 1 that might describe a personal meeting room include meet-me and static bridges.
A conference call planned in advance. The start time and resources needed are set ahead of time. For scheduled conferences, generally, the required confer- encing resources are reserved and guaranteed available at start time. As noted in Figure , conferencing uses the Conductor and TelePresence server. The Conductor coordinates resources for conferences.
Collaboration Edge Businesses have long struggled to find the most efficient way to provide secure, reliable ser- vices to their user communities working outside of the traditional office setting. The bring- your-own-device BYOD movement has done little more than increase the pressure to find innovative access methodologies which provide the necessary access to services and applica- tions while aligning to business and security policies.
Collaboration edge is a new implementation of an existing technology, firewall traversal. The solution consists of two core components: Expressway-E and Expressway-C. Expressway-E acts as a traversal server for external clients, video endpoints, and so on. It will be the device also in charge of handling B2B calls and cloud connectivity WebEx.
Expressway-C acts as the traversal client. It creates outbound connections to the Expressway-E and therefore through the firewall without need to open specific ports.
The firewall traversal mechanism opens a connection through the Expressway-E, across the firewall to the Expressway-C, and then on to the other relevant components as requested by the mobile client. In Figure , the architecture shows the Expressway-C on the internal network; the Expressway-E sits in the demilitarized zone DMZ to handle external requests coming in.
When the user launches a client from a mobile device or laptop, the DNS lookup resolves the records for services required by the client application and makes contact.
Registration is processed, and the user is able to log in successfully. It is suggested that the Expressway-E and Expressway-C be deployed in a highly available configuration that is, in clustered pairs. This ensures that services are always available even when there may be network-related issues in progress. The collaboration edge architec- ture also enables native interoperability with Microsoft Lync audio and video. This allows Expressway-C to support standards-compliant H.
Applications Applications available for end users are numerous. However, the applications that apply here are those mentioned in the video architecture. Cisco Prime Collaboration is a suite of applications that allow provisioning, deploy- ment, monitoring, management, and measurement of collaboration-related metrics. It can provide a one-jump path for CUCM migration from very old versions to the latest version.
It makes the needed changes throughout the cluster. PCP is a provisioning tool that allows the creation of business rules and work flows that allow for zero-touch deployment of new users, their endpoints, clients, and voice mailbox- es. It imports them into the database and provisions all the configured services for a user of that type and in that location. It all comes down to work flows and the desired degree of granularity.
PCA is the monitoring, troubleshooting, and reporting module of the Prime Collaboration suite. It keeps constant track of the processes, services, call quality, and so on, just as a tradi- tional network management suite might do. However, it is monitoring metrics such as jitter, mean opinion score MoS , and more for voice and video calls. Introduction to Video Communications 13 Summary Video is indeed the new dial tone.
Video technologies are seeing expansive growth on all 1 fronts, be it consumer, personal, desktop, immersive, conferencing, B2B, or any other of the implementation types you might think of. People are simply coming to expect to be able to make eye con- tact in any conversation regardless of device, distance, or circumstance.
The Cisco Preferred Architecture for Video guide details the basics of the architectures and what is needed to implement the capabilities discussed both in that document and in this book. This chapter addressed only the high-level video architecture and its core constituent components. It is highly recommended that anyone seeking a collaboration certification be familiar with the Cisco Preferred Architecture documents and the architectures they describe for the certification pursued.
Exam Preparation Tasks This chapter provided an overview of the architecture and components contained in the core Cisco video architecture. The information presented here is not included in the exam blueprint. Therefore, it is unlikely that you will encounter it on the exam itself.
However, the information presented in this chapter is part of a prescriptive best practice for video architecture. It is necessary information for deploying and managing Cisco video solutions. This chapter covers the following topics: This section provides an overview of the evo- lution of digital media as a viable form of content delivery over recent decades.
This section discusses the Cisco Digital Media Suite solution, including high-level architecture and the individual components therein. This section briefly overviews the content capture, transcoding, and publication using the DMS architecture, along with optimiza- tion capabilities.
DMS is a video content creation, editing, transformation, and delivery architecture intended for use in a variety of manners, including education, sport stadiums, restaurant menus, staff training, and as many other uses that a moderately active imagination might contrive. Every question deserves an answer. In addressing that simple question, it is necessary to understand, at least in part, the roots of the technology. With that in mind, a small discussion of history is in order, followed by a more lengthy discussion of the DMS solution and its constituent components.
Like many architectural solutions, DMS consists of a number of software and hardware components, each dependent on one another. They, in turn, make use of the underlying network and collaboration infrastructure. As the name implies, DMS is a video-based solu- tion.
As such, its traffic must be properly protected and prioritized throughout the network. A well-designed quality of service QoS deployment is critical to the success of any video implementation. Although QoS is beyond the scope of this chapter, it is well worth explor- ing and understanding. For more information on QoS, check out the following sites: Giving yourself credit for an answer you correctly guess skews your self-assessment results and might pro- vide you with a false sense of security.
By what means was content distribution accomplished in legacy architecture? Dynamic distribution using network-based architecture b. Manual distribution c.
Proprietary distribution methodologies d. Distribution via standards-based protocols 2. In legacy architecture, early content portals were constructed using what resource?
Intranet resources including internal servers, simple web pages, and wiki pages b. Internet resources including hosted servers and network services c. Digital media architecture solutions d. Multicast network protocol capabilities 3. Which Cisco DMS component is used for content recording? Cisco Cast b. Cisco TCS c. Cisco DMM d.
Cisco DMP 4. Which of the following Cisco DMS components is used as a centralized application for managing, scheduling, and publishing content? Cisco TCS b. Cisco DMM c. Cisco Cast d. Cisco Digital Media and Content Delivery 17 5. Which Cisco DMS component is used in transcoding recorded media content? Cisco MXE b. Cisco Cast c. Cisco DMP d. Cisco TCS 2 6. Which Cisco DMS component is used in controlling playback of digital media? Cisco DMM 7. Among the services offered by the Cisco Capture Transform Share solution is which of the following?
Videoconferencing b. Video on demand and streaming c. WAN optimization d. Audio conferencing 8. ECDS is a solution that provides which of the following benefits? Video on demand capabilities b. Audio conference resources c. Content distribution management d. Initial systems were watch-only systems; they lacked any capability to record and store the images being collected.
This meant that someone had to be physically watching the screens at all times. As the technologies advanc- ed, recording capabilities for audio and video started to be implemented and used. These systems were adapted for use in delivering content to televisions stationed throughout office buildings, plants, and so on.
This could be used to deliver morning news relevant to the business, announcements, and so on. These systems were not attached to any external content provider, of course. All content to be presented was largely created and sourced by the entity owning the system. Over time, recording capabilities evolved from reel-to-reel systems to the videocassette recorder VCR and then on to network-based storage capabilities.
These network-based capabilities were often server-based solutions that would store content on local hard disks then push it out across a private network to proprietary display systems. With the coming of applications such as Microsoft PowerPoint and other slide-show- capable software packages, digital signage became a viable capability.
These architectures were typically built upon PC-based platforms. Those PCs would be network attached in order to provide remote management and content access.
They would also provide the interface to keyboard, mouse, and monitor to make local tweaks to and display the created content. The PC-based architecture has a number of significant drawbacks that really prevented its widespread use for dedicated digital signage. The cost of PC hardware, certainly, was one significant limiting factor. In addition to these, the fact that many early solutions were proprietary meant that there could only be one source of content in specific formats for the solution.
The lack of standards-compliant media was a huge challenge in attempting to make use of this kind of technology. The fact that many systems were closed and proprietary is no surprise. Innovation waits for no one. These types of systems were needed by businesses for a number of reasons.
And, they were needed right now. The business world had no time to wait for the battles to be won and lost in order to implement the systems they needed for security, content hosting, and content delivery.
Where there is a need, there is going to be someone smart enough to meet it and capitalize on it. Chapter 2: Cisco Digital Media and Content Delivery 19 Cisco has done much of that type of innovation over the three decades of its existence.
No standard existed to fill the needs demanded by businesses. So, Cisco created a temporary solution while the relevant standards were being ratified and put in place.
Once the respective standards became a reality and ready 2 for prime time, Cisco instituted a technology migration to those standards. ISL gave way to Cisco PoE has become Streaming Video Providing access to streaming video in legacy environments was similarly fraught with chal- lenges.
Again, the problem largely goes back to proprietary formats and the absence of viable standards in video creation, encoding, transport, and delivery. During this time in the evolutionary stage of video streaming, the world was still largely server-based, rather than network-based. So, in the minds of many, servers were the network.
The media and proto- cols used in making the servers communicate was largely irrelevant. No one single protocol had yet won the day, so to speak. At the same time, Ethernet had a number of available flavors and competing technologies. Ethernet eventually won that battle as well.
But, it is worth keeping in mind that the technologies in use in the s were a wild mix of Layer 1, Layer 2, and Layer 3 protocols as numerous communications methodologies fought for survival.
The video battle still rages to a large degree, of course. But, it too will be settled in due time. With all the chaos in the industry, content distribution was almost entirely manual. That is, the content had to be pushed by an administrator to a server somewhere, which is then made accessible to the PC end stations actually presenting the content.
In many architec- tures, administrators were required to manually push the content to each local PC. It all came down to just how network aware the proprietary application in use happened to be. The use of web-based services with audio, video, and other content overlay is quite new on the scene. The use of multicast technologies became a prevalent delivery mecha- nism during this time.
All these content sources could be pushed through a video encoder and onto the IP network. However, these feeds could not typically be easily stored or archived, nor could they typi- cally be deployed in a mixed-vendor endpoint environment. This was the case even once standards-compliant streaming protocols, formats, and clients were in play. Content Portals In the pre-YouTube world, video distribution technologies presented more challenges than solutions, it seems.
During the early evolutionary phases of content distribution technolo- gies, ease of use was not all that high on the list. The proper use of video still required an IT personnel resource.
Those user-facing tools that were available were somewhat less than intuitive. As the concept of the intranet came about, network administrators began to push more and more of the capabilities out to the user community. In most cases, this amounted to a simple web page format or a wiki-type blog format that presented links to the video files and hopefully some kind of description of the file content. As the user clicked each link, the files could be accessed and downloaded. There was no means of simply embedding the video into the web page to be streamed from a central location.
Resources were largely decentralized at this point. Once downloaded, a client installed on the desktop could then be used to play each file individually. It was not unusual for a separate desktop client to be needed for each type of video format to be played.
Although the use of intranet services and wikis did offer a more streamlined means of pro- viding content, it did not allow users to share content. In many cases, they were not allowed to upload their own content either. Each server held a different library of content and, therefore, had to be accessed independently. This limits user interactivity, sharing, and con- tent upload.
There are obvious needs for security and protection of confidential information, of course. Those security mechanisms are certainly in place. User interfaces for these content portals are intuitive and support a wide range of software clients and hardware platforms, both static and mobile. These services are intended to provide anytime, anywhere, any device support for all content relevant to the business.
Cisco Digital Media and Content Delivery 21 Cisco Digital Media Suite In DMS, Cisco provides a comprehensive set of tools that enable companies to create flex- ible, scalable, and easily accessible content for end users, departments, peers, customers, and more. Making the integration of digital media into the day-to-day business 2 flow enhances communication and changes the way we collaborate and interact with our peers, colleagues, and others.
Like any other architecture, DMS includes a number of modular components. This modular- ity allows the creation of a custom-tailored solution based on the business needs at the time of deployment and the ability to grow, and add additional modules, as desired. The subsys- tems of the DMS solution are as follows: Enables users to create live and on-demand content using social media aspects such as tagging, commenting, and rating Each of these subsystems is discussed in later in this chapter.
DMM is a cen- tralized web-based management portal through which all products can be administered. The DMM is also used in managing, scheduling, and publishing digital media content. Figure shows the core components of the Cisco DMS solution.
Clicking the Administration tile on the home page brings you to the Dashboard. The Dashboard provides a summary of DMPs in inven- tory, Show and Share server status, in addition to failover, clustering, and so on. Figure shows the DMM Dashboard page. Along the top row of the page are additional tabs for configuration of the system and its controlled subsystems.
Users can be assigned to groups and roles specific to their function, be it admin, read-only, digital signage users, and so on. This administration portal is the heart of the DMS solution. It is where configuration and troubleshooting take place, ser- vices are stopped and started, licensing is applied, and so on. The file is uploaded via the Browse button. Once uploaded, a title is given to the video. Optionally, a description and tags can be added followed by a click of the Next button.
With that done, the output formats need to be selected. Figure shows the output format selection page. What is shown in the figure is only a subset of the available options. Once you select the desired output formats and click the Next button, additional enhancements become available. Figure shows the options avail- able to enhance the video.
Once the video is selected and configured, you can preview the video and make changes if so desired. After all options are satisfactorily chosen, you can convert the video into the selected formats. Figure shows the job status page. Each format will have a sub- mission date and time and a status. When each one completes, a link becomes available to download it or stream it, as permitted by the format.
SnS provides the following functions and features: This allows content to be published from SharePoint to SnS. It also allows the user to surface all video from SnS directly in SharePoint. In addition to allowing for viewing of videos, it allows posting of comments directly from SharePoint. As might be expected, the solution provides for video on-demand and video-streaming services. For recording, the solution uses TCS. To end recording, simply hang up the call.
Once the call is dropped, the workflow kicks in. The recording is pushed to the MXE for transcoding to any desired format and optimized for numerous playback devices.
The layout can be customized based on the type of device or media format. With that complete, the content can be pushed automatically to the SnS portal or held for approval. Additional options can be added, such as bumpers, watermarks, or Pulse Analytics.
Pulse Analytics is a speech- and voice-recognition mechanism that transcribes audio to text and identifies speakers in recorded content. Once a speaker is named, it will remember that speaker for future content publications. Once Pulse Analytics has completed processing a particular video, the text of the audio is available to those viewing the content.
Spoken words are associated with individual speakers and made searchable. If the keywords were spoken during the class session, each instance will be returned along with actionable links to the specific point in the discussion where the keyword occurs and who spoke the word. This section covers the evolution of video surveillance from the early CCTV monitoring systems to the IP cameras in use today.
This section covers the hardware and software products of the Cisco video-surveillance solution. This section provides an overview of Cisco cameras and analytics, Cisco video-surveillance management software, and the Cisco media management and storage components. Most people assume that means video communications exclusively. However, Cisco has many prod- ucts in other venues of video, like IP video surveillance and digital signage. To some degree, all three of these venues overlap.
However, each can stand independently from the others as well. This chapter offers a high-level overview of the solution Cisco offers in IP surveillance.
The first section reviews legacy closed-circuit TV CCTV video-surveillance architecture and how it has evolved into what is available today. In a traditional video-surveillance solution, what product is used to allow multiple cameras feed to display on a single monitor?
CCTV b. Multiplexer c. Multicast d. VHS recorder 2. As the traditional video-surveillance solution evolved, what product was developed that increases the capacity of recordable storage? VHS recorder b. Encoders c. DMPs d. DVRs 3. What product allows for Cisco Physical Access Gateway devices to connect conven- tional wired sensors, along with other physical-security elements, through a converged IP network? The Cisco Physical Access Manager appliance c.
Cisco VSM d. Cisco Video Surveillance Multiservices Platform 4. What Cisco product is a complete IP-based dispatch and incidence-response solution?
Cisco Video Surveillance Manager d. Cisco Video Surveillance 39 5. What Cisco product is used to leverage analog video cameras in an IP video- surveillance deployment? VSM b. ISR c.
Encoders d. Decoders 6. Which Cisco product is responsible for changing layouts that are displayed on the 3 viewer portal stations? Cisco Video Surveillance Manager b.
Cisco Video Media Server Software c. Cisco Video Operations Manager Software d. Cisco Video Virtual Matrix Software 7. Which Cisco product is responsible for sending video feeds to storage and viewer portal stations? Cisco VSM b. Cisco Video Virtual Matrix Software 8. Which Cisco product is responsible for interacting with the video-surveillance software through a web portal?
Cisco Video Virtual Matrix Software 9. Which Cisco product allows for up to 1 TB of storage for video-surveillance feed? Cisco Video Surveillance Multiservices Platform b. Cisco Integrated Services Router Generation 2 c. NAS d. Cisco Video Surveillance 43 A Cisco end-to-end solution can be broken down into three categories: Such services may include door sensors and badges, fingerprint scanners or other biometric sensors, video-surveillance monitoring software, and other media management and stor- age components.
All three of these services work together to offer a complete and highly effective Cisco video-surveillance solution. Cisco Video-Surveillance Components The remainder of this chapter covers Cisco cameras and analytics, Cisco video-surveillance management software, and the Cisco media management and storage components.
The Cisco video-surveillance solution can be divided into four service domains: This chapter does not go into microphones and motion sensors in a Cisco video-surveillance solution. Management elements include features like central management of previously mentioned devices, operations like PTZ and camera switching, media control, distribution, and layout changes.
Management can also determine where recorded media is to be stored. Storage involves compressing media when needed and using scalable storage solutions, whether that be locally attached storage or a network- attached storage NAS or storage-area network SAN. Interactive view elements monitor endpoints such as operator view stations. It also contains distribution elements notifications and media store distribution. Cisco IP surveillance cameras also include embedded security and networking, motion detection, and video analytics.
As mentioned before, Cisco Medianet offers the features PoE, automated provisioning, bandwidth optimization, storage optimization, and enhanced network security. Each has different capabilities to cater to the various needs of the customers. Some come in a box model, and some come in the dome model. The series comes in both box and dome models. Figure shows box and dome cameras. It is an outdoor fixed HD camera in vandal-resistant housing. This series offers excellent image quality with resolutions up to x and PTZ support.
These cameras can be used indoors or outdoor and support up to p30 resolutions. These dome IP digital cameras are designed for superior performance in a wide variety of video-surveillance applications.
These dome cameras can support resolutions up to x at 30 frames per second. Cisco PTZ IP cameras can be remotely controlled to monitor a wider area than traditional fixed cameras.
Table compares each of the camera series mentioned. These devices use digital signal processors DSPs to convert analog signal from legacy analog cameras to digital format. This includes third-party IP sur- veillance cameras and legacy analog cameras through encoders. Also, Cisco IP surveillance cameras are supported by third-party management software, as well.
These software components of the VSM are the three management software solutions that are discussed in this section. The Cisco Video Surveillance Media Server software is the core component of the network- centric Cisco video-surveillance solution. This software is responsible for the record- ing, storing, and streaming of video feeds. This software is responsible for simultaneously distributing live and archived video streams to viewers over an IP network.
In case of multiple view requests, the software rep- licates the unique input video streams to multiple output streams, based on request.
For archive viewing, the Cisco Video Surveillance Media Server continuously receives video from the IP camera or encoder, as configured per the archive settings.
The software sends video streams to the viewer only when requested. In environments with remote branch locations, this process becomes efficient because traffic needs to traverse the network only when requested by remote viewers. It offers centralized administration of all the Cisco video-surveillance solu- tion components and supports Cisco video-surveillance endpoints.
For security purposes, it uses authentication and access management for video feeds. Application programming interfaces APIs can be used for third-party integration, and third-party camera and encoder support is provided. Tools available in the Cisco Video Surveillance Operations Manager include a web-based portal that can be used to configure, manage, display, and control video from any Cisco surveillance camera or encoder.
Many third-party endpoints are sup- ported as well. When an operator is interacting with the Cisco video-surveillance software, the Cisco Video Surveillance Operations Manager software is being used through Microsoft ActiveX web browser.
Using this software, the operator can select which cameras need to be viewed on which displays and in what camera positions. The Cisco Video Surveillance Operations Manager updates the view on the appropri- ate view portal stations based on the parameters selected by the operations manager. If all the feeds are displayed, some might show as thumbnails only or might even make the PC unresponsive.
No additional requests are made to the camera. Figure illustrates the Operations Manager Viewer scenario.
This section covers the history and evolution of videoconferencing technologies and infrastructure. This section provides an overview of the technology categories comprising Cisco collaboration solutions.
This section explains how these technologies work together to create a cohesive, end-to-end user experience second to none. Which of the following transport technologies uses 23 B channels and a D channel? T1 CAS b. T1 PRI c. E1 CAS d. E1 PRI 2. Which of the following first provided centralized call control capabilities for H.
Gatekeeper b. CUCM c. MGCP d. MCU 3. Which of the following provided a total usable bandwidth of kbps? BRI b. T1 CAS d. Cisco Collaboration Overview 55 4. Which of the following are needed to facilitate a videoconference? Select all that apply. Endpoints b. Bridging resource c. Call control d. Cisco TCS 5. Customer collaboration refers primarily to which of the following? Call control solutions b. Conferencing solutions c. Contact center solutions 4 d. Unified communications 6. Cisco WebEx Meeting Center b.
Cisco WebEx Meetings Server c. Cisco WebEx Event Center d. Cisco WebEx Training Center 7. Which management tool is Microsoft Windows Server based and can be installed onto either a virtual or physical server operating system instance? MXE b. TMS c. VCS d. VTS 8. Which of the following are call control elements? CUCM b. VCS c. Expressway d. TMS 9. Expressway b. ASA d. This is largely due to the fact that H. The PSTN side of the connection handled audio, albeit out of band.
At this point, there is still no true central call control element; however, we do finally see the advent of true conferencing as a technological possibility, even over distance. This is accomplished largely by the rapid spread of WAN technologies throughout the globe. By keeping the traffic on-net, large corporations are suddenly able to eliminate the geographic barriers that made ISDN-based calling so expensive.
A video call is generally accepted to imply a point-to-point nature. The call does not become a conference until a third endpoint is added to the call. As mentioned at the begin- ning of this chapter, a conference requires a bridging resource. Bridging resources can come in the form of hardware-based multipoint control units MCUs , or they may be software- based MCU equivalent entities.
Either way, there is a means of mixing the media and get- ting it to all participating endpoints. Many early adopters of videoconferencing technolo- gies did eventually get around to investing in their own infrastructure.
For those companies that were just not quite there financially, hosted MCU providers began popping up all over the place. A large percentage of these providers were productizing hosted best-effort MCU services and expanded reachability made possible by a brand-new transport option called the Internet. Multipoint conferencing technologies began to rapidly evolve in terms of reachability. With the availability of both hosted and private videoconferencing resources came the need to expand the options of who could and could not attend a videoconference.
Obviously, the need to support the use of Internet-based endpoints revealed a somewhat significant issue regarding quality of service and reliability.
Figure shows how this expanded architecture looked in terms of transport and reach- ability between endpoints. In the figure, all the transport mechanisms discussed thus far are represented. Chapter 4: Introducing Cisco Collaboration Solutions Cisco collaboration solutions consist of a number of architectural components. The net- work provides the foundation on which the collaboration applications rely. The technology categories include the following: Solution components aimed at bringing together voice, video, data, and mobile applications.
This includes call control, gateways, and applications. Solution components aimed at customer interaction, such as contact center applications and voice self-service products. These are the video and telephony desktop, mobile, and software components used by end users to communicate.
This includes IP Phones, col- laboration desktop endpoints, Cisco TelePresence room-based and immersive endpoints, software clients, and Cisco TelePresence integrations.
Regardless of how the Cisco collaboration solution architecture is broken down, the pieces remain fairly much the same. There is a high degree of modularity in the overall solution. Many of the pieces can be mixed and matched to fit what is right for a given business or need.
The underlying foundation is the call control element. The gate- ways are essentially extensions of the CUCM as it controls the ports through which calls will ingress and egress. Additional flexibility in the solution is provided by the simple fact that the solution can be wholly on-premises or it can be cloud-based in the form of a hosted collaboration service HCS. The architecture is nearly identical aside from the fact that a service provider is host- ing all of the relevant pieces within their network.
In an HCS solution, the only components typically on premises are the IP Phones, collabo- ration endpoints, conferencing resources, and gateways. The rest of the collaboration solu- tion components are in the provider cloud infrastructure. Cisco Collaboration Overview 63 Conferencing Conferencing has expanded greatly over the years to encompass more than simply bridg- ing phone calls together. Audio and videoconferencing architectures have become more and more feature rich, allowing companies to scale their solutions to never-before-seen capacities.
The scope of possibilities has also expanded. Conferencing now requires a much wider array of service offerings, including the traditional on-premises audio and videoconferencing, but expanding to include web conferencing, application integration, cloud-based conferencing options, and hybrid solutions allowing the seamless integration of both on-premises and cloud-based conferencing resources in a single meeting. As men- tioned in the chapter introduction, there are three essential types of conferences: In the context of this discussion, they require CUCM or Video Communication Server VCS for call control, a conference bridge resource hardware or software based MCU , and of course the actual video endpoints par- ticipating in the conference.
Cisco WebEx includes four centers for meetings: The default meeting front end for Cisco WebEx. Meeting Center allows attendees to use audio, web, and video resources for day-to-day meetings.
Content can be shared into the meeting by any authorized participant. Meetings can be recorded with the click of a single button.
Allows for large-scale meetings. Provides an education-focused, interactive environment. This includes video capabilities, breakout sessions for discussion, and labs.
Reporting is pro- vided on a per-attendee basis, showing participation level. Any time WebEx is not the primary application on the screen, an indicator is placed by the attendee name and the time away from the main screen logged.
A customer support meeting interface primarily aimed at remote desktop and content sharing for real-time IT support and customer service regardless of geographical separation. CMR provides the capability to use cloud-based videoconferencing infrastructure rather than a company needing to purchase its own on- premises infrastructure. CMR allows the creation of user-specific, personalized WebEx meeting rooms. These rooms can be scheduled or launched instantly.
The service domains of particular importance in this discussion include the following: Call agents a. The user interface to the collaboration infrastructure. This includes desk phones, video endpoints, immersive room systems, desktop clients, smartphone clients, tablet clients, and other advanced collaboration user systems.
Connectivity to other systems and their associated network infrastructure. It is common for these systems to inte- grate with both e-mail services on the back end and e-mail clients at the user interface. Call Control Of all the service domains, call control is the most important simply due to the fact that every other aspect of the Cisco collaboration architecture relies on it as the common foun- dation.
Even the other service domains depend entirely on the existence of the call control plane to function. Over the course of the evolutionary path of both voice and video technologies, call control has come in numerous flavors, including both standards-compliant and non- standards-compliant that is, proprietary forms. This is the case both for on-premises solutions and hosted solutions.
VCS is a video aggregation and call processing engine for standards-based video endpoints. It provides not only for H. The domain portion of the URI had to be stripped or added as appropriate for the call direction. Cisco has released a new twist on the VCS firewall-traversal mechanism that allows for mul- tiple traffic types to make use of the secure connection. This new architecture is known as Cisco Expressway. For example, it does not need to actually register endpoints as it has in the past.
All endpoints register to CUCM. Expressway supports video, voice, content sharing, voice mail, presence, and IM traffic over the same connections rather than simply video traffic.
This brings to light the two additional man- ners in which VCS can be deployed: Expressway-C and Expressway-E. Expressway architecture provides a means of allowing VPN-less access to collaboration resources to clients and endpoints outside the network.
Gone are the days wherein a virtual private network VPN tunnel was required on each device that wanted to access corporate collaboration services. Expressway provides secure firewall traversal and line-side support for CUCM registrations. Expressway is also the mechanism that allows the use of the CMR Hybrid capability. Figure shows how the Expressway architecture ties into the Cisco Preferred Architecture for collaboration. Note that not all endpoints are supported with the MRA functionality.
At present, the series, series, and EX and DX series endpoints are supported for external connectivity. If greater scale is needed, a hardware conference bridge resource consisting of digital signal processors DSPs is required.
These resources are registered to CUCM as a conference bridge resource and those resources invoked when required.
PVDM3 modules can also handle some degree of videoconferencing, but they are not necessarily optimized to do so.
If both are detected, the PVDM2s will be shut down. Cisco TelePresence MCUs are hardware resources specifically created to deal with video- conference bridging. MCUs come in many shapes and sizes depending on the number of conferences, number of attendees per conference, resolution desired, and desired video codec support. The hardware can support multipoint collaboration up for full high- definition HD video at p60 or p This includes high-density support for vari- ous conference views, including continuous presence and picture-in-picture PIP.
These hardware resources also support multiple formats and adaptive rate matching to provide the best possible experience to a wide array of standards-compliant endpoints, be they H.
The CTS can be hardware based or software based. The hardware-based version is essentially a virtual server running on a blade in an MCU chassis. CTS supports conferencing services for both H.
This includes enhanced view modes, multiscreen, active pres- ence, multivendor interoperability, and multistream. Multistream is a new Cisco feature that allows the use of multiple screens both for videoconference and content sharing. TCS is a software-based virtual appliance that provides recording, live streaming, and on-demand sharing of videoconference content. The content can then be distributed to any PC or portable media device, or it can be posted to a Cisco Show and Share portal.
The recording function can be invoked manually, scheduled as a videoconfer- ence resource to automatically record the call and all shared content, or it can be invoked for every call. When VCS is in play, a traversal license is used for each H. For Expressway, an RMS is used. TMS is a Microsoft Windows Server-based software package geared specifically for providing a web browser- based interface using Microsoft Internet Information Services and the.
NET Framework to 4 the video units, available resources, and more. The Microsoft Windows Server installation can be virtualized or installed on a bare-metal server. Obviously, Cisco prefers the use of Cisco UCS platforms, but the only real requirement is that the Microsoft Windows Server and its hardware platform meet the required specifications.
TMS offers the capability to control and manage multiparty conferences, infrastructure, any standards-compliant endpoints, and more. This includes feature augmentations such as one-button joining of a meeting.
Shortly before the scheduled start time of the meeting, a button shows up on the video endpoints scheduled to join a particular conference.
At meet- ing time, a participant merely touches the button to join or initiate the conference. TMS integration with Microsoft Exchange and Outlook combine to provide a flexible, easy inter- face for quick conference scheduling and resource booking options.
The one-button-to-push meeting access feature is available in TMS Cisco Collaboration Overview 77 Define Key Terms Define the following key terms from this chapter and check your answers in the Glossary: This section provides an overview of the features and capabilities of the currently available Cisco IP Phone models.
This section provides a high-level description of the Cisco Jabber software client and platforms on which it is available. The portfolio has evolved greatly since the first Cisco IP Phones were made available after the Cisco acquisition of Selsius in A possibly-not-so-well known reference to Selsius remains in the system to this day. Cisco has slowly started to move away from differentiating IP Phones, software-based clients, desktop video endpoints, and immersive TelePresence room-based video end- points.
In the past, the distinction was important.