Ticket #5186 (closed defect: duplicate)

Opened 2 years ago

Last modified 2 years ago

MSN switchboard errors - can't send messages

Reported by: i-nZ Owned by: khc
Milestone: Component: MSN
Version: 2.4.0 Keywords: httpmethod
Cc:

Description

When using MSN on an unreliable (3G modem connection) it will randomly start throwing "Message could not be sent because an error with the switchboard occurred:" after a while after I have sent a message. But pidgin doesn't say MSN has disconnected me, also all other protocols are connected. I can no longer send messages if that happens unless the person on the other side sends me a message - then I will stop getting those errors. Else I have to go Offline -> go Online to be able to send messages on MSN again.

From the Debug Window:

(12:04:50) msn: S: SB 003: MSG xxxxxx@hotmail.com XXXX 129
(12:05:36) msn: C: NS 000: PNG
(12:05:50) msn: S: SB 003: BYE xxxxxx@hotmail.com
(12:05:50) msn: destroy httpconn (0x8073fd08)
(12:06:06) msn: new httpconn (0x80c266b8)
(12:06:06) msn: C: NS 000: XFR 14 SB
(12:06:06) msn: Appending message to queue.
(12:06:36) msn: C: NS 000: PNG
(12:07:06) msn: cal_timeout: command CAL timed out
(12:07:06) msn: cal_error_helper: command CAL failed for reason 7
(12:07:06) msg: Error: Unable to call the user xxxxxx@hotmail.com for reason 7
(12:07:06) msn: Switchboard with unassigned conversation
(12:07:06) msn: destroy httpconn (0x80c266b8)
(12:07:06) msn: C: NS 000: PNG
(12:07:36) msn: C: NS 000: PNG

Change History

  Changed 2 years ago by Apewall

This is confirmed on any connection, you may receive a "Connection Error" instead of the typical "Switchboard error" but the result is the same. You are connected to MSN and can see your contacts online, but you are unable to send or receive messages from them.

  Changed 2 years ago by rubin

Hi,

I can confirm this issue. It does not matter if I'm behind my company's firewall using a socks or http proxy or at home using a regular nat connection. What happens is:

  • Connect to MSN fine, everything green and happy
  • Message some people, who respond normally

(random amount of time passes)

  • Type a message to someone, wait approx. 2 minutes..
  • See messages like: "Message could not be sent because a connection error occurred".
  • See a whole stream of messages like above because you were typing a lot..

This problem has been bugging me on and off for about a year now; To the end-user it is not really explainable and he/she will then switch back to microsoft's msn messenger thingie. I've heard it said that this could have to do with protocol changes at ms, but this is not clear to me; how can i assist in debugging this?

Imho we should eradicate this bug to extinction once and for all ;-)

  Changed 2 years ago by felipec

  • owner changed from khc to felipec
  • status changed from new to assigned

  Changed 2 years ago by mots

i am having the same problem here (behind a socks proxy). it so annoying that i am considering switching back to Live Messenger.

here is the log : (10:45:27) msn: cal_timeout: command CAL timed out (10:45:27) msn: cal_error_helper: command CAL failed for reason 7 (10:45:27) msg: Error: Unable to call the user alexis_baert@… for reason 7 (10:45:27) msn: Switchboard with unassigned conversation (10:45:27) msn: destroy httpconn (01E8A720)

what i did : -status => online -wait 2 minute -send a message to a buddy -wait 2 minutes -get the error back.

this makes MSN basically not usable at all....

I think this issue should not be considered as minor but major as it affects the main purpose of Pidgin, sending Messages !

  Changed 2 years ago by felipec

  • keywords httpmethod added
  • priority changed from minor to critical

I agree, this must be fixed.

The problem is that httpmethod is one of the features that gets less attention. I implemented this in a week or so, and never worked on it seriously again.

Can you try without httpmethod?

  Changed 2 years ago by mots

i have two MSN accounts on my pidgin. one was HTTP method, the other not.

I think both accounts gave me the error i think.

i use a socks proxy. (putty in facts...)

I'll remove the HTTP method anyways.

but in a general way, i think this messages should trigger some kind of autofix in the code and not be displayed to the user, or at least after a few retries.

  Changed 2 years ago by felipec

These timeout errors should not happen, that's the whole idea of the error, so users get annoyed and report it.

From the code it seems like everything got screwed up after sending an PNG command, which afaik should not happen if you are using the httpmethod.

It seems there was an unhandled disconnection from the server.

follow-up: ↓ 10   Changed 2 years ago by bernmeister

Does this still occur in 2.5.1 which now uses MSNP15? Can you please verify?

  Changed 2 years ago by vkoval

Yes. Yesterday I'm install pidgin 2.5.1 and error present.

in reply to: ↑ 8   Changed 2 years ago by vkoval

Replying to bernmeister:

Does this still occur in 2.5.1 which now uses MSNP15? Can you please verify?

Yes. Yesterday I'm install 2.5.1 and error present. I'm work through the proxy and with use HTTP Method, port 1863.

  Changed 2 years ago by felipec

  • owner changed from felipec to khc

Hmm, I forgot I still have owned tickets.

I can't do much here except suggest to try msn-pecan :p

  Changed 2 years ago by khc

  • status changed from new to closed
  • resolution set to duplicate

Closed as duplicate of #3330.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!