Opened 10 years ago

Closed 10 years ago

Last modified 7 years ago

#10067 closed defect (duplicate)

Can't receive messages reliably after msn switchboard timeout

Reported by: adam.lantos Owned by: khc
Milestone: Component: MSN
Version: 2.6.1 Keywords: msn switchboard receive
Cc:

Description

Since pidgin upgrade to 2.6.1, I can't reliable receive messages from official WLM clients.

Steps to reproduce:

Open up chat with someone using the official wlm client. After the 1 minute timeout, switchboard connection will be closed. Then send some message from the wlm client.

Expected result: Message is received instantly.

Current result: Message is not received (at least not every message), WLM timeouts and notifies the user the message could not be sent.

I suspect this issue is related to the fix of #3330.

Change History (2)

comment:1 Changed 10 years ago by QuLogic

  • Resolution set to duplicate
  • Status changed from new to closed

Closed as duplicate of #10049.

comment:2 Changed 7 years ago by kjbpalm

I do not believe that this is a duplicate of #10049. I am still seeing this problem as of Pidgin 2.9.0 on Windows, as well as my mobile client that is built on libpurple 2.9.0. If you connect to MSN using HTTP method, then you will not receive any incoming IM messages from the Windows Messenger desktop or web client sent after 1 minute of idle time. Debug log shows the http connection is getting destroyed after 1 min.

(14:50:05) msn: S: NS 000: RNG 1225798377 64.4.44.30:1863 CKI 6513120.99115237 kjbpalm@gmail.com Karen U messenger.msn.com 1
(14:50:05) msn: new httpconn (02D8B2C8)
(14:50:05) dnsquery: Performing DNS lookup for 64.4.44.30
(14:50:05) msn: C: SB 002: ANS 1 kjbpalm@hotmail.com;{172C5865-6C92-4C04-3FDF-6B7450FA80EF} 6513120.99115237 1225798377
(14:50:05) dnsquery: IP resolved for 64.4.44.30
(14:50:05) proxy: Attempting connection to 64.4.44.30
(14:50:05) proxy: Connecting to 64.4.44.30:80 with no proxy
(14:50:05) proxy: Connection in progress
(14:50:05) proxy: Connecting to 64.4.44.30:80.
(14:50:05) proxy: Connected to 64.4.44.30:80.
(14:50:05) msn: S: SB 002: IRO 1 1 2 kjbpalm@gmail.com;{8b98e9fb-b759-4c39-a585-7cec4e599f42} Karen 2788999468:3624129584
(14:50:05) msn: S: SB 002: IRO 1 2 2 kjbpalm@gmail.com Karen 2788999468:3624129584
(14:50:05) msn: S: SB 002: ANS 1 OK
(14:50:07) msn: S: SB 002: JOI kjbpalm@hotmail.com Karen 2416181284:2147619840
(14:50:07) msn: Processing queue
(14:50:07) msn: S: SB 002: MSG kjbpalm@gmail.com Karen 90
(14:50:07) msn: S: SB 002: MSG kjbpalm@gmail.com Karen 121
(14:50:07) sound: Playing C:\Program Files\Pidgin\sounds\purple\receive.wav
(14:50:17) msn: S: NS 000: NOT 598
(14:50:24) msn: Sending UUX command with payload: <EndpointData><Capabilities>262180:00</Capabilities></EndpointData>
(14:50:24) msn: C: NS 000: UUX 15 67
(14:50:24) msn: Sending UUX command with payload: <PrivateEndpointData><EpName>Pidgin</EpName><Idle>false</Idle><ClientType>1</ClientType><State>NLN</State></PrivateEndpointData>
(14:50:24) msn: C: NS 000: UUX 16 128
(14:50:24) msn: Sending UUX command with payload: <Data><PSM/><CurrentMedia/><MachineGuid>172C5865-6C92-4C04-3FDF-6B7450FA80EF</MachineGuid><DDP/></Data>
(14:50:24) msn: C: NS 000: UUX 17 103
(14:50:24) msn: C: NS 000: CHG 18 NLN 2416181284:00 0
(14:50:24) msn: S: NS 000: NLN NLN kjbpalm@hotmail.com 1 Karen 262180:2147483648 0
(14:50:24) msn: S: NS 000: UBX kjbpalm@hotmail.com 1 501
(14:50:24) msn: UBX received.
(14:50:24) msn: msn get PSM
(14:50:24) msn: Get CurrentMedia
(14:50:24) msn: No currentmedia string
(14:50:24) msn: Get EndpointData
(14:50:24) msn: S: NS 000: UUX 15 0
(14:50:24) msn: UUX received.
(14:50:24) msn: S: NS 000: UUX 16 0
(14:50:24) msn: UUX received.
(14:50:24) msn: S: NS 000: UUX 17 0
(14:50:24) msn: UUX received.
(14:50:25) msn: S: NS 000: NLN NLN kjbpalm@hotmail.com 1 Karen 2416181284:2147619840 0
(14:50:25) msn: S: NS 000: UBX kjbpalm@hotmail.com 1 505
(14:50:25) msn: UBX received.
(14:50:25) msn: msn get PSM
(14:50:25) msn: Get CurrentMedia
(14:50:25) msn: No currentmedia string
(14:50:25) msn: Get EndpointData
(14:50:25) msn: S: NS 000: CHG 18 NLN 2416181284:0 0
(14:50:31) msn: S: NS 000: CHL 0 10744683739530307172142054695
(14:50:31) msn: C: NS 000: QRY 19 PROD0119GSJUC$18 32
(14:50:31) msn: S: NS 000: QRY 19
(14:50:57) msn: destroy httpconn (02C2B7F0)
(14:51:03) msn: S: SB 002: MSG kjbpalm@gmail.com Karen 90
(14:51:05) msn: destroy httpconn (02D8B2C8)

If you wait a bit longer (like 4-5 min) then something changes in the MSN server side and as soon as I start typing in the Messenger client, Pidgin receives a RNG notification and the http connection is re-established and messages are received again (for another minute):

(19:04:58) msn: S: NS 000: RNG 136536647 207.46.124.144:1863 CKI 16188200.324209 kjbpalm@gmail.com Karen U messenger.msn.com 1
(19:04:58) msn: new httpconn (0x2c167a00)
(19:04:58) dnsquery: Performing DNS lookup for 207.46.124.144
(19:04:58) msn: C: SB 003: ANS 1 kjbpalm@hotmail.com;{A7744006-9C46-8B3E-4BEA-1C6E9E6D1BE9} 16188200.324209 136536647

There are no errors in the Messenger client to indicate to the sender that nothing is being received, and Pidgin presence is still online, but there is a window of time between 1 and 4-5 min where incoming messages to Pidgin are lost forever.

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!