Quote:
I have PMed hudai.terzioglu on the VoIPBuster forum and described the IP address mechanism I mentioned and waiting for his reply. |
with my little knowledge about voip, as i posted in another thread voxalot-support/4578-betamax-fup-again-2.html i have a spa3102 registered to voxalot, when i tried to make the call through voxalot with the betamax account added as a VSP in my voxalot account, they charged me for FUP
but when i make the call directly from the ATA using the gateways in spa3102 or by adding the betamax account directly in the dial plan, i had no FUP charges. so the conclusion for me is that voxalot was the problem. |
No, Voxalot is not the problem. What Martin is telling us is that Voxalot bypass user's IP to Betamax providers in a way that Betamax should not only be aware, but that they contributed to the implementation of the process. Several things may be happening here, but I doubt Voxalot can do a dime to overcome this issue. Never forgetting thay may not be in the Betamax best interest that their costumer uses Voxalot as a SIP user agent (because in this way their customer can very easily chose, in a call per basis, to route their call through another competitor VSP), there are several other possible causes:
|
Quote:
|
That's easy. When you call through Voxalot, Betamax knows that your call is bypassing through Voxalot, despite Voxalot in sending your IP address in SIP headers. That happens because the IP from which comes the first SIP invite message is from Voxalot servers. So, Betamax has two diferent IP address: yours (on SIP headers) and one from Voxalot's server (on IP headers). Differently, when you call directly from your computer or ATA, Betamax has only one IP address (in fact, they have both but they are the same).
So, what maybe happens is that Betamax no more honours the IP address sent in SIP headers from Voxalot servers to them. And Voxalot can not modify their IP address on IP headers because that is something that depends directly on the internet infrastructure and IP protocol. Also, don't forget that Voxalot servers are not at Voxalot facilities but they are rent from data centres in Holland, United States, and Australia. That means: the only way to overcome this FUP issue is if Betamax servers honour the IP sent to them in the SIP header and not the IP from which the first SIP invite message is coming from. Voxalot can not modify something that deals with internet infrastructure and in equipment rent on data centres around the world. It's easier to implement some kind of other solution at the users side, as suggested some where else in this forum. Regards, |
BETAMAX "(FUP exceeded)"
Quote:
it all make sense to me, but can you please point a "possible" solution at the client side to this problem? Thanks in advance OlaDAVIES |
Main solutions to FUP on Betamax accounts at user side:
1 - With a soft phone: there are some soft phones that handle more than one line. Some of these are Twinkle (Twinkle - SIP softphone for Linux) and Zoiper (Free Zoiper softphone for windows, mac & linux, webphone and SDK). These are general purpose soft phones which handle two or more SIP accounts. 2 - Some hardware phones are also capable of registering with two or more SIP accounts as for example Linksys SPA 941. 3 - Another suggested solution works with a dial plan on the hardware phone but you must have the same credentials at Voxalot and Betamax accounts (user and password must be the same at both accounts). Then, on the phone dial plan configuration, you add a rule as the following one: '<#,:>xx.<:@sip.voipbuster.com>'. Then, when you which to dial through VoipBuster, you start dialling the '#' key (you will listen to a different dial tone) and then dial your number in international format, ending with the '#' key again. The call will be routed through VoipBuster despite you are using an hardware phone capable of one SIP registration only (and no one SIP gateway). In these example, if you also which to receive VoipBuster calls, you must register your SIP phone with VoipBuster and forward your Voxalot account (the above rule on your dial plan should also be modified, ending with '<:@us.voxalot.com>' instead of '<:@sip.voipbuster.com>'), through SIP, directly to your phone on a similar manner explained on the SIP Broker FAQs (forwarding direct calls to your SIP phone). Another way is to forward your VoipBuster account to Voxalot using your Voxalot iNum number and leaving your SIP phone registered with Voxalot. Regards, |
Quote:
(00xx.<:@sip.voipbuster.com;usr=name;pwd=password> ) this will forward all calls starting by 00 through yourvoipbuster provider directly |
These are nice solutions but one thing that you can do with Voxalot and not with the ATA is to set the "From User" field (unless you have any clever ideas!)
I use this so that I can set my outgoing CID on a call-by-call basis for each Betamax-verified number in my account. |
Is it just me or FUP started again on US server? I use 2 Betamax clones and I get FUP on both of them (I barely used one so that should be FUP free); I need Betamax to forward DIDs to regular phones so I can’t escape the FUP issue by using an ATA :(.
|
All times are GMT. The time now is 01:40 PM. |
Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.