Greg Kujawa

Sooner or later if you are looking for a long-term solution, this project will need to reference Google's newer OAUTH mechanism. Google apparently starting providing this mechanism way back in 2012 --> https://developers.google.com/talk/jep_extensions/oauth. So perhaps it's not that new :) If someone contributed to recoding this project to utilize that then the project would certainly be more sustainable!

Wish I could offer some insight. I too ran into this awhile back, in that Google changed their API and this introduced breaking changes into how this project worked. Or didn't work I suppose :( I was utilizing Google Voice in a more diverse pager-type messaging app. With little time to try to uncover how things were broken, I just moved to Microsoft Yammer instead. Its API seems to be less of a moving target so far. Best of luck though!

Wish I could offer some insight. I too ran into this awhile back, in that Google changed their API and this introducted breaking changes into how this project worked. Or didn't work I suppose :( I was utilizing Google Voice in a more diverse pager-type messaging app. With little time to try to uncover how things were broken, I just moved to Microsoft Yammer instead. It's API seems to be less of a moving target so far. Best of luck though!

I personally haven't looked at this for awhile. From what I recall, I abandoned this messaging angle, in favor of a Yammer client instead. There were some breaking changes in Google's API that seemed to push developers toward Google Hangouts IIRC. What I'd recommend is placing a breakpoint around that call() function and see the debugging details in the various local variables. Perhaps that would point you in the right directions as to why the function fails?

Alternate project?

Added C header files for reference purposes. Cl...

Virtual Machines added!

I too ran into issues with the authentication. Purely URI-based authentication suddenly...