This morning I received an email from VoIP Supply alerting me to the fact that they've started offering solutions built around Microsoft Response Point. Personally, I have no experience with Response Point but I hear good things from people who…
Talk about perfect timing! Cory Andrews over at VoIP Supply just post a great list of 20 open source soft phones. Nice work Cory!
From this list I found that the French soft phone formerly called OpenWengo has mutated into QuteCom. Best of all, it’s G.722 capable. That makes it a viable candidate for use on this Friday’s VUC call on wideband VoIP.
What’s Happening This Friday?
The VoIP Users Conference weekly call on Friday, November 7, 2008 is all about wideband telephony. That is, using VoIP to deliver call quality vastly superior to the normal public telephone network (PSTN.) Our guest will be David Frankel, CEO of ZipDX, a commercial conferencing service that is specializing in wideband conference calling for businesses.
As usual anyone may join the call which gets underway at 12 noon EST on the Talkshoe conference service. That conference service can be reached by dial-in over the PSTN or by SIP URI. Details on how to connect to Talkshoe by various means can be found here.
For this one call only we will also be using the ZipDX wideband conference bridge. ZipDX and Talkshoe will be connected so that everyone will be on the call. Anyone connected to the ZipDX bridge using a suitable phone will be able to experience the call in G.722-based wideband quality.
Everyone else will experience the normal G.711 based narrowband conference quality that we all know and (despise) love.
A short while ago VUCs Randulo tweeted that he had recently updated the firmware on his Polycom phones. He said that he did this using a local provisioning server setup temporarily just for the task. If you’re using a hosted IP-PBX then you may not have a suitable server running 24/7/365.
If you don’t run a provisioning server all the time then booting the phones can take a lot longer. On boot-up the phones simply fail to contact the provisioning server and eventually boot using their existing internal settings. But this means waiting through a series of time-outs, which is the principle source of delay.
For quite some time I've had a SIP URI of one sort or another. It started with FWD, but I also have Gizmo5 and OnSIP accounts as well. I've made some of them public for over three years. I even…
A recent beta firmware for the snom m3 cordless system introduced a most annoying bug. The handset could be turned off with a simple press of the end call button if the phone was not actually on a call. This…