"The number you dialed has not received a response from the service provider"??

(1/3) > >>

Pedro675:
Did a Goggle search but found nothing useful.

Our phone is basically dead, cannot receive incoming except for the caller to leave voice message. No outgoing calls and the above message. We have a dial tone. This has happened before but usually fixed with "unplug OBi device, reconnect OBi device". Just changed Goggle password, but can't see how that matters?

Can anyone help I am stumped. Please answer with known solutions, not guesses as I found on all Goggle search for same issue.

Thanks,
Peter

holtdw01:
having the same issue and resetting the device is not the remedy. 

drgeoff:
Do you successfully reach the Obihai echo test when you dial **9 222 222 222 ?

holtdw01:
Echo test **9 22s://support.goog2.222.222 works fine.  Could this be related to the Google authentication and the update needed by Polycom?   httple.com/voice/thread/114914789.  The error on the Obi adapter says it cannot connect to a specific google server (Connect Failed: No Response (server=216.239.36.145).  I contacted Google Voice support and they are pointing back to Obi.  This started for me about a week ago.  Why is the forum so quite on this topic?   

drgeoff:
Quote from: holtdw01 on July 10, 2021, 07:32:47 am

Echo test **9 22s://support.goog2.222.222 works fine.  Could this be related to the Google authentication and the update needed by Polycom?   httple.com/voice/thread/114914789.  The error on the Obi adapter says it cannot connect to a specific google server (Connect Failed: No Response (server=216.239.36.145).  I contacted Google Voice support and they are pointing back to Obi.  This started for me about a week ago.  Why is the forum so quite on this topic?  

The probable reason the forum is quiet on the issue is because it isn't a widespread issue.  Within the 10 minutes prior to typing this I have confirmed that an OBi200 and an OBi202 are connecting OK to GV.  They had been packed away in their boxes since before the GV certificate problem a few weeks ago so definitely have not had a recent firmware update.  To me that suggests that the matter described in that thread (https://support.google.com/voice/thread/114914789) is not yet applicable.

I don't know what is causing your problem.

Navigation

[0] Message Index

[#] Next page