Hi Alok You've probably made my day! I hope this will resolve my issue. I've tried updating my SRV records, but for some reason they're not propagating, so as soon as they work I'll update you on the success (or not).
Cheers Benjamin On Fri, Dec 11, 2009 at 7:54 AM, Alok Jha <[email protected]> wrote: > Sorry i have put the wrong information before. The new DNS record is looking > as below > > So i have now changed the DNS entry as below and this solved the issue. > _xmpp-server._tcp.edalan.com > 10 0 5269 edalan.com > _xmpp-server._tcp.wave.edalan.com > 10 0 5269 edalan.com > > > > On Fri, Dec 11, 2009 at 1:23 PM, Alok Jha <[email protected]> wrote: >> >> Hey, >> >> Finally i am done and can see my wave on Wavesandbox account. >> >> It was small mistake or lack of knowledge from my end. >> >> I have setup my Openfire with domain as "edalan.com" and i was having its >> A record pointing to my external IP address >> >> Previous DNS Entry (not working) >> _xmpp-server._tcp.edalan.com >> 10 0 5269 wave.edalan.com >> >> _xmpp-server._tcp.wave.edalan.com >> 10 0 5269 wave.edalan.com >> >> So in my opinion this was creating the confusion for openfire server >> because the incoming Wavesandbox request was coming on wave.edalan.com port >> 5269 but Openfire is configured to accept incoming connection on port >> edalan.com port 5269. >> >> So i have now changed the DNS entry as below and this solved the issue. >> _xmpp-server._tcp.edalan.com >> 10 0 5269 edalan.com >> _xmpp-server._tcp.wave.edalan.com >> 10 0 5269 wave.edalan.com >> >> >> I can see Benjamin your SRV entry is entered as >> >> _xmpp-server._tcp.wave.1011ltd.com >> 10 0 5269 wave.1011ltd.com >> >> So try to change the entry in your DNS server with 10 0 5269 1011ltd.com >> hope this might solve your issue as well. >> >> Cheers, >> Alok >> >> >> On Sun, Dec 6, 2009 at 12:21 AM, Alok Jha <[email protected]> wrote: >>> >>> Hi Benjamin, >>> >>> I can see on the Openfire debug logs that all the packets are being >>> acknowledged by Wavesandbox sending the receipt back, but not sure as to >>> what is stopping at Sandbox end to display it on the client. >>> I am doing my all the research i could to make things working and will >>> share if finds anything interesting. >>> >>> Cheers, >>> Alok >>> >>> Not sure if i am correct but it seems that there is some issue with the >>> Wavesandbox server itself as i was reading some another blog in which even >>> the active federation has stopped working. I can see on the Openfire debug >>> log that all the >>> >>> On Fri, Dec 4, 2009 at 8:31 PM, Benjamin Nortier <[email protected]> >>> wrote: >>>> >>>> Hi Alok >>>> >>>> Unfortunately I'm seeing the same situation. I have a similar setup >>>> (Ubuntu 8.04.3 LTS, Openfire). >>>> >>>> I've attached my log as well (starting server, creating new wave, >>>> adding sandbox participant, saying 'hello?') >>>> >>>> I also receive a >>>> >>>> <message id="1492-8" from="wave.wavesandbox.com" to="wave.1011ltd.com"> >>>> <received xmlns="urn:xmpp:receipts"/> >>>> </message> >>>> >>>> message which should indicate a successful receive according to the >>>> draft protocol >>>> (http://www.waveprotocol.org/draft-protocol-specs/draft-protocol-spec#wavelet-ops). >>>> >>>> >>>> On Fri, Dec 4, 2009 at 7:39 AM, Alok Jha <[email protected]> wrote: >>>> > Hi All, >>>> > I have implemented the federation server using Openfire XMPP on Ubuntu >>>> > 9.10 >>>> > using the StartSSL certificates for my domain but i am struggling to >>>> > see >>>> > the basic federation of FedOne client with my Wavesandbox id. >>>> > I have ensured that XMPP SRV entries are in place for server to server >>>> > federation. I have attached the screen log from run-server.sh command >>>> > to >>>> > review. >>>> > If anyone has faced the similar issue and he was successful in getting >>>> > it >>>> > corrected then please let me know. >>>> > Thanks, >>>> > Alok >>>> > >>>> > >>>> > >>>> > >>>> > -- >>>> > >>>> > 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. >>>> > >>>> >>>> >>>> >>>> -- >>>> Benjamin Nortier >>>> e: [email protected] >>>> c: +44 (0)778 946 1959 >>>> gtalk: [email protected] >>>> >>>> -- >>>> >>>> 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. > -- Benjamin Nortier e: [email protected] c: +44 (0)778 946 1959 gtalk: [email protected] -- 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.
