| Author |
Message |
![[Post New]](/forums/templates/default/images/icon_minipost_new.gif) 2010/03/24 05:07:45
|
evalUser
Joined: 2010/03/24 05:04:41
Messages: 1
Offline
|
Could someone pls share the openfire configuration for the XMPP GW, I have a openfire install and trying to point the XMPP GW to use openfire.
BTW is sametime as an backend server supported ?
|
|
|
 |
![[Post New]](/forums/templates/default/images/icon_minipost_new.gif) 2010/03/24 16:50:00
|
jbuddysupport
Joined: 2007/05/03 18:15:29
Messages: 156
Location: Glastonbury, CT
Offline
|
Important Installation Notes:
On the Gateway Configuration page of the JBuddy XMPP Gateway installer, you are prompted for several items. They are described below.
XMPP Server Host Name/IP Address: hostname or IP address of your XMPP Server. If JBuddy XMPP Gateway is installed on the same machine, the default 127.0.0.1 should work.
XMPP Gateway Port: the port that the XMPP Server will listen for external components to connect on (default 5275)
XMPP Server Name (domain.com): the domain of your XMPP Server (the @domain.com part of your user's JID). Not typically the fully qualified machine name.
XMPP Gateway Secret: the secret/password used by the XMPP Server to authenticate external components
Confirm XMPP Gateway Secret: same as value above
In order for the JBuddy XMPP Gateways to connect to your XMPP Server, the XMPP Server must be compliant with XEP 0114 and be properly configured to accept connections from external components. Below I will describe the OpenFire settings required to support JBuddy XMPP Gateway:
Openfire External Component Configuration:
In the Openfire web console, navigate to Server/Server Settings/External Components. Under "Service Enabled", choose "Enabled", and set the same port and shared secret values you supplied in the JBuddy XMPP Gateway installation (or vice versa). Finally, press "Save Settings".
Testing Connectivity:
To test that your Openfire XMPP Server is listening on the expected port for external components to connect and is reachable from your JBuddy XMPP Gateway installation do the following: From the server where JBuddy XMPP Gateway is installed, telnet to the hostname and port supplied during installation. If you connect, all is well, if not, check that the server doesn't have some sort of firewall running that is preventing connection on the specified hostname and port.
Running JBuddy XMPP Gateway:
To run JBuddy XMPP Gateway, simply type bin/XMPPGateway.bat on a Windows machine or bin/xmpp-gateway.sh on Unix, Linux or Mac OS X. Assuming everything was configured properly, the JBuddy XMPP Gateways should start up and connect to Openfire successfully. Openfire will then advertise these new public IM gateways to XMPP Clients supporting XEP 0100
|
|
|
 |
![[Post New]](/forums/templates/default/images/icon_minipost_new.gif) 2010/03/24 16:55:42
|
jbuddysupport
Joined: 2007/05/03 18:15:29
Messages: 156
Location: Glastonbury, CT
Offline
|
Currently only AIM, ICQ, MSN, and Yahoo are included in the JBuddy XMPP Gateway installer. XMPP Gateway connectivity to Lotus Sametime and Microsoft LCS 2005 and OCS 2007 may be available upon special request.
As with the public IM gateways, each XMPP user wishing to connect through an xmpp gateway must have a valid screen name and password for the given IM network.
I believe that both Lotus Sametime 8.x and Microsoft OCS can now support server to server federation with XMPP servers, however some organizations may require that the user login using the Sametime or OCS specific user name which is what an XMPP gateway would do.
|
|
|
 |
|
|
|