Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

Voice Over IP (VOIP)

Equipment Provider

Overview:

Voice over IP has gone from a what-if to a when. Companies everywhere are implementing the technology in their networks. Suddenly, what was two separate networks -- voice and data -- are merging. But how do you get up to speed? What are the gotchas that will befall you? This class provides a solid overview of technology used in delivering voice over the Internet Protocol (VOIP). The devices, gateways, protocols and standards that make such calls possible are at the heart of the course. Protocol traces that reveal call set-up, control, delivery and termination will be fully examined. Find out what can impair a VoIP network and how to discover and resolve the impairments. You learn the ins and outs of troubleshooting VoIP networks. Get hands-on experience with a VoIP lab where you use test equipment and sniffing devices to investigate problems in the network configuration. Various vendor implementations will be compared, to include Avaya.

In this seminar you learn about:

  • The Real Time Protocol that is used to transport voice over packet networks.
  • The difference between implementing voice in circuit switched and packet networks.
  • Analyzing packets to answer question such as: What compression algorithm is the phone using? Is it the same as the other phone? What does the phone report as arrival jitter? Does it match our measured value?
  • Comparisons of the various implementations of call control.
  • The overall structure of a packet containing voice, including the Ethernet, IP, UDP and RTP portions.
  • Diagnostics for how the phone boots and connects to the network and determine whether or not the phone isn’t receiving configuration information.
  • The approximate bandwidth used by a call and estimate the bandwidth needed per call path.
  • The options available to provide quality of service.
  • The difference between the standards developed by the telecommunications industry and the Internet community.
  • The feasibility of implementing voice over your intranet or the Internet.
  • Measuring the critical parameters that affect voice quality including delay, packet loss, and jitter.
  • Comparisons of the standards to actual implementations.
  • How RTP can carry more than one audio or video source.
  • Troubleshooting tools and features.
  • Why TCP isn’t used for voice transport.

To bring this course on-site, please call Michele Zarella at 508.490.6620 or email at mzarella@nww.com
Need another class to meet your training needs? Call us! We can tap into our extensive network of instructors and tailor a custom program for you.

Error 404--Not Found

Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

Error 404--Not Found

Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.