Anveo issues - not good choice for set and forget
JH2011:
Quote from: AlanB on May 13, 2014, 09:34:39 am
I would have to disagree with some of your comments.
That's no big surprise... you generally always disagree with anyone who has issues with Anveo.
Quote from: AlanB on May 13, 2014, 09:34:39 am
Two, you don't know for sure yet that the latest problem is related to Anveo.
Does he really need to be sure "the problem is related to Anveo" before posting here?
Quote from: AlanB on May 13, 2014, 09:34:39 am
Finally, in a sense there are two completely separate Anveo products. One is the Anveo for ObiTalk product which has controlled SIP access and requires automated provisioning. Anveo's standard offerings are not so tightly controlled and can be provisioned manually.
Wadewood is talking about Anveo for ObiTalk... which he correctly states is not a good choice for set and forget.
What does "Anveo's standard offerings" have to do with this?
Quote from: AlanB on May 13, 2014, 09:34:39 am
I would agree that Anveo is not a good choice for anyone who wants a lot of "hand holding".
"I would agree that Anveo is not a good choice for anyone"<<< Correct!
The "hand holding" you suggest is total condescending garbage.
Anveo should write scripts for Obi boxes that actually work.
Anveo should promptly refund people who are not satisfied without resorting to calling them "fraudulent" while at the same time hijacking funds from unsatisfied customers accounts.
AlanB:
Quote from: JH2011 on May 13, 2014, 06:01:08 pm
The "hand holding" you suggest is total condescending garbage.
I don't want to get into an argument, but this was not meant to be condescending. We all have our comfort levels. Some of us can program the Obi with no problems (not me) and others barely know what VOIP is. In other matters, some of us want an financial advisor to guide us, where as some of us are comfortable using a discount broker and making financial decisions with little help. Anveo is much more like a discount broker than a full service one. They have limited help documents and customer support. Some people would never be comfortable without that, others wouldn't mind at all.
My other point was that the ObiTalk version, even though it was meant to be simpler I think, actually can be much more limiting than a standard Anveo plan.
I agree that the scripts can be a pain. The Anveo e911 script had very few complaints. The new Anveo and PhonePower scripts seem to been lots of resets. It would be good if Obihai did a little more testing on them before they roll them out.
JH2011:
Quote from: AlanB on May 13, 2014, 07:14:19 pm
I don't want to get into an argument, but... it would be good if Obihai did a little more testing on them [scripts] before they roll them out.
No argument: Anveo's scripts are certified junk, so stop blaming Obi.
Hopefully, Obi will soon trash Anveo's "official Obi provider" masquerade.
MikePA:
Help me understand...
I assume the 'scripts' being referred to are the same for everyone. If true, why would the same script work for some and not others?
Like many, my original configuration was a 110 with GV.
I replaced GV with Anveo with no problems. Thought I'd try PP and put that on SP2 and had nothing but troubles.
Learned PP had to be on SP1. Why? No idea why.
More problems.
Finally replaced 110 with a 202. Put PP on SP1 and Anveo on SP2. Made SP2 primary for outgoing and incoming plus e911.
It's been this way for over a week. No problems. No SIP scanner calls. My Obi environment has gone back to normal, i.e., it works.
As an aside, I also switched my landline to a ATT Wireless Home Phone and saved $25/month. The only 'downside' has been no callerid, but am working through that with adding names with numbers to the cordless phone phone book.
AlanB:
Quote from: MikePA on May 14, 2014, 01:34:53 am
Help me understand...
I assume the 'scripts' being referred to are the same for everyone. If true, why would the same script work for some and not others?
Mike, I would think you are correct in assuming that the scripts are the same for everyone. However, the initial configurations are not.
I'm not a programmer, although I do write some simple scripts in a proprietary language not related to Obi. But, I can probably give you some simplistic examples.
Let's assume that you have three setting that must be set for the Obi to work with the provider.
A = 1
B = 2
C = 3.
Now lets assume the script writer set A and B, but did not set C = 3 because they thought no one changed the default. Well, if you had changed C = 2, and the script did not change it, your service wouldn't work. If most people still had C = 3 it would work for them.
Another example might be if there are two more values that need to be set.
Y = 25
Z = 26
Now let's assume that the script simply sets the values A, B, Y, Z in order. Well Y didn't exist until Version 2.0 of the Firmware which has been out for a while. If Y is present it needs to be 25, if it's not present the service will still work. Someone on Version 1.0 runs the script. The script could check that Y is not present and then set Z. The service works. Now let's assume the script writer didn't know that Y was not present a year ago and doesn't check to see if it's present. The script may go to set Y, not find it, and have no way to handle it, so it "crashes" and never sets Z. Thus your service does not work.
These are just simplified examples of course of how the same script can give different results.
As far as who writes the Anveo and PP scripts, I don't know. I would think it would be Obi since they would be the experts at it, but I have no proof. Either way, the script involves TWO parties, it can not be written without consultation. A "handshake" of information must occur.
The SP is picked from the Obi website, so at a minimum, it must be passed on to Anveo or PP (a handshake) to then continue setting up the Obi. More than likely, the script is mainly on the Obi side, you set pick the SP, and then the script logs you into the Anveo or PP website (a handshake) to provide some information. Anveo or PP creates an account and passes the account number and SIP password back to Obi (another handshake) to finish the setup.
This is similar to how paying through PayPal is often handled. Often, the shopping website, passes the payment amount over to Paypal, you log in there, pay and are then passed back to the shopping website to complete payment. I think I've also seen it where the entire transaction including the shipping, is actually completed at the Paypal site.
Navigation
[0] Message Index
[#] Next page
[*] Previous page