August 24, 2019, 01:28:48 pm *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: Obi products and GV now on PBX (need reliable info sources NOT nerdvittles)  (Read 14171 times)
livefortechnology
Newbie
*
Posts: 17


« on: July 26, 2018, 05:52:00 pm »

I have to say that after wasting literally DAYS now on that f'ing Nerdvittles site I can say IMO with 3 decades under by belt in this business that has to be one of the most misleading sources I have ever seen.  You get these BS phrases like "GV trunk setup in literally 10 seconds"........yep the COMMAND takes 10 seconds.....and then you wind up staring at a an ALL RED ERROR screen on the dash for 3 days, but thanks for rubbing the 'it's easy' BS in to my open wound and heck, I've only been doing it 30 yrs I can't imagine how someone with little to no experience feels right now with a GV device that just broke.

I really need (as it appears do many others) a reliable and most importantly ACCURATE source of info on how to set up and use PIAF, IncrediPBX, ANY FRIGGIN PBX that in under an hour can be virtualized to have a single friggin trunk and single friggin phone working with the new GVSIP.  Like actual soup to nuts not the nerdvittles expectation that after the 10 second command, you are then taking 4 YEARS of SIP training to become an asterisk expert and will just "magically" know what in HOLY H3LL needs to be done to actually make the newly created GVSIP trunk function with their "it's simple" statements.

It's all relevant here because I have, like many, an entire DRAWER full of Obi products now that unless I get the above set up properly as step 1, will no longer function.  That and, unlike the nerdvittles site that leaves it's readers high and dry for any kind of help, there are some actual decent folks here that help people I know I've gotten my share of advanced dial plan help in the past.  Any help/walkthrough for even a stop-gap pbx GV solution would be greatly appreciated!  TIA!

Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 5649



« Reply #1 on: July 26, 2018, 06:08:19 pm »

Heh heh, I have to agree about "Nerdvittles" and it's bizarre owner.  He's like a televangelist, except he isn't imploring you to send money to God every five minutes.

Given your need to have one phone service working with one Google Voice number, why even bother with all that complexity.  As you wisely point out, there are better things to do with your life then become a PBX expert.

All of the current OBiTALK products work just fine with Google Voice.  The 100/110 series are now only useful for non-Google Voice ITSPs.  So: either use some other service provider on your drawer full of devices, or buy a new device and use Google Voice.
Logged

--Steve

Google Voice Forum Product Expert

https://support.google.com/voice/community
livefortechnology
Newbie
*
Posts: 17


« Reply #2 on: July 26, 2018, 06:50:23 pm »

Good point.  You know probably as well as I do that NONE of this SIP stuff (I come from both a DEV and then infrastructure background) EVER EVER had to be nearly this complex.  The only reason I believe web interfaces with 400 individual buried SIP params were ever put together that way was for one reason - job security for the SIP guys piecing it all together.  In any other system I've seen, the DEV effort would have simply been HALTED and the paying sponsor would have just said "hell, no, place those 400 params into logical sets and for god sake, put a simple wrapper around them"...even as a former unix geek the SIP evolution IMO is just total job security BS, made frankly as IMPOSSIBLE to configure by the same folks selling how powerful it is.  Even in UNIX we came up with SED AWK GREP etc and shell script and don't type 400 params at a time like you wind up for SOME reason having to do in SIP.  How is it that can I VIRTUALIZE CPU INSTRUCTIONS ACROSS THE PLANET in far less operator commands then configuring a single line on Google Voice, LOL?

The proof of course is in the RFC's vs the implementations (or lack thereof).  More so in the case of SIP than an other I've seen did the RFC literally become the friggin man pages. Smiley

Can you imagine DOCKER if it had approached the world like SIP has?  Docker was smart and even as the param and config file sets grew, so did the ability to logically group and actually DEAL with them.  SIP should slow down and perhaps use Docker as an example of how to best get the community to jump onboard instead of always wasting unneeded days to perform trivial tasks and always finish by wanting to throw their product against the wall. Smiley

