> > ________________________________ > > From: [email protected] > [mailto:[email protected]] On Behalf Of Chitralekha > Sent: Wednesday, January 13, 2010 8:27 AM > To: [email protected] > Subject: [sipX-dev] Federation between External IM > Accounts and sipXecs XMPPserver. > > > Hi All, > > This is a query regarding Federation between External > IM Accounts and sipXecs XMPP server. > > Precondition: > ----------------- > 1.Create a test account on gmail. > > Steps: > ------- > 1.Add a user say 500 and configure IM. > 2.Login as an end user 500 and navigate to My > Information>>Instant Messaging page. > 3.Click on the link "Add External IM Account" > 4.The page navigates to "External User IM Account". > > Scenario: > Add "test account" as External account(for 500 user). > After this, I could see all the contacts associated with the > test account added as buddies to 500 user.I was able to chat > with one of the buddies online as well. > > Query: > I could get the above scenario working withOUT > enabling server-to server federation cofiguration NOR > providing the "gmail.com" in list of allowed servers on > enabling server-to-server federation page. In other words I > did not change anything in S2S page(login as > superadmin>>Features>>Instant Messaging tab) , to chat from > scs user to a gmail buddy. > Please advise if it is intended to work like this or is a bug. > > > Can you verify that the (superadmin>>Features>>Instant > Messaging tab) screen is equivalent to the Openfire screen > under (Openfire console->Server->Server Setttings->Server to > Server) which should be accessible via http://<sipXecs > FQDN>:9094/server2server-settings.jsp <http://<sipXecs > FQDN>:9094/server2server-settings.jsp> ? > > Both screens should be in sync. Note that the Instant > Messaging service needs to be restarted to make a change effective.
I think you are on the wrong path here. The kind of configuration you are testing has no relationship with Server-to-server federation. What you are doing is client->server connections via the Kraken plug-in hence the Server-to-server (S2S) restrictions do not play a role in this. S2S restrcitions do come into play in the following two examples: 1- someone using a googletalk client logs into its googletalk IM account and adds [email protected] as a buddy. In this case, the google IM server will contact your server to make that connection. Based on the S2S settings, that connection will either be allowed or rejected. 2- You log into your [email protected] IM account on your SCS and you add [email protected] as a buddy. This will also create a S2S connection between the SCS and the google IM server and will be subject to the S2S configured policy. > > > Could anybody let me also know on how extensive the s2s > federation(login as superadmin>>Features>>Instant Messaging > tab) to be tested. Not very much. Just the basic functionality. > [Here for example, if we consider the scenario > mentioned above,I could get the federated working with the > gtalk account even withOUT configuring anything on the s2s > federation page(login as superadmin>>Features>>Instant Messaging tab)] I think my previous comments explain that 8< _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
