VoXaLot Release Notes - 20070122 - Page 3

casch · 01-31-2007, 11:22 AM

Hi,

just tried to call s.o. at voxalot (*010280281) and I got a buzzy signal
immediately - even with my second number at voxalot (*010408236).
Even *XXXXX does not work.

When I try to reach the echo test:
*010600 => We're sorry the no. you have dialed could not be connected.
*600 => You're entereing the echo test... (so this works).
I have a SPA941 (hardphoone) and pressing it's voicemail button directly
connects me to my voicemail box, this is ok.

casch · 01-31-2007, 11:28 AM

Hi again,

would it be possible to send announcements about changes to the email
addresses instead of posting it (only) in the forum?

Otherwise all of a sudden somthing or everything does not work anymore
and I don't know why!

I really would appreciate knowing about changes in advance.

But of course your service is greate!
Carl

martin · 01-31-2007, 11:42 AM

Hello casch,

Thanks for the suggestion we have already decided that we should do this in the future.

As for your problem.

280281 is currently no in the registry. You may want to check that a device is registered using this account.

408234 is not working because you have a bad call forwarding entry beginning with sip:// (there is no need for the //)

Anyway thanks again for the suggestion.

p2pvoice · 02-13-2007, 05:07 AM

Martin:
This is a very impressive service!
I had had registered with Voxalot some time ago but didn't understand the POWER of this service until now. Today, I spent most of the day reading/testing tutorials.

One particular item - symmetric NAT handling - in this changelog caught my attention:

Quote:

Originally Posted by martin

VoXaLot Release Notes - 20070122
================================
New symmetric NAT handling setting

a). A new field has been added to the member details page that allows members to turn on/off VoXaLot NAT handling. This option is useful for disabling NAT handling for non symmetric NAT de vices such as the Cisco 7961G.

Note: If unsure, please leave this setting to "Yes"

I have many Grandstream ATAs, that are behind common SOHO router NATs, working well with my Asterisk server. However, one particular router - Zyxell Prestige 660HW-61 - is causing major headaches. So, I wanted to register this HT286 behind Prestige 660HW-61 with Voxalot and see how it works.

Prestige 660HW-61 apparently has a symmetric NAT/Firewall. Will an HT286 behind Zyxell Prestige 660HW-61 router work with Voxalot?

Do I have to set an "Outbound Proxy" to work with Zyxell?

If so, what is the relavent setting for HT286?

One more thing: I didn't quite understand "symmetric NAT handling capability" that is useful for "disabling NAT handling for non symmetric NAT de vices". an you please expand on this?

affinity · 03-08-2007, 03:32 PM

I thought that we could use 500 or *500 and 600 or *600 -- it now seems that both 500 and 600 fail to work on the test server and on the production server.

Wasn't 500 and 600 supposed to be set to still work to help those that couldn't send a * in their dialed number?

affinity · 03-08-2007, 03:38 PM

I've added dial plan entries as mentioned earlier in this thread.

_500 => *600 via VoXaLot
_600 => *600 via VoXaLot

Perhaps these can be added as default dial plan entries as well as the new 999 catch all one for new accounts -- or better still have these as automatic 'implied' dial plan entries that don't need to be set up.

martin · 03-08-2007, 10:10 PM

Quote:

Originally Posted by affinity

I've added dial plan entries as mentioned earlier in this thread.

_500 => *600 via VoXaLot
_600 => *600 via VoXaLot

Perhaps these can be added as default dial plan entries as well as the new 999 catch all one for new accounts -- or better still have these as automatic 'implied' dial plan entries that don't need to be set up.

Just change the default dial plan pattern from _x. to _xxxx. We do not recommend adding the 2 entries you document above.

affinity · 03-09-2007, 02:34 AM

500 _500 *500 VoXaLot No
600 _600 *600 VoXaLot No
99999 _xxxx. ${EXTEN} SIPME Yes

A call to:500 will not get forwarded.
A call to:600 will not get forwarded.

[same results exactly on test.voxalot.com and voxalot.com dial plan test]

martin · 03-09-2007, 03:31 AM

Quote:

Originally Posted by affinity

500 _500 *500 VoXaLot No
600 _600 *600 VoXaLot No
99999 _xxxx. ${EXTEN} SIPME Yes

A call to:500 will not get forwarded.
A call to:600 will not get forwarded.

