Would I be correct in assuming you have one port of your SPA2000 registered with VoXaLot and the other port registered with either Voxee or Vbuzzer, depending on which you're testing at that time? Is your SPA2000 also behind a router (what model)? If so, you might be fighting the same issues I had when I first tried to get Web Callback to work.
Prior to finding VoXaLot and especially prior to testing Web Callback, I was convinced everything was working perfectly here, VoIP-wise. My first tests with Web Callback were nothing but failures. In some cases, the calls wouldn't go through and in others I had one-way or no-way audio. I was using a Linksys WRT54G router with HyperWRT+tofu13c firmware. Finally, out of desperation, I switched to a Motorola WR850G router with DD-WRT v23 firmware. Like magic, everything VoXaLot related worked perfectly. I'm confident the different firmware is the key here, not the hardware platform.
A short while later I discovered that 3-way calling had audio problems with either firmware. To finally get everything working properly, I had to:
1. Use a STUN server with STUN Test enabled.
2. Set 'Substitute VIA Address' to Yes. All other VIA options have to be No.
3. Use explicit port range forwarding in the router for both SIP and RTP ports. If you have more than one ATA online, you must not have any overlapping port ranges across the devices.
Whether any of this has any bearing on your problem, I can't say.
Ron
|