IAX2 services are now back online. Our engineers have identified the problem and restarted the IAX2 service. All SIP services were unaffected - these seems to be a bug in Asterisk that failed registrations on one of our IAX2 platforms. Around 50% of 2talk's IAX2 users were affected by the problem. We apologise for any inconvenience caused and recommend for business critical users that they use the SIP protocol or at least have a SIP configuration as backup.
We are also looking at improving our monitoring of the IAX2 platforms as a result of today's issues.
FYI: We have implemented new monitoring scripts now to better analyse IAX2 peer information to avoid further issues like this in the future. This should alert our engineers when there is a similar issue in the future. Our monitoring systems did not pick up this issue since the problematic IAX2 host was still listening on port 4569 and responding to polling however there appears to have been a software issue causing registration failures. This issue is still unknown but looks like a deadlock issue inside the Asterisk code.
We remain committed to IAX2 support for the NZ community and although the service is officially still in Beta we will continue to improve our IAX2 offering for customers into the future.
While There's a 2talk person here: I signed up with you recently and haven't had any problems, but your website is horribly out of date. There's broken links to the forums, text that is out of date, blog which hasn't been updated since 2009 etc. Was a little worried that you didn't actually still exist!
We have fixed a couple of links to the Blog from the 2talk web portal - but apart from these we are unable to find any more broken web links - can you please email firstname.lastname@example.org with these broken links so we can investigate for you.
And, yes we are very much still here. Many user guides though have remained unchanged since 2009 since nothing has changed in the setup instructions!