"Pressing one" issue
SteveInWA:
OH, and do you understand that you must make the changes via the OBiTALK portal, and not via the local web UI? Changes made on the web UI will be overwritten by the portal next time the devices reboots.
RAMOSEL:
Quote from: SteveInWA on August 24, 2021, 06:32:39 pm
What the heck.
Is this an OBi 200 or 202? If it's a 202, the recent firmware update disabled local access via the device's WAN port, and you need to re-enable it: pick up the phone and key in *** then 0 then 30# then 1 then 1# to enable WAN access.
It's a 202
Hmmm... I guess it survived the update, just not the reset.
Done, fixed...
Any other gotchas from the firmware update?
RAMOSEL:
Quote from: SteveInWA on August 24, 2021, 06:34:18 pm
OH, and do you understand that you must make the changes via the OBiTALK portal, and not via the local web UI? Changes made on the web UI will be overwritten by the portal next time the devices reboots.
I do Sir, and thanks.
I'll live with the call screening turned off for now, I'll keep an eye on this thread and see if anyone else has the issue and a fix is found.
RAMOSEL:
SteveInWA,
Just wanted to say thanks again for your help. Although we didn't fix the precise issue I was having, it works. That, and walking through your full reload process (twice) gave me a much better understanding of the workings of the interconnectivity of the Polycom/OBi 202, the Obitalk web page and Google Voice.
I felt comfortable enough in the process, I spun up the 2nd port as a my FAX line after I had Google Voice port the number over from my place holder mobile after dropping Suddenlink.
So far, so good.
Rick
SteveInWA:
Great; I'm glad that was helpful.
Navigation
[0] Message Index
[*] Previous page