Started by Taoman, May 26, 2015, 01:05:52 PM
Quote from: SteveInWA on May 01, 2018, 03:55:16 PMAs per my post, 3.2.2 (Build: 5829EX) is the new Google Voice VoIP firmware.Try this:On OBiTALK, click on the OBi with the problem, and delete the SPx that has the Google account linked that doesn't work properly.Press Ctrl-T to open another browser tab. On that tab, sign into the correct Google / Gmail account that holds the Google Voice phone number that you want to use on that OBi, that is not working correctly, and go here:https://myaccount.google.com/Click the section that says "Apps with account access", then click "MANAGE APPS". On the next page, find and delete the entry for OBiTALK Google Voice, and also delete any entries for third party services like Simonics GVGW.Go back to the OBiTALK tab, and click the SPx again, and go through the Google Voice setup again.Does that fix it?
Quote from: CosmoEPTX on May 06, 2018, 08:04:11 PMFirst!Looks like my obi200 was automatically updated to firmware 3.2.2 (Build: 5853EX) Now google contacts show in caller id, which is neato. Also, looking at the settings, seems like google has set up a couple of proxies for our obihai devices, obihai.sip.google.com and obihai.telephony.goog.Discuss.
Quote from: LTN1 on May 07, 2018, 05:38:12 AMI can confirm that these updates are silently continuing to be pushed out automatically.
Quote from: SteveInWA on May 06, 2018, 09:37:48 PMIt's to be expected, that, as the conversion rolls out, some unforeseen, and typically-minor "edge case" bugs will pop up.
Quote from: LTN1 on May 07, 2018, 08:27:46 AMYes, am currently using GV. Since you are the expert in these things, I've taken some screenshots for you to confirm if I am actually using SIP via GV yet.
Quote30 June 2018 is the deadline for disabling SSL/early TLS and implementing a more secure encryption protocol – TLS 1.1 or higher (TLS v1.2 is strongly encouraged) in order to meet the PCI Data Security Standard (PCI DSS) for safeguarding payment data.