December 02, 2021, 12:56:39 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: "The number you dialed has not received a response from the service provider"??  (Read 37656 times)
Pedro675
Full Member
***
Posts: 89


« on: June 11, 2021, 11:45:36 am »

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
Logged
holtdw01
Newbie
*
Posts: 3


« Reply #1 on: July 06, 2021, 09:36:00 am »

having the same issue and resetting the device is not the remedy. 
Logged
drgeoff
Hero Member & Beta Tester
*****
Posts: 5516


« Reply #2 on: July 06, 2021, 11:24:28 am »

Do you successfully reach the Obihai echo test when you dial **9 222 222 222 ?
Logged
holtdw01
Newbie
*
Posts: 3


« Reply #3 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?   
Logged
drgeoff
Hero Member & Beta Tester
*****
Posts: 5516


« Reply #4 on: July 10, 2021, 09:03:12 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.
« Last Edit: July 10, 2021, 09:06:51 am by drgeoff » Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 6433



« Reply #5 on: July 10, 2021, 02:59:42 pm »

This:  https://support.google.com/s/community/forum/589387/thread/114914789 is not yet applicable to any current OBi/Google Voice problem.  However, it is absolutely going to be a problem "soon", if Poly doesn't get their act together.

holtdw01 has some other problem.

Cleaning out and re-provisioning may solve it, assuming that their Google Voice service hasn't been suspended or the number was reclaimed (which can be tested by using the Google Voice website to make and receive a call):  https://voice.google.com/u/0/calls

Follow these steps fully, in order:  https://www.obitalk.com/forum/index.php?topic=13868.msg89076#msg89076

Logged

bergeboonp60
Newbie
*
Posts: 1


« Reply #6 on: July 13, 2021, 03:24:55 am »

This:  https://support.google.com/s/community/forum/589387/thread/114914789 is not yet applicable to any current OBi/Google Voice problem.  However, it is absolutely going to be a problem "soon", if Poly doesn't get their act together.

holtdw01 has some other problem.

Cleaning out and re-provisioning may solve it, assuming that their Google Voice service hasn't been suspended or the number was reclaimed (which can be tested by using the Google Voice website to make and receive a call):  https://voice.google.com/u/0/calls

Follow these steps fully, in order:  https://www.obitalk.com/forum/index.php?topic=13868.msg89076#msg89076


You are right thank you
Logged

Jim Rohn

"Discipline is the bridge between goals and accomplishment."
Hero
Newbie
*
Posts: 5


« Reply #7 on: July 16, 2021, 01:38:16 pm »

I also am having the same issue. Except I get the following prompt when attempting to make a call:
"Call Error - The requested service is not available at the moment"

I wonder what could be causing this
Logged
drgeoff
Hero Member & Beta Tester
*****
Posts: 5516


« Reply #8 on: July 16, 2021, 02:49:58 pm »

I also am having the same issue. Except I get the following prompt when attempting to make a call:
"Call Error - The requested service is not available at the moment"

I wonder what could be causing this
I've never heard that message nor seen any other post mention it.  Thus I think that message is not generated by an OBi device but elsewhere in the outgoing chain from your Internet Telephony Service Provider onwards.
Logged
Hero
Newbie
*
Posts: 5


« Reply #9 on: July 16, 2021, 04:41:58 pm »

This is the error message I receive directly from the OBIHAI device:


FYI, it was correctly configured for over two years now. I'm not doing this for the very first time. I'm not a new user. I've had this configured since February 2019. And it inexplicably stopped working yesterday.
Logged
drgeoff
Hero Member & Beta Tester
*****
Posts: 5516


« Reply #10 on: July 16, 2021, 05:14:21 pm »

You neglected to mention that you are using an OBiPHONE and that the message is a visual one.

Is this pertaining to GV?  What does your dashboard at obitalk.com show for the status of your phone and the SP?
Logged
Hero
Newbie
*
Posts: 5


« Reply #11 on: July 16, 2021, 06:51:15 pm »

Actually I was experiencing the same exact issue as the person in this thread:
http://www.obitalk.com/forum/index.php?topic=18468.0

When I unplugged the power cord and plugged it back in, that fixed the issue.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC

Advertisement
Advertisement