我自己的OBi200也有幾天無法外撥，上OBiTalk看了要update firrmware，可我明明是設置了自動update firmware。OBi200 update firmware後就好了。
我也不知道Google Voice究竟變動了什麽造成所有（！）OBi設備不能用。下麵是幾段信息：
SteveInWA:
OBi devices act as Google "Chat" (XMPP) clients, that can receive calls forwarded from a Google Voice inbound phone number. To do that, the OBi device needs to connect to a XMPP server in Google's pool of servers. Since this is a secure connection, the device needs a valid SSL/TLS certificate to connect. Google is changing their server certificates. This is causing some, but not all, OBi<-->Google XMPP connection attempts to be rejected by the server, when attempting to connect to one of their servers with a new certificate installed. Since the server pool is load-balanced, some users are affected, and others not.
Google is rolling out the new certificates, and so eventually, all OBi devices will fail to connect.
OBiHai 寄給我的廣告email:
OUT WITH THE OLD AND IN WITH THE NEW!
As you may have already known, in August of 2016 we notified customers that the OBi1 Series Devices (OBi100 & OBi110) had reached their EOL (end of life) and would no longer be supported by Obihai. Unfortunately, a recent google Voice server security requirement has caused the OBi1 Series to no longer be compatible with Google Voice. Thankfully, Obihai has a solution and it starts with the OBi2 series (OBi200 & OBi202). Both devices are fully supported and capable of using Google Voice as a service. If you are concerned about the transition, don't worry, we posted aBLOG showing how simple it is to move your Google Voice and, if you have one, an Anveo E911 account to your new OBi2 Series device.
關於 SSL/TSL certificate 驗證，據我所知，有3個 party 牽涉其中。限於我們所討論的問題，第一是Server，也就是Google XPMM server；第二是client, 也就是 OBi devices；第三是trusted CA (certificate agent)， 比如 VeriSign。Certificate 是server 做的，但要去CA sign 一下，client 用SSL/TSL 去連 server， server 就發個 certificate 給 client。Client 粗粗檢查，如果沒什麽問題，就看看是那個 CA signed certificate，如果這個CA 在client's trusted CA list 那就去找那個 CA 再驗證一下，無誤後同意鏈接，否則拒絕連接。注意同意或拒絕連接是 client 的決定，不是server的決定。
有些server 為了省錢不找其他CA sign，自己就signe了。如果 client 與server 互相認識那client 也可以認可 server self-signed certificate，同意連接。
我猜測兩種可能情況：
1. Google Voice rolls out many self-signed certificates, OBi devices refuse to connect to servers with non-CA signed certificate, causing "backing off". Google Voice then fixed the issue, rolled out CA-signed certificate, and all OBi devices are happy.
2. Google Voice rolls out many CA-signed certificates but those CAs are not in OBi devices' trusted CA list.
我覺得第一種情況可能性比較大，因為許多OBi100設備後來又都能用了。如果Google Voice 為了省錢今後隻用 self-signed certificate，那些能用的OBi100隻是沒碰到 server with new certificate, 那 OBi100 慢慢就徹底完了。
關於firmware update，如是情況1 那OBi new firmware needs to accept self-signed certificate。如是情況2，那OBi new firmware needs to add new CA into trusted list.
選擇“Disable on www.wenxuecity.com”
選擇“don't run on pages on this domain”
