While attending the 2013 Aastra analyst event in Dallas in early, May I had the good fortune to sit next to Simon Beebe, Vice President of Product Management at Aastra. Among Simon’s responsibilities are all of the communications endpoints Aastra makes, including Aastra’s line of SIP phones and BluStar video devices.

So, it was with interest that I approached Simon on the idea of a WebRTC-based endpoint device. With his knowledge of endpoint design and manufacturing, I wanted to get a sense as to whether he saw any merit in the idea of a future in which some enterprising person or group creates a dedicated WebRTC device.

Clearly, WebRTC is in its early, and some would say “heady”, days. Simon really saw no drivers for creating a WebRTC-based standalone endpoint that could sit on the desktop. The discussion centered around the bill of materials (BOM) required for such a device and the reality that like any communications device, there would be some real manufacturing costs associated with it. In his mind, Simon could see no real need or advantage for a WebRTC-based dedicated device.