How do I love thee? Let me count the upgrade cycles. I bought my first copy of ThumbsPlus in August of 2000 when v4.0 was released. For going on fourteen years it has been my preferred software for managing our…
While many people make use of webcams, the simple fact is that most application software that makes use of a webcam doesn’t give the end-user much control of its settings. Most video chat or conferencing software offer only a few…
This morning’s inbox included an announcement from Voxbone about their own WebRTC service. Based in Belgium Voxbone are a provider of various services to telecom companies. They are most commonly known for providing DIDs in 50+ countries around the world.…
T-Mobile has been supporting mobile HDVoice for over a year. However, my sense is that not very many people are actually experiencing HDVoice. If they are, they might not even know it.
For example, two of my associates have the Google/LG Nexus 5 handsets on T-Mobile’s network. Both are the sort of people who would hear and appreciate the difference that HDVoice makes. That said, both were initially of the impression that the Nexus 5 did not support HDVoice on T-Mobile!
This gave rise to the idea that we should devise a simple way to verify that a call was in HDVoice. If convenient, this would allow anyone interested to make a call between two handsets and know with certainty that the devices and call path was actually delivering HDVoice.
Devising such a test turns out to be very easy in a world of smart phones. All you need is a tone generator or a recording of a specific continuous tone.
This week OnSIP, long known for its popular SMB hosted PBX service, launched a new initiative offering WebRTC– based platform-as-a-service. Their core business has been the hosted PBX service, which is built upon SIP standards. This new service targets web developers who want to easily incorporate WebRTC into their applications.
The companies web site has been extended to include an area described as OnSIP For Developers which details the service offering. The principle behind the service is to leverage their core SIP infrastructure to deliver the signaling solution that WebRTC alone does not provide. Thus a web developer can easily create a WebRTC based front-end that’s backed by the scalable, geographically distributed infrastructure of the OnSIP hosted PBX platform.
For the several weeks we’ve had the new “Extended Range” Doorbot installed in place of the original device. The only apparent difference between the two is the addition of a short external antenna to enhance the Wifi connectivity.
Happily, the new unit does seem to stay better connected to our WLAN. In the past I was not comfortable evaluating the behavior of the Doorbot+client application given the questionable connectivity. At present the network connection seems sufficient to examine the behavior of the system as a whole.
I have the DoorBot client application installed on a variety of devices:
The fact that I’m using so many devices may be a little unusual, but I would expect that many families will use 2-3 devices, most likely a couple of cell phones (his & hers) and a tablet. Although a family with kids may well have more than this.