search

TReKiE / msnp-sharp

Automatically exported from code.google.com/p/msnp-sharp
0 stars 0 forks source link

Cannot send message to Yahoo contact. #52

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Sign in to MSN with example client.
2. Send message to Yahoo contact.
3.

What is the expected output? What do you see instead?
Contact joined conversation (CAL command sent, RNG etc.)

What version of the product are you using? On what operating system?
v_251 on Windows Vista Business 32-bit.

Please provide any additional information below.
See attached file for trace log.
It starts at the point where a switchboard session is requested (XFR SB).

Original issue reported on code.google.com by Andre.du...@gmail.com on 27 Nov 2008 at 2:33

Attachments:

GoogleCodeExporter commented 9 years ago 
"Contact joined conversation (CAL command sent, RNG etc.)"

The YIM Message won't send these, it's handled in a different way.
Are you sure the YIM user is online when the message sends to it?

Original comment by freezing...@gmail.com on 27 Nov 2008 at 3:45

GoogleCodeExporter commented 9 years ago 
Actually, UBM command is a payload command. No need to create a handler for it 
CAL,
RNG etc. A yahoo user can be offline and UBM sends it when user offline. So, 
there is
no need to create a SB.

Original comment by hepha...@gmail.com on 27 Nov 2008 at 3:50

GoogleCodeExporter commented 9 years ago 
@freezingsoft Yes; I am sure the YIM user is online.  I have both clients 
(YIM/MSNP#) 
open on my machine.
@hephappy Thanks.  I am not an expert on MSNP (yet); so I'll have to read up 
what 
that means exactly and what the expected sequence of command/response should be 
:)

What is interesting to me is that messaging from YIM to MSNP# client works; but 
not 
vv.  Guess I can check the WireShark logs for the successful (YIM:MSNP#) 
messaging 
and compare that with the unsuccessful messaging (MSNP#:YIM).

Thanks for the replies.

Original comment by Andre.du...@gmail.com on 27 Nov 2008 at 5:55

GoogleCodeExporter commented 9 years ago 
OK, I know what's wrong with it. Just wait for my fix.

Original comment by freezing...@gmail.com on 27 Nov 2008 at 7:27

GoogleCodeExporter commented 9 years ago 
Wow; you guys work quick ;).
Thanks.

Original comment by Andre.du...@gmail.com on 27 Nov 2008 at 7:31

GoogleCodeExporter commented 9 years ago 
Try the code in /trunk/MSNP-Sharp15, I think it can work, but need test 
carefully.

Original comment by freezing...@gmail.com on 28 Nov 2008 at 8:08

GoogleCodeExporter commented 9 years ago 
OK; will do.

Original comment by Andre.du...@gmail.com on 29 Nov 2008 at 3:33

GoogleCodeExporter commented 9 years ago 
But, wait. I will change the design, current Conversation design looks freaky.

Original comment by freezing...@gmail.com on 29 Nov 2008 at 3:52

GoogleCodeExporter commented 9 years ago 
OK. A side question though : How does your source layout work? /trunk is for 
latest 
HEAD revision; /tags for released versions and /branches ... well for branches. 

Right? So; /trunk/MSNP-Sharp15 relates to which version?

Good luck ;)

Original comment by Andre.du...@gmail.com on 29 Nov 2008 at 4:07

GoogleCodeExporter commented 9 years ago 
Trunk relates to the current working version (The unstable developing version)
Branches are the latest stable versions we had released (bug fix for /tags).
And, tags are the first release versions (maybe after releasing, we found bugs, 
then 
we will fix them in /branches).

Original comment by freezing...@gmail.com on 29 Nov 2008 at 5:47

GoogleCodeExporter commented 9 years ago 
So; /trunk/MSNP-Sharp15 is /trunk/MSNPSHARP_DEV :) Sure, it is MSNP18 
MSNP-Sharp18...

After tested this bug, Pang will merge it to 25_STABLE branch.

Original comment by hepha...@gmail.com on 29 Nov 2008 at 9:00

GoogleCodeExporter commented 9 years ago

Original comment by hepha...@gmail.com on 29 Nov 2008 at 9:04

GoogleCodeExporter commented 9 years ago 
Thanks.  Will watch the updates.

Original comment by Andre.du...@gmail.com on 2 Dec 2008 at 9:42

GoogleCodeExporter commented 9 years ago 
hi,
  I won't merge the changes of Conversation to the 2.5.x because there are some
design problem (If I do so, I need to merge the dev version in trunk to 2.5). 
And, by
the way, I am getting busy again, so the update may delay.

Original comment by freezing...@gmail.com on 3 Dec 2008 at 11:02

GoogleCodeExporter commented 9 years ago 
OK; no problem.  Thanks for the update.
I'll stick with 2.5.1 release until further notice.

Original comment by Andre.du...@gmail.com on 3 Dec 2008 at 6:45

GoogleCodeExporter commented 9 years ago 
New design updated.

Original comment by freezing...@gmail.com on 10 Dec 2008 at 5:03