The number you dialed, has not received a response from the service provider?
B0b.:
Quote from: A_Friend on August 19, 2018, 04:28:29 pm
B0b,
At this point, I don't have any advice, only more questions.
A_Friend,
Yes, the status on the System Status page under SP1 Service Status always says connected.
It is any number I try to call. It seems random whether it connects or gives the error message. It is also random if the phone rings for incoming calls.
If I redial the same number (for testing, I'm calling my local T-Mobile cell phone ending in 751 in the quotes above), half the time it will go through, the other half it will give the error message again. Other times, the call will go through right away without the error message. While writing this rely, I just tried it again and got the error message 4 times in a row, then restarted the OBi.
Right after I restart the OBi, it almost always goes through. When the call does go through, I do get a Peer RTP Address as the phone is ringing, but as it is connecting and immediately before it starts ringing the Peer RTP Address is 0.0.0.0:0 .
I thought about the readback not saying the full number some more and realized that since it is a local number and I have the local area code entered in the dashboard, I usually don't dial in the area code for my local cell phone when calling it. I tried entering the full number with the area code and it read back the full number with the area code when I heard the error message again.
As you said, it reads back exactly what I dialed when it say the error message. just when it connects, it automatically adds the 1 then the area code on the user interface page.
I'm not dialing outside North America, so i haven't funded my GV account.
As for the charge-related failure, I'm calling my cell phone, a local T-Mobile number. I have never had a problem calling T-Mobile numbers previously with GV or OBi when I had AT&T U-Verse.
https://freecarrierlookup.com/ does confirm my number is a T-Mobile wireless number.
SteveInWA:
Again: there is no such thing as a "keep alive". The fact that OBiTALK network calls fail confirms that this is not a ITSP problem. Period. The error message you are hearing is generated by the OBi, not by any ISP/ITSP.
Remove the hotspot Internet service from the installation, connect the OBi to a non-wireless ISP, and see what happens.
B0b.:
Quote from: SteveInWA on August 19, 2018, 09:30:23 pm
Again: there is no such thing as a "keep alive". The fact that OBiTALK network calls fail confirms that this is not a ITSP problem. Period. The error message you are hearing is generated by the OBi, not by any ISP/ITSP.
Remove the hotspot Internet service from the installation, connect the OBi to a non-wireless ISP, and see what happens.
I realize that the message is generated by the OBi. I am trying to figure out why the calls sometimes go through and sometimes do not connect with the hotspot.
When I had AT&T U-Verse internet (non-wireless ISP) a couple months ago, the OBi worked correctly. I do not have this U-Verse service any longer and am only using the hotspot for home internet.
SteveInWA:
Why is this so hard to comprehend? You proved it yourself. It worked when connected to the Internet via U-Verse, but it is unreliable when using the hotspot. The failures are because you are using a connection that is guaranteed to fail at some point, every day.
B0b.:
Quote from: SteveInWA on August 19, 2018, 09:55:28 pm
Why is this so hard to comprehend? You proved it yourself. It worked when connected to the Internet via U-Verse, but it is unreliable when using the hotspot. The failures are because you are using a connection that is guaranteed to fail at some point, every day.
It is "so hard to comprehend" because the hotspot connection works for all other connected devices at the time when the OBi doesn't connect. I can even place a call using the same GV account on the GV app on the computer or GV / Hangouts on a smartphone connected to the same hotspot.
I am not asking if the hotspot is causing the calls to not go through. I am asking why the hotspot is causing the calls to not go through with the OBi.
I posted the question here to try different settings to try to get the OBi to work with the hotspot, not hear "tough luck".
Navigation
[0] Message Index
[#] Next page
[*] Previous page