(FUP exceeded) and Voxalot and Betamax

Tony · 04-26-2007, 09:11 PM

I will contact Betamax to see what the issue is with the Fair Use Policy with all voxalot members.

Tony.

craig · 04-27-2007, 12:02 AM

There are two scenarios in play here:

You make a call directly via your ATA. VoXaLot is still sending your ATA's IP address (as it has done since we made the change a fortnight or so ago.) Nothing has changed on our side. Betamax must have changed something on their side.
You make a call via the web-callback. In this case, VoXaLot is initiating both call legs, so Betamax will receive the VoXaLot IP address. This is a limitation of the web-callback service. Because you aren't initiating the call from your ATA, we don't know what your ATA's outward-facing IP address is, so we can't send that to Betamax. In this case, Betamax may block the calls (I suspect this is the case for web-callback).

We will contact Betamax to try to understand why the first scenario is not working as you would expect.

--
Craig

Lanh · 04-27-2007, 01:55 AM

Lovely, same message here and I have used a grand total of 13 minutes and 58seconds this MONTH let alone week :lol:

Calls made using EU server together with ATA, VoipBusterPro product.

haifischjunge · 04-27-2007, 04:37 AM

Ive red somewhere else, that the 300 minutes/ip-address limit for free calls is in power since yesterday.

raphoumail · 04-28-2007, 06:25 PM

Quote:

Originally Posted by craig

There are two scenarios in play here:

You make a call directly via your ATA. VoXaLot is still sending your ATA's IP address (as it has done since we made the change a fortnight or so ago.) Nothing has changed on our side. Betamax must have changed something on their side.
You make a call via the web-callback. In this case, VoXaLot is initiating both call legs, so Betamax will receive the VoXaLot IP address. This is a limitation of the web-callback service. Because you aren't initiating the call from your ATA, we don't know what your ATA's outward-facing IP address is, so we can't send that to Betamax. In this case, Betamax may block the calls (I suspect this is the case for web-callback).

We will contact Betamax to try to understand why the first scenario is not working as you would expect.

--
Craig

Hi. Even without using the web call back feature.
Just using Betamax thru Voxalot makes this prob.
Using the ata directly registered to betamax (-> no voxalot), no prob.

Thanks

Raphael

04-27-2007, 12:02 AM	#2
craig Join Date: Feb 2006 Posts: 243 Thanks: 8 Thanked 130 Times in 72 Posts	There are two scenarios in play here: You make a call directly via your ATA. VoXaLot is still sending your ATA's IP address (as it has done since we made the change a fortnight or so ago.) Nothing has changed on our side. Betamax must have changed something on their side. You make a call via the web-callback. In this case, VoXaLot is initiating both call legs, so Betamax will receive the VoXaLot IP address. This is a limitation of the web-callback service. Because you aren't initiating the call from your ATA, we don't know what your ATA's outward-facing IP address is, so we can't send that to Betamax. In this case, Betamax may block the calls (I suspect this is the case for web-callback). We will contact Betamax to try to understand why the first scenario is not working as you would expect. -- Craig

04-26-2007, 09:11 PM	#1
Tony Join Date: Jan 2007 Location: Sydney Posts: 221 Thanks: 64 Thanked 106 Times in 49 Posts	I will contact Betamax to see what the issue is with the Fair Use Policy with all voxalot members. Tony.

04-27-2007, 01:55 AM	#3
Lanh Member Join Date: Feb 2007 Posts: 71 Thanks: 10 Thanked 1 Times in 1 Posts	Lovely, same message here and I have used a grand total of 13 minutes and 58seconds this MONTH let alone week :lol: Calls made using EU server together with ATA, VoipBusterPro product.

04-27-2007, 04:37 AM	#4
haifischjunge Member Join Date: Apr 2007 Location: Vienna, Austria Posts: 56 Thanks: 5 Thanked 4 Times in 4 Posts	Ive red somewhere else, that the 300 minutes/ip-address limit for free calls is in power since yesterday.