Hi
Sorry for delay, I was out on a tour.
I tried to change the config file to mxit.daljeet-pc but i am getting
the same problem, I even tried Ejabberd on windows but again the same
problem , the mxit transport connects sucessfully to jabber server but
it can not be seen in the service discovery.
I even tried to replace all the occurences of localhost to daljeet-pc.
Here is my current config file :
<?xml version="1.0" ?>
<pymxitt>
<!-- This file contains options to be configured by the server
administrator. -->
<!-- Please read through all the options in this file -->
<!-- The JabberID of the transport -->
<jid>mxit.daljeet-pc</jid>
<!-- The JabberID of the conference room handler. -->
<confjid>chat.mxit.daljeet-pc</confjid>
<!-- The public IP or DNS name of the machine the transport is
running on -->
<!-- This is used to select the outgoing IP address used to
connect to the MXit network -->
<!-- otherwise known as the vanity address, it's safe to leave it
commented -->
<!-- <host>daljeet-pc</host> -->
<!-- The name of the transport in the service discovery list. -->
<discoName>Mxit Transport</discoName>
<!-- The location of the spool file.. if relative, relative to the
PyMXitt dir. -->
<!-- Include the jid of the transport, if running multiple copies
of the same transport -->
<spoolFile>mxituser.dbm</spoolFile>
<!-- The location of the PID file, relative to the PyMXitt
directory -->
<!-- Comment out if you do not want a PID file -->
<pid>PyMXitt.pid</pid>
<!-- The IP address or DNS name of the main Jabber server -->
<mainServer>daljeet-pc</mainServer>
<!-- The JID of the main Jabber server -->
<mainServerJID>jabber.daljeet-pc</mainServerJID>
<!-- The TCP port to connect to the Jabber server on (this is the
default for Jabberd2) -->
<port>5347</port>
<!-- The authentication token to use when connecting to the Jabber
server -->
<secret>password</secret>
<!-- SASL username used to bind to Jabber server. -->
<!-- secret, above, is used for sasl password -->
<!--<saslUsername>username-for-jabberd2-connection</saslUsername>--
>
<!-- Allow users to register with this transport -->
<allowRegister/>
<!-- Use external component binding. -->
<!-- This dodges the need to manually configure all jids that talk
to this transport. -->
<!-- Jabberd2 requires saslUsername and useRouteWrap for this to
work. -->
<!-- Wildfire as of 2.6.0 requires just this. -->
<useComponentBinding/>
<!-- Wrap stanzas in <route> stanza. -->
<!-- Jabberd2 requires this for useComponentBinding. -->
<!-- <useRouteWrap/> -->
<!-- You can choose which users you wish to have as
administrators. These users can perform some tasks with Ad-Hoc
commands that others cannot -->
<admins>
<jid>manj...@daljeet-pc</jid>
</admins>
<!-- The file to log to. Leave this disabled for stdout only -->
<debugFile>mxiterror.log</debugFile>
<!-- Show the raw data being sent and received from the xmpp and
MXit servers -->
<dumpProtocol/>
</pymxitt>
On Aug 22, 4:32 pm, Norman Rasmussen <[email protected]> wrote:
> Sorry, I've been offline for a few days:
>
> You need to change the jid in the config file from mxit.localhost to
> mxit.daljeet-pc
>
> Regards
>
> Norman
>
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
