HI

As far as I understand Following changes:

1       <!-- The JabberID of the transport. -->
        <jid>aim.YourDomain.com</jid>

2. example.org should be replaced by YourDomain.com

3        <!-- The IP address of the main Jabber server -->
        <mainServer>Actual IP of YourDomain.com</mainServer>


4        <!-- The JID of the main Jabber server -->
        <mainServerJID>YourDomain.com</mainServerJID>

Vishal

On Sep 22, 6:24 pm, "Peter Cheung" <[EMAIL PROTECTED]> wrote:
>         <!-- The JabberID of the transport. -->
>         <jid>127.0.0.1</jid>
>
>         <!-- The JabberID of the conference room handler. -->
>         <!-- GROUPCHAT IS NOT STABLE YET -->
>         <confjid>chatrooms.aim.example.org</confjid>
>
>         <!-- The component JID of the transport. Unless you're doing
> clustering, leave this alone -->
>         <!-- <compjid>aim1</compjid> -->
>
>         <!-- The location of the spool directory.. if relative, relative to
> -->
>         <!-- this directory.  Do not include the jid of the transport. -->
>         <spooldir>.</spooldir>
>
>         <!-- The location of the PID file.. if relative, relative to this
> dir. -->
>         <!-- Comment out if you do not want a PID file -->
>         <!-- <pid>PyAIMt.pid</pid> -->
>
>         <!-- The IP address of the main Jabber server -->
>         <mainServer>127.0.0.1</mainServer>
>
>         <!-- The JID of the main Jabber server -->
>         <mainServerJID>127.0.0.1</mainServerJID>
>
>         <!-- The website of the Jabber service -->
>         <website>http://jabber.localhost/</website>
>
>         <!-- The TCP port to connect to the Jabber server on -->
>         <!-- (this is the default for Jabberd2) -->
>         <port>5347</port>
>
>         <!-- The TCP port that the web admin interface will answer on -->
>         <!-- (uncomment to enable) -->
>         <!-- <webport>5280</webport> -->
>
>         <!-- The authentication token to use when connecting to the Jabber
> server -->
>         <secret>secret</secret>
>
>
>
> On Mon, Sep 22, 2008 at 4:07 AM, Vishal <[EMAIL PROTECTED]> wrote:
>
> > Hi
>
> > Post your config file here.
>
> > Vishal
>
> > On Sep 22, 12:01 pm, pete <[EMAIL PROTECTED]> wrote:
> > > I'm trying to setup an ejabberd server with pyaimt transport on
> > > ubuntu. My ultimate goal is to be able to have a discoverable AIM
> > > transport server so I can use googletalk to talk with people on AIM.
> > > The reason for this is because I use a blackberry and googletalk is
> > > the only decent chat program that the blackberry supports. The current
> > > AIM transport jabber server that I'm using disconnects a lot, so I'm
> > > thinking about making my own.
>
> > > I have ejabberd up and running. I'm able to connect to it with Psi
> > > using my admin account, however, I can't seem to get PyAIMt setup
> > > correctly. Everytime I use Psi to discover service on my server I'm
> > > unable to find any AIM transport services. If I want to host a server
> > > on my computer, can I just set the JID as 127.0.0.1, with main jabber
> > > server IP/ID as 127.0.0.1 as well? That's what I have it set to so
> > > far. Any help would be appreciated. Thanks a lot for your time.- Hide 
> > > quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"py-transports" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/py-transports?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to