Andrew, thanks for the reply. No, to my knowledge everything is opened from our venue server. I connected with PSI from the Venue server to check my outbound connection and it connected. I chatted for awhile with Cindy who helped me browse the active group chats.
On 9/29/06, Andrew A Rowley <[email protected]> wrote: > Hi, > > It looks to me like your client hasn't managed to connect to the jabber > server. It also looks like it is still waiting to connect since in the code > there would be an exception displayed in the log if it had failed. > > Could there be something that is blocking the outgoing connection from your > client to the Jabber server (note that it is using the secure port 5223 > rather than the insecure 5222, which you may have opened already for using > Psi)? > > Andrew :) > > ============================================ > Access Grid Support Centre, > RSS Group, > Manchester Computing, > Kilburn Building, > University of Manchester, > Oxford Road, > Manchester, > M13 9PL, > UK > Tel: +44(0)161-275 0685 > Email: [email protected] > > > -----Original Message----- > > From: Jeremy Mann [mailto:[email protected]] > > Sent: 28 September 2006 16:53 > > To: [email protected] > > Cc: [email protected] > > Subject: Re: [AG-TECH] AG 2.4 and 3.0 servers > > > > The VenueClient log shows: > > > > 09/28/06 10:17:37 28510208 JabberClient JabberClient.py:33 INFO > > Connecting to Jabber Server 'jabber.mcs.anl.gov' ... > > 09/28/06 10:17:37 -1610567004 VenueClient VenueClientUI.py:3333 > > DEBUG ContentListPanel.AddParticipant:: AddParticipant Jeremy Mann > > (Mac) (called from > > ('//Library/Python/2.3/wx-2.6-mac-unicode/wx/_core.py', 13465, > > '<lambda>', 'lambda event: event.callable(*event.args, **event.kw) > > )')) > > 09/28/06 10:17:37 -1610567004 VenueClient VenueClientUI.py:3333 > > DEBUG ContentListPanel.AddParticipant:: AddParticipant Jeremy Mann > > (XP) (called from > > ('//Library/Python/2.3/wx-2.6-mac-unicode/wx/_core.py', 13465, > > '<lambda>', 'lambda event: event.callable(*event.args, **event.kw) > > )')) > > 09/28/06 10:17:37 -1610567004 GroupMsgClient GroupMsgClient.py:112 > > INFO Connected. Connection ID: 816f45a75edf7ee69b0637cfe6bf6f7d > > 09/28/06 10:17:37 -1610567004 EventClient > > InsecureVenueEventClient.py:60 INFO BaseVenueEventClient made > > connection. > > 09/28/06 10:18:08 -1610567004 JabberClient JabberClient.py:55 > > DEBUG currentRoom inside sendMessage(): '' > > 09/28/06 10:18:08 -1610567004 JabberClient JabberClient.py:59 > > ERROR No venue is selected > > > > > > On 9/28/06, Andrew A Rowley <[email protected]> wrote: > > > Hi, > > > > > > In Psi, once you are connected (Online) select "Service Discovery" from > > the "Psi" menu. There should then be an "AG Text Chats" list containing > > all the current chats. If your client is connecting then your venue will > > be listed here. > > > > > > As Tom states, there might be something in the VenueClient.log file to > > suggest what is going wrong. > > > > > > Andrew :) > > > > > > ============================================ > > > Access Grid Support Centre, > > > RSS Group, > > > Manchester Computing, > > > Kilburn Building, > > > University of Manchester, > > > Oxford Road, > > > Manchester, > > > M13 9PL, > > > UK > > > Tel: +44(0)161-275 0685 > > > Email: [email protected] > > > > > > > -----Original Message----- > > > > From: [email protected] [mailto:[email protected]] On > > > > Behalf Of Jeremy Mann > > > > Sent: 28 September 2006 15:36 > > > > To: [email protected] > > > > Cc: [email protected] > > > > Subject: Re: [AG-TECH] AG 2.4 and 3.0 servers > > > > > > > > How do I browse the group chats? I have PSI installed and I'm > > > > connected to jabber.mcs.anl.gov. I go to Join Group Chat and it asks > > > > me for host, room and nickname. There is no way, that I can tell, to > > > > browse the group chats. > > > > > > > > > > > > On 9/28/06, Andrew A Rowley <[email protected]> wrote: > > > > > Hi, > > > > > > > > > > This is odd - this suggests that you cannot connect to the jabber > > server > > > > from your client (I am fairly sure this is all done on the client side > > > > now). It is worth logging on to the ANL server with another jabber > > client > > > > and seeing if you can see any rooms for your server in the service > > > > discovery. Room names are the venue name with the spaces removed with > > > > your server hostname appended in brackets (take a look and you should > > see > > > > what I mean). > > > > > > > > > > Andrew :) > > > > > > > > > > ============================================ > > > > > Access Grid Support Centre, > > > > > RSS Group, > > > > > Manchester Computing, > > > > > Kilburn Building, > > > > > University of Manchester, > > > > > Oxford Road, > > > > > Manchester, > > > > > M13 9PL, > > > > > UK > > > > > Tel: +44(0)161-275 0685 > > > > > Email: [email protected] > > > > > > > > > > > -----Original Message----- > > > > > > From: Jeremy Mann [mailto:[email protected]] > > > > > > Sent: 27 September 2006 20:00 > > > > > > To: Andrew Rowley > > > > > > Cc: [email protected] > > > > > > Subject: Re: [AG-TECH] AG 2.4 and 3.0 servers > > > > > > > > > > > > On 9/27/06, Andrew Rowley <[email protected]> wrote: > > > > > > > Hi, > > > > > > > > > > > > > > If you copied your old server config, you will need to change > > the > > > > > > textPort to > > > > > > > 5223 (it is probably 8002 or something like that just now). You > > can > > > > run > > > > > > your > > > > > > > own Jabber server, but anl host one that seems stable (plus > > there > > > > are > > > > > > > loads out > > > > > > > there) at jabber.mcs.anl.gov. This should be set by default as > > your > > > > > > textHost > > > > > > > in your VenueServer.cfg file. > > > > > > > > > > > > Thanks Andrew. I have changed textPort to 5223 and left the > > address to > > > > > > the ANL jabber server. However, when I enter my Lobby and type > > > > > > something it says: > > > > > > > > > > > > You have to be connected to a venue to send a text message > > > > > > > > > > > > > > > > > > -- > > > > > > Jeremy > > > > > > > > > > > > > > > > > > > > > > -- > > > > Jeremy > > > > > > > > > > > > > > > > -- > > Jeremy > > -- Jeremy
