Feeling a bit duped
azrobert:
Quote from: Taoman on March 03, 2018, 11:47:45 am
Have you tried any of Naf's firmware?
I also have a spare OBi110 and defined GV on it after a factory reset without OBiTalk.
I manually defined GV with SignallingProtocol and an AuthUserName.
The trunk still shows as undefined on the Status page.
You now need to update 2 hidden parms with an XML file
The XML file to update SP1 is found here:
https://www.dslreports.com/forum/r31790819-
Copy and paste into Notepad then save as file name "file.xml" and file type "All Files".
You need to use ITSP Provisioning under Auto Provisioning to update the config.
Use ConfigURL to point to an HTTP server hosting the XML file.
This is how I did it:
https://www.dslreports.com/forum/r31793011-
For some unknown reason you can't use the Config Restore option to update the parms with the XML file.
The status for GV shows Backing Off after the update..
Somewhere in that thread someone hosted the XML file, so you can just point to their HTTP server.
Now you need to acquire your GV credentials.
I used RonR's instructions to acquire an OAuth 2.0 Client ID, Client Secret, and Refresh Token here:
https://www.dslreports.com/forum/r30983990-Asterisk-OAuth-2-0-Support-for-Asterisk-13-or-Asterisk-14
You need to update the AuthPassword with the credentials in this format:
https://www.dslreports.com/forum/r31779486-
BillDoe:
Thanks for all the recent advice, but sadly I'm still missing something. Specific, non-technical step-by-step instructions for how to do this. I'm not unable to go this route (I've rooted at least a few Android phones in my time, but again, I had specific instructions to follow). Everything I'm reading here or via the links supplied seem to assume a working knowledge of how this all works, jargon, etc. So can anyone point me to a noob guide?
azrobert:
Quote from: BillDoe on March 03, 2018, 01:16:01 pm
Thanks for all the recent advice, but sadly I'm still missing something. Specific, non-technical step-by-step instructions for how to do this. I'm not unable to go this route (I've rooted at least a few Android phones in my time, but again, I had specific instructions to follow). Everything I'm reading here or via the links supplied seem to assume a working knowledge of how this all works, jargon, etc. So can anyone point me to a noob guide?
Download the 3rd party firmware here:
http://fw.obifirmware.com/OBi1-1-3-0-2886-naf7.fw
Update your OBi with this firmware.
If you already have GV defined on your OBi1xx, you're done.
If you don't have GV defined, define it the same as with the stock firmware.
GPz1100:
@Taoman
I've been running the modded firmware on a 202 model for about a month now. No issues as far as gv is concerned. It's easy to change gv account just updating a few entries.
Probably the most challenging part of implementing this type of set up was generating the oauth credentials. RonR's guide simplifies things, but novices may still have issues. For the 1xx units, can one still do gv provision using obitalk? If so, then the whole credential generation doesn't really apply [yet].
azrobert:
The 3rd party firmware will work exactly like the stock firmware. It has the new certificates, so fixes the problem when connecting to a server requiring the new certificates.
In addition it has the option to accept your own GV credentials. The procedure I posted in my Reply#10 above is only used when you want to define GV without the OBiTalk portal after a factory reset.
If you already have GV defined by the OBiTalk portal and want to use your own credentials, you can skip updating your OBi with the XML file. Those parms have already been defined from OBiTalk. The reason you might want to do this is to change GV accounts without the portal.
The developer only supplied a patch file and you needed to apply the patch to the stock firmware. The owner of the obifirmware site updated the stock firmware and made it available for download, so users don't have to patch the firmware themselves.
Navigation
[0] Message Index
[#] Next page
[*] Previous page