I just made an IP call to my 7402VGO, my Exetel number @ ip.ad.dr.ess -- it was fine. VM worked fine and 600 failed to work again. Currently with voxalot STUN server.

VoXaLot does not require a STUN server as we do RTP Proxying although using one does have benefits. I am wondering if the problem is STUN related hence the request to remove the STUN server from your ATA config.

The ATA is behind a NAT SPI firewall, so it needs the help of a STUN server for incoming calls at least.

Just turned off the STUN server setting and 600 works now, but this is no good if I wish to receive calls on the ATA.

I would sanity check your STUN setup vs the recommendations here:

http://faq.sipbroker.com/tiki-index....%20or%20Sipura

STUN is good but can be prone to setup problems. This is the reason we setup an RTPProxy to make it easier for people to get going.

As Ron suggested try a bunch of other STUN servers. I just re-tested VoXaLot using one of our ATA's setup with STUN and it worked ok with 600.

@Ron as you are setup using voxalot.com with STUN can you try dialling *7607600 (the voxalot.com.au echo test).

The ATA that I am using has very simple ON/OFF setting for STUN with the server name (or IP) and the port. It has worked with STUN before, so it _should_ work now.....

STUN server re-enabled, using stun01.sipphone.com now. 500 (VM) works fine, 600 doesn't.... the ATA has no dial plans of its own setup. With no STUN, 600 worked okay as reported above.

When you say 500 works fine is it 2 way audio?

Also what happens when you dial *010600 ?

Edit: and *7607600 ?

500 works 2 way, so does *010600 -- calling 600 directly doesn't work.

Ok what about *7607600?

*7607600 fails, so it seems it is just the 600 routing for voxalot.com.au when a STUN server is used....

What about registering your ATA to voxalot.com and dialing:

600
*7607600