Based on the description at http://code.google.com/p/wave-protocol/wiki/Federation and the draft-ietf-xmpp-3920bis the address returned by dig +short -t SRV _xmpp-server._tcp.cordys.co.in should point to the server that has XMPP running on it.
In your case, cordys.co.in and wave.cordys.co.in are the same so it shouldn't matter. For an contrast, check out dig +short -t SRV _xmpp-server._tcp.wave.wavesandbox.com This returns several different SRV records, none of which point to the wavesandbox.com domain. I've tried connecting again, but I'm still getting a severe error that wave is not running on cordys.co.in At this point, I wonder about your XMPP server. Which XMPP server are you running? Is it supporting discovery? Does it recognize your wave server as a component session? I'm establishing XMPP connects but not getting any further. Aldon -----Original Message----- From: [email protected] [mailto:[email protected]]on Behalf Of Sathish Sent: Tuesday, December 22, 2009 7:25 PM To: Wave Protocol Subject: Re: Wave server Federation. Validation FAILED from: wave.wavesandbox.com Hoi Aldon, I got an information at http://groups.google.com/group/wave-protocol/browse_thread/thread/30e02612c7 f3503f#. But this is conflicting with the information you provided. The developer says, the output should be like, _xmpp-server._tcp.edalan.com 10 0 5269 edalan.com _xmpp-server._tcp.wave.edalan.com 10 0 5269 edalan.com I have configured the other way, both these return wave.cordys.co.in. Can you confirm the output at your server ? Meanwhile, i would try with this settings again. Regards Sathish On Dec 23, 5:12 am, Sathish <[email protected]> wrote: > Hi Aldon, > > Thanks for the info. > I got the configuration done and i see messages exchanged between > wavesandbox.com and my domain, in the wave server console. > > Still there are no waves getting displayed in the clients. Am checking > this forum for any help in this regard. > Will revert if i face any issues. > > Regards > Sathish > > On Dec 21, 5:48 pm, "Aldon Hynes" <[email protected]> > wrote: > > > Satish, > > > I've tried connecting and notice a couple things. > > > First, > > > > dig +short -t SRV _xmpp-server._tcp.cordys.co.in > > returns > > > 10 0 5269 . > > > It really should be returning > > > > 10 0 5269 wave.cordys.co.in. > > > I'm not sure if this is part of the problem, but I'm still getting errors > > when I try to connect. > > > I also went into Pidgin, where I can type XMPP commands directly into an > > XMPP console. I attempted sending XMPP commands directly from there, and > > also had no success. > > > This lead me to check my XMPP log, where I discovered that my XMPP server > > is closing XMPP connections with your XMPP server with the error message: > > Closing session due to incorrect hostname in stread header. Host: > > cordys.co.in. By the looks of this, however, it may be that it is because > > of the incorrect SRV record described above, and it is trying to connect to > > my host (as . ) instead of your host ( as wave.cordys.co.in. ) > > > Aldon > > > -----Original Message----- > > From: [email protected] > > > [mailto:[email protected]]on Behalf Of Sathish > > Sent: Monday, December 21, 2009 5:35 AM > > To: Wave Protocol > > Subject: Re: Wave server Federation. Validation FAILED from: > > wave.wavesandbox.com > > > Hi Joe, > > > Please discard the previous message. > > > I got a A record configured for my main domain cordys.co.in. > > Still the log remains same. Can you try pinging the server from your > > end? > > > Regards > > Sathish > > > On Dec 10, 11:36 pm, Joe Gregorio <[email protected]> wrote: > > > You appear to have an A record for the wave subdomain, but do not appear > > > to have an A record for the domain itself: > > > > $ dig +short -t A cordys.co.in > > > ~ > > > $ dig +short -t A wave.cordys.co.in > > > 210.210.79.29 > > > ~ > > > > The first lookup needs to resolve because that is what you > > > are pointing your SRV records at: > > > > $ dig +short -t SRV _xmpp-server._tcp.cordys.co.in > > > 10 0 5269 cordys.co.in. > > > ~ > > > $ dig +short -t SRV _xmpp-server._tcp.wave.cordys.co.in > > > 10 0 5269 cordys.co.in. > > > ~ > > > > Thanks, > > > -joe > > > > -- > > > Joe Gregorio > > > Developer Advocate, Google Wave > > > > On Thu, Dec 10, 2009 at 10:19 AM, Sathish <[email protected]> wrote: > > > > Hi > > > > > I am trying to configure a wave server in my custom domain. > > > > Ubuntu + openfire and the server is behind a firewall with port 5269 > > > > open. > > > > > I get the following error when I start the server. > > > > > INFO: Couldn't find wave on wavesandbox.com > > > > wavesandbox.com does not appear to have wave > > > > > I see the following error in Openfire logs.Can anyone help me solving > > > > the Validation FAILED error? > > > > -------------------------------------------------------------------------- > > - ------------------------------------------------------------------------ -- > > - --------------------------------------------------------- > > > > > 2009.12.10 20:27:59 LocalOutgoingServerSession: OS - Trying to connect > > > > to wave.wavesandbox.com:5269(DNS lookup: xmpp-server3.l.google.com: > > > > 5268) > > > > 2009.12.10 20:28:00 LocalOutgoingServerSession: OS - Plain connection > > > > to wave.wavesandbox.com:5269 successful > > > > 2009.12.10 20:28:00 LocalOutgoingServerSession: OS - About to try > > > > connecting using server dialback XMPP 1.0 with: wave.wavesandbox.com > > > > 2009.12.10 20:28:00 ServerDialback: OS - Sent dialback key to host: > > > > wave.wavesandbox.com id: 2084659B1794C314 from domain: > > > > wave.cordys.co.in > > > > 2009.12.10 20:28:01 ServerDialback: OS - Validation FAILED from: > > > > wave.wavesandbox.com id: 2084659B1794C314 for domain: > > > > wave.cordys.co.in > > > > 2009.12.10 20:28:01 LocalOutgoingServerSession: OS - Error, SERVER > > > > DIALBACK with wave.wavesandbox.com failed > > > > 2009.12.10 20:28:01 LocalOutgoingServerSession: OS - Going to try > > > > connecting using server dialback with: wave.wavesandbox.com > > > > 2009.12.10 20:28:02 ServerDialback: OS - Trying to connect to > > > > wave.wavesandbox.com:5269(DNS lookup: xmpp-server3.l.google.com:5268) > > > > 2009.12.10 20:28:02 ServerDialback: OS - Connection to > > > > wave.wavesandbox.com:5269 successful > > > > 2009.12.10 20:28:02 ServerDialback: OS - Sent dialback key to host: > > > > wave.wavesandbox.com id: A1B60DEABEE1C081 from domain: > > > > wave.cordys.co.in > > > > 2009.12.10 20:28:04 ServerDialback: OS - Validation FAILED from: > > > > wave.wavesandbox.com id: A1B60DEABEE1C081 for domain: > > > > wave.cordys.co.in > > > > 2009.12.10 20:28:04 LocalOutgoingServerSession: OS - Trying to connect > > > > to wavesandbox.com:5269(DNS lookup: wavesandbox.com:5269) > > > > 2009.12.10 20:30:04 OutgoingSessionPromise: Error sending packet to > > > > remote server: > > > > <iq type="get" id="2882-1" to="wave.wavesandbox.com" > > > > from="wave.cordys.co.in"> > > > > <query xmlns="http://jabber.org/protocol/disco#info"/> > > > > </iq> > > > > java.lang.Exception: Failed to create connection to remote server > > > > at org.jivesoftware.openfire.server.OutgoingSessionPromise > > > > $PacketsProcessor.sendPacket(OutgoingSessionPromise.java:252) > > > > at org.jivesoftware.openfire.server.OutgoingSessionPromise > > > > $PacketsProcessor.run(OutgoingSessionPromise.java:216) > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask > > > > (ThreadPoolExecutor.java:886) > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run > > > > (ThreadPoolExecutor.java:908) > > > > at java.lang.Thread.run(Thread.java:619) > > > > -------------------------------------------------------------------------- > > - ------------------------------------------------------------------------ -- > > - --------------------------------------------------------- > > > > > Sathish > > > > > -- > > > > > You received this message because you are subscribed to the Google > > Groups "Wave Protocol" group. > > > > To post to this group, send email to [email protected]. > > > > To unsubscribe from this group, send email to > > [email protected]. > > > > For more options, visit this group > > athttp://groups.google.com/group/wave-protocol?hl=en. > > > -- > > > You received this message because you are subscribed to the Google Groups > > "Wave Protocol" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group athttp://groups.google.com/group/wave-protocol?hl=en. -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en. -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
