ejabberd - Comments for "Google Talk and ejabberd" https://www.ejabberd.im/google-talk en Can you please tell me, how https://www.ejabberd.im/google-talk#comment-65051 <p>Can you please tell <noindex><a href="http://www.geekscab.com" rel="nofollow" >me</a></noindex>, how to open port no 5269, I think my firewall is blocked that port, Any way by which i can open that port manually?</p> Sat, 04 Oct 2014 23:58:27 +0000 cybersniffer comment 65051 at https://www.ejabberd.im By default unencrypted S2S is enabled https://www.ejabberd.im/google-talk#comment-53281 <div class="quote-msg"> <div class="quote-author"><em>jocelyncloutier</em> wrote:</div> <p>Server to server communication is NOT enabled when using the default ejabberd 2.0.1 configuration.<br /> You need to turn it on to be able to have Google Talk (or any XMPP server) to connect to your server.</p> <p>The following congif parameter should be set to appropriate value:<br /> {s2s_use_starttls, true}.<br /> {s2s_certfile, "/ejabberd-2.0.1/conf/server.pem"}.<br /> {s2s_default_policy, allow}.</p></div> <p>The default configuration in ejabberd 2.0.1 has S2S enabled. But STARTTLS encryption is disabled, because the certfile may or may not exist.</p> <p>So, when ejabberd is just installed and the default config file is not modified, ejabberd behaves as if you configured this:</p> <pre>{s2s_use_starttls, false}. {s2s_certfile, "/path/to/ssl.pem"}. {s2s_default_policy, allow}.</pre><p> This is enough to connect to many Jabber servers, but some Jabber servers require STARTTLS. If you have a certfile, it's obviously better to enable STARTTLS as explained by jocelyncloutier.</p> Mon, 09 Jun 2008 16:26:55 +0000 mfoss comment 53281 at https://www.ejabberd.im Extra steps: Google Talk and ejabberd 2.0.1 https://www.ejabberd.im/google-talk#comment-53271 <p>Extra step #1<br /> Server to server communication is NOT enabled when using the default ejabberd 2.0.1 configuration.<br /> You need to turn it on to be able to have Google Talk (or any XMPP server) to connect to your server.</p> <p>The following congif parameter should be set to appropriate value:<br /> {s2s_use_starttls, true}.<br /> {s2s_certfile, "/ejabberd-2.0.1/conf/server.pem"}.<br /> {s2s_default_policy, allow}.</p> <p>In that case, any server will be able to talk to your server. Read guide for other configuration parameters to limit access to your server.</p> <p>Extra step #2 (if behind a firewall)<br /> If your server is behind a firewall (like ours), then make sure that the s2s ejabberd port is open (5269 is default port).<br /> Note: you may have to open other ports if you are not using ejabberd default port numbers.</p> <p>Jocelyn</p> Sun, 08 Jun 2008 17:07:38 +0000 jocelyncloutier comment 53271 at https://www.ejabberd.im Don't forget what you need to do to your DNS https://www.ejabberd.im/google-talk#comment-51488 <p>You also must add a SRV record to your DNS for your chat server's FQDN (Fully Qualified Domain Name)</p> Fri, 21 Dec 2007 00:05:36 +0000 yohnson comment 51488 at https://www.ejabberd.im Another GTalk<>ejabberd issue https://www.ejabberd.im/google-talk#comment-50936 <p>There is also another GTalk&lt;&gt;ejabberd problem besides the DNS SRV issue. Have a look at <noindex><a href="http://thread.gmane.org/gmane.network.jabber.devel/29105" title="http://thread.gmane.org/gmane.network.jabber.devel/29105" rel="nofollow" >http://thread.gmane.org/gmane.network.jabber.devel/29105</a></noindex> for the description of the problem. It seems to be a problem in the GTalk implementation.</p> Sun, 23 Sep 2007 18:33:25 +0000 gst comment 50936 at https://www.ejabberd.im