May 2009
13 posts
Spot of trouble on atl.teliax.net, however it is up and running at this time.
Just posted the overview of Ivy, the ‘next big thing’ at Teliax: http://help.teliax.com/faqs/ivy-documentation/ivy-overview
Maintenance: Sat 23 May Upgrades to all four proxies to address issue with Session-Expires timers: http://jira.freeswitch.org/browse/SFSIP-147
Deploy complete. Booyah. IB IAX2 caller ID for TF and Domestic numbers works flawlessly.
Deploying fix for IAX2 caller ID for tollfree numbers to all proxies.
Caller ID to IAX2 Toll-Free numbers fixed, alternately, caller ID to IAX2 Domestic US numbers impaired. Working on this.
Update to voip.nyc.teliax.com - Everything is up and running stable at this time, we’ll continue to monitor the proxy for any further trouble.
voip.nyc.teliax.com
HDD failure on legacy NYC proxy voip.nyc.teliax.com.
Repair underway.
ETR 1 hr.
Scratch that. I think I just solved the early media problem. I’m going to leave den.teliax.net as-is until Monday (probably) for testing. If you call an endpoint that doesn’t ring, but does pick up, please please let me know - benji@teliax.com - alternately, if anything is broken, definitely let us know.
Maintenance complete, but I’m really no further in fixing this early media problem - a problem that really shouldn’t exist. Broken endpoints suck completely. If only every phone could generate its own ringback! Please let us know if there are any problems, although none are expected whatsoever.
Starting maintenance described earlier. Possible dropped calls on den.teliax.net.
Fixed an issue with voicemail on voip-co4.teliax.com yesterday. Voicemail failover would fail, now it doesn’t.
Feel free to join us on IRC, #teliax on freenode!