Anyway, for me it was more a matter of principle. Youre absolutely right I can certainly throw the obi110's on any other SIP provider and be done with it.  It's just that I know SOMEONE is successfully getting this horrendous pbx install process to work, and boy would it be nice to share the magic methods to get all these new potential community members with their obi1x's as the driver to begin utilizing their pbx systems.....which they then go to work and tell their companies, IT managers, directors, to adopt in the workplace as well, who then become paying revenue streams for incredible pbx......it worked for VMware!
Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 3875


« Reply #3 on: July 26, 2018, 07:18:01 pm »

I have naf's native Asterisk install on 2 computers. My install went fairly smoothly AFTER I figured out what had to be done. It's still a fairly long procedure. I had no interest to install it under FreePBX.

Here are the steps needed for the procedure I followed:

1. Get a Google ClientID and password for one of your GV accounts. Using these get a Refresh Token for your GV account. You can use the same ClientID/PW to acquire additional Refresh Tokens for other GV accounts.
Here is a procedure to obtain these. Ignore anything about an OBi box.
http://www.obifirmware.com/OAuth2/

2. Install a Linux OS. I used Raspian on my RaspberryPi and Ubuntu Server 18.04 on an Atom PC.

3. Install some prerequisite packages. This doesn't take very long.

4. Download naf's source with patches then build Asterisk from source. This took about 25 minutes on my Atom PC, but over 3 hours on my RaspberryPi One Model B. People have said it takes about an hour on a newer Pi.

5. Configure 3 Asterisk conf files.

If you are interested, complete the 1st 2 steps and post back. I'll show you the rest.

There is another setup for the GV callback method. It's a much easier install, but requires a DID for the callback. My DID support 2 channels and I successfully made 2 simultaneous calls, so this method could support more than one OBi.
https://hobbiesbytwinclouds.wordpress.com/2018/05/27/how-to-make-and-receive-calls-using-google-voice-without-xmpp-may-2018-revision/

All the above was a challenge/hobby for me. I'm using my OBi200 as a proxy server for my OBi110's. I have 2 GV accounts defined on the OBi200 and access them with the OBi110's. You can buy an OBi200 and define up to 4 (preferably 3) GV accounts on it and access them with your OBi1xx's over your local network.

Edit:
The Asterisk install is much easier when using Putty and WinSCP
« Last Edit: July 26, 2018, 07:42:24 pm by azrobert » Logged
TSElliot
Newbie
*
Posts: 3


« Reply #4 on: July 29, 2018, 01:23:36 pm »

Here's my current plan of attack, requires a reinstall of everything then a recompile of Asterisk (yeah, that bad):

Hardware:  Raspberry Pi Zero W and ObiHai 110.  Also have a 100 with Nat's firmware that I will try if this fails

Set your router to give your Pi and Obihai static IPs
Burn a Raspbian/Asterisk/FreePBX image to a micro SD (I used Etcher)
   Raspbian - An OS for Raspberry Pi
   Asterisk - a free PBX
   FreePBX - a free web GUI for Asterisk
