April 10, 2021, 09:37:28 pm *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: RESOLVED RE: No response from service provider... AGAIN  (Read 1373 times)
Moonwalker
Newbie
*
Posts: 15



« on: November 20, 2020, 03:56:08 pm »

Here we go. Again...  Angry Shocked

So this seems to happen VERY frequently when one certain number is called. Oddly, it seems whenever I dial through OBI and get this massage, Iíll try using my cell and get a busy signal. Obviously if thatís happening, theyíre on the phone. Well, this happens to be our fave take out number, so they are VERY OFTEN busy. Weíve had so many issues connecting to this particular number, getting the no response from service provider, tonight a possible pattern occurred to me. I have NEVER ONCE gotten a busy signal calling ANY number, EVER, using my OBI. So Iím now wondering, is it possible that instead of getting a proper busy signal, the system is simply telling me it canít connect?

This has been happening for years now, with two different OBIís, and ALWAYS with this one number, which also always seems to be busy at the same times called from my cell phone. Beginning to think this cannot be a coincidence. Add to this the fact that I donít think Iíve ever even heard a busy signal over the OBI line an I think Iím onto something here. I could be wrong though.

Thoughts?
« Last Edit: April 07, 2021, 03:05:25 pm by Moonwalker » Logged
Moonwalker
Newbie
*
Posts: 15



« Reply #1 on: January 21, 2021, 11:31:51 am »

Guess nobody had any thoughts. Either that or yíall couldnít think of anything ďniceĒ to say about my half-cocked postulate. No matter. We can FINALLY (after six years of use) confirm that we actually DO hear busy signals. My wife called the local hospital today. All lines were tied up, and she heard it. First time in six years! Almost forgot what it sounded like.🤣

However, this ďhas received no response from the service providerĒ issue has persisted now for years and there is still no satisfactory answer. Iím getting it consistently with one number that I KNOW is not a VOIP service. Itís a land line. The message does come calling other numbers, on occasion, but nearly half or more of the times I call this one place, I get the no response message and cannot connect. Reboots of routers and the Obihai may help, but thereís no way to know since it could just be something that happens and clears up on its own over time.

What gives?

Has anyone ever figured out what this issue is? Googling it ALWAYS turns up that itís an issue with either the Obihai or the Polycom system itself. What is this problem? Is it ever going to be fixed?
Logged
jholme004
Jr. Member
**
Posts: 34


« Reply #2 on: January 21, 2021, 04:58:23 pm »

Have you tried calling from the Google Voice app on your cell phone?

That message is usually from an Obi that literally has not heard from the service provider for that SPx. Based on this and, as you described, hearing other busy signals, I wonder if it is how Google is treating that number?

Trying a call from that app would help determine is it how GV is handling the call or the Obi/Poly.
Logged

-Jason
Moonwalker
Newbie
*
Posts: 15



« Reply #3 on: January 21, 2021, 06:11:52 pm »

Have you tried calling from the Google Voice app on your cell phone?

That message is usually from an Obi that literally has not heard from the service provider for that SPx. Based on this and, as you described, hearing other busy signals, I wonder if it is how Google is treating that number?

Trying a call from that app would help determine is it how GV is handling the call or the Obi/Poly.

This is exclusive to Obi/Polycom. The message is unique to their system. Itís the same message you get when the Obi/Polycom system chokes in certain areas from time to time. When that happens you get that message no matter what number you call and all you can do is wait until the issue is fixed in your region.

The same message is triggered by other issues too. Itís these other issues that seem to persist but not for everyone. Regional service dropouts arenít as common as they once were. Itís these seemingly random occurrences when the number called is not off line and can be reached by other means such as cell, land lines, and, yes, the GV app. Itís a well known, and apparently random issue, that I personally donít believe is truly random at all.
Logged
drgeoff
Hero Member & Beta Tester
*****
Posts: 5243


« Reply #4 on: January 22, 2021, 02:20:44 am »

Only calls over the Obitalk network, ie those initiated by dialling **9 followed by a 9 digit Obi number, utilise any infrastructure operated by or onbehalf of Obihai/Poly.  For all other calls both the setup and voice data flow directly between your OBi device and your VoIP service provider.  As such, any "regional dropouts" cannot be caused by Obihai/Poly.
Logged
jholme004
Jr. Member
**
Posts: 34


« Reply #5 on: January 22, 2021, 03:05:18 pm »

Until a call is connected (i.e ringing begins on the other end), everything you hear is generated by the Obi device - dial tones, busy signal, reorder, intercept messages, etc. That doesn't mean the Obi is causing the error - it is programmed to play certain sounds when it receives certain codes from providers. This is how telephony has long worked - your local central office would do the same if you were calling the other side of the country in the POTS world.

 The Obi initiates the call via Google Voice. A hardware issue would be all or nothing, a configuration or software issue could be intermittent, but wouldn't discriminate against a certain number. You could always removed the GV line and then re-added it to ensure it's not a configuration issue. (If you changed any settings under "Expert" go into the corresponding ITSP and SP profiles and ensure the "ObiTalk" check box is checked on every line).

It truly sounds like a GV issue, which may include the signaling to your Obi, which triggers the intercept.
Logged

-Jason
Moonwalker
Newbie
*
Posts: 15



« Reply #6 on: April 07, 2021, 03:04:48 pm »

Well, this particular issue (getting the no response message from one particular number), can now be considered to be resolved.

After many occurrences, and as many investigative calls using my cell phone whenever the message is heard over the Obi, I have confirmed that 100% of the time the Obi gets this message, the cell phone gets a busy signal. So I have no idea why the Obi (or GV or the other phoneís service, I really donít care), wonít sound a busy signal, but at least now I know (just as I suspected earlier in the thread) that for THIS ONE NUMBER that message simply means the line is busy. And they are often so busy they actually unplug their phone. Itís just a stupid fluke.

Whatever. At least I can quit rebooting every device I own when I just want to order a darn PIZZA! Roll Eyes
Logged
Moonwalker
Newbie
*
Posts: 15



« Reply #7 on: April 07, 2021, 03:51:34 pm »

Only calls over the Obitalk network, ie those initiated by dialling **9 followed by a 9 digit Obi number, utilise any infrastructure operated by or onbehalf of Obihai/Poly.  For all other calls both the setup and voice data flow directly between your OBi device and your VoIP service provider.  As such, any "regional dropouts" cannot be caused by Obihai/Poly.

This makes sense, and although the average user probably doesnít care and thinks itís as simple as ďthis didnít happen until I plugged in the Obi,Ē itís good information for people like me who do want to understand. There are a lot of different techís at play here. In this case I donít really care what the exact cause is. I just wanted to know whether getting the message meant I need to continue rebooting crap or not, in this case it simply means wait and try again. The regional dropouts cause I mentioned earlier came from a much older thread wherein an Obihai technician replied explaining that it could sometimes occur and the only thing to do is wait until techs at wherever the cause is get it fixed. He did not specifically say it was anything to do with the Obi system. From what youíre saying, Iím gathering there actually isnít an Obi system outside the boxes and inter-Obi calling, so issues like this are more to do with GV (or whatever VoIP we use), and how the Obi is programmed to respond to various telephony signals. And if you add other Voips into the mix a lot of weird stuff is bound to happen that really isnít anyoneís fault in particular.

Think Iím gonna ask the owner of the shop if heís using something other than a hard line. Curiosity might kill the cat but Iím not a cat.  Shocked
Logged
ProfTech
Sr. Member
****
Posts: 478


« Reply #8 on: April 08, 2021, 02:35:53 am »

This is an interesting thread. I've used 2 different Obi's in several different configurations since 2012 and NEVER have I seen the "Dead air" / "No response" error except when there was either a problem with the service provider or I had an incorrect setting in the Obi. Bottom line, you should always either hear ringing or a busy signal. You didn't indicate what provider you were using until you intimated in your last post but since this mostly occurs with a single number the problem definitely smells like either a GV problem or at the least some sort of interaction between them and the Obi. Not a problem you can fix on your end. They used to do some weird stuff and since they're free they aren't going to look into it.
Logged
Pages: [1]
  Print  
 
Jump to:  

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

Advertisement
Advertisement