 dbmavenThere's no shortagePremium,Mod
join:1999-10-26
Sty in Sky
kudos:2 | reply to mazilo
Re: [Proggy] Google Voice dialer Check the original post - which has been amended, with an explanation, and a new ZIP file
--
Ad astra per alas porci!!
|
|
|
|
 brg
join:2001-01-03
Chicago, IL
kudos:1 | said by dbmaven:Check the original post - which has been amended, with an explanation, and a new ZIP file
Aha! Well =that= was un-intuitive!  Never would have thought of going back to the original message; thanks for the direction.
And thanks, DogFace05 for the revision. I use the program regularly! |
|
dbmavenThere's no shortagePremium,Mod
join:1999-10-26
Sty in Sky
kudos:2 | Yes - it was un-intuitive - I should have made the note to go to the OP in the first place.
--
Ad astra per alas porci!!
|
|
curro
join:2003-10-24
Seabrook, TX | reply to DogFace05
Re: [Proggy] Update! Google Voice dialer Another great work by DogFace05! Thanks a lot pal! |
|
| reply to brg and curro
said by brg:And thanks, DogFace05 for the revision. I use the program regularly! said by curro:Another great work by DogFace05! Thanks a lot pal! You're very welcome! Glad you're finding some use for the program. BTW, be sure to check out its new SMS text message sending function. |
|
brg
join:2001-01-03
Chicago, IL
kudos:1 | said by DogFace05:BTW, be sure to check out its new SMS text message sending function.
I have not yet tried that, but I'm going to give it a whirl soon! |
|
curro
join:2003-10-24
Seabrook, TX | reply to DogFace05
Another question on the topic for DofFace05:
Have you seen/heard a way to unlock one of the popular Linksys ATAs to work with GV? |
|
maziloFrom MaziloPremium
join:2002-05-30
Lilburn, GA
kudos:1 | said by curro:Another question on the topic for DofFace05:
Have you seen/heard a way to unlock one of the popular Linksys ATAs to work with GV? Sorry if we hi-jack the thread because this is really off topic.
AFAIK, unlocking and/or un-customizing a Linksys SPA ATA devices should not be a problem with DogFace05. But, I sure would like to know if you had seen/heard what you had said above because I never know any Linksys SPA ATA devices has a support for XMPP to handle a GV/GTalk call.
--
don't and stop are the ONLY two 4-letter words considered offensive to men, but not when used together. |
|
Reviews:
 ·Future Nine Corp..
