SOLVED Google voice crashes asterisk

[chris_c_]

Fresh install of Incredible PBX with Asterisk GUI for Ubuntu 14.04 32 bit on Virtualbox 512MB VM.
Followed this how to:
http://nerdvittles.com/?p=12181

Connectivity is OK from the notebook Yate sip client, to the desktop (running the PBX VM). The SIP login works fine, call extension 6002 and leave a voicemail, checking voicemail works, and the yahoo news app works.

Added a dedicated set of google voice credentials to the proper area of Asterisk GUI, "Incredible PBX apps / Google voice". They saved ok.

Try to make a call to a normal US phone number by entering 10 digit US phone number in yate and click the call icon. It rings about 20 times then yate seems to give up and hang up. The actual phone being called, fails to ring. Leads you to believe the call didn't actually go through. The Asterisk call log inside the Asterisk GUI show the call. Not sure what actually happened.

Looked on this forum, on another google voice thread, and found a suggestion from WM to go thru a google voice "display unlock captcha" process to looosen up some of the possible security restrictions google might have been applying that might've prevented the call from working. https://accounts.google.com/b/1/DisplayUnlockCaptcha

Tried to make a call from yate thru the PBX to the same US phone number.
Now it behaves totally differently.
Asterisk service stops running, and the web interface logs out.
Check in the logs.

asterisk segfault libikseme1.so.3.0.0

Anyone else experience this?

How to fix it?

 

[wardmundy]

We can't replicate your problem. Sorry. Did you try BOTH of the Google Voice fixes documented in the other thread?? What does the Asterisk CLI show??

 

[chris_c_]

We can't replicate your problem. Sorry. Did you try BOTH of the Google Voice fixes documented in the other thread?? What does the Asterisk CLI show??

Asterisk CLI shows this.
It's scrolling by quite fast.

incredible@incrediblepbx:~$ sudo asterisk -r
Asterisk 11.15.1, Copyright (C) 1999 - 2013 Digium, Inc. and others.
Created by Mark Spencer <[email protected]>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
Connected to Asterisk 11.15.1 currently running on incrediblepbx (pid = 3782)
[Feb  6 15:55:53] WARNING[3796]: res_xmpp.c:3573 xmpp_client_receive: Parsing failure: Hook returned an error.
[Feb  6 15:55:53] WARNING[3796]: res_xmpp.c:3570 xmpp_client_receive: Parsing failure: Invalid XML.
[Feb  6 15:55:53] WARNING[3796]: res_xmpp.c:3637 xmpp_client_thread: JABBER: socket read error
[Feb  6 15:55:58] WARNING[3796]: res_xmpp.c:3573 xmpp_client_receive: Parsing failure: Hook returned an error.
[Feb  6 15:55:58] WARNING[3796]: res_xmpp.c:3570 xmpp_client_receive: Parsing failure: Invalid XML.
[Feb  6 15:55:58] WARNING[3796]: res_xmpp.c:3637 xmpp_client_thread: JABBER: socket read error
[Feb  6 15:55:59] WARNING[3796]: res_xmpp.c:3573 xmpp_client_receive: Parsing failure: Hook returned an error.
[Feb  6 15:55:59] WARNING[3796]: res_xmpp.c:3570 xmpp_client_receive: Parsing failure: Invalid XML.
[Feb  6 15:55:59] WARNING[3796]: res_xmpp.c:3637 xmpp_client_thread: JABBER: socket read error
[Feb  6 15:55:59] WARNING[3796]: res_xmpp.c:3573 xmpp_client_receive: Parsing failure: Hook returned an error.
[Feb  6 15:55:59] WARNING[3796]: res_xmpp.c:3570 xmpp_client_receive: Parsing failure: Invalid XML.
[Feb  6 15:55:59] WARNING[3796]: res_xmpp.c:3637 xmpp_client_thread: JABBER: socket read error
[Feb  6 15:55:59] WARNING[3796]: res_xmpp.c:3573 xmpp_client_receive: Parsing failure: Hook returned an error.
[Feb  6 15:55:59] WARNING[3796]: res_xmpp.c:3570 xmpp_client_receive: Parsing failure: Invalid XML.
[Feb  6 15:55:59] WARNING[3796]: res_xmpp.c:3637 xmpp_client_thread: JABBER: socket read error
[Feb  6 15:56:00] WARNING[3796]: res_xmpp.c:3573 xmpp_client_receive: Parsing failure: Hook returned an error.
[Feb  6 15:56:00] WARNING[3796]: res_xmpp.c:3570 xmpp_client_receive: Parsing failure: Invalid XML.
[Feb  6 15:56:00] WARNING[3796]: res_xmpp.c:3637 xmpp_client_thread: JABBER: socket read error
[Feb  6 15:56:00] WARNING[3796]: res_xmpp.c:3573 xmpp_client_receive: Parsing failure: Hook returned an error.
[Feb  6 15:56:00] WARNING[3796]: res_xmpp.c:3570 xmpp_client_receive: Parsing failure: Invalid XML.
[Feb  6 15:56:00] WARNING[3796]: res_xmpp.c:3637 xmpp_client_thread: JABBER: socket read error
incrediblepbx*CLI> exit
Asterisk cleanly ending (0).
Executing last minute cleanups
incredible@incrediblepbx:~$

