In the ITEXPO Press Room I just met with Cliff Rees, President & CEO of XCast Labs. They have some interesting VoIP technology, including a patent called "direct RTP" which reduces VoIP bandwidth requirements in half.
The example Cliff gave was a VoIP call from Los Angeles to San Francisco using Net2Phone based out of New Jersey. When the Los Angeles user calls the San Francisco user, it initiates a 90Kbps IP call cross-country to Net2Phone's headquarters in New Jersey. Net2Phone then routes the call cross-country back to a termination gateway which connects to the San Francisco user. This too uses 90Kbps of bandwidth for a total of 180Kbps for the RTP media. The Net2Phone server in New Jersey has to allocate and hold 180Kbps of bandwidth for each call. Additionally, the call has to cross the country twice which adds more jitter and latency.
XCast Labs on the other hand uses their patented "direct RTP" which is able to tunnel through both user's firewalls and setup a direct peer-to-peer (P2P) RTP session between the two users. Once the call is setup, the two users are able to send the RTP media directly to each other. Since both callers are in California, they are just a few hops/routers away from each other thus dramatically reducing latency and jitter. XCast Labs simply maintains a small signaling connection to determine when the call ends for billing purposes.
When Cliff from XCast Labs explained to this me, I was dumbfounded that no one else had thought of this. It seemed so obvious that a direct RTP session would result in less bandwidth requirements, better latency, and better voice quality. Their technology sounded eerily similar to Skype's ability to penetrate firewalls and initiate high quality peer-to-peer calls so I made the analogy with Skype and Cliff agreed they are very similar. Though in the case of XCast Labs they use standard SIP while Skype uses proprietary technology. Further, XCast Labs offers both a consumer (residential) and a hosted business offering with advanced functionality such as call parking, call transfer, etc. They also support video calls and video mail. They support both Polycom video phones as well as Grandstream, including the new GVX3140 H.264 video phone seen here:
XCast Labs developed everything in-house, including their own SIP stack and softswitch so they are not paying Sonus Networks, Acme Packet, Broadsoft, etc. any sort of licensing fees. They told me this helps them be extremely competitive when compared to other VoIP providers. They offer their own residential VoIP service but they also sell to the cable MSOs who white label it for their Triple Play packages. Lastly, XCast Labs said they support HD Voice using G.722 so if you have a G.722 end device you have have HD audio.
android apple asterisk at&t blackberry cell phone cisco dell digium e911 facebook fcc google google talk gps im ip-pbx ipad iphone ipod itexpo ITEXPO lync microsoft mobile phone open source outage phone review sip skype sony unified communications verizon video video conferencing voip vonage wireless xbox 360
- Apple (280)
- Bittorrent (2)
- Call Center and CRM (48)
- Computer Hardware (183)
- Computer Software (71)
- Gadgets (650)
- Google (225)
- Home Entertainment (263)
- Internet (173)
- Linux (111)
- Microsoft (376)
- MovableType (48)
- News (187)
- Personal and Humor (118)
- Politics (9)
- Reviews (246)
- Security (2)
- Social Networking (42)
- Sports/Outdoor Technology (9)
- Tablets (32)
- Technology and Science (355)
- Unified Communications (471)
- VoIP (2285)
- Wireless (584)
- p2p (20)
- March 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
- July 2004
- June 2004
- May 2004
- April 2004
- March 2004
Featured Videos
I Would like to read more about standard SIP. I use Vopium to call my family in India.
Of course you were dumbfounded that no one else had thought of this: Because XCast labs is using the the STANDARD way of doing RTP (prior to the hosted VoIP industry). There's nothing new here.
And let's not forget Verizon's patent, US Patent 6,104,711. In 2006, Vonage was found to be infringing of that patent. That patent covers cases where the IP address of the called party is returned to the calling party. This is exactly the requirement for XCast's direct media to occur!
So this is prior art -- and actually covered under another patent. Verizon has not apparently tried to enforce this patent, yet, against all the other service provides. In fact, Verizon USES BroadWorks and Acme Packet itself in their new fIOS VoIP architecture.
Tom, I agree with Mark that they are probably using a variation of the well-known FW/NAT traversal procedure as codified in ICE. But I am surprised to hear that Verizon has a patent on that. Gaming applications have used such a scheme for some time now. If I recall correctly, VZ/Vonage dispute was related to PSTN interconnection.
Same feelings as Adrain here, sounds very interesting.
It’s funny how many of today's technological advances are usually a ‘tweak’ here or there on something already available in some form. Mark’s points seem to provide a great example of this.
Ok, some clarification from XConnect. The key point which I guess I may not have made clear in my article is that their direct RTP is able to penetrate firewalls and initiate direct RTP sessions. That's their "secret sauce".
Here's what Vlad Smelyansky from XConnect told me:
Your description of our RTP is wrong and the comments (except reference to the patent) are correct. The guy actually picked on the core mistakes and ignored the rest.
There are gazillions of other cases when people are using direct RTP. Our patent and technology is not about the idea of sending traffic directly between end points because that is part of the RFC. Our patent and technology is that we actually can do it between endpoints behind firewall(s) without any special configuration of firewalls (NAT) or deploying additional technologies (STUN) on those endpoints. ACME, Nextone, and Ditech tried to do this and came to the conclusion that it is impossible without additional protocol or special firewall configuration. But if endpoint devices are on a public IP or the user is willing to do special NAT or use STUN, they all can do Direct RTP for last eight-nine years. Our specialty is that we can do it with almost any endpoint behind a firewall and do it totally plug-n-play. No one else can do that.
Tom -- Thanks for getting some clarification.
He referred to my comment about the patent. I am not a lawyer, but Vonage was found infringing of the claim in the patent where the IP address of the called party is provided to the calling party. (AFAIK, Verizon hasn't tried to sue anybody else about that claim in US patent 6104711.) Perhaps XCast has some way of setting up direct media between the calling and called parties without returning their IP addresses to each other.
Nevertheless, I only mentioned the patent because it's a dated legal document showing that people were thinking about sending media directly between the two voice-over-packet endpoints.
If XCast can setup direct media between any two port-restricted NAT'd endpoints, then congratulations are indeed in order.
Tom, it looks like you need to get more clarification. From your description and the new clarification it is not clear what is the new procedure. A quick search at USPTO site for "direct RTP" brings up a patent application 2009077245, "Client-to-client Direct RTP Exchange in a Managed Client-Server Network". Since the first inventor is also a cpo-founder and CTO of Xcast, I am assuming that the procedure described in that application is the correct reference.
I am not able to see how the procedure described is much different than ICE. Indeed, their procedure does not cover some of the cases, like when an end-point has multiple IP addresses. Assuming that they are not trying to patent ICE procedure and ignoring the additional cases covered by ICE, the two procedures are materially the same and yields the result using the same amount of overhead. So it is evident that I am missing something big in their proposed scheme. Interestingly, they mention STUN as a prior art, but do not mention ICE.
Folks what about the LI aspect? No one has mentioned CALEA requirements that they aren't able to meet.