Voxalot / SIP Broker Support Forums

Voxalot / SIP Broker Support Forums (https://forum.sipbroker.com/index.php)
-   Voxalot Support (https://forum.sipbroker.com/forumdisplay.php?f=4)
-   -   can't register on US server. EU and AU work OK (https://forum.sipbroker.com/showthread.php?t=5163)

rchalk 05-13-2010 01:31 AM

can't register on US server. EU and AU work OK
 
I posted previously that I couldn't get my PAP2T to register on Voxalot. I tried it with XLite softfone, and it works sometimes, while other times I get error 401 forbidden.

I then tried on the EU and AU servers, and everything worked OK, so I tried the PAP2T, and it also registers on these two, but not on US.

I even tried my Asterisk PBX, with the same results. Is there something wrong with the US server, or am I missing something?

Thanks for your help

Richard

beaver 05-13-2010 04:04 AM

us.voxalot.com is ok.
but proxy01.us1.voxalot.com is down.

richard 05-13-2010 08:36 PM

rchalk

Did you ever get this issue resolved? Is the Voxalot account in question a new account?

I too cannot register a new Voxalot Account (opened for my cousin) on us.voxalot.com, but it registers just find on eu.voxalot.com and au.voxalot.com.

My personal Voxalot account which i s many years old registers just fine on us.voxalot.com.

Thanks

Richard

balazer 05-17-2010 07:16 PM

Same here: in Sipdroid, I can't register with us.voxalot.com; eu and au work. But strangely, using Phonerlite on my desktop, I can connect to us.voxalot.com

I think that us.voxalot.com is resolving to proxy02.us1.voxalot.com on my phone. proxy02 appears to be down - I can't connect to it from my phone or my desktop. proxy01.us1.voxalot.com works on my phone and my desktop

I don't know if this is a DNS caching problem, or what. I can't find any tools for Android to tell me what the system resolver is doing.

rchalk 05-18-2010 01:57 AM

Quote:

Originally Posted by balazer (Post 27943)
Same here: in Sipdroid, I can't register with us.voxalot.com; eu and au work. But strangely, using Phonerlite on my desktop, I can connect to us.voxalot.com

I think that us.voxalot.com is resolving to proxy02.us1.voxalot.com on my phone. proxy02 appears to be down - I can't connect to it from my phone or my desktop. proxy01.us1.voxalot.com works on my phone and my desktop

I don't know if this is a DNS caching problem, or what. I can't find any tools for Android to tell me what the system resolver is doing.

I am still not able to get this to work right. If I use proxy01.us1.voxalot.com it works OK, but if I just use us.voxalot.com it will not register. eu and au also work, but ping times are much longer of course.

beaver 05-18-2010 04:34 AM

Yep, latency is unacceptable long, with serious echo.
but that' the way to go.
This proxy problem has been a while. sounds no fix at all. Most of recent post were talking about this.

richard 05-18-2010 03:20 PM

Hi Guys

Okay, when I use proxy01.us1.voxalot.com on the new account I created for my cousin, it works!!! Great.

Odd thing is that my personal Voxalot account works on the same ATA when registered with us.voxalot.com, just not the new account.

I'm assuming using proxy01.us1.voxalot.com is a good workaround as just as effective as if I got us.voxalot.com working.

Thanks for you help

Richard

Milzon 05-19-2010 09:35 PM

Quando voce tenta se conectar via us.voxalot.com e isso não é possivel, dependendo do seu ATA ou softphone, ele automaticamente tenta em eu.voxalot.com ou au.voxalot.com. Parece que contas novas não estão funcionando no us.voxalot.com.

Outro problema é com a alteração no dial-plan que não é atualizado em us.voxalot.com.

No ata pap2, as opções "Use DNS SRV: yes" e "DNS SRV Auto Prefix: yes"
permitem a busca automatica por outros proxyes (eu e au) quando o us não funciona.
------------------------------------------------------------------------------
When you try to connect via us.voxalot.com and this is not possible, depending on your ATA or softphone, it automatically tries in eu.voxalot.com or au.voxalot.com. It seems that new accounts are not working in us.voxalot.com.

Another problem is the change in dial-plan that is not updated in us.voxalot.com.

In pap2 ata, then "Use DNS SRV: yes" and "DNS SRV Auto Prefix: yes"
allow searches automatic by another proxy (eu or au) when the us does not work.

Milzon 05-20-2010 01:18 AM

Acabei de conferir a dica do rchalk e o richard.
us.voxalot.com vai para proxy02.us1.voxalot.com, que esta desatualizado, não funciona contas novas e tambem não funciona atualizações em contas antigas. Usem no lugar do us.voxalot.com o proxy01.us1.voxalot.com.
-----------------------------------------------------------------
I just give the tip of the rchalk and richard.
us.voxalot.com goes proxy02.us1.voxalot.com that this outdated, not working new accounts and not work also updates in old account. Use in place of the us.voxalot.com proxy01.us1.voxalot.com.

martin 05-26-2010 09:23 AM

Root cause has been identified. Please see:

http://forum.voxalot.com/voxalot-sup...html#post28204

richard 05-26-2010 11:56 AM

Yes I can confirm that registering with us.voxalot.com now works find on the problem 'new' account. Thanks :-)

beaver 05-27-2010 04:07 AM

Just tested.
No problem to register at us.voxalot.com.
most of my dial plan is working, but still some not.
500 *${EXTEN} still not work. No dial tone, need to dial *500 to access my VM.
xxxxxx *010${EXTEN} not working either. No dial tone. member/sip call needs to dial *010xxxxxx.
didn't try betamax. I deleted it from my voice providers since us server mal-functional.

beaver 06-17-2010 04:20 AM

have to use eu.voxalot.com again.
us.voxalot.com not working for me today.

Update

My betamax wouldn't work if set eu.voxalot.com as proxy (I am at USA). It only takes us.voxalot.com.
But I had a problem (no audio) to make USA call if staying with us.voxalot.com. what a pain.
I am removing betamax from my VSP list temporarily while keep using eu.voxalot.com. Possibly set betamax on 2nd ata.


2nd update
I am using 64.34.173.199 static IP. seems working so far.


All times are GMT. The time now is 12:46 PM.

Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2022, Jelsoft Enterprises Ltd.