This Question is Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (5 pts)
1,818 Views 1 Replies Last post: Jun 30, 2009 12:31 AM by jazzlover RSS
jazzlover Bronze 4 posts since
Jun 29, 2009
Currently Being Moderated

Jun 29, 2009 9:30 AM

s2s setup: need help

Hello,

Can someone help me with s2s conference configuration?

I have two servers in different domains:
server.a.com (10.1.1.1/24) and server.b.com (10.1.2.1/24)

Every server has a jabber service (Openfire) started on secondary
interface:
jabber.a.com (10.1.1.2/24) and jabber.b.com (10.1.2.2/24)
respectively.

Messages between these servers are going successfully
(user1@jabber.a.com is able to send/get messages from
user2@jabber.b.com).

I  got  stuck  with  enabling  chatrooms at jabber.b.com to be seen at
jabber.a.com.  When  I  run  service  discovery  for  jabber.b.com  in
user1@jabber.a.com clinet, I got following in the servers logs:
1. jabber.a.com
2009.06.29 20:14:02 LocalOutgoingServerSession: OS - Trying to connect to jabber.b.com:5269(DNS lookup: jabber.b.com:5269)
2009.06.29 20:14:02 LocalOutgoingServerSession: OS - Plain connection to jabber.b.com:5269 successful
2009.06.29 20:14:02 LocalOutgoingServerSession: OS - Indicating we want TLS to jabber.b.com
2009.06.29 20:14:02 LocalOutgoingServerSession: OS - Negotiating TLS with jabber.b.com
2009.06.29 20:14:02 LocalOutgoingServerSession: OS - TLS negotiation with jabber.b.com was successful
2009.06.29 20:14:02 LocalOutgoingServerSession: OS - About to try connecting using server dialback over TLS with: jabber.b.com
2009.06.29 20:14:02 ServerDialback: OS - Sent dialback key to host: jabber.b.com id: 675ea686 from domain: jabber.a.com
2009.06.29 20:14:07 Connect Socket[addr=/10.1.2.2,port=39377,localport=5269]
2009.06.29 20:14:07 ServerDialback: AS - Verifying key for host: jabber.b.com id: 675ea686
2009.06.29 20:14:07 ServerDialback: AS - Key was: VALID for host: jabber.b.com id: 675ea686
2009.06.29 20:14:07 ServerDialback: AS - Connection closed for host: jabber.b.com id: 675ea686
2009.06.29 20:14:07 Connection closed before session established
Socket[addr=/10.1.2.2,port=39377,localport=5269]
2009.06.29 20:14:07 ServerDialback: OS - Validation GRANTED from: jabber.b.com id: 675ea686 for domain: jabber.a.com
2009.06.29 20:14:07 LocalOutgoingServerSession: OS - SERVER DIALBACK OVER TLS with jabber.b.com was successful
2009.06.29 20:14:08 Connect Socket[addr=/10.1.2.2,port=39378,localport=5269]
2009.06.29 20:14:08 ServerDialback: RS - Received dialback key from host: jabber.b.com to: jabber.a.com
2009.06.29 20:14:08 ServerDialback: RS - Trying to connect to Authoritative Server: jabber.b.com:5269(DNS lookup: jabber.b.com:5269)
2009.06.29 20:14:08 ServerDialback: RS - Connection to AS: jabber.b.com:5269 successful
2009.06.29 20:14:08 ServerDialback: RS - Asking AS to verify dialback key for idd36a3328
2009.06.29 20:14:08 ServerDialback: RS - Key was VERIFIED by the Authoritative Server for: jabber.b.com
2009.06.29 20:14:08 ServerDialback: RS - Closing connection to Authoritative Server: jabber.b.com
2009.06.29 20:14:08 ServerDialback: RS - Sending key verification result to OS: jabber.b.com
2009.06.29 20:14:08 LocalOutgoingServerSession: OS - Trying to connect to pubsub.jabber.b.com:5269(DNS lookup: pubsub.jabber.b.com:5269)
2009.06.29 20:14:08 LocalOutgoingServerSession: OS - Trying to connect to conference.jabber.b.com:5269(DNS lookup: conference.jabber.b.com:5269)
2009.06.29 20:14:08 LocalOutgoingServerSession: OS - Trying to connect to search.jabber.b.com:5269(DNS lookup: search.jabber.b.com:5269)
2009.06.29 20:14:08 ServerDialback: RS - Received dialback key from host: conference.jabber.b.com to: jabber.a.com
2009.06.29 20:14:08 ServerDialback: RS - Trying to connect to Authoritative Server: conference.jabber.b.com:5269(DNS lookup: conference.jabber.b.com:5269)
2009.06.29 20:14:08 Logging off jabber.b.com on org.jivesoftware.openfire.net.SocketConnection@2f71e2 socket: Socket[addr=/10.1.2.2,port=39378,localport=5269] session: org.jivesoftware.openfire.session.LocalIncomingServerSession@1c84885 status: -1 address: jabber.b.com id: d36a3328

