Dialogic Blog

Chad Hart

 

Recent Posts

Dean Bubley Guest Post: Can WebRTC give new life to IMS?

by Chad Hart

Dec 4, 2014 11:57:54 AM

c

Standard telephony is considered a commodity. To grow beyond this, innovative developers and service providers have made attempts at Value Added Services (VAS) for decades. These VAS have manifested in many forms over the years, including Color Ring Back Tones, voice portals, and other creative Interactive Voice Response (IVR) services. More than a decade ago IP Multimedia Subsystems (IMS) was created to usher in a new era of telecom VAS by making new services easier to create and deliver at scale.

Read More

Solving WebRTC’s Media Server and NAT Traversal Problems in One Shot

by Chad Hart

Nov 19, 2014 7:41:32 AM

Our own John Hermanski and Hanzhong Gu recently wrote a tech note showing how the widely used rfc5766-turn-server can run on the same server with PowerMedia XMS.  If you are not a hardcore WebRTC implementer you probably have no idea what I am talking about, so let me explain rfc5766-turn-server is and why is this important.

The Firewall & NAT Problem

Getting VoIP traffic through Network Address Translators (NAT) and firewalls is tough. These devices change and restrict the IP address information. This is not a problem for website traffic because the underlying routing architecture is consistently implemented, usually left open, and transparent to the application. That is not the case for VoIP which has IP address and port information embedded inside its protocol layers, out of the reach of firewall and NAT devices.

These problems are in the realm of SBCs with their NAT traversal techniques. The people standardizing WebRTC wanted to traffic to be able to travel in a peer-to-peer fashion without mandating the use of SBCs. WebRTC leverages 3 standardized technologies that have been around for a while, but not widely used:

WebRTC endpoints need to support one or more variations of ICE. WebRTC providers should at a minimum offer a STUN server. STUN is a lightweight function that is inexpensive to operate.

TURN servers are not always needed, but they are needed often enough that any serious WebRTC provider should also include that too. TURN servers needs to terminate and reorginate media streams, consuming a lot of bandwidth, so operating one is a lot more expensive.

 

So what is RFC5766?

RFC5766 is an Internet Engineering Task Force (IETF) standard that defines TURN.

rfc5766-turn-server is a fully functional open source project that includes STUN and TURN capabilities lead by Oleg Moskalenko. This project has become very popular and is even used as part of Amazon’s Mayday service. John Hermanski was one of the first users of this project and wrote a great setup guide for it.

 

So what does this mean for PowerMedia XMS?

TURN servers relay media. Media servers by their nature manipulate and relay media. Relaying twice adds latency that hurts quality. Wouldn’t it be easier if these two elements could be one and the same? That effectively what happens when you run rfc5766-turn-server on PowerMedia XMS. Putting rfc5766-turn-server on the same instance also gives XMS considerably more flexibility for dealing with network and addressing intricacies. Having a single device instead of two also simplifies network management.

Check out John’s tech note for more details.

Read More

Topics: WebRTC

WebRTC Video Codec Debate – a Transcoding Vendor Perspective

by Chad Hart

Nov 10, 2014 10:06:05 AM

Here we go again. The Internet Engineering Task Force (IETF) is scheduled to discuss WebRTC Mandatory to Implement (MTI) codecs again this week at IETF 91. We have been here a few times before – the community failed to reach a consensus on this issue last year.  Will this time be any different? What does this all mean for the industry and transcoding vendors like Dialogic?

Read More

Topics: WebRTC

Bubley Talks Sentiment Analysis and WebRTC

by Chad Hart

Oct 23, 2014 9:12:47 AM

In the traditional telephony world we often forgot how often machines are part of our regular communication. Dialling into a conference bridge? Odds are you need to enter a few digits to enter you into the right conference and there is a machine analysing the tones on the line to see what you pressed to- initiate some action. As we move into a Web-telephony world driven by WebRTC, the opportunity for machine-interaction as part of our communications is going to grow dramatically.

Read More

IIT RTC Conference Recap

by Chad Hart

Oct 16, 2014 10:56:59 AM

Read More

Does Microsoft Want to Kill WebRTC?

by Chad Hart

Apr 28, 2014 2:41:41 PM

Does Microsoft care about WebRTC? Is Microsoft trying to kill or delay WebRTC? These are questions that have been asked since WebRTC became a more mainstream buzzword and one that I am asked all the time. I will address both of these topics below along with Microsoft’s new WebRTC prototype it announced last Friday.

Read More

Topics: WebRTC

ORCA, the Telecom Industry and WebRTC

by Chad Hart

Apr 16, 2014 5:17:00 PM

If reading the title of this article only brought to mind a whale, it’s time to learn more. WebRTC has not one, but two different and totally distinct ORCA projects. Here is what they mean for both WebRTC and the telecom industry as a whole.

Read More

Topics: WebRTC

How Will WebRTC Work With Mobile?

by Chad Hart

Apr 14, 2014 11:48:16 AM

No doubt you’ve seen one of the numerous headlines talking about “mobile first” design and development. Whether or not you agree with this approach, it’s undeniable that mobile is on the rise – and WebRTC is part of that growth. Just as on a desktop, WebRTC can be used on Android mobile devices with supported browsers such as Chrome, Firefox and Opera. (Unfortunately, the technology does not yet work with iOS because Apple requires browsers to use its own Web renderer.)

Read More

Topics: WebRTC

Video Telephony: From the Picturephone to WebRTC

by Chad Hart

Apr 2, 2014 9:50:00 AM


Caption: AT&T introduced the Picturephone service in 1970, but telco-provided consumer video telephony services never found success.

Read More

Topics: WebRTC