·callwithus
·Google Voice
·Anveo
·ViaTalk
·Callcentric
| said by mazilo:said by curro:Another question on the topic for DofFace05:
Have you seen/heard a way to unlock one of the popular Linksys ATAs to work with GV? Sorry if we hi-jack the thread because this is really off topic. AFAIK, unlocking and/or un-customizing a Linksys SPA ATA devices should not be a problem with DogFace05. But, I sure would like to know if you had seen/heard what you had said above because I never know any Linksys SPA ATA devices has a support for XMPP to handle a GV/GTalk call. I believe Dogface05 implemented a GV module for Asterisk or Freeswitch which uses GV callback feature without XMPP.
It's different from Gtalk modules.
It may be possible to add small GV callback module to ATA. |
|
1 edit | reply to curro
said by curro:Another question on the topic for DofFace05:
Have you seen/heard a way to unlock one of the popular Linksys ATAs to work with GV?
There's no such thing as "unlocking" an ATA to work with GV, unless some ATA has specifically been designed with built-in GV support and for some reason had the feature merely disabled in its configuration. I've never heard of such an ATA (with the exception of the Obi units, but because they don't have their GV support locked, they don't count).
One cannot unlock an ATA that doesn't have built-in support for GV, in order to make it work with that service. What could theoretically be done, is to create the necessary code to add support for it (either the call-back method or the g-talk/XMPP protocol). From a practical standpoint, however, it's a non-starter. No ATA that I know of has publicly available open source, so one cannot just recompile the code with new modules for GV support added, to produce a new GV-able firmware image.
Instead, one would have to patch the code of an existing firmware release. But you can't just arbitrarily add new code to a code base that already has all its memory usage hard-coded at link time, so it's necessary to reuse its existing code space. One has to find functions in the existing base code that can be rewritten more tightly in assembly language, in order to squeeze out space to fit the new code in. The new GV support also has to be written in assembly language, and manually linked to any functions/data it needs to access in the base code. Although I've done this kind of thing to modify some behaviors for testing purposes, for something of the order of complexity of adding support for a whole new protocol, it would be a gargantuan task that no one in their right mind would ever want to bother with. And most importantly, because the base code is proprietary and copyrighted, any endeavor to try to modify it would be a totally fruitless and wasted effort, since the results could not legally be redistributed.
The only real practical solution is to use some kind of workaround running on a standalone embedded device--either something like Asterisk/Freeswitch, which already have built-in support for GV, or some kind of SIP-to-GTalk/XMPP translator/proxy. |
|
curro
join:2003-10-24
Seabrook, TX | Thanks for taking the time to reply! |
|
| reply to DogFace05
Thanks, I think this is what I am looking for, although when I ran it I got the error "{"ok":false,"data":["code":20}}. Any suggestions? Please reply to phyllis@aardwolfalpacas.com. |
|
| See »Re: [Proggy] Google Voice dialer. |
|
| is there an update version for this proggy?
i believe this has stopped working (gvdial-0-80-0)
i do everything as described; im getting back
{"ok":true,"data":{"code":0}}
but no call is being placed!
SMS works though.
Thanks in advance |
|
| gvdial-0-80-0 is the latest version, and I just verified that it still works ok for me. Also note that '{"ok":true,"data":{"code":0}}' is Google Voice's 'success' code, so your callback request is being accepted fine by them.
That said, you have to make sure that the phone type index on the command line (5th parameter, defaults to 2 [mobile] if not specified) matches the call back number's type as registered in your list of forwarding phones in your Google Voice account. For example, if your callback number is registered as type "Home", set the 5th parameter to 1. |
|
1 edit | reply to DogFace05
Thank you DogFace05, i must be doing something wrong then
i run the command the way you have stated while using 9
gvdial my@gmail.com mypass 2101234567 8181234567 9
if i use anything other then 9 or 4 for the phone index
i get this error
{"ok":false,"data":{"code":20}}
are there any prerequisites for this to work properly
other then an active GV account, GVdial.exe and a cmd?
im on winxp sp3, behind a router with a static NAT address
is there a service or a module needed to be running in the background, or port mapped for this to work?
kind regards
Eric |
|
4 edits | OK so Ive fiddled with this a bit more, here is what i found
if i send the command this way -
gvdial my@gmail.com mypass 2101234567 8181234567 9
i get
{"ok":true,"data":{"code":0}}
but nothing happens, no call comes in
if i run the command with my email instead of my GV number
gvdial my@gmail.com mypass 2101234567 my@gmail.com 9
i get
{"ok":true,"data":{"code":0}}
Now the call comes in on my Yate Client!!!
Brilliant work DogFace05, Thank you for sharing!
is there a way to disconnect the call if not answered?
or to dial an extension after the call is picked up?
kind regards
Eric |
|
| said by MyPC8MyBrain:if i send the command this way -
gvdial my@gmail.com mypass 2101234567 8181234567 9
i get
{"ok":true,"data":{"code":0}}
but nothing happens, no call comes in
if i run the command with my email instead of my GV number
gvdial my@gmail.com mypass 2101234567 my@gmail.com 9
i get...
There's your problem. The 4th parameter is the number you want the callback to ring. It has to be one of the forwarding phone numbers you've defined in your GV account. It is NEVER your GV number. And as I stated before, the type index has to match the type as defined in your GV account's list of forwarding phone numbers. Index 9 only applies to email addresses (or implied gmail addresses, where "@gmail.com" is implied, but left out). |
|