Tried only the one Google Voice fix, so as to pinpoint which of the 2 fixes is effective in addressing the issue.

Here is a tail of the /var/log/kern.log - the last line (segfault) appears moments after trying to place a call with the yate client from the notebook.

incredible@incrediblepbx:~$ tail /var/log/kern.log
Feb  6 14:31:55 localhost kernel: [  22.928399] intel8x0: measured clock 128243 rejected
Feb  6 14:31:55 localhost kernel: [  22.928419] intel8x0: clocking to 48000
Feb  6 14:31:56 localhost kernel: [  24.014549] audit_printk_skb: 12 callbacks suppressed
Feb  6 14:31:56 localhost kernel: [  24.014554] type=1400 audit(1423251116.212:16): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/mysqld" pid=1597 comm="apparmor_parser"
Feb  6 14:31:56 localhost kernel: [  24.064812] type=1400 audit(1423251116.260:17): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/etc/my.cnf" pid=1600 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Feb  6 14:31:56 localhost kernel: [  24.081331] type=1400 audit(1423251116.280:18): apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld" name="/etc/my.cnf" pid=1629 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Feb  6 14:32:56 localhost kernel: [  86.816002] nf_conntrack version 0.5.0 (7925 buckets, 31700 max)
Feb  6 14:32:57 localhost kernel: [  87.066060] ip6_tables: (C) 2000-2006 Netfilter Core Team
Feb  6 14:36:42 localhost kernel: [  312.083386] asterisk[2615]: segfault at 8 ip b6a75e4e sp b30a9060 error 4 in libiksemel.so.3.0.0[b6a70000+c000]
Feb  6 16:03:22 localhost kernel: [ 5512.704508] asterisk[13582]: segfault at 8 ip b6a9ce4e sp b2efa060 error 4 in libiksemel.so.3.0.0[b6a97000+c000]
incredible@incrediblepbx:~$

Could this be a 32-bit vs. 64-bit bug ?

 

[chris_c_]

UPDATE: Did the second Google Voice fix, the one for "Less Secure Apps using this Google tool", and the phone call now goes thru....! Success.

Looked into what this "Less Secure apps" actually means:

That's why, beginning in the second half of 2014, we'll start gradually increasing the security checks performed when users log in to Google. These additional checks will ensure that only the intended user has access to their account, whether through a browser, device or application. These changes will affect any application that sends a username and/or password to Google.

Looks like the problem is, Incredible PBX (and many other "less secure apps") is saving cleartext passwords and transmitting them to google on behalf of the google voice account (or any account) owner. These saved cleartext passwords are subject to abuse/theft by hackers, hardware thieves, as well as "evil admins". The solution is some form of token or hash based authentication such as OAuth 2.0 that requires the account owner to authorize connecting to the various accounts only. Once a day, once a week, once every two weeks, via a secure channel messaging to a personal device such as smartphone....