Announcement: AU Server Upgrade
 

Announcement
===========

We would like to advise members of a planned system upgrade scheduled to take place on Friday 7th Sept at 4:00am AEST (GMT+10)

This upgrade is necessary to enable us to cater for the current growth in the AP region.

For most users this will be a seamless upgrade with no telephony interruptions.

Members that use MNF as a provider will however, need to make a change to their device / phone to explicitly point to the new proxy.

Over the next day or two we will be sending an email to these members advising them on what needs to be done as well has posting the instructions here.

If you have any questions / concerns please feel free to contact us.

Thanks.
.

Upgrade is now complete.
.

Does this mean that we can now all use au.voxalot.com and it will now work exactly as it did before -- including MNF ?

The majority of users can continue to use au.voxalot.com while the DNS updates take place.

MNF users have been emailed directly with instructions. We will email these users again in (24-48hrs) notifying them when they can go back to using au.voxalot.com
.

Great, so au.voxalot.com and proxy.au1.voxalot.com should both resolve to 202.60.88.238 then?

Yes, although proxy.au1.voxalot.com has been temporarily setup to help with the MNF transition and is not recommended to be used in long term.

Once au.voxalot.com points to 202.60.88.238 you are up and running on the new server.
.

Broken
 

Currently voxalot connection is broken for me.
It is a "silent call" issue - such that the phone rings at other end but i hear nothing. Same problem occured several months ago when Pennytel upgraded their proxy - ( my workaround was to use voxalot to register with pennytel ). Problem appears to be due to the old model of router/firewall I am using. (Billion BiPac 741).

Is a non-upgraded voxalot proxy still available somewhere?

I'm having the same problem. If I change to the US cluster. i.e. us.voxalot.com everything works. au.voxalot.com and I get the same "silent call" problem.

au.voxalot.com resolves to the correct IP address.

Any ideas?

Sorry guys,

The RTPProxy on the new server was missing a setting. Please re-test and let us know if there is still a problem.
.

All good now :) Thx.