ATA registered but cannot call each other

shahidr100 · 07-25-2010, 04:15 PM

Hello room,

I have 2 voxalot numbers 5154XX and 5154YY.

4XX is configured in SPA 2100 with latest firmware.
4XX is registered with Voxalot. Device in India in city 1.

4YY is configured in SPA 1001 with latest firmware.
4YY is registered with Voxalot. Device in India in city 2.

4XX can call 4YY but 4YY cannot call 4XX. Sometimes both cannot call each other. Facing this problem since last 2 months. It was working fine earlier. Have done all permutations and combinations of settings to resolve it but in vain.

I thought that maybe provider is blocking it but that also has been ruled out. To be on the safer side, I have changed the port to 80 as showed in the FAQ and tutorials section.

Interesting fact is that I can receive call on the devices from US without any hassle.

Can i take a trace between the ATA and Voxalot from my laptop.

Need help. Any suggestions?? Am i missing something.

emoci · 07-27-2010, 04:35 AM

Have you tried to call them by using *010-123456 (where 123456 is your 6 digit VoXalot number)?

It sounds like a NAT issue with 4XX (affecting incoming calls)...

The other thing to try is use a different server cluster (if using eu try us) and don't forget to change the respective cluster in your VoXalot acct. online...

beaver · 07-27-2010, 11:39 PM

emoci is right.

But if you mentioned it had happened "since last 2 months". Most likely it's due to recent voxalot server issue. Even it reported it's fixed. But as I know, I still have USA friends couldn't use them as usual.

yes, try all au/eu/us.voxalot.com proxy and see if the problem is gone or improved.

07-25-2010, 04:15 PM	#1
shahidr100 Junior Member Join Date: Mar 2009 Posts: 8 Thanks: 0 Thanked 0 Times in 0 Posts	ATA registered but cannot call each other Hello room, I have 2 voxalot numbers 5154XX and 5154YY. 4XX is configured in SPA 2100 with latest firmware. 4XX is registered with Voxalot. Device in India in city 1. 4YY is configured in SPA 1001 with latest firmware. 4YY is registered with Voxalot. Device in India in city 2. 4XX can call 4YY but 4YY cannot call 4XX. Sometimes both cannot call each other. Facing this problem since last 2 months. It was working fine earlier. Have done all permutations and combinations of settings to resolve it but in vain. I thought that maybe provider is blocking it but that also has been ruled out. To be on the safer side, I have changed the port to 80 as showed in the FAQ and tutorials section. Interesting fact is that I can receive call on the devices from US without any hassle. Can i take a trace between the ATA and Voxalot from my laptop. Need help. Any suggestions?? Am i missing something.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Free DID Numbers, Free Voip Calls, & more Voip Info	amroe	Voxalot General	54	01-13-2014 09:11 AM
Only 1 of 2 registered contacts receiving the call	green	Voxalot Support	0	09-14-2008 11:43 AM
Call recieve problem from registered provider	majo	Voxalot Support	10	07-13-2007 06:49 AM
Call Forward Tpad Status Registered	richard99	Voxalot Support	1	06-22-2007 11:38 AM

07-27-2010, 04:35 AM	#2
emoci Join Date: Jul 2007 Location: Toronto, Canada Posts: 1,422 Thanks: 123 Thanked 369 Times in 282 Posts	Have you tried to call them by using *010-123456 (where 123456 is your 6 digit VoXalot number)? It sounds like a NAT issue with 4XX (affecting incoming calls)... The other thing to try is use a different server cluster (if using eu try us) and don't forget to change the respective cluster in your VoXalot acct. online...

07-27-2010, 11:39 PM	#3
beaver Member Join Date: Feb 2010 Location: Beaverton, USA Posts: 72 Thanks: 8 Thanked 3 Times in 3 Posts	emoci is right. But if you mentioned it had happened "since last 2 months". Most likely it's due to recent voxalot server issue. Even it reported it's fixed. But as I know, I still have USA friends couldn't use them as usual. yes, try all au/eu/us.voxalot.com proxy and see if the problem is gone or improved.