[Serusers] RE: How does Instant Message work?

[Klaus Darilion]

I had the same experiences with Windows Messenger 5.1. I think there is 
no way tol solve this. Maybe it works setting up an instant message 
session using INVITE-MESSAGE-BYE.

regards,
klaus

Steven Wang wrote:
> 
> -----Original Message-----
> From: xwang at comcast.net [mailto:xu.wang at comcast.net]
> Sent: Friday, December 31, 2004 12:46 PM
> To: serusers at lists.iptel.org
> Subject: How does Instant Message work?
> 
> 
> Hello
> 
> I used 'SER' to send a IM to Messenger. SER gets '200 OK' reply, but
> messenger doesn't show anything. Here is the ngrep's output. Does anyone
> know what the probem is?
> 
> thanks!
> steven
> 
> U 192.168.1.104:5060 -> 192.168.1.103:4139
>   MESSAGE sip:192.168.1.103:4139 SIP/2.0..Max-Forwards: 10..Record-Route
>   : <sip:192.168.1.104;ftag=a707bfce77c9367d1734afac7b3de6ca-e9b8;lr=on>
>   ..Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bK7881.af588177.0..Via: S
>   IP/2.0/UDP 192.168.1.104;rport=5060;branch=z9hG4bK7881.9f588177.0..To:
>    <sip:8668150718 at 192.168.1.104>..From: sip:8016102 at 192.168.1.104;tag=a
>   707bfce77c9367d1734afac7b3de6ca-e9b8..CSeq: 10 MESSAGE..Call-ID: 6ddff
>   bfe-0 at 192.168.1.104..Content-Length: 7..User-Agent: Sip EXpress router
>   (0.10.99-dev0 (i386/linux))..p-version: Astbill-xwang-0.5..Contact: <s
>   ip:admin at 192.168.1.104:5060>..Content-Type: text/plain; charset=UTF-8.
>   .P-hint: fixed NAT contact for request....hello..
> #
> U 192.168.1.103:4139 -> 192.168.1.104:5060
>   SIP/2.0 100 Trying..Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bK7881.
>   af588177.0..Via: SIP/2.0/UDP 192.168.1.104;rport=5060;branch=z9hG4bK78
>   81.9f588177.0..From: sip:8016102 at 192.168.1.104;tag=a707bfce77c9367d173
>   4afac7b3de6ca-e9b8..To: <sip:8668150718 at 192.168.1.104>;tag=a4f9c9853ee
>   54a9783c18ffd41692d06..Call-ID: 6ddffbfe-0 at 192.168.1.104..CSeq: 10 MES
>   SAGE..User-Agent: RTC/1.2..Content-Length: 0....
> #
> U 192.168.1.103:4139 -> 192.168.1.104:5060
>   SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.1.104;branch=z9hG4bK7881.af58
>   8177.0..Via: SIP/2.0/UDP 192.168.1.104;rport=5060;branch=z9hG4bK7881.9
>   f588177.0..From: sip:8016102 at 192.168.1.104;tag=a707bfce77c9367d1734afa
>   c7b3de6ca-e9b8..To: <sip:8668150718 at 192.168.1.104>;tag=a4f9c9853ee54a9
>   783c18ffd41692d06..Call-ID: 6ddffbfe-0 at 192.168.1.104..CSeq: 10 MESSAGE
>   ..Record-Route: <sip:192.168.1.104;ftag=a707bfce77c9367d1734afac7b3de6
>   ca-e9b8;lr=on>..Contact: <sip:192.168.1.103:7110>..User-Agent: RTC/1.2
>   ..Content-Length: 0....
> #
> U 192.168.1.103:4139 -> 192.168.1.104:5060
>   BYE sip:192.168.1.104;ftag=a707bfce77c9367d1734afac7b3de6ca-e9b8;lr=on
>    SIP/2.0..Via: SIP/2.0/UDP 192.168.1.103:7110..Max-Forwards: 70..From:
>    <sip:8668150718 at 192.168.1.104>;tag=a4f9c9853ee54a9783c18ffd41692d06..
>   To: sip:8016102 at 192.168.1.104;tag=a707bfce77c9367d1734afac7b3de6ca-e9b
>   8..Call-ID: 6ddffbfe-0 at 192.168.1.104..CSeq: 1 BYE..Route: <sip:admin at 1
>   92.168.1.104:5060>..User-Agent: RTC/1.2..Content-Length: 0....
> #
> U 192.168.1.104:5060 -> 192.168.1.103:7110
>   SIP/2.0 404 Not Found and no voicemail turned on..Via: SIP/2.0/UDP 192
>   .168.1.103:7110..From: <sip:8668150718 at 192.168.1.104>;tag=a4f9c9853ee5
>   4a9783c18ffd41692d06..To: sip:8016102 at 192.168.1.104;tag=a707bfce77c936
>   7d1734afac7b3de6ca-e9b8..Call-ID: 6ddffbfe-0 at 192.168.1.104..CSeq: 1 BY
>   E..Server: Sip EXpress router (0.10.99-dev0 (i386/linux))..Content-Len
>   gth: 0....
> 
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
> 
>