Designing for Collaboration
V O I CE A N D VID E O CONS I D ERAT I O NS A N D S E RV I C E PL A CEME N T
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community
Ask the community for help and clear up your study doubts
University Rankings
Discover the best universities in your country according to Docsity users
Free resources
Our save-the-student-ebooks!
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
Designing for Collaboration: Voice and Video Considerations and Service Placement, Summaries of Network Design
Training network design and architect cable fiber another equitment
Typology: Summaries
2022/2023
1 / 12
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Designing for Collaboration: Voice and Video Considerations and Service Placement and more Summaries Network Design in PDF only on Docsity!
Designing for Collaboration
V O I C E A N D V I D E O C O N S I D E R A T I O N S A N D S E R V I C E P L A C E M E N T
Terminology Overview
- (^) Grade of Service (GoS) – probability a call will be blocked due to congestion CCDA mostly focuses on voice with a little bit of video
- (^) Erlang – measure of call time used per unit time. 2 calls for 60min during 1hr = 2 Erlangs
- (^) Busy hour – The most used hour during a work day for calls
- (^) Busy hour traffic – measure of call time used during busy hour, in erlangs
Deployment Models - Centralized
Centralized call processing in single-site and multi-site environments
- (^) Centralized CUCM cluster in server farm/data center
- (^) Survivable remote site telephony (SR ST) at remote sites in the event of WAN failure
- Converged network with PSTN site connectivity Images courtesy of cisco.com
Deployment Models - Distributed
Distributed call processing in multi-site environments
- (^) Separate CUCM cluster at each site
- (^) Separate Unity cluster at each site
- Most redundant deployment
- (^) Call manage Express (CME) integrated call manager for ISRs
- (^) Supports up to 450 phones. Valid for branch office design Images courtesy of cisco.com
QoS Trust Boundary
- (^) Best practice is to mark traffic as close to the source as possible – ie. phone
- Auto-QoS will enforce trust boundary at the Cisco IP phone
- (^) The practice of defining where traffic handling markings are trusted from
- (^) Bad actors can cause improper traffic to be handled with priority by marking at workstation
Voice and Video Service Limits
- (^) Voice and video are both very sensitive to service degradation
- (^) Video is more sensitive to packet loss due to delta encoding Acceptable limits
Voice Video
RTT 150ms^ 150ms
Jitter <35ms^ <30ms
Packet loss % <1%^ <0.05%
Video Capacity and Throughput
- (^) H.264 is by far the most popular video codec today
- (^) Table gives the typical bandwidth requirements of H.264 video sources Table courtesy of cisco.com
Q&A Which IP telephony design model should you implement to fulfill these requirements:
- (^) Single, large location with many remote sites
- (^) Multi-site WAN connectivity
- (^) Requires SR ST for call processing redundancy A. Distributed B. Centralized C. Clustered D. Decentralized