Comments for this page:
firstname.lastname@example.org on 2012-05-17 17:15:18 220.127.116.11
Thank you for fixing this; I had been noticing it over the past couple of years but haven't used VoIP enough to try to track down the problem and I assumed it was a configuration issue. I appreciate that you are still fixing bugs as so many companies seem to abandon their products as quickly as they can. -Matt
Woodyposted on 2012-05-17 17:46:31 18.104.22.168
Thanks for the feedback, Matt. Next time when you find anything strange, please let us know as soon as possible.
email@example.com on 2013-04-11 18:16:19 22.214.171.124
Actually, it isn't because of a lack of need for IAX2 support. We have several gateways and phones based on the PA1688 chipset, in fact we tested multiple manufacturer's phones. We configured these to use IAX, and they have never worked without terrible garbling and dropouts across multiple asterisk switches, across many different network scenarios, and were basically unusable. So we moved to using Asterisk IAXY's and analog phone sets.
I came here as a last ditch effort before finally throwing the units out to see if any new firmware had arrived that would make them work.
I would carefully consider continuing to support IAX due to SIP's NAT limitations. I would guess that the lack of interest hasn't been that IAX is dead, rather, that the PA1688 implementation just hasn't worked and people have moved on to other IAX solutions.
Just my perspective, not necessarily that of the rest of the population...
firstname.lastname@example.org on 2013-11-06 11:16:26 126.96.36.199
IAX2 has no limitations like sip protocol. i have a company and we have only iax2 devices.
Woodyposted on 2013-12-12 02:39:55 188.8.131.52
Only have iax2 devices may hurt your company.
“It is not the strongest or the most intelligent who will survive but those who can best manage change.”
― Charles Darwin