I got the mxit running without hanging when i ran using the command Prompt instead of IDLE. saw the applications that are running and could see a python program running in the Windows Task manager .(that refers to MXIT) T
On Aug 17, 10:13 am, Brandon Dixon <[email protected]> wrote: > Run the MXIT transport on the actual server and not through IDLE. That could > be causing some issues. I am not sure of the server details, but there is > more than likely a debug way of starting MXIT as well as pushing it to the > background. Once you start it up check your processes and ensure that MXIT > is actully running. If you still can't get it working than send more details > about your setup so I can better help you. > > On Mon, Aug 17, 2009 at 12:44 AM, daljeet <[email protected]>wrote: > > > > > > > I was able to connect to server without SASL as the server now showed > > an external component named "mxit.localhost.daljeet-pc" . But the > > python program (i used IDLE to run) seemed to hang , and i could not > > see mxit in the service discovery on spark. > > firther i am using a geteway plugin on openfire which provides > > yahoo ,msn and gtalk transport. i can see those in the service > > discovery and use them. > > this is the config.xml file i used. > > > <?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.localhost</jid> > > > <!-- The JabberID of the conference room handler. --> > > <confjid>chat.mxit.localhost</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>vanity.host.example.net</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>127.0.0.1</mainServer> > > > <!-- The JID of the main Jabber server --> > > <mainServerJID>jabber.localhost</mainServerJID> > > > <!-- 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>1234567</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>[email protected]</jid> > > <jid>[email protected]</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 17, 9:19 am, Brandon Dixon <[email protected]> wrote: > > > Quick search on Google turned this up: > > > >http://github.com/normanr/mxit-transport/blob/b558061daf2e8b1973863a5... > > > > Check out the project site and documentation before sending out for help. > > > Not sure if you have looked at this stuff yet, but it should provide some > > > insight into the issue you are experiencing. > > > > On Mon, Aug 17, 2009 at 12:15 AM, daljeet <[email protected] > > >wrote: > > > > > No I was not able to use MXIT transport at all. what would be the > > > > example configuration for non SASL authentication,, right now i can > > > > use my openfire server with spark . > > > > > On Aug 17, 9:12 am, Brandon Dixon <[email protected]> wrote: > > > > > Looking at the error it looks like it is not a SASL issue, but more > > of a > > > > bad > > > > > namespace somewhere in your configuration. Are you able to connect > > and > > > > use > > > > > the Jabber server without SASL (standard authentication)? > > > > > > On Mon, Aug 17, 2009 at 12:00 AM, daljeet < > > [email protected] > > > > >wrote: > > > > > > > What should be my SASL username ? > > > > > > !-- 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/> > > > > > > > this was my error . > > > > > > Traceback (most recent call last): > > > > > > File "C:\Users\Daljeet\mxit\mxit.py", line 1001, in <module> > > > > > > if not transport.xmpp_connect(): > > > > > > File "C:\Users\Daljeet\mxit\mxit.py", line 919, in xmpp_connect > > > > > > connected = self.jabber.connect((config.mainServer,config.port)) > > > > > > File "C:\Python26\Lib\site-packages\xmpp\client.py", line 284, in > > > > > > connect > > > > > > CommonClient.connect(self,server=server,proxy=proxy) > > > > > > File "C:\Python26\Lib\site-packages\xmpp\client.py", line 184, in > > > > > > connect > > > > > > if not self.Process(1): return > > > > > > File "C:\Python26\Lib\site-packages\xmpp\dispatcher.py", line 303, > > > > > > in dispatch > > > > > > handler['func'](session,stanza) > > > > > > File "C:\Python26\Lib\site-packages\xmpp\dispatcher.py", line 215, > > > > > > in streamErrorHandler > > > > > > raise exc((name,text)) > > > > > > BadNamespacePrefix: (u'bad-namespace-prefix', '') > > > > > > > Please help , thank you in advance . > > > > > > > On Aug 17, 12:30 am, Brandon A Dixon <[email protected]> > > > > > > wrote: > > > > > > > I have always used localhost in testing and it works fine. > > Openfire > > > > > > > tells you your server name too so you should be able to go there. > > > > > > > > Brandon Dixon > > > > > > > G2 - ISSEwww.dueyesterday.net > > > > > > > > On Aug 16, 2009, at 3:13 PM, Norman Rasmussen < > > > > [email protected]> > > > > > > > wrote: > > > > > > > > > If I remember correctly mainServerJID isn't critical to get > > > > > > > > perfectly right. You should be able to use localhost without a > > > > > > > > problem. > > > > > > > > > On Sun, Aug 16, 2009 at 6:37 PM, daljeet > > > > > > > > <[email protected]> wrote: > > > > > > > > > I am running openfire server . > > > > > > > > Can anyone tell me how to get JID of my main jabber server. > > > > > > > > how to get SASL username for my openfire server running on my > > local > > > > > > > > host. > > > > > > > > Here is my config.xml that i am trying to use. > > > > > > > > > <!-- The JID of the main Jabber server --> > > > > > > > > <mainServerJID>localhost</mainServerJID> <!- please hlp me > > with > > > > > > > > this -> > > > > > > > > > -- > > > > > > > > - Norman Rasmussen > > > > > > > > - Email: [email protected] > > > > > > > > - Home page:http://norman.rasmussen.co.za/ > > > > > > -- > > > > > 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 Engineerwww.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 -~----------~----~----~----~------~----~------~--~---
