Audio issues on wifi have nothing to do with the signaling protocol, they have everything to do with the codecs and other media features. My biggest issue with wifi based sip phones is the battery life sucks. Don't bother w/ IAX2 its a solution looking for a problem. Mike On Oct 10, 2013, at 10:19 PM, Karl Schmidt <karl@xtronics.com> wrote:
A few more notes:
It appears that Skype and Google voice work well enough over wifi - but not SIP. So I'm starting to think that the SIP protocol stack is the problem?
There are other standards - Most are proprietary, but it looks like jingle is on a BSD licenses.
I can't seem to find anything that mentions the license of IAX2 ?? There are some softphones that support IAX2. Mod Opal lets freeswitch talk via IAX2 - I don't know if it is working? If anyone has tested a IAX2/freeswitch/wifi combination - I would be quite interested in the results.
Squinting into the future - the question is if the new wifi standard 802.11ac or a move beyond SIP will be the solution to VoIP/wifi
It does look like 802.11ac has addressed some latency issues with MU-MIMO, but I've been unable to find any real-world numbers. This is a complex new standard that will take a while to get debugged and bench marked. Could be that any wifi that has more than one connection will glitch audio - and MU-MIMO could fix that.
Right now it still looks like a SIP world that we live in..