If you have been upgraded to DOCSIS 3.0 and were issued a cable modem from your cable provider, you are probably paying a monthly fee for that device. I have always been a strong advocate of owning my own cable modems because it likely pay for itself over the two or three years you own it.
Everyone is familiar with Internet Protocol version 4 (IPv4) addresses. You probably even set them up in your home network, such as 192.168.1.1 IPv4 is described in IETF publication RFC 791 (September 1981), which replaced the previous version RFC 760, dating back to January 1980. So its safe to say that IPv4 has been around for some time and serving us quite well. New in DOCSIS 3.0 has support for IPv6. Why do we need this new version? IPv6 has a vastly larger address space than IPv4. This results from the use of a 128-bit address, whereas IPv4 uses only 32 bits. Believe it or not, major cable operators are running out IP address. This is due to more customers, not just for cable modems, but also for set top boxes and VoIP eMTAs. Further, deployed in cable networks are IP devices such as power supplies with embedded cable modems for monitoring voltage, temperature, current and more. All networks are getting more IP devices requiring more and more IP addresses, so the 2128 addresses allocated in IPv4 are no longer sufficient and we turn to the 3.4×1038 addresses provided in IPv6.
In my article on DOCSIS 3.0 M-CMTS architecture, I talked about the distributed nature of the CMTS with an M-CMTS core (the CPU of the system), a DOCSIS Timing Server, and an edge Quadrature Amplitude Modulator (EQAM). I am going to cover the EQAM in detail in this article because in the past couple of years, EQAM (also spelled eQAM) has rapidly become part of our vocabulary but its operation and value often go unappreciated. Further, in order to fully understand DOCSIS 3.0 operation, downstream channel bonding, and possible issue which may arise, a thorough understanding of the eQAM is critical.
DOCSIS 1.0 enabled data over coax with a “best effort” service using a data request-grant methodology. DOCSIS 1.1 and subsequent specifications added guaranteed Quality of Service (QoS) by providing Unsolicited Grant Synchronization (UGS) which means that a cable modem does not have to send a data request in order to receive a bandwidth grant from the CMTS. The new UGS service is an enabling technology which has allowed cable operators to successfully deploy the highly revenue generating Voice-over-IP (VoIP) services. In the following sections I will illustrate the differences between best-effort (request-grant) and QoS (UGS) services.
In this blog I will address delay and jitter as they pertain to VoIP in a DOCSIS network. Delay, jitter and packet loss are the three primary impairment in a VoIP network, but packet loss was addressed in my Troubleshooting DOCSIS – VoIP Impairments > Packet Loss blog. After packet loss, delay is the second
In this blog I am going to focus on VoIP packet loss, which is just one of the three (3) primary types of VoIP impairments that are present in a DOCSIS network. I will cover many RF and IP terms in this blog that I have not discussed in my previous tutorials, not to worry! This terminology is all fodder for future blogs. 
To review, the three fundamental impairments which impact call quality of VoIP communications are as follows:
* Packet Loss – The complete or partial loss of a packet containing actual voice payload.
* Delay – The time a packet takes to traverse the space between the source and destination of a voice call. The space is comprised of both the physical distance the data must travel in addition to the active network routing and switching elements, which contribute additional delay.
* Jitter – The variance of inter-packet arrival time from one transmitted packet to the next sequential packet.
In this blog I am going to digress for a moment from my standard DOCSIS 101 tutorial and spend a little time on DOCSIS troubleshooting basics, especially with respect to Voice-over-Internet Protocol (VoIP). I am doing this as due to many offline questions specific to this topic. Don’t worry, though I may start to inter-mix some troubleshooting blogs now and again, just check the DOCSIS 101 page to stay on top of the latest DOCSIS tutorial blogs.
bradyvolpe.com is Stephen Fry proof thanks to caching by WP Super Cache
