Woody Home Page
 
   
The End of IAX2
  
Nov 13, 2011
Yesterday Tang Li fixed an IAX2 outgoing voice bug when used as callee. This bug was the result of 1.57 changes back in 4 and a half years ago. An user added remote ring back tone for IAX2 and we merged the source code changes without careful test.
It is surprising this obvious bug was not found until recently reported by another user. Considering that our website has very steady visitors about 1k per month, and over half of them are looking for PA1688 software update, the only explanation would be that nobody is interested in IAX2 any more.
We were proudly to support 7 different communication protocols in PA1688, but wisely reduced to SIP and IAX2 only with AR1688. As video and voice over IP market getting mature today, now I believe SIP will be the only one we need to support with the coming PA6488 solution.

Comments for this page:

darkstar@city-net.composted on 2012-05-17 17:15:18 24.143.94.36
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 125.33.179.148
Thanks for the feedback, Matt. Next time when you find anything strange, please let us know as soon as possible.

bmusker@xposurenetworks.composted on 2013-04-11 18:16:19 70.50.229.4
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...

Woodyposted on 2013-05-07 13:54:47 203.189.158.123,
PA1688 based ATA had never been a successful product. Sorry for the bad experience. This is why we gave it up in AR1688 and other later products.
But this is not IAX2 protocol related.

constantin_ciuntu_mihai@yahoo.composted on 2013-11-06 11:16:26 82.78.162.67
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 50.199.3.33
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

More options? Please login or register account.