ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Using UDP for VoIP instead of TCP

Updated on September 27, 2012
Using UDP for VoIP
Using UDP for VoIP

How VoIP Is Different from Regular Internet Traffic

While it is certainly ideal for all Internet traffic to be treated in the same way regardless of which application is using it or where it's going to, in reality the technical nature of different types of traffic necessitate various strategies for handling them. Some might argue that this goes against the principle of net neutrality – but net neutrality has more to do with restrictions on traffic imposed by the Internet service provider or the ISP. VoIP however requires a management strategy that is implemented based on the protocol that is being used – namely SIP.

The Internet is widely based on the TCP/IP protocol which proves extremely reliable for data transfer. Most Internet applications have very little tolerance for error rates. For example, if you have a webpage, erroneous data will mean that you receive junk and that results in a very poor user experience. Far better to spend a few additional milliseconds requeriying the data and making sure that it arrives intact rather than provide the user with bad packets. This works well for most areas of web content.

VoIP however is a very different beast compared to traditional Internet traffic. It needs a different set of rules and the TCP/IP protocol isn't well-suited for VoIP.

Problems with the TCP/IP Protocol

The process of re-querying data when bad packets are received or when a timeout occurs is great for receiving quality data but introduces a certain time lag that is unacceptable in cases of real-time communication like VoIP. Experience as well as research has shown that there is a certain tolerance for delay when talking over the phone beyond which, it becomes very difficult for proper two-way communication. VoIP applications cannot afford to spend tens of milliseconds on requesting old data because they need to reduce latency and lag as much as possible.

Because of this, the TCP/IP protocol is insufficient for VoIP and we need something else that is known as The User Datagram Protocol or UDP for short. UDP is a technique that requires very little setup as compared to TCP/IP and consists of sending a stream of messages as soon as they're available and the receiver accepts them and processes them regardless of whether or not they received correctly. While this may introduce a few glitches during talk time, the human brain is more than capable of making sense of what is coming in even with a bit of faulty data thrown in. As a result, UDP has significantly less latency unlike TCP/IP when it comes to VoIP – and this is something that customers notice very quickly.

If you know what you're doing, you can use certain configuration options in your VoIP client that will force it to use the TCP/IP protocol instead of UDP. Contact a Philadelphia phone services VoIP provider to ask them about it if you have any doubts. SIP is one of the most flexible VoIP protocols and depending on your needs, anything can be configured to suit them.


    0 of 8192 characters used
    Post Comment

    No comments yet.


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

    Show Details
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)