VoXaLot Changes / Fixes

[martin]

We have put in place the final patches to the new Oz server and upgraded both servers to the latest versions of software.

As a result, users may need to re-record any voicemail greetings they may have previously had.

MWI should now work for both servers

You should also now be able to call other VoXaLot users registered on either of the two servers.

Please report any issues.

Thanks.

[richard]

Hi Martin

Okay, this got rid of the MWI staying on on my eyeBEAM even though there are no message ;-), but unfortunately now that I have messages, the MWI does not come back on :-(

Richard

[moollar]

Originally Posted by martin

We have put in place the final patches to the new Oz server and upgraded both servers to the latest versions of software.

You should also now be able to call other VoXaLot users registered on either of the two servers.

Thanks.

Does this mean I can now change my ENUM entry and point my DID at xxxxxx@voxalot.com.au?

[martin]

I would first test by dialling one of the SIP Broker PSTN access numbers and trying:

*010<voxalot-number>

If your phone rings then you should be in good shape.

[moollar]

Originally Posted by martin

If your phone rings then you should be in good shape.

It rang!

[martin]

Originally Posted by moollar

It rang!

Good stuff. If you are registered with voxalot.com.au and the *010 dialling worked then you are good to make the ENUM change.

Note: The above test may not work for a small number of users due to a NAT issue on registration. We are currently looking at a work around for these users and will advise.

[moollar]

Originally Posted by martin

Good stuff. If you are registered with voxalot.com.au and the *010 dialling worked then you are good to make the ENUM change.

Done! Thanks again Martin.

[richard]

Martin

Good News!!!

MWI now works fine on eyeBEAM.

Comes on when a message comes in....

Goes off after message is retrieved ;-)

This is all after changing to voxalot.com.au

Thanks - works great - great service!!!!


Richard

[martin]

The NAT issue has been resolved. Both voxalot.com and voxalot.com.au should now fully inter-operate

Please let us know if you find any problems.

[affinity]

Originally Posted by martin

The NAT issue has been resolved. Both voxalot.com and voxalot.com.au should now fully inter-operate

Please let us know if you find any problems.

Okay, here's something for you... perhaps it should be a different thread, but you are talking about NAT issues, so here goes.

When using my 7402VGO:
1- **320 1777xxxxxx [via sipbroker profile]
2- **320 1777xxxxxx [via voxalot.com.au registered port]
(dial plans setup to replace ** with *)

3- 320 1777xxxxxx [call made via voxalot.com.au registration using voxalot dial plan routes to SIPME as provider to laptop]


Laptop [on other network]
- SIPME number registered with eyeBeam

1 and 2 above cause eyeBeam to ring, but cannot get any audio, no matter what I forward from my NAT SPI firewall [ipcop] to my laptop.

3 works perfectly.

Where is my NAT problem?




Further call tests that all work fine:

Sipbroker PSTN to VoIP gateway call to SIPME account on the laptop.

Web callback -- 85xxxx using voxalot.com.au to 0387xxxxxx using SIPME works fine.
[call between voxalot.com.au registered 7402vgo port and fixed line number]

Web callback -- 85xxxx using voxalot.com.au to 1777xxxxxx using SIPME works fine.
[call between voxalot.com.au registered 7402vgo port and SIPME account on laptop running eyeBeam]