also FUP here. on eu us and au servers.

same here, it's a voxalot problem

i tried to make the call through voxalot and charged me for FUP

but when i make the call directly from the ATA, no FUP. i think this is the best solution, if you don't have spa3102 that u can add betamax as a gateway, you can any VSP in your dial plan , it works for the linksys ATAs

Are you suggesting a 'FUP issue' solution could come from Voxalot?

i am suggesting a solution for the users away from voxalot. instead of adding betamax as a VSP in voxalot, adding it in their ATA as a gateway or directly in the dialplan

i tried both within an hour with the same account, and with voxalot i was charged for FUP

Indeed, adding a Betamax provider in the dial plan is a convenient way to bypass the FUP issue, and also slightly shortens the RTP packet (voice) path between your ATA and the Betamax endpoint. I have not worked with the SPA3000 and SPA3102 but I understand there is a way to specify SIP user_ID and password in the dial plan of these units.

The same dial plan solution could be used with other Linksys devices, such as PAP2 and SPA2102, if Voxalot were to offer users an alias SIP user_ID. The user's SIP device could then register to Voxalot using the alias which could be chosen identical to their Betamax user_ID, thereby allowing the PAP2/SPA2102 to successfully authenticate with Betamax. I have been using this method for over a year with Gizmo5. As you may know, Gizmo5 allows users to choose an alias SIP user_ID (the Gizmo5 name), which can often be the same as ones Betamax ID.

i have the spa3102 and i think spa3000 is similar, you can add up to 4 providers (gateways). for the pap2 and the spa2102, you can add them in the dial plan as follow : (00xx.<:@sip.smartvoip.com;usr=name;pwd=password>) this will forward all calls starting by 00 through your betamax (smartvoip here as an ex.) provider directly

i didn't understand well the authentication with betamax with the SIP alias

Some of us don't use an ATA, that was to point of subscribing to Voxalot, to free me from ATA adapters. For me the FUP issue doesn't have an alternative fix :(
I really do hope Betamax will play nice and Voxalot can be FUP free again.

so what are you using? sofphones? like X-lite?

Thanks for this information. It will be very useful for me to avoid the FUP problem. I tried the following dialplan in my PAP2T, but I could not make it work yet. When I dial 00xxxxx ended with #, I got fast busy. Could you help me to find out what is wrong? I am trying to use nonoh.net for international calls while the line is registered to sipsorcery. Thank you very much.

(00xx.<:@sip.nonoh.net:5060;usr=username;pwd=passw ord>|*xx|[34689]11|0|00|[2-9]xxxxxx|1xxx[2-9]xxxxxxS0|xxxxxxxxxxxx.)

Well, so far has ended. I just saw more FUP charges the other day. Maybe they have some sort of trigger that results in FUP charges? Like, I never saw any FUP exceeded message using my Betamax provider (justvoip) until I let my account completely run out of funds. It was after I'd recharged it that I started seeing FUP exceeded messages: it's as if my account was "off their radar screen" until I ran it dry. Likewise, the FUP exceeded messages ceased for awhile after I'd switched to the US server. But now, they cropped up again after I'd made a non-free international call (to Estonia).

I've made two complaints to justvoip so far, which have been met with stony silence. Given their "business model" (which seems to be to take as much money as they can with the least accountability possible) I'm not too surprised. I do have an ATA so maybe I'll try the workaround suggested by mohnashaat.

James