View Single Post
Unread 10-27-2010, 02:56 AM   #4
Join Date: Jul 2007
Location: Toronto, Canada
Posts: 1,422
Thanks: 123
Thanked 369 Times in 282 Posts
emoci is a name known to allemoci is a name known to allemoci is a name known to allemoci is a name known to all

The gist of things (ideally) is as follows:

-Your Device or SoftPhone should be registered with the specific cluster that you have selected in your acct. (you must use rather than just where xx is us, eu or au--)

Question: When you say you could not reach a you mean you could not perform a registration to it ... or you could not reach it as in you could not call from SipBroker?

Sidenote: If you are doing a lot of on/off regostration between clusters expect some oddities...changes across all proxies can take sometime to propagate. If you wanna monitor the registration VoXalot is seeing (and which server it sees you registered to) go to ... after you've logged in to your VoXalot acct.

-Incoming SIP URI calls to your acct. should preferrably be sent to: (this form of forwarding should work most of the time... xx must match the cluster you've set in your acct. and to which your device/softphone is registered).

One issue that may arise here is due to a combination of the "Failover" strategy ( and the fact that the US and EU clusters each involve two different proxies ( If one of the proxies is having issues, and the calling-party provider is not performing a DNS SRV lookup reliably issues may arise with calls reaching you.

-Calls to should also work (one catch is that if the calling-party service does not do an DNS SRV lookup reliably you may come accross issues here ... even if it is not a failover situation).

-As far as SipBroker goes... *010 should work reliably (and has more or less been tested) to reach most of the user accounts, regardless of their cluster. Theoretically the other two *xxx codes for eu and au should also be interchangeable...however there hasn't been too much testing from the user community in that front.

Issues with incoming calls can also be possible NAT issues... here's a few quick crash-test things to try:


-Try calling a SIPBroker number (SIPBroker - PSTN Numbers), then *010123456 , 123456 replaced with your VoXalot number. Do you receive this call, and is this also suffering from audio problems?

-Try entering your voxalot URI in the link below. Instead of you calling Echo, echo will call you so you can see how it behaves when it is an incoming call: SIPBroker - EziDial

-If your router has UPnP I would suggest activating that rather than DMZ

-Preferably make sure you have STUN set up (

-This is optional, but it may help to open these port ranges and forward them to your ATA's IP:

16300-16500 (for PAP2/SPA3102...this maybe slightly different for your ATA, there should be an RTP port range setting on your ATA, if it is different, note the range and open that range instead in your router...)
For some background on this see:

-Make sure there are no Internet Connection problems. Run a SpeedTest, or maybe VoIP test at

-If Nat Symmetric Hanlding is set to NO and Optimize audio to YES (these are both settings in your VoXalot account), try setting Nat Symmetric Handling to YES and Optimize audio to NO

-Make sure that the codec string used for providers (personally I've had good results with this string) is: ulaw;alaw;g726;g729;ilbc;gsm

-Another good resource for info: Main Page - Voxalot FAQ
emoci is offline   Reply With Quote