News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

GV Outbound Calls After EOL

Started by azrobert, May 27, 2022, 07:34:55 AM

Previous topic - Next topic

azrobert

#80
Quote from: Taoman on November 03, 2022, 05:55:59 AMCan't seem to break it.

If you have the Bookmark Bar enabled and have GV warning "Your browser might prevent calls from ringing" do this:
Reduce the width of the window until the warning message expands to 3 lines. Keep the window height at max. The script will now fail. Adding "&parm4=100" will fix this.

Zoom 250% will also cause the script to fail.

AHK will not detect a window title when there is a 2nd tab and it's active. In this scenario the script will open another GV window and complete the call. I haven't researched why it doesn't detect the window.

Taoman

Quote from: azrobertIf you have the Bookmark Bar enabled and have GV warning "Your browser might prevent calls from ringing" do this:
Reduce the width of the window until the warning message expands to 3 lines. Keep the window height at max. The script will now fail. Adding "&parm4=100" will fix this.
I've always had the Bookmark Bar enabled but have never seen that error/warning message before. But I take your point about how parm4 would be used.

PS.
From the time I dial the number and then hear the dial tone it takes 6.5 seconds until my Callcentric extension starts ringing. Pretty damn fast.

azrobert

#82
I have an updated GV_Server and have a new version.

I made a change in Chrome settings and the script started failing, so I fixed the code again. I also created a more stable version 2. The old script repositions the cursor, so it takes 1 tab to the outbound number field and then enters the number. I explained in a previous post why this target area changes based on different settings.

The new version takes a different approach. It enters the full GV URL which contains the outbound number. Selecting the Forwarding Number is the only thing left for the script to do. This is basically the same as the old script when it doesn't find a GV window. I originally didn't use this method because it takes about 2 seconds longer to receive the callback.

If the old script works, you can continue using it. If it doesn't work, try the new V2. The updated old version and the instructions are found at the link below. The OBi forum only allows 4 attachments per post, so I attached the new GV_Server_V2 here.

https://www.obitalk.com/forum/index.php?msg=112105



Taoman

#83
Very cool.
FYI: the ahk script works fine for me but the exe does nothing. It executes and I can see that it loaded (alongside my personal ahk script) but when I make a call nothing happens.*
Edit: so while I was writing this post I still had the exe loaded. I just now exited the exe and loaded the new ahk script and the script immediately started completing the call I had tried to make with the exe. It completed the call with no issues.

Also, how hard would it be to just hardcode in my forwarding number or is that even possible? The more I think about I'm guessing it's not possible......

* I compiled the working version 2 ahk script but still no joy with the exe.

PS. Nice touch.
Quoteif (Winfound != "Y")
   WinClose, Voice

azrobert

GV_Server.exc and GV_Server_v2.exe both work for me.

Did you allow it access thru the firewall?

Go to:
Windows Security.
Firewall & network protection
Allow an app through firewall

Is GV_Server.exe checked?

I thought that there might be a way to pass the forwarding number with the URL, but I couldn't find anything. I even posted a question on the GV forum and they said it can't be done.

Taoman

Quote from: azrobert on May 26, 2023, 02:23:42 PMDid you allow it access thru the firewall?

Yeah, that was it. Thanks.