Hi. People here are complaining that when they change state on jabber the state change doesn't reflect in MSN. This happens only sometimes. The status in MSN is in this case the initial state when you connected to jabber.. but if you change it, it doesn't change in MSN.. I don't know if the problem is with pymsnt or Pandion cliente itself.. Any idea?
I'm using pymsnt rev164 I think.. Regards, Sergio Freire From [EMAIL PROTECTED] Fri Jun 9 11:03:36 2006 From: [EMAIL PROTECTED] (Stian B. Barmen) Date: Fri Jun 9 11:03:43 2006 Subject: [py-transports] Two more things :) In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> > On 04/06/2006, at 6:44 PM, Stian B. Barmen wrote: > > > First thing is an issue that one of my users are reporting. > > > > "Sometimes when I use MSN transport on jabber.no I get a > message like > > this and It logs me off. (when I log in again it log me off > and I've > > to wait 30 min or longer to try log) On aMSN client or > somewhere MSN > > works correct. > > > > Disconnected from MSN servers: [Failure instance: Traceback > (failure > > with no frames): exceptions.UnicodeDecodeError: 'utf8' codec can't > > decode byte 0xa9 in position 1: unexpected code byte ]" > > > > I have enquired him for his passport name so I can search the log > > files for more evidence but I thought maybe I would just send it to > > you, maybe you already know what it is? Also I dont know which rev > > this was, but I guess 166 or 170. > > *snip* > > > If you can grab me some log files, I'll be able to look into > the first. Thanks. > I cannot seem to find any logged information about this, but I did enable the logging after he had the error, so I now have asked him if the error still occurs. Will get back to you. > As for the second. Yes, I need to code support for offline messages. > I will be doing it soonish. > Loving it :) You do great work ! :) -stian -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 4490 bytes Desc: not available Url : http://modevia.com/pipermail/py-transports/attachments/20060609/5c882789/smime.bin From [EMAIL PROTECTED] Fri Jun 9 11:29:01 2006 From: [EMAIL PROTECTED] (Rajnish Bhaskar) Date: Fri Jun 9 11:29:14 2006 Subject: [py-transports] Ports needed for PyMSNt In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> > Rajnish Bhaskar schrieb: > > I've been notified of changes in our organisational firewall > > coming up over the next few months that will block all incoming > > requests except on ports explicitly unblocked. My question is > > what ports will I need open to allow Jabber/PyMSNt to continue > > to run. > > Where is the jabber server running? Is it external? Then you > don't need any additional port than the ports you already > mentioned. If I'm interpreting you correctly, then no, the Jabber server is also inside the firewall (it's ejabberd) and is on the same machine. Raj. From [EMAIL PROTECTED] Fri Jun 9 11:38:44 2006 From: [EMAIL PROTECTED] (Stian B. Barmen) Date: Fri Jun 9 11:38:49 2006 Subject: [py-transports] Ports needed for PyMSNt In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> > > > Rajnish Bhaskar schrieb: > > > I've been notified of changes in our organisational > firewall coming > > > up over the next few months that will block all incoming requests > > > except on ports explicitly unblocked. My question is what > ports will > > > I need open to allow Jabber/PyMSNt to continue to run. > > > > Where is the jabber server running? Is it external? Then you don't > > need any additional port than the ports you already mentioned. > > If I'm interpreting you correctly, then no, the Jabber server > is also inside the firewall (it's ejabberd) and is on the > same machine. > Do you have external Jabber users connecting to the Jabber server, and do you have jabberserver<->jabberserver traffic? If yes to one or more: Clients: TCP port 5222 (normal and TLS) and 5223 (legacy ssl) Server2Server: TCP port 5269 If you need to contact ejabberds admin interface from outside the the firewall then: TCP port 5280 Pymsnt users from outside need TCP port 8010 open for File Transfer, or whichever port number is in the config.xml file inside <ftJabberPort>8010</ftJabberPort>. If you enabled out of band file transfer then check <ftOOBPort>8011</ftOOBPort> and open this too (if you dont proxy it through apache port 80 that is, then add port 80 obviously). That should do it :) -stian -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 4490 bytes Desc: not available Url : http://modevia.com/pipermail/py-transports/attachments/20060609/063c1bf7/smime.bin From [EMAIL PROTECTED] Fri Jun 9 12:11:45 2006 From: [EMAIL PROTECTED] (Rajnish Bhaskar) Date: Fri Jun 9 12:11:49 2006 Subject: [py-transports] Ports needed for PyMSNt In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> > > > > My question is what ports will > > > > I need open to allow Jabber/PyMSNt to continue to run. > > > > > > Where is the jabber server running? Is it external? > > > > If I'm interpreting you correctly, then no, the Jabber server is > > also inside the firewall > > Do you have external Jabber users connecting to the Jabber server, Yes, I do have Jabber users outside the firewall > and do you have jabberserver<->jabberserver traffic? If yes to one > or more: And yes, I do have s2s traffic (if you mean do I talk to Jabber users outwith my server: Google Talk) > Clients: TCP port 5222 (normal and TLS) and 5223 (legacy ssl) > Server2Server: TCP port 5269 > <snip /> > That should do it :) So you're saying that PyMSNt needs /no/ extra inbound ports open after the normal Jabber ones? That's cool, but how does it manage it? Raj. From [EMAIL PROTECTED] Fri Jun 9 12:31:17 2006 From: [EMAIL PROTECTED] (Stian B. Barmen) Date: Fri Jun 9 12:31:24 2006 Subject: [py-transports] Ports needed for PyMSNt In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> > > Clients: TCP port 5222 (normal and TLS) and 5223 (legacy ssl) > > Server2Server: TCP port 5269 > > > <snip /> > > That should do it :) > > So you're saying that PyMSNt needs /no/ extra inbound ports > open after the normal Jabber ones? That's cool, but how does > it manage it? > The normal traffic is done over the standard Jabber ports, only file transfer from MSN to the Jabber server needs to be customized. Its a wonderful Jabber world! :) -stian -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 4490 bytes Desc: not available Url : http://modevia.com/pipermail/py-transports/attachments/20060609/c148faf2/smime.bin From [EMAIL PROTECTED] Fri Jun 9 13:38:15 2006 From: [EMAIL PROTECTED] (James Bunton) Date: Fri Jun 9 13:38:27 2006 Subject: [py-transports] problem changing state in MSN with pymsnt In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On 09/06/2006, at 8:44 PM, S?rgio Freire wrote: > Hi. > People here are complaining that when they change state on jabber > the state change doesn't reflect in MSN. This happens only sometimes. > The status in MSN is in this case the initial state when you > connected to jabber.. but if you change it, it doesn't change in MSN.. > I don't know if the problem is with pymsnt or Pandion cliente itself.. > Any idea? > > I'm using pymsnt rev164 I think.. > Regards, > Sergio Freire I think I fixed this in r173. The problem was that the transport was initially trying to sign in with offline presence, and so MSN rejected the status change. If you look in your debug log you probably have a lot of Tracebacks with just numbers (I think it was 715 for changing status). --- James