2. jabber.b.com
2009.06.29 20:14:02 Connect Socket[addr=/10.1.1.2,port=56215,localport=5269]
2009.06.29 20:14:02 ServerDialback: RS - Received dialback key from host: jabber.a.com to: jabber.b.com
2009.06.29 20:14:02 ServerDialback: RS - Trying to connect to Authoritative Server: jabber.a.com:5269(DNS lookup: jabber.a.com:5269)
2009.06.29 20:14:07 ServerDialback: RS - Connection to AS: jabber.a.com:5269 successful
2009.06.29 20:14:07 ServerDialback: RS - Asking AS to verify dialback key for id675ea686
2009.06.29 20:14:07 ServerDialback: RS - Key was VERIFIED by the Authoritative Server for: jabber.a.com
2009.06.29 20:14:07 ServerDialback: RS - Closing connection to Authoritative Server: jabber.a.com
2009.06.29 20:14:07 ServerDialback: RS - Sending key verification result to OS: jabber.a.com
2009.06.29 20:14:08 LocalOutgoingServerSession: OS - Trying to connect to jabber.a.com:5269(DNS lookup: jabber.a.com:5269)
2009.06.29 20:14:08 LocalOutgoingServerSession: OS - Plain connection to jabber.a.com:5269 successful
2009.06.29 20:14:08 LocalOutgoingServerSession: OS - Indicating we want TLS to jabber.a.com
2009.06.29 20:14:08 LocalOutgoingServerSession: OS - Negotiating TLS with jabber.a.com
2009.06.29 20:14:08 LocalOutgoingServerSession: OS - TLS negotiation with jabber.a.com was successful
2009.06.29 20:14:08 LocalOutgoingServerSession: OS - Stream compression not supoprted by jabber.a.com
2009.06.29 20:14:08 LocalOutgoingServerSession: OS - About to try connecting using server dialback over TLS with: jabber.a.com
2009.06.29 20:14:08 ServerDialback: OS - Sent dialback key to host: jabber.a.com id: d36a3328 from domain: jabber.b.com
2009.06.29 20:14:08 Connect Socket[addr=/10.1.1.2,port=56357,localport=5269]
2009.06.29 20:14:08 ServerDialback: AS - Verifying key for host: jabber.a.com id: d36a3328
2009.06.29 20:14:08 ServerDialback: AS - Key was: VALID for host: jabber.a.com id: d36a3328
2009.06.29 20:14:08 ServerDialback: AS - Connection closed for host: jabber.a.com id: d36a3328
2009.06.29 20:14:08 Connection closed before session established
Socket[addr=/10.1.1.2,port=56357,localport=5269]
2009.06.29 20:14:08 ServerDialback: OS - Validation GRANTED from: jabber.a.com id: d36a3328 for domain: jabber.b.com
2009.06.29 20:14:08 LocalOutgoingServerSession: OS - SERVER DIALBACK OVER TLS with jabber.a.com was successful
2009.06.29 20:14:08 ServerDialback: OS - Sent dialback key to host: jabber.a.com id: d36a3328 from domain: conference.jabber.b.com
2009.06.29 20:14:08 ServerDialback: OS - Sent dialback key to host: jabber.a.com id: d36a3328 from domain: search.jabber.b.com
2009.06.29 20:14:08 ServerDialback: OS - Unexpected answer in validation from: jabber.a.com id: d36a3328 for domain: conference.jabber.b.com answer:<stream:error xmlns:stream="http://etherx.jabber.org/streams"><remote-connection-failed xmlns="urn:ietf:params:xml:ns:xmpp-streams"/></stream:error>
2009.06.29 20:14:08 XMPP specs forbid us to respond with an IQ error to: <iq type="result" id="mir_598" from="conference.jabber.b.com" to="user1@jabber.a.com/Miranda"><query xmlns="http://jabber.org/protocol/disco#info"><identity category="conference" name="Public Chatrooms" type="text"/><identity category="directory" name="Public Chatroom Search" type="chatroom"/><feature var="http://jabber.org/protocol/muc"/><feature var="http://jabber.org/protocol/disco#info"/><feature var="http://jabber.org/protocol/disco#items"/><feature var="jabber:iq:search"/><feature var="http://jabber.org/protocol/rsm"/></query></iq>
2009.06.29 20:14:08 ServerDialback: OS - Sent dialback key to host: jabber.a.com id: d36a3328 from domain: pubsub.jabber.b.com

In the service discovery window I get "Info request error: request
timeout" against every found service of jabber.b.com.

Tags: s2s

More Like This

  • Retrieving data ...

Bookmarked By (0)