<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 5.50.4522.1800" name=GENERATOR></HEAD> <BODY> <DIV><SPAN class=260355119-03052001><FONT face=Arial color=#0000ff size=2>I've got conferencing and the MSN transport working. I found during the configuration of the jabber.xml that formatting the tags (i.e., indenting) is a no-no.</FONT></SPAN></DIV> <DIV><SPAN class=260355119-03052001><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=260355119-03052001><FONT face=Arial color=#0000ff size=2>for example (from my notes), the following produces an error:</FONT></SPAN></DIV> <DIV><SPAN class=260355119-03052001><SPAN class=260355119-03052001><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV> <DIV><SPAN class=260355119-03052001><FONT face=Arial color=#0000ff size=2><conference>./conference-0.4.1/conference.so</FONT></SPAN></DIV> <DIV><SPAN class=260355119-03052001><FONT face=Arial color=#0000ff size=2></conference></FONT></SPAN></DIV> <DIV><SPAN class=260355119-03052001><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=260355119-03052001> <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=260355119-03052001>Maybe I had a blank space after the .so or a carriage return. I don't know </SPAN>but <SPAN class=260355119-03052001>it </SPAN>works just fine like this:</FONT></FONT></FONT></SPAN></DIV></DIV> <DIV><SPAN class=260355119-03052001><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV></SPAN></DIV> <DIV><SPAN class=260355119-03052001><FONT face=Arial color=#0000ff size=2><conference>./conference-0.4.1/conference.so</conference></FONT></SPAN></DIV> <DIV><SPAN class=260355119-03052001><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=260355119-03052001><FONT face=Arial color=#0000ff size=2>Your best bet is not to assume anything about the formatting of the jabber.xml file, use/modify the examples that comes with the services/transports, and follow the directions precisely.</FONT></SPAN></DIV> <DIV><SPAN class=260355119-03052001><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=260355119-03052001><FONT face=Arial color=#0000ff size=2>Randy</FONT></SPAN></DIV> <DIV><SPAN class=260355119-03052001><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> jdev-admin@jabber.org [mailto:jdev-admin@jabber.org]<B>On Behalf Of </B>Bill Farrell<BR><B>Sent:</B> Thursday, May 03, 2001 3:47 PM<BR><B>To:</B> JDEV Mailing List (E-mail)<BR><B>Subject:</B> [JDEV] Newbie<BR><BR></FONT></DIV> <DIV><SPAN class=690191419-03052001><FONT face=Arial size=2>Hello, Everyone,</FONT></SPAN></DIV> <DIV><SPAN class=690191419-03052001><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=690191419-03052001><FONT face=Arial size=2>I'm having a good experience with the basic jabberd and got a local JUD added with zero problem.  That was a Good Thing.  </FONT></SPAN></DIV> <DIV><SPAN class=690191419-03052001><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=690191419-03052001><FONT face=Arial size=2>I've since tried to add a conference, and AIM transport, and an ICQ transport.  Each of these exercises have met with nothing but mysterious messages like "Not acceptable" and "Not Implemented".  The AIM transport wouldn't compile at all, regardless of what the FAQ's and HowTo's said.</FONT></SPAN></DIV> <DIV><SPAN class=690191419-03052001><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=690191419-03052001><FONT face=Arial size=2>I've checked every character of XML, verified it with the HOWTO and the FAQ's, straightened away the indents so it looked pretty (with some servers, neatness counts!), run the server in debug mode (which basically produces zillions of useless lines) and by this point, IF I had hair, I'd be tearing it out.</FONT></SPAN></DIV> <DIV><SPAN class=690191419-03052001><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=690191419-03052001><FONT face=Arial size=2>Is there anyone who has actually gotten ICQ or conferencing to work?  I'm running the server on both RH6.2 and RH7.1 with identical results.  That is, the basic server comes up beautifully and JUD is a TREAT!  If that were all I needed to work, I could be happy with that.</FONT></SPAN></DIV> <DIV><SPAN class=690191419-03052001><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=690191419-03052001><FONT face=Arial size=2>I'm convinced there has GOT to be a config problem, but looking at the docs and looking at what I've got in jabber.xml, they're near identical (except for machine name, of course).  All the virtual machine names in the id's are unique and present in DNS (both internal and external DNS's, that is).  The FAQ's didn't have a whole lot to go on and I didn't find the other documentation to be much help.  I've read everything I could get to on the jabber.* sites...</FONT></SPAN></DIV> <DIV><SPAN class=690191419-03052001><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=690191419-03052001><FONT face=Arial size=2>Could anyone share their experience in bringing up the latest version of conferencing and/or ICQ transport?  I'd be a most grateful!!</FONT></SPAN></DIV> <DIV><SPAN class=690191419-03052001><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV><SPAN class=690191419-03052001><FONT face=Arial size=2></FONT></SPAN> </DIV> <DIV> <P><FONT face=Arial size=1>Bill Farrell<BR>Webmaster<BR><A href="http://www.ages.com/">http://www.ages.com</A><BR><A href="http://www.vaspartsonline.com/">http://www.vaspartsonline.com</A></FONT></P> <P><FONT face=Arial size=1>************</FONT></P> <P><FONT face=Arial size=1>Please visit us at www.vaspartsonline.com for quotes, order updates, specials, AGES / Volvo Aerospace general information, and related aviation news.</FONT></P> <P><FONT face=Arial size=1>All price quotations are provided for information purposes only and are subject to change, prior sale, lease, or removal from the market of the material quoted, without prior notice. Any contract for purchase of material is expressly conditioned upon buyer`s acceptance of AGES` terms and conditions of sale. Any material sold and shipped to a Customer, and/or resold and shipped (to a third party, etc.), MUST comply with U.S. Export Regulations. No material can be sold or shipped to a debarred entity or country embargoed by the United States of America. Verification of parts offered as potential alternates and/or interchangeables, is ultimately the responsibility of the quote requester.</FONT></P> <P><FONT face=Arial size=1>All AGES` purchases must have full traceability to a regulated source faxed/e-mailed beforehand, and must accompany parts. All parts purchased must be non-incident related, and statement faxed, e-mailed, etc. beforehand, and must also accompany parts. All NEW parts purchased must have traceability documentation back to the OEM! All parts must have U.S. Maint 8130, Canadian DOT 24-0078, or JAA FORM 1, and company C of C, when applicable. Any HAZMAT material purchased, such as Oxygen, Fuel, Oil, Hydraulic, etc. type related material, must include Material Safety Data Sheets, if applicable. All applicable HAZMAT documentation and labeling must accompany HAZMAT shipped material.</FONT></P> <P><FONT face=Arial size=1>This e-mail message/fax, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message/fax to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message/fax is strictly prohibited.</FONT></P> <P><FONT face=Arial size=1>If you received this message/fax in error, please immediately notify the sender and delete this e-mail message/fax from your computer.</FONT></P></DIV> <DIV> </DIV></BLOCKQUOTE></BODY></HTML>