Weird incoming Google Voice problem
dhobi:
Weird part is that I have Call Screening set to Off in the GV Calls preferences tab, so I'm not sure why I'm required to press '1' to accept a call. X_SkipCallScreening is also enabled on the OBI which from what I understand does exactly that, it sends a '1'.
I messed with the Trusted Callers today and that's how I noticed that the AA was not picking up my calls, they were being sent to GV voicemail. And after that I could not pickup any incoming GV calls. I would say that's when the trouble started and adding my mobile as a Trusted Caller caused it though it might be just a coincidence.
I have nothing on the list of Trusted Callers now but things are still not working without pressing '1' to accept incoming calls. Any ideas what changes to the OBI the Trusted Callers list may have made? I even removed the device, reset the settings and added it again to OBiTalk and still not working. It seems that something is still persisted and gets changed on the device again.
RonR:
Quote from: dhobi on March 01, 2012, 10:59:53 pm
Weird part is that I have Call Screening set to Off in the GV Calls preferences tab, so I'm not sure why I'm required to press '1' to accept a call. X_SkipCallScreening is also enabled on the OBI which from what I understand does exactly that, it sends a '1'.
Even with Call Screening disabled, Google Voice still expects a '1' to be pressed in order to accept the call when the XMPP interface is used. It's the way the Google Voice folks implemented it. Simply enable X_SkipCallScreening and this problem will be solved.
Quote from: dhobi on March 01, 2012, 10:59:53 pm
I have nothing on the list of Trusted Callers now but things are still not working without pressing '1' to accept incoming calls. Any ideas what changes to the OBI the Trusted Callers list may have made?
There is absolutely no relationship between Trusted Callers and pressing '1' to accept incoming Google Voice calls. When you specifiy a Trusted Caller, it simply causes the OBiTALK Web Portal to configure the OBi's InboundCallRoute with rules to allow single-stage calling through the PrimaryLine as well as go to the Auto Attendant. Nothing about Trusted Callers is related to pressing '1' to accept a Google Voice incoming call.
dhobi:
Quote from: RonR on March 01, 2012, 11:18:37 pm
Quote from: dhobi on March 01, 2012, 10:59:53 pm
Weird part is that I have Call Screening set to Off in the GV Calls preferences tab, so I'm not sure why I'm required to press '1' to accept a call. X_SkipCallScreening is also enabled on the OBI which from what I understand does exactly that, it sends a '1'.
Even with Call Screening disabled, Google Voice still expects a '1' to be pressed in order to accept the call when the XMPP interface is used. It's the way the Google Voice folks implemented it. Simply enable X_SkipCallScreening and this problem will be solved.
X_SkipCallScreening is already enabled, but it seems to have stopped working. Strange that it worked for about a week and it stopped working today. I think there may be a bit of a delay before the connection is established and the very first packets that send the '1' don't make it to GV.
RonR:
Quote from: dhobi on March 01, 2012, 11:29:11 pm
[X_SkipCallScreening is already enabled, but it seems to have stopped working. Strange that it worked for about a week and it stopped working today.
Are you verifying this by logging into the OBi directly or are you looking at the OBiTALK Web Portal? The OBiTALK Web Portal doesn't always reflect what's actually in the OBi. The only settings that really count are those in the OBi itself.
If X_SkipCallScreening is actually enabled in the OBi itself, you might try resetting the OBi to factory defaults and then reconfiguring it. The OBi occasionally gets corrupted internally with no outward evidence of such in any of its settings.
dhobi:
I verified both on the device and on OBiTalk. I also unchecked the setting, let it sync and reboot, tried a call then checked the setting again, let it sync and reboot and tried a call.
Still not working without pressing '1', something is broken somewhere.
I tried resetting the device, deleting it from OBiTalk, re-adding it and configuring again and still the same behavior. I might try just removing it from OBiTalk and just managing it locally so nothing else pushes any settings into it. But I have to figure out how to configure GV "by hand" straight on the device. Are the settings posted anywhere?
Navigation
[0] Message Index
[#] Next page
[*] Previous page