Inbound GV call problem - get dead silence when call is answered
dvbhardware:
I have the same problem for 4-5 days , I did a clean re-install of the obi100 last night and problem returned.
I un-checked X_SkipCallScreening for GV sp1 and it seem fine now.
Jimmy
AndrewH:
Unfortunately, I'm still experiencing this problem after applying the new firmware update released today.
TroyB:
I just installed the following version of firmware and it resolved the problem I reported at the beginning of this thread. -> 1.3.0 (Build: 2690)
Thank you Obihai !!! ;D
R_Chandra:
I also had this issue (sorry for posting an additional thread). I did a Web-based factory reset, and reconfigured from scratch (I didn't have a LOT changed from the defaults, so it went fairly quickly), plus the option 27=1 full/100 from the builtin IVR (aa2). It's been working fairly well since then. If I restored a config XML made previously, the problem would return. So GV seems to have changed something slightly, just enough to trick the OBi firmware into not working properly. I agree, I also wanted the SSL option, but as of right now, it doesn't work. I also applied the firmware released 15-Mar-2012, but it didn't cause much of a change (although I don't experience any other issues).
Another maybe slightly interesting data point is that calls from VoicePulse would not connect properly or would be reported by voice announcement as being out of service, but using an alternate GV account (with an IPKall number to serve as the termination of the first call initiated from the Web page) seemed to work OK regardless. But then again, I kind of figured that would work "better" because it's Google calling Google :-).
Marc:
Quote from: AndrewH on March 15, 2012, 11:01:03 am
Unfortunately, I'm still experiencing this problem after applying the new firmware update released today.
Same here. Problem started maybe 3 or 4 days ago and happens to 5 out of 6 calls I receive.
In the same time frame, on out going calls to busy phone #s, I hear one standard ring before the busy signal. This is quite annoying because the *05 doesn't work since it calls right back after detecting the normal ring. This too was not corrected by the new firmware released yesterday (2690).
I'm putting a support ticket in now, as was suggested earlier in the thread.
Navigation
[0] Message Index
[#] Next page
[*] Previous page