Hey Lonnie, Nope, using 1.4. I thought about possibly switching over to it, but decided against it. Didn't want to have to rewrite all my dialplan, etc. Plus we use 1.4 at work.
I played around with it a bit more, and I was able to login to both accounts using other jabber clients. So that eliminates things on the Google side. I have to believe it's some type of issue with either the module or Asterisk 1.4, since every other variable seems to be eliminated. Has anyone else on 1.4 got it working? Thanks. -James On 01/15/2012 06:27 PM, Lonnie Abelbeck wrote: > Hi James, > > Are you using Asterisk 1.8 ? If not, you may have better results with > Asterisk 1.8. > > I know along with Michael, David Kerr also got GTalk working properly. Both > use Asterisk 1.8. > > Lonnie > > > On Jan 15, 2012, at 3:49 PM, James Babiak wrote: > >> Very weird... >> >> Since it seems like my configuration is kosher, I started looking into >> possible networking/system problems which might be causing this. I tried >> pinging talk.google.com, and low and behold I see that the traffic is going >> across my ipv6 tunnel with he.net. I assumed this might be the source of the >> issue, so I disabled the tunnel and tried again. I confirmed that >> talk.google.com was resolving to an ipv4 address, and that I could ping it >> and connect to port 5222, and tried again. Still having the problem. I did a >> packet capture on the traffic and confirmed two-way communication. I'm >> seeing the following: >> >> (Omitting irrelevant ACKs) >> SYN, SYN/ACK, ACK Handsake >> 4 0.041189 71.180.124.168 74.125.157.125 Jabber/XML >> Request:<?xml version='1.0'?><stream:stream >> xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' >> to='gmail.com' version='1.0'> >> 6 0.082673 74.125.157.125 71.180.124.168 Jabber/XML >> Response:<stream:stream from="gmail.com" id="BBB9884723EE981C" version="1.0" >> xmlns:stream="http://etherx.jabber.org/streams"; xmlns="jabber:client"> >> 8 0.082711 74.125.157.125 71.180.124.168 Jabber/XML >> Response:<stream:features><starttls >> xmlns="urn:ietf:params:xml:ns:xmpp-tls"><required/></starttls><mechanisms >> xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>X-GOOGLE-TOKEN</mechanism><mechanism>X-OAUTH2</mechanism></mechanisms></stream:features> >> 10 0.082872 71.180.124.168 74.125.157.125 Jabber/XML >> Request:<starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/> >> 11 0.123579 74.125.157.125 71.180.124.168 Jabber/XML >> Response:<proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/> >> 13 4.084386 71.180.124.168 74.125.157.125 Jabber/XML Request: >> \200\211\001\003\001\000`\000\000\000 >> \000\0009\000\0008\000\0005\000\000\210\000\000\207\000\000\204\000\000\026\000\000\023\000\000 >> 14 4.084660 71.180.124.168 74.125.157.125 Jabber/XML Request: >> \200\211\001\003\001\000`\000\000\000 >> \000\0009\000\0008\000\0005\000\000\210\000\000\207\000\000\204\000\000\026\000\000\023\000\000 >> 15 4.084850 71.180.124.168 74.125.157.125 Jabber/XML Request: >> \204\000\000\026\000\000\023\000\000 >> 16 4.126101 74.125.157.125 71.180.124.168 TCP xmpp-client> >> 43773 [ACK] Seq=430 Ack=1744 Win=19200 Len=0 TSV=165017604 TSER=14984656 >> 17 4.126252 71.180.124.168 74.125.157.125 Jabber/XML Request: >> \000\000A\003\000\200\000\000\005\000\000\004\001\000\200\000\000\025\000\000\022\000\000\t\006\000@\000\000\024\000\000\021\000\000\b\000\000\006\004\000\200\000\000\003\002\000\200\000\000\377\336\252*\217a\322\177f\035@)\215\0314L\303\023\230\341 >> 18 4.131094 74.125.157.125 71.180.124.168 TCP xmpp-client> >> 43773 [FIN, ACK] Seq=430 Ack=3162 Win=22016 Len=0 TSV=165017608 TSER=14984656 >> 19 4.131200 71.180.124.168 74.125.157.125 Jabber/XML Request: >> \211\001\003\001\000`\000\000\000 >> \000\0009\000\0008\000\0005\000\000\210\000\000\207\000\000\204\000\000\026\000\000\023\000\000 >> 20 4.168569 74.125.157.125 71.180.124.168 TCP xmpp-client> >> 43773 [RST] Seq=430 Win=0 Len=0 >> 21 4.171068 74.125.157.125 71.180.124.168 TCP xmpp-client> >> 43773 [RST] Seq=430 Win=0 Len=0 >> 22 4.171097 74.125.157.125 71.180.124.168 TCP xmpp-client> >> 43773 [RST] Seq=430 Win=0 Len=0 >> 23 4.173563 74.125.157.125 71.180.124.168 TCP xmpp-client> >> 43773 [RST] Seq=431 Win=0 Len=0 >> 24 4.176065 74.125.157.125 71.180.124.168 TCP xmpp-client> >> 43773 [RST] Seq=431 Win=0 Len=0 >> >> I've never really messed around with jabber, so I'm not sure if the output >> above looks normal or not. It seems like it begins the authentication >> negotiation, begins TLS, sends a bunch of Jabber requests, but then gets a >> FIN back followed by a bunch of RSTs. >> >> It's at this point that the Jabber module basically begins to freak out and >> loop. No more communication continues on after this point, unless I restart >> Asterisk. >> >> So, it seems like my configuration is good and the network connectivity is >> good. Since I'm running the standard Astlinux 1.0.1 build of Jabber (which >> others have no problem with), I have to believe it's not a module/Asterisk >> related issue. Any ideas? >> >> -James >> >> On 01/15/2012 04:12 PM, Michael Keuter wrote: >>> Am 15.01.2012 um 19:11 schrieb James Babiak: >>> >>> >>>> I just upgraded to 1.0.1 and decided to play with GoogleTalk integration. >>>> I've followed various guides online, but am unable to get jabber connected >>>> to google. In fact, I get caught in some kind of loop which almost crashes >>>> my system. As soon as jabber loads, I get flooded with this: >>>> >>>> JABBER: gtalk_account INCOMING:<proceed >>>> xmlns="urn:ietf:params:xml:ns:xmpp-tls"/> >>>> JABBER: gtalk_account INCOMING:<procee >>>> JABBER: gtalk_account INCOMING:<procee >>>> JABBER: gtalk_account INCOMING:<procee >>>> <and so on ad infinitum> >>>> >>>> Originally I thought it was because I was using a non-standard domain >>>> which I have with Google (ie: not gmail.com) so I changed it to my >>>> gmail.com address. Still didn't work, so I thought it was because I had a >>>> password/secret with special characters. So I changed it to strictly >>>> alpha-numeric. Same problem. I copied and pasted the configuration from >>>> two different websites in case I was mistyping something, but alas, >>>> problem persists. >>>> >>>> Here is my jabber.conf config: >>>> [general] >>>> debug=no ;;Turn on debugging by default. >>>> autoprune=no ;;Auto remove users from buddy >>>> list. >>>> autoregister=no ;;Auto register users from buddy >>>> list. >>>> >>>> [gtalk_account] >>>> type=client >>>> serverhost=talk.google.com >>>> >>>> [email protected]/Talk >>>> >>>> secret=XXXXX >>>> port=5222 >>>> usetls=yes >>>> usesasl=yes >>>> statusmessage="This is an Asterisk server" >>>> timeout=100 >>>> >>>> I've tried it with and without the /Talk option in the username field. >>>> >>>> If debugging is turned on, the console is flooded to the point of being >>>> completely unusable, and it will fill up all the messages files in a >>>> couple of seconds. If I turn off debugging, I can still use the console, >>>> but the load level is still through the roof. Also, running jabber show >>>> connected returns the account, but shows Disconnected. >>>> >>>> Any ideas? >>>> >>>> Thanks. >>>> >>>> -James >>>> >>> The same settings you have (except statusmessage) do work for me. >>> I have commented the setting in the [general] section. All in gtalk.conf >>> and jingle.conf is commented out. >>> >>> Michael >>> >>> >>> http://www.mksolutions.info >>> >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> RSA(R) Conference 2012 >>> Mar 27 - Feb 2 >>> Save $400 by Jan. 27 >>> Register now! >>> >>> http://p.sf.net/sfu/rsa-sfdev2dev2 >>> >>> _______________________________________________ >>> Astlinux-users mailing list >>> >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/astlinux-users >>> >>> >>> Donations to support AstLinux are graciously accepted via PayPal to >>> [email protected] >>> . >>> >> ------------------------------------------------------------------------------ >> RSA(R) Conference 2012 >> Mar 27 - Feb 2 >> Save $400 by Jan. 27 >> Register now! >> http://p.sf.net/sfu/rsa-sfdev2dev2_______________________________________________ >> Astlinux-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to >> [email protected]. > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Mar 27 - Feb 2 > Save $400 by Jan. 27 > Register now! > http://p.sf.net/sfu/rsa-sfdev2dev2 > _______________________________________________ > Astlinux-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > [email protected]. ------------------------------------------------------------------------------ RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [email protected].
