You are a network administrator responsible for all network platforms and servic
ID: 3576335 • Letter: Y
Question
You are a network administrator responsible for all network platforms and services. The Teta Company currently has only one building which houses its sole data center. The CIO indicates the company recently purchased the building next to existing building that will house 150 employees. Unfortunately, only a wireless solution will work for providing access to the data network. What network requirements and recommendations would you make to the CIO that will allow the employees in the new building to access the company LAN?
Explanation / Answer
Implement QoS before you implement VoIP. Preferably, this could be end-to-end QoS, which implies that voice traffic should incline higher priority than information traffic on each link. i like to recommend that you just use IEEE 802.1p/q enabled switches. once mistreatment 802.1q VLANs, the 802.1p priority tag resides within the 802.1q traffic header. Routers ought to be DiffServ code points (DSCP). 802.1p & letter of the alphabet work along.
By implementing this QoS traffic prioritization, you're making certain timely VoIP packet delivery and providing the simplest decision quality.
As a part of this QoS arrange, you ought to break voice traffic off into its own VLANs to induce it far from the info traffic. These VLANs can place the phones on their own broadcast domains and information processing subnets.
notice how to live the standard that the VoIP traffic receives on your network. this could be finished a tool provided by your merchandiser, or it should be enclosed in your VoIP troubleshooting tool, that we tend to point out next. while not a tool to live VoIP quality, you'll got to take your users' word for it. it'd be higher to own a mensuration tool that may provide you with a true metric of VoIP performance.
notice a troubleshooting tool for VoIP traffic. Network troubleshooting tools, particularly for VoIP, area unit out there from Network Instruments, NetIQ, Wireshark and lots of others. after you move to implement a VoIP troubleshooting tool, take into account the subsequent questions:
wherever can you deploy analysis tools -- on the computer network or WAN , on every VLAN, or at the VoIP decision management server?
what is going to you measure?
are you able to notice how to be proactively notified if decision quality begins to deteriorate?
Before implementing VoIP, conduct analysis to see network bottlenecks -- develop a baseline. however smart is network performance nowadays, before VoIP traffic gets on the network? This baseline will suggests some important problems regarding your computer network and WAN. for instance, does one have enough information measure on the WAN links that the VoIP traffic are traversing? Even with the calculable most range of cooccurring calls, given the codec you've got designated, and therefore the different information traffic on the link? For a lot of data, see VoIP Bandwidth: Calculate consumption.
What you wish to understand regarding your network and VoIP traffic
To ensure that VoIP can work well on your network, you wish to require many things into consideration before you implement VoIP or begin creating network changes.
First, confine mind that VoIP may be a mission-critical network application. Perhaps, till this time, your most important company application was email. though email is incredibly important, it usually demands very little of a network as a result of it's forgiving of network delays. Email was designed to be queued and slowly travel the net. Thus, once your network has slowdowns, it does not mind.
Second, VoIP traffic desires a solid infrastructure. Those previous hubs within the wiring closet simply are not planning to cut it if your new VoIP phones area unit to supply high-quality calls. you'll want a network infrastructure that's quick and reliable to hurry on that VoIP traffic with borderline delays. Also, make sure that your network is secure -- freed from viruses, worms and intrusions. you do not need this mission-critical application brought down by a security hole.
Third, you'll have to be compelled to implement Quality of Service (QoS) on your network.VoIP traffic can not be competitory with somebody downloading a a hundred MB PowerPoint presentation from the digital computer or somebody paying attention to streaming audio from the net. The network should be designed in order that VoIP has higher priority than simply regarding each different application presently on the network. that's as a result of VoIP is a lot of delay-sensitive than ninety nine of different applications usually run on your network. In fact, audio is a lot of sensitive to delay than video.
Besides knowing your network, recognize what VoIP desires so as to be a "happy application." Here area unit some belongings you ought to know:
Ideally, disturbance ought to be twenty ms or less. VoIP phones use disturbance buffers to undertake to cut back the impact of disturbance on the voice decision. a lot of severe disturbance may result in packet loss. different causes of packet loss area unit issues on the physical network. while not QoS, a burst of knowledge traffic will cause packet loss on voice calls. Packet loss ought to be a hundred and twenty fifth or less between end-to-end connections, however a VoIP decision could tolerate up to three.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.