Anveo for ObiTalk (Approved Service Provider)

<< < (4/24) > >>

AlanB:
Quote from: c3c3 on March 08, 2014, 12:38:06 pm

Quote from: AlanB on March 08, 2014, 09:32:45 am

Overall, the porting process from Google Voice was quite simple.


Thanks for the report.  I'm still debating whether I should port or stay with forwarding.  Did you have problem with calls forwarded from GV to Anveo?

Occasionally I did have garbling.

Since my port was just completed this morning, I have no comparison of incoming calls directly with Anveo yet.  I'll report back on that in a few weeks, but I don't anticipate any problems based on general Anveo reviews.

My main reason to port was for simplicity.  We typically use our answering machine at home, not GV voicemail.  Now I have control over time to go to voicemail and I can extend the number of rings at home.

Jackson:
Great post, thanks for taking the time to explain it so thoroughly.

Two questions.

Quote

3) If you already have an Anveo 911 account provisioned, the provisioning tool may fail.  I tried three times to provision and had problems.  I finally decided to delete the Anveo 911 provisioning and then my reprovision of my new Anveo account worked.


So in my existing account I have a phone number (which I don't really need) and e911.  So you are saying I should basically delete both?  When I jump on the new plan will it not use my current account? I'm not concerned about my balance it's <$2.

BravoKilo:
Quote from: AlanB on March 08, 2014, 07:35:09 pm

Quote from: BravoKilo on March 08, 2014, 02:06:06 pm

Thanks Alan.
Item #6 on your list (no out-going CNAM) means if we keep our number on GoogleVoice we cannot send that number on out-going calls originated from the Obi device, right?

http://blog.obihai.com/2013/12/what-does-40-bucks-and-obi-device-buy.html

No, your statement is not correct.  You can "spoof" your Google Voice phone number so that your GV number will show when you make a call using Anveo for ObiTalk.

CNAM is the TEXT (or NAME) that goes along with the phone number.  This won't apply if you are keeping Google Voice, as Google Voice controls your CNAM and they don't let you modify it.

In other words, if you port a number to Anveo, like with GV, you won't be able to set a NAME that displays on outbound calls. 

Actually, for $2/month more, it is possible to have CNAM (by having a second number on the account), but I'm not going to pay that fee.

Thanks Alan.  I'm considering using GoogleVoice for voicemail and forwarding to Anveo for the Obi device.  If Anveo let's me spoof my number on outgoing calls, then it sounds like the main thing I'm losing when converting from GoogleVoice XMPP service to Anveo is MWI (message waiting indicator) for voicemails.

c3c3:
Set up my call flow to ring Obi and mobile at the same time.  If no answer, go to voicemail.  I also changed the voicemail notification email format to MP3, so GMail can play it back directly.

AlanB:
Quote from: Jackson on March 09, 2014, 07:22:28 am

Great post, thanks for taking the time to explain it so thoroughly.

Two questions.

Quote

3) If you already have an Anveo 911 account provisioned, the provisioning tool may fail.  I tried three times to provision and had problems.  I finally decided to delete the Anveo 911 provisioning and then my reprovision of my new Anveo account worked.


So in my existing account I have a phone number (which I don't really need) and e911.  So you are saying I should basically delete both?  When I jump on the new plan will it not use my current account? I'm not concerned about my balance it's <$2.


Based on my experience, you will need to remove any Anveo accounts you currently have provisioned.  You can then run the Anveo for ObiTalk provisioning to assign to an SP.   Your new account will have a phone number and 911.

Should you want the old account, still until it expires, you can always set it up again on another SP after provisioning Anveo for ObiTalk.  In my case I still had three months on my Anveo e911 account, but I don't need it anymore so I didn't reprovision it.

Navigation

[0] Message Index

[#] Next page

[*] Previous page