The number you dialed, has not received a response from the service provider?
A_Friend:
So, Steve, to sum up...
If YOU don't have an answer for someone who posts a problem, no one should try to help?
Look, I know you're a very valuable resource here and have helped numerous people for a number of years, and being one of them, I greatly appreciate that. And, maybe it's your OCD that motivates you to help, and I hope you stay motivated, but it's also clearly the reason that my apparently feeble and not self-assured responses are getting under your skin.
Why don't we leave it to the OP to curse me out for wasting their time, or whatever? Aren't there other posters you could be helping right now?
Yes, the ethernet connection is dropping. Some hotspots disconnect connections if they're not actively being polled. Forcing the VoIP connection to be more aggressive MIGHT (just might!) keep it from disconnecting. At least that's the theory behind my response. Having played with 4 hotspots from 4 different carriers over the years, and having used the WiMax one to support a whole-house LAN (including an Obi202) a number of years ago in a setup not unlike the poster, I think I'm entitled to my suspicion as to what MIGHT be going on, if not exactly what to do about it. So, it's not ENTIRELY random.
LTN1:
I see this "I need to answer syndrome" (applies to both genders) all the time on social media. It is especially unhelpful when it has no evidentiary support and is wrong.
I think the "I need to answer syndrome" has to do with the need to be heard than the need to be helpful.
A_Friend:
LTN1, perhaps, as you're responding to this thread, you could offer some advice or encouragement to Bob. Wouldn't that be more productive, and on-subject, than your message?
You're clearly more experienced than I am and have certainly helped many people over the years in this forum. I'm sure he'd be very grateful, as I have been when you've helped me.
B0b.:
Quote from: A_Friend on August 16, 2018, 10:38:33 pm
The "connected" message on the Obitalk dashboard is just talking about the dashboard being able to communicate with the device. It says nothing about whether your device is attached to the carrier (GV). For that, you need to read the Status of the device. (Forgive me, but I'm not a big dashboard fan, so I tend to do everything through the local user interface, but you may also be able to access this under ObiExpert from the Dashboard. Just don't try using the ObiExpert and local UI routines at the same time.)
To access the local User Interface, you need the IP address of the Obi on your LAN, and you need another computer, tablet, or other gizmo with a browser on the same LAN. To find the IP address, you pick up the phone, dial *** and then 1. Then, browse to that address and login. (admin/admin)
The Status screen displays as the first thing when it comes up. The menu is at left where you can look at other things and settings. Scroll down the Status screen and it will show you which SP is connected, which isn't, and sometimes why.
Then, under Status, at left, you might want to check Call History for more clues. There will be error codes for failed calls.
After you find out what's happening, maybe someone else can help you. I haven't had this problem myself on an Obihai before. Years ago, though, when I was running Nextiva on a PAP2T, I remember tech support had me change similar settings for a similar problem. Something is letting your connection expire. That's where my useful wisdom on this subject expires, too. Under SP1 you'll find some settings for keep_alive. I don't know what to change or what to suggest changing it to, but if you do some research, and experiment a bit, maybe you'll get lucky. Just make a note of what the setting was when you started. Or, better yet, maybe someone else here can tell you.
You also might get some useful information from your hotspot service's tech support, but probably not from its level 1, although you never know. I never got anything useful out of AT&T, Verizon, etc., without getting to level 3. Good luck.
Thank you A_Friend for all your help! I am just trying different things myself to try to fix it and any guidance (even if speculation) is helpful.
I was looking at the local user interface before and at the call history, but I didn't know what to change. I'll do some more research.
On the call history page, when a call fails it always says "Time | From PH1 | to SP1(*Number*)"
then on the next line it is blank with "Call Ended" in the right column. It is at the same second that the call is placed.
When a call goes through, he call history page says "ringing" then "Call Connected" at different times.
Right now, any call I make does go through except two, so I will have to wait to try some different keep alive settings until it isn't working anymore.
During the two calls that didn't go through, I took screenshots of the call status page. This was before it gave the error message over the phone. Usually the "The number you dialed, has not received a response from the service provider" message is said 30 seconds or so after I try to place the call. The second picture is while the error message is being said on the phone.
Can pictures be attached? I'm having trouble adding the screenshots.
edit: Ah, I see there are still issues with the forum attachment software since July 1.
Basically the screenshots say while calling:
Quote
Call 1.......................Terminal 1.........Terminal 2
Terminal ID...............Phone1.............SP1
State........................trying...............calling
Peer Name
Peer Number..............1*******751....1*******751
Start Time.................15:43:48..........15:43:48
Duration....................00:00:17..........00:00:17
Direction....................Outbound.........Outbound
Peer RTP Address...............................0.0.0.0:0
Local RTP Address..............................192.168.1.151:16612
RTP Transport................................... UDP
Audio Codec.......................................tx=; rx=
RTP Packetization (ms)........................tx=0; r=0
RTP Packet Count............................... tx=0; r=0
RTP Byte Count..................................tx=0; r=0
*Everything else is blank.
And while hearing the error message:
Quote
Call 1.......................Terminal 1.........Terminal 2
Terminal ID...............Phone1.............Announcement1
State........................connected.........connected
Peer Name
Peer Number..............****751
Start Time ................16:14:10...........16:14:10
Duration....................00:00:03...........00:00:03
Direction....................Outbound..........Inbound
Peer RTP Address
Local RTP Address
RTP Transport
Audio Codec
RTP Packetization (ms)
RTP Packet Count
RTP Byte Count
Everything after Direction is blank
I thought it was interesting that the phone number country code and area code was removed while playing the error message.
The SP1 Service Status always says:
Quote
Status............................ Connected
Primary Proxy Server........
Secondary ProxyServer.....
CallState....................... 0 Active Calls
Unless I'm on a call or hearing the error message, then it says:
Status............................ Connected
Primary Proxy Server........
Secondary ProxyServer.....
CallState....................... 1 Active Calls
A_Friend:
B0b,
At this point, I don't have any advice, only more questions.
The Peer RTP host being 0.0.0.0 would seem to indicate you don't have a server connection for that call, and yet your Status says Connected? Sounds a bit like the host (GV) is just refusing to place that call for you for some reason.
And, these two phone numbers you're unable to call, is that consistent? Like if you redial them, you get the same results?
Also, you mentioned that the error readback is not saying the full number, but stripping the country code? Is the country code not "1"? That's interesting. Those "the number you have dialed" messages are typically either exactly what you dialed, or what your dial plan and outbound call route have translated them into. If an overseas country code or an area code is getting stripped, that's probably happening right in your device. Check those settings.
And speaking of country codes... Are you dialing outside of North America on Google Voice, and if so, have you funded your account?
There's one other charge-related failure I read about a couple years ago, although it concerned "Magic Jack" and not Google Voice. Apparently, there are some telephone exchanges that charge extraordinarily large incoming connection fees to complete a call. Magic Jack had blacklisted them and wouldn't connect to them as it ruined whatever passed for their business model.
While I have no idea whether Google Voice does this, you might want to run those numbers through this and see if it's some tiny/unusual company: https://freecarrierlookup.com/
Navigation
[0] Message Index
[#] Next page
[*] Previous page