Vestalink Sign-Up
Taoman:
It's not going to ask you if you want to spoof your outbound number. You need to go into Vestalink's web portal and set this up yourself.
Numbers>Spoof Caller ID
1>If you are already committed to Vestalink then yes
2>Click on "gear" icon. On subsequent page you will see "garbage can" icon to delete current SP
3>Vestalink's Easy Setup configuration is easier but your Obi is then locked and provisioned by Vestalink. It is quite easy to set it up manually in Obitalk. Just get SIP credentials from Devices>Softphone/BYOD in web portal
Also: http://support.vestalink.com/ Advanced Obi configuration shows step by step procedure
4>According to Vestalink support the reason is: Quote
This delay is due to calls being forwarded through Google Voice. The only way to resolve this issue is to transfer your Google Voice number. Changing your phone number will not fix the issue as Google Voice still has to essentially echo the conversation between it’s carrier and the one we have numbers with."
5>No. Vestalink is relatively new to the game.
PS. If it was me, I would delete Anveo on SP2 (be sure and cancel service) and then configure Vestalink on SP2 manually, check the box to make it your primary line for outgoing calls and thoroughly test out Vestalink to see if it meets your needs before wiping out your GV config on SP1. Don't forget to add Vestalink number as forwarding number in Google Voice and uncheck box in front of Google Chat.
lrhyne:
Thanks BigJim and Taoman. I guess I will begin by trying to do the manual setup via Obitalk, just know that if I run into issues, you will have to put up with more rambling questions from me...
As far as # 4 goes, I had seen Vestalink's reason, but I was just curious as to why some who have not ported their GV # have issues and some do not. If it had been isolated to a particular part of the country or internet speed, etc... then I might be able to tell if I would be affected or not.
Thanks again!
Taoman:
Quote from: lrhyne on April 18, 2014, 12:38:22 pm
As far as # 4 goes, I had seen Vestalink's reason, but I was just curious as to why some who have not ported their GV # have issues and some do not. If it had been isolated to a particular part of the country or internet speed, etc... then I might be able to tell if I would be affected or not.
It is contingent upon the CLEC for your GV number and the CLEC for the number Vestalink assigns you and the route taken between the two. You can't possibly know ahead of time what you will experience. You can only try it and see what happens.
Note: The reason I suggested leaving GV on SP1 is so you could easily contrast and compare the two as far as voice quality and latency. Outgoing will probably be OK with Vestalink. It is on incoming calls where you might see problems. To switch back and forth between GV and Vestalink would just be a matter of checking and unchecking the boxes in Google Voice.
lrhyne:
Ah, makes sense. Oh well, it will just be a roll of the dice.
One more question (last one for today, I promise). If I do my setup through the Obitalk site, it looks like I would just delete the Anveo on SP2 and set up Vestalink on that SP as you suggested leaving GV on SP1. I'm assuming that I would not need to then do a factory reset as I had originally thought - Is that correct?
Taoman:
Correct. If you are just going to be deleting SP2 and manually configuring Vestalink you shouldn't need to do a factory reset. However, once you are done testing and have made your final decision and are ready to delete GV from your Obi I would suggest resetting your Obi to factory defaults, deleting and re-adding your Obi from the Obitalk portal and then manually adding the service provider of your choice.
Navigation
[0] Message Index
[*] Previous page