Pygooglevoice problem
I was successful to use google on 19/3/2016, nothing changed in system. The problem now:
Traceback (most recent call last):
File "/usr/bin/gvoice", line 97, in
Facing same issue. Though, GV might have change API parameters, but that doesn't seems to be the case
Following is the REST request from CHROM.
rest URL:https://www.google.com/voice/call/connect/ Request Method:POST Status Code:200 Remote Address:1.1.1.1:443 Response Headers alt-svc:quic=":443"; ma=2592000; v="32,31,30,29,28,27,26,25" alternate-protocol:443:quic cache-control:no-cache, no-store, must-revalidate content-disposition:attachment content-encoding:gzip content-length:100 content-type:text/javascript; charset=UTF-8 cookie: date:Thu, 14 Apr 2016 16:01:14 GMT expires:Mon, 01 Jan 1990 00:00:00 GMT pragma:no-cache, no-store server:GSE set-cookie:S=grandcentral=mKhle2E31hUWeXyFJMQi7vZ9Tx3MvDIp; Domain=.google.com; Path=/; Secure; HttpOnly status:200 x-content-type-options:nosniff x-frame-options:SAMEORIGIN x-xss-protection:1; mode=block Request Headers Provisional headers are shown Content-Type:application/x-www-form-urlencoded;charset=UTF-8 Origin:https://www.google.com Referer:https://www.google.com/voice?pli=1 User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36 Form Data view source view URL encoded outgoingNumber:XXX82XXXXX forwardingNumber:YYYYYYYY subscriberNumber:ZZZZZZZZZ phoneType:2 remember:0 _rnr_se:q
Have you guys tried this? https://github.com/pettazz/pygooglevoice/issues/18#issuecomment-185398220
{Have you guys tried this? #18 (comment)}
Of course I did. same problem.
Just figured, for US numbers provide +1 before forwarding number. for example +14445556666. Surprisingly without that I am getting error GV: {u'data': {u'code': 1}, u'ok': False}. Earlier it used to work without country code.
Will monitor my asterisk for couple of more days before saying anything for sure.
Thanks so much aprajapati, it is OK now if add +1 before my forward number.
@aprajapati @edmond25 @illgitthat Any update? I am having a similar issue on #44.