Provisioning Failure
drgeoff:
Quote from: vsc1062 on December 10, 2020, 10:56:38 am
I disabled Obitalk provisioning on the phone via its web page where I don't believe there is an option to do this from the screen/keypad.
It might be possible to delete the device from Obitalk and recreate it to get around the broken database on their end. But I had so much trouble getting their server to recognize the phone in the first place I'm leaving well enough alone for now.
Unless you want to use GV, which can only be configured via the portal dashboard, or remote configuration, everything else can be done via the phone's onboard web server. With or without the phone being registered to the dashboard.
slennett:
Don't remove it from the Obitalk portal. That is what I did along with a hard factory reset on the Obi device. After struggling to add it back to my Dashboard, now it won't provision at all. All 4 lines including GV, other VoIP provider, local Asterisk, can't be configured through Obitalk at this time.
I was able to restore using an old backup though the local web interface of Obi device. Some lines work with exception of the GV lines which sit at Service Not Configured. Even though everything looks like its there in Service Providers and Voice Services, it appears GV can't restore through a backup correctly.
drgeoff:
Quote from: slennett on December 10, 2020, 11:17:14 am
Don't remove it from the Obitalk portal. That is what I did along with a hard factory reset on the Obi device. After struggling to add it back to my Dashboard, now it won't provision at all. All 4 lines including GV, other VoIP provider, local Asterisk, can't be configured through Obitalk at this time.
I was able to restore using an old backup though the local web interface of Obi device. Some lines work with exception of the GV lines which sit at Service Not Configured. Even though everything looks like its there in Service Providers and Voice Services, it appears GV can't restore through a backup correctly.
OBi backups do NOT contain passwords*. Also GV authentication isn't the same as the standard SIP username and password method. That's one of the reasons it must be done via the portal while other SIP providers can be configured by putting SIP username and password in the appropriate boxes on portal or local GUI.
* See 'Important Note', middle of page 241 of https://www.obitalk.com/info/documents/admin_guide/OBiPhoneAdminGuide.pdf
slennett:
Thanks. I was aware of the passwords not being stored as I had to re-enter to clear 403 Forbiddens with other lines. Great for security purposes and not a big deal to correct for non GV lines. As for GV, I was hoping a restore would work but damn. Now stuck until this gets fixed.
I did reach out to a Polycom contact I have from work and I was told they sent my issue and the forum reported issues I provided over to the Product owner of Obi. But not so hopeful for any immediate turnaround.
slennett:
It appears to have been fixed within the past hour or so. Provisioning through Obitalk is working now but wasn't working when a checked about 2 hours ago.
Navigation
[0] Message Index
[#] Next page
[*] Previous page