Seems that any contact with betamax is always difficult but it might be worth looking at. The question is if pbxes can do something about this. This is a good question, I also use betamax for outgoing and it's a valid point. It appears that I could lose outbound service via PBXes at any time (and have probably just been lucky so far).ĭoes anyone know of another provider to use as a backup that offers good rates and passes callerID ? This is extremely worrying as Betamax companies are my only outgoing providers. You could better ask why 3 servers are blocked and indeed how this can be prevented in future. since everyone shares the ip so are the minutes. How could you misuse the service, one of the problems has always been that betamax gives 300 minutes per 7 days per unique ip address. In the future consider that PBXes is a shared resource and as such it should not be abused. It is highly probable that some PBXes users had attempted to defraud Betamax in some way, and for Betamax to have responded by blocking access from a certain IP(s). Will they take similar action in the future, and how can this be prevented? Which leads us to the question, whether Betamax had blocked these IPs from delivering calls to their network, and what made them do so. Well, if some or all Betamax trunks started working after last Wednesday, for accounts hosted on the If the trunks in question started to deliver calls, without any changes, then chances are the IP change, rendered Betamax's block of the old IPs ineffective. Not sure, who changed what exactly (I thinkg PBXES had some maintenance going on on the 21st though), but to whoever it was: Thanks a lot for doing it! :-) My VoipBuster Account has been working fine again for like four days. This post has been edited 1 time(s), it was last edited by bob on at 17:13. In case www5 has a problem my account would be transfereed to www3 meaning maybe I could not use voicetrading anymore ? I would also ask pbxes to look into this as it seems strange that some users have a problem and others not.
If it does work on www5 than it's related to www3 (Nürnberg) where you are. If it doens't work than there is another problem that could be related to your pbxes account. You might want to try to change to server www5 (Paris) to see if voicetrading will work than. I am on WWW3 and voicetrading refuses to work, i signed up with another ISP and that is working well with PBX. I am on www5 also, no problems with voicetrading Maybe other users that have problems are on another server that has another ip and betamax blovked the ip ? (just thinking out loud) I am on www5 and no problem. could this be pbxes server or ip address related. It seems strange that some users have a problem and others not.
that said sometimes I just can't get a connection, hang up dail again no problem. I replied before and I am using voicetrading daily bases. If you think another approach should be taken, please let us know. So in my opinion, a deluge of nearly identical complaints, from several users of their services, bringing up an issue in relation with their PBXes accounts, might supply them with the required jolt, to resolve it. It might never get resolved if they choose to, but I am pretty sure they will at least read it.
They might not reply, but magically your issue might be resolved in 3-4 days or in a week. As it is known universally, they are hard to reach, difficult to work with, and extremely unresponsive.īut they will listen to customer complaints. I got the same error through PBXes, although they work fine if I configure them on my phone.Ĭan PBXes check the different behavior using PBXes and a simple ATA ?Įven if we verify the behavior of a Betamax account with an ATA, and it works properly, what difference will it make?Īpparently, this is not the first time Betamax has created issues for PBXes users. Print Page | Recommend to Friend | Add Thread to FavoritesĪll Betmax servers seems to have the same problem (at least mine Voipraider and Justvoip). » RE: Voicetrading - Outbound trunk issue PBXes - RE: Voicetrading - Outbound trunk issue
0 kommentar(er)