[same results exactly on test.voxalot.com and voxalot.com dial plan test]

The test feature must not have factored in these rules. Try makeing a call using the above.

affinity · 03-09-2007, 03:59 AM

Okay thanks, my bad. I did try it, the catchall must have got me before I changed that.

01-31-2007, 11:22 AM	#21
casch Senior Member Join Date: Oct 2006 Posts: 122 Thanks: 5 Thanked 5 Times in 5 Posts	can't reach voxalot numbers anymore Hi, just tried to call s.o. at voxalot (010280281) and I got a buzzy signal immediately - even with my second number at voxalot (010408236). Even XXXXX does not work. When I try to reach the echo test: 010600 => We're sorry the no. you have dialed could not be connected. *600 => You're entereing the echo test... (so this works). I have a SPA941 (hardphoone) and pressing it's voicemail button directly connects me to my voicemail box, this is ok. __________________ Ata: Fritzbox 7270 VoIP: VoipDiscount, VoipCheap, VoXaLot.com

01-31-2007, 11:28 AM	#22
casch Senior Member Join Date: Oct 2006 Posts: 122 Thanks: 5 Thanked 5 Times in 5 Posts	please use my email address when you change the behaviour Hi again, would it be possible to send announcements about changes to the email addresses instead of posting it (only) in the forum? Otherwise all of a sudden somthing or everything does not work anymore and I don't know why! I really would appreciate knowing about changes in advance. But of course your service is greate! Carl __________________ Ata: Fritzbox 7270 VoIP: VoipDiscount, VoipCheap, VoXaLot.com

01-31-2007, 11:42 AM	#23
martin Join Date: Feb 2006 Posts: 2,930 Thanks: 528 Thanked 646 Times in 340 Posts	Hello casch, Thanks for the suggestion we have already decided that we should do this in the future. As for your problem. 280281 is currently no in the registry. You may want to check that a device is registered using this account. 408234 is not working because you have a bad call forwarding entry beginning with sip:// (there is no need for the //) Anyway thanks again for the suggestion. __________________ Martin Please post support questions on the forum. Do not send PMs unless requested.

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
Voxalot and Sipura/ATA Tutorial: A Comprehensive Walkthrough	ctylor	Voxalot General	5	04-28-2010 12:52 AM
Can't get voice packets to bypass VoXaLot	v164	Voxalot Support	35	08-23-2009 10:25 PM
VoXaLot not working with PBXes (VoXaLot as an extension of PBXes)	wilsonhlacerda	Voxalot Support	31	12-09-2007 02:30 PM
VoXaLot Release Notes - 20070227	martin	Voxalot Support	31	03-25-2007 08:55 AM
Newbie - but please be nice	Mallycat	Voxalot Support	21	04-15-2006 07:50 AM

03-08-2007, 03:32 PM	#25
affinity Join Date: Apr 2006 Posts: 799 Thanks: 66 Thanked 61 Times in 44 Posts	I thought that we could use 500 or 500 and 600 or 600 -- it now seems that both 500 and 600 fail to work on the test server and on the production server. Wasn't 500 and 600 supposed to be set to still work to help those that couldn't send a * in their dialed number?

03-08-2007, 03:38 PM	#26
affinity Join Date: Apr 2006 Posts: 799 Thanks: 66 Thanked 61 Times in 44 Posts	I've added dial plan entries as mentioned earlier in this thread. _500 => 600 via VoXaLot _600 => 600 via VoXaLot Perhaps these can be added as default dial plan entries as well as the new 999 catch all one for new accounts -- or better still have these as automatic 'implied' dial plan entries that don't need to be set up.

03-09-2007, 02:34 AM	#28
affinity Join Date: Apr 2006 Posts: 799 Thanks: 66 Thanked 61 Times in 44 Posts	500 _500 500 VoXaLot No 600 _600 600 VoXaLot No 99999 _xxxx. ${EXTEN} SIPME Yes A call to:500 will not get forwarded. A call to:600 will not get forwarded. [same results exactly on test.voxalot.com and voxalot.com dial plan test]

03-09-2007, 03:59 AM	#30
affinity Join Date: Apr 2006 Posts: 799 Thanks: 66 Thanked 61 Times in 44 Posts	Okay thanks, my bad. I did try it, the catchall must have got me before I changed that.