[jdev] Recent Google Talk S2S Problems

Wed, 08 Mar 2006 16:08:12 -0800

Also, what's up with this? This is from my jabberd2 logs:

Wed Mar  8 16:00:44 2006 [notice] [9] [64.233.167.125, port=5269] outgoing connection
Wed Mar  8 16:00:45 2006 [notice] [9] [64.233.167.125, port=5269] sending dialback auth request for route 'deepdarc.com/gmail.com'
Wed Mar  8 16:01:05 2006 [notice] [9] [64.233.167.125, port=5269] disconnect
Wed Mar  8 16:01:08 2006 [notice] [9] [64.233.166.129, port=59886] incoming connection
Wed Mar  8 16:01:08 2006 [notice] [9] [64.233.166.129, port=59886] incoming stream online (id fb0bnheig2ryer70iwdedyckh4frmikofo3si2ow)
Wed Mar  8 16:01:08 2006 [notice] [9] [64.233.166.129, port=59886] received dialback auth request for route 'deepdarc.com/gmail.com'
Wed Mar  8 16:01:08 2006 [notice] [10] [64.233.167.125, port=5269] outgoing connection
Wed Mar  8 16:01:08 2006 [notice] [10] [64.233.167.125, port=5269] sending dialback auth request for route 'deepdarc.com/gmail.com'
Wed Mar  8 16:01:08 2006 [notice] [9] [64.233.166.129, port=59886] checking dialback verification from gmail.com: sending valid
Wed Mar  8 16:01:08 2006 [notice] [10] [64.233.167.125, port=5269] outgoing route 'deepdarc.com/gmail.com' is now valid
Wed Mar  8 16:01:09 2006 [notice] [9] [64.233.166.129, port=59886] incoming route 'deepdarc.com/gmail.com' is now valid

I got this after trying to send a message who was a gmail contact. The first packet bounced. Notice that when trying to execute a dialback auth request, it apparently fails... but then all of the sudden gmail.com decides send my server some packets, and both an incoming and outgoing route are negotiated with no problems. Whaaa?

Is this a problem with gmail or a problem with my server?

On Mar 8, 2006, at 3:22 PM, Robert B Quattlebaum, Jr. wrote:

Is it just me or has it suddenly gotten much more difficult to chat with someone who is using a non-gtalk client on google talk? (That is, from outside the google network)

My friend who is using trillian says that the trillian log is complaining that <cli:message ...> isn't a valid top level stanza and drops it. Looks like a namespace issue of some sorts? Pandion doesn't seem to work too well either...

Anyone else have any ideas?

__________________
Robert Quattlebaum
Mobile: +1(650) 223-4974

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to