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

Course Outline: DAY ONE / DAY TWO

 

DAY ONE

8:30 – 9:00 a.m.

  • Introductions, overview of course and administrative matters

9:00 – 10:20 a.m.

  • Background
    •
    • The IP, TCP and UDP protocols

    • Voice conversion and compression

    • Why packet technology for voice and video

    • Feasibility

    • Software PBX’s
      •

10:30 -11:00 a.m.

  • G7xx: voice compression

11:00 – 12:00 p.m.

    Call Signaling Protocols
    • H323: the umbrella
      • Architecture

        • Gateways

        • Gatekeepers

        • Media Gateway Controllers

        • Multipoint Control Units

      • Q931, H225: call set-up

      • H245: call control

1:00 — 2:00 p.m.

Lab 1: Capturing voice packets, packet header analysis
Lab 2: H323 Control

2:00 — 3:15 p.m.

  • SIP: Session Initiation Protocol
    • HTTP background

      •
    • Overview Messages

      •
    • Operations
      • Proxies and redirects

3:30 - 4:00 p.m.

  • Lab 3: SIP Control

(back to top)

DAY TWO

8:30 - 9:30 a.m.

  • Transport Protocols
  • RTP: Real Time Protocol

    • Headers

    • Sources

    • Handling silence

  • RTCP: Real Time Control Protocol

9:30 - 10:00 a.m.

Lab 4: Determining the compression algorithm being used; RTP and RTCP study

10:00-11:30 a.m.

  • Quality of service
    • Issues
    • Implementations
    • Jitter
    • Delay

11:00 - 12:00 p.m.

  • Lab 5: Phone boot sequence, access, jitter measure and the effect of network loading

1:00 - 2:00 p.m.

  • Vendor Implementations
    • Cisco

      •
      • Control protocols

        •
      • Architectures

        •
      • Management

2:00 - 2:30 p.m.

  • Lab 6: Analysis of Cisco packets

2:30 - 3:30 p.m.

  • Avaya
    • H323 implementation

      •
    • Administration

      •
    • Integration with existing systems

3:30 - 4:00 p.m.

  • Lab 7: Analysis of Avaya packets
    Equipment Provider

4:00 — 4:30 p.m.

  • Review and discussion
    •

(back to top)

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.