Under *Server > Server Settings > External Components* make sure it is
turned on. Note the shared secret and the port.
When using it you need to tell your transport to connect back to your Jabber
server on the port you specify within the external components section.
Here is a sample from the PyAIMt transport:
<!-- The TCP port to connect to the Jabber server on -->
> <!-- (this is the default for Jabberd2) -->
> *<port>5275</port>*
>
> <!-- The authentication token to use when connecting to the Jabber
> server -->
> *<secret>secret</secret>*
>
On Mon, Aug 17, 2009 at 4:40 PM, daljeet <[email protected]> wrote:
>
> I could not find the how to configure the extension if you can find it
> i will be highly greateful .
>
> regards
> Daljeet
>
> On Aug 17, 10:10 pm, Brandon Dixon <[email protected]> wrote:
> > Alright. Check out Openfire and its extensions configuration. I believe
> > there is something you have to do that involves that. I do not have an
> > Openfire instance right in front of me, but I can get one up sometime
> > tonight and let you know if you don't find it by then.
> >
> > On Mon, Aug 17, 2009 at 12:40 PM, daljeet <[email protected]
> >wrote:
> >
> >
> >
> >
> >
> > > I ran it from windows commandLine, I would be very grateful for your
> > > help.
> > > I am not sure if the problem lies with openfire or with windows.
> > > I will be waiting for your help.
> >
> > > regards
> > > Daljeet
> >
> > > On Aug 17, 7:16 pm, Brandon Dixon <[email protected]> wrote:
> > > > What exactly do you mean you are running it from the command line?
> Are
> > > you
> > > > referring to Python's command line or Window's command line?
> >
> > > > I am not certain how everything operates within the Windows realm. I
> > > always
> > > > host these kinds of services on a Linux server, but I can try and
> > > continue
> > > > to help you out.
> >
> > > > On Mon, Aug 17, 2009 at 1:35 AM, daljeet <[email protected]
> >
> > > wrote:
> >
> > > > > Below are the derails of external compoent shown on openfire
> server,
> > > > > I find the name ,category and type are blank, that may be the
> reason
> > > > > the clients are not being able to show MXIT transport in the
> service
> > > > > discovery.
> >
> > > > > External Component Connection Details
> >
> > > > > Below are details about the session with the external component
> > > > > mxit.localhost.daljeet-pc.
> > > > > External Component Connection Details
> > > > > Domain mxit.localhost.daljeet-pc
> > > > > Name
> > > > > Category:
> > > > > Type:
> > > > > Creation Date Aug 17, 2009 10:59:28 AM
> > > > > Last Activity Aug 17, 2009 10:59:28 AM
> > > > > Session Statistics: Packets Received/Sent: 1/1
> > > > > Client IP / Hostname: 127.0.0.1 / 127.0.0.1
> >
> > > > --
> > > > Brandon Dixon - CCNA, OSCP, WebSphere DataPower Solution Developer
> > > > Information Systems Security
> Engineerwww.dueyesterday.net-Documentation
> > > for the masses
> >
> > --
> > Brandon Dixon - CCNA, OSCP, WebSphere DataPower Solution Developer
> > Information Systems Security Engineerwww.dueyesterday.net- Documentation
> for the masses
> >
>
--
Brandon Dixon - CCNA, OSCP, WebSphere DataPower Solution Developer
Information Systems Security Engineer
www.dueyesterday.net - Documentation for the masses
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
