Hi Joe,

Thanks for your effort. Found out that the problem lies with the
domain name configuration on my Openfire xmpp server. When I first
installed it I haven't yet got a dedicated domain name so I've used a
host name instead! I reinstalled Openfire (from scratch) to get it
sorted, and now I can federate with wavesandbox! All the hard
work... :)

cheers,

Chiang

On Jan 17, 3:48 am, Joe Gregorio <[email protected]> wrote:
> On Sat, Jan 16, 2010 at 6:43 PM, chiang <[email protected]> wrote:
> > Hi Joe,
>
> > The domain name I'm using is wavybox.co.uk.
>
> > By doing dig +short -t SRV _xmpp-server._tcp.wavybox.co.uk, whether
> > locally or from another machine outside the LAN, I get the answer of:
> > 10 0 5269 wavybox.co.uk
>
> > Does it matter if the SRV records point to wavybox.co.uk or
> > wave.wavybox.co.uk, if both these addresses point to the same machine?
>
> No, it doesn't matter, as long as the domain name the SRV records
> point to exist. From my box I can look up your SRV and A records
> and everything looks fine. When I telnet to the designated port I also
> seem to be talking to an XMPP server, so it looks like things
> are configured OK on that end.
>
> What happens when you run check-certificates.sh ?
>
> One way that is easier to test your server setup is to set
>
>   XMPP_SERVER_PING=wavesandbox.com
>
> in run-config.sh. That will tell FedOne to ping wavesandbox on
> startup. You will note that on startup you will get about a one
> minute delay before wavesandbox.com responds to the ping, so
> you have to be patient.
>
>    Thanks,
>    -joe
>
> > Because from the Google Wave wiki I was told to use example.com. But
> > when I did a dig on someone else's wave server, the SRV records point
> > to wave.example.com. What difference does it make?
>
> > I also wonder if the hostname for my wave server needs to be named as
> > "wave"?
>
> > cheers,
>
> > Chiang
>
> > On Jan 15, 6:59 pm, Joe Gregorio <[email protected]> wrote:
> >> Chaing,
>
> >> What domain name are you using for your wave provider?
>
> >> What do you see when you run
>
> >> $  dig +short -t SRV _xmpp-server._tcp.example.com
>
> >> but substituting your domain name for 'example.com'?
>
> >>   Thanks,
> >>   -joe
>
> >> --
> >> Joe Gregorio
> >> Developer Relations, Google Wave
>
> >> On Fri, Jan 15, 2010 at 10:13 AM, chiang <[email protected]> wrote:
> >> > Hi I'm having problem with federation as well. My wave/XMPP server
> >> > (with private IP address) is behind my NAT/gateway. I think my
> >> > firewall and port forwarding have been set up correctly, as I can see
> >> > XMPP messages exchange between my wave server with another external
> >> > wave server, using port 5269. However I can't tell if it is federating
> >> > properly...
>
> >> > When I try to federate with wavesandbox.com, by adding a wavesandbox
> >> > user (i.e. myself), I can see XMPP messages sent to wavesandbox.com,
> >> > but nothing comes back. This I yet to figure how why. And I did see
> >> > that I get no response from the DNS when trying to resolve _xmpp-
> >> > server._tcp.wavesandbox.com, which is what I expected, but don't
> >> > understand why my waveserver doesn't then try wave.wavesandbox.com
> >> > instead.
>
> >> > If anyone can shed some light on what I might have done wrong I'd very
> >> > much appreciate your assistance.
>
> >> > cheers,
>
> >> > Chiang
>
> >> > On Jan 9, 12:29 am, Joe Gregorio <[email protected]> wrote:
> >> >> Have you tried searching in your sandbox inbox for some text that
> >> >> appears in that wave?
>
> >> >> I just created a wave on bitworking.net and successfully added
> >> >> [email protected]
> >> >> and [email protected] to it on my local client and it showed
> >> >> up in the Wave client.
> >> >> Are you able to see that wave?
>
> >> >>   Thanks,
> >> >>   -joe
>
> >> >> --
> >> >> Joe Gregorio
> >> >> Developer Advocate, Google Wave
>
> >> >> On Fri, Jan 8, 2010 at 5:04 PM, Rob <[email protected]> wrote:
>
> >> >> >    I believe I have my server federating properly since I see what
> >> >> > appear to be successful transmission of blips reported from the server
> >> >> > log.  But when I use the console to add "[email protected]", I
> >> >> > don't get the wave in my inbox.  And when I add
> >> >> > "[email protected]" to a sandbox wave, I don't see a new wave show
> >> >> > up in the console.
>
> >> >> >    Some other folk have reported this and pointed to the Federation
> >> >> > page (http://code.google.com/p/wave-protocol/wiki/Federation)
> >> >> > indicating that it clarified something, but if it has some comment on
> >> >> > this issue, I couldn't discern it.
>
> >> >> >    Thanks for your help,
> >> >> >    -Rob Corell
>
> >> >> > --
> >> >> > 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 
> > 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.


Reply via email to