Boot it up
Login as root/raspberry
sudo raspi-config to change root password, set wireless settings and expand to the rest of the card (last under advanced)
sudo shutdown -r now
raspbx-upgrade
sudo shutdown -r now
raspbx-upgrade (again - sometimes this does more updates, sometimes not)
sudo shutdown -r now
Configure FreePBX by HTTPing from your PC to your Pi
Make a SIP Extension in FreePBX for your Obihai (don't worry about routes or trunks)
Change your Obihai settings to use it (SIP on port 5160 - NOT THE DEFAULT OF 5060!)
Keep doing this until your Obihai can log into Asterisk (you will see it on the SP1 Service Status on the Obi)
Do Module Update on FreePBX until they all are updated.  
Make sure your Obi can still connect
Use Putty to connect from your PC to your Pi.
sudo apt-get install git
sudo apt-get install subversion
sudo apt-get install libbluetooth-dev
sudo apt-get install uuid-dev
sudo apt-get install libjansson-dev
sudo apt-get install openssl libxml2-dev libncurses5-dev sqlite3 libsqlite3-dev pkg-config
sudo apt update
sudo apt-get upgrade
Get the zip and follow these steps:  
https://www.dslreports.com/forum/r32037680-PBX-GVSIP-for-FreePBX
Get the three GV authorization strings you need (like refresh token) from http://www.obifirmware.com/OAuth2/
Use FileZilla to sftp files back and forth.  
chmod gvsip u+x
sudo ./gvsip

3 months later - when Google Voice changes who knows what yet again, scour the net for half written suggestions on how to fix the latest issue.
Suggestion #1 would be to try this all again.  Who knows, it might work.

I've updated the list of steps several times today, keep getting further in the build script.  If I do not post a success message, that means I gave up, more/different steps may be required or this may not be possible.

Update:  Rebooted and fired up FreePBX.  Can't connect to Asterisk.  Asterisk logs show one error after another, LOL.

« Last Edit: July 29, 2018, 06:25:41 pm by TSElliot » Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 5649



« Reply #5 on: July 29, 2018, 05:40:59 pm »

You just made livefortechnology's case. 
Logged

--Steve

Google Voice Forum Product Expert

https://support.google.com/voice/community
TSElliot
Newbie
*
Posts: 3


« Reply #6 on: July 29, 2018, 06:09:01 pm »

In one sense.  But the reality is, eventually the 200 will be in the same situation.  Hardware plus free GV is a moving target.  It's only a matter of time before problems arise with the 200 and folks will be faced with a mile of hoops or buying something else.

Any solution that uses GV is temporary, unless Google sells that solution.
Logged
GPz1100
Sr. Member
****
Posts: 329


« Reply #7 on: July 30, 2018, 11:54:41 am »

To the OP,

I used this method -

https://community.freepbx.org/t/how-to-guide-for-google-voice-with-freepbx-14-asterisk-gvsip-ubuntu-18-04/50933/1

It's long, complicated but the end result works 99.9% just as good as the motif module before it.

If installing 32bit, make sure you the 32 bit versions of some dependencies (and adjust paths accordingly).

Agreed, sip should be easier, but can fully appreciate a software engineer's perspective about job security and promoting future demand.  Remember back in the days we had a dos command prompt gui was a type of brownie.
Logged
Koby
Jr. Member
**
Posts: 46


« Reply #8 on: July 30, 2018, 10:13:49 pm »

Hardware:  Raspberry Pi Zero W and ObiHai 110.  Also have a 100 with Nat's firmware that I will try if this fails

For installation on a Raspberry Pi of any recent model, your best plan of attack may be to use the instructions here:

https://www.dslreports.com/forum/r30661088-PBX-FreePBX-for-the-Raspberry-Pi

Then to add Naf's patches:

https://www.dslreports.com/forum/r32037680-PBX-GVSIP-for-FreePBX

I would stay away from the Nerdvittles software. It's been pointed out recently on DSLreports that if you read their install script they install quite a bit of extra software that isn't needed, and that could possibly slow down a Pi.  And then half the time the NV guy responds with insults rather than addressing the points raised.  I did take a look at their script, and saw some rather bizarre inclusions.  And nearly every article tries to get you to sign up with some service, such as a cloud server, that generates a commission for the site owner.

The posts linked above will give you a much cleaner install on a Raspberry Pi.
Logged
Indirection987
Newbie
*
Posts: 1


« Reply #9 on: October 15, 2018, 02:33:31 pm »

After GV just changed their certificates on Friday yet again, I gave up on Asterisk/FreePBX/Raspberry Pi.  It was an adventure and good to brush up my UNIX skills - been running that with a 110 for a couple years.  But over the past year or so, every couple weeks to every couple months I need to monkey around with the system. 

I've spent over a hundred hours building new images, compiling, DLing and combing through forum after forum, trying to find the latest fixes, the right combination of all the different applications and the right settings for each of them to get it set up.  Then a short time later, it dies and I start all over again. 

This stuff is unbelievably complicated.  There are thousands of settings and hundreds of combinations of all the different software parts like Debian, Asterisk, FreePBX, GVSip.  So I broke down, paid $46 for a 200 off of eBay and set it up.  Price has jumped a bit, guess many people are bailing on this as well.  What a shame, loved the ability to block an entire area code.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC