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. |
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 |
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. |
Will "new symmetric NAT setting" work for ATA behind a Zyxell symmetric firewall?
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:
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? |
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? |
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. |
Quote:
|
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] |
Quote:
|
Okay thanks, my bad. I did try it, the catchall must have got me before I changed that.
|
All times are GMT. The time now is 08:33 PM. |
Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.