‹ Back
Deploy360 6 January 2014

No Jitter: IPv6 Impact on VoIP

Dan York
By Dan YorkDirector, Online Content

No Jitter logoHow well do voice-over-IP (VoIP) and unified communications (UC) systems work with IPv6?  That’s a topic that has long been a personal passion of mine – and we maintain a page here on Deploy360 specifically about IPv6 and VoIP/UC systems. So naturally I was very pleased when right before the holidays on December 20, 2013, Gary Audin wrote a piece on the No Jitter site about IPv6 and VoIP.

Gary identifies several issues that enterprises need to think about with regard to migrating their VoIP systems to IPv6, including:

  • Increased bandwidth needs due to expanded IPv6 headers
  • Upgrading IP PBXs, IP phones, softphones and gateways to IPv6
  • Running dual stack operations with both IPv4 and IPv6
  • Network Address Translation modifications
  • Port sharing for signaling protocols

From my own perspective of having worked in the VoIP field  I think his second bullet is probably going to be the most problematic, particularly the IP phones.  Many of the older IP desk phones used by enterprises are severely resource constrained and may not be able to support dual-stack operations and may not be upgraded to IPv6.  In many cases it may be the newer IP phones and the softphones that will lead the way to IPv6.

But interestingly in this article Gary is more focused on the potential bandwidth increases.  He’s right that one of the differences in VoIP traffic from, say, web or file traffic is that VoIP is composed of a zillion tiny packets. This has to do with how most VoIP systems use a very small sampling size – they slice the voice stream into very tiny pieces, typically around 20 milliseconds, and then send those pieces in individual packets.

So, given all the tiny little packets, any increase in the overall size of the VoIP packets results in an increase in bandwidth.  Gary’s argument is that the increased size of IPv6 headers will have an impact on bandwidth.  Not necessarily a huge impact, perhaps only a 10% increase in needed bandwidth, but still, there will be an impact. Though I have not done the math as Gary has to make his table, I can see his argument.

His main point, really, is that as enterprises plan their moves to IPv6 they need to think not only about potential software and hardware upgrades, but also about additional bandwidth requirements.  It’s good advice to think about.

Are you ready to migrate your VoIP or UC system to IPv6?  Or have you already done so?  If you haven’t, check out our page on VoIP and UC resources for IPv6 – and if you have already done so, we’d love to talk to you about writing up a case study! 🙂

‹ Back

Disclaimer: Viewpoints expressed in this post are those of the author and may or may not reflect official Internet Society positions.

Related articles

Improving Technical Security 15 March 2019

DNS Privacy Frequently Asked Questions (FAQ)

We previously posted about how the DNS does not inherently employ any mechanisms to provide confidentiality for DNS transactions,...

Improving Technical Security 14 March 2019

Introduction to DNS Privacy

Almost every time we use an Internet application, it starts with a DNS (Domain Name System) transaction to map...

Improving Technical Security 13 March 2019

IPv6 Security for IPv4 Engineers

It is often argued that IPv4 practices should be forgotten when deploying IPv6, as after all IPv6 is a...

Join the conversation with Internet Society members around the world