RE: [Serusers] problem with IM b/w windows messenger 4.7 and 5.0

Rao, I have had one issue with with MS Windows Messenger 5.0, and that is the list of contacts updating when they come online. Other than that I can make a call to them if I enter their login directly. What I use for captures is ethereal - www.ethereal.com Decode support for SIP is not builtin. Scott Morris Enterprise Network Engineer DOE - ORAU / ORISE 865-576-4672 -----Original Message----- From: Rao [mailto:rao_ser@yahoo.com] Sent: Monday, March 29, 2004 3:33 PM To: Jan Janak Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] problem with IM b/w windows messenger 4.7 and 5.0 Jan, Ralph and Daniel thanks for your responses. Here is some more calrification. 1) I am using windows messaeger 5.0 and MSN messenger. 2) The link Ralph provided only works for wondows XP. On one of my machines I am running windows 2000 and would like to see IM work on win2K. I cannot find IM 4.7 for any version of windows except XP. 3) I can not get IM to work even when both machines are running messenger 5.0. Seems to be the same issue when one is running 4.7 i.e. maddr in route header is being ignored and ser tries to deliver it to the local machine and tcp connect fails. Has any one made IM to work b/w MM 5.0 Following is a trace of a SIP message request that has maddr in the Route request. Let me know if more traces are needed. So I have following questions 1) Can there be an maddr parameter in the Route header ? Cannot find an answer in RFC 3261. 2) In any case why can't we fix ser to interpret maddr. windows OS is probably the most important OS with which ser needs to support. 3) What is a better utility than ngrep to get traces which are better formatted. I have seen folks post very nicely formatted traces, what are they using. Let me know if I need to post these questions on the development list. Regards. Rao. ## T 129.150.32.27:1064 -> 129.146.175.207:5060 [AP] MESSAGE sip:rao-toshiba@129.146.175.207; ftag=3b3b0bff72424892aa8e78d5bbf3a316;lr=on SIP/2.0..Via: SIP/2.0/TCP 129.150.32.27:7685.. From: <sip:rao-toshiba@sipserver>; tag=6d5db818-3a2a-40b3-b919-5cd06b18d8e9.. To: "rao-sony@sipserver" <sip:rao-sony@sipserver>; tag=3b3b0bff72424892aa8e78d5bbf3a316; epid=8bb54d4c1b.. Call-ID: 72452f0ccee6437193a271e057d52725(a)129.146.85.163.. CSeq: 4 MESSAGE..Route:<sip:rao-sony@sipserver:13395; maddr=129.146.85.163;transport=tcp>.. Contact: <sip:129.150.32.27:7685;transport=tcp>..' User-Agent: Windows RTC/1.0..Content-Type: text/plain; charset=UTF-8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA9AE0AU wA lADIAMABTAGgAZQBsAGwAJQAyADAARABsAGcAOwAgAEUARgA9ADsAIABDAE8APQAwADsAIABDAFM AP QAwADsAIABQAEYAPQAwAA0ACgANAAoA..Content-Length: 20....sending from toshiba # T 129.146.175.207:5060 -> 129.150.32.27:1064 [AP] SIP/2.0 477 Unfortunately error on sending to next hop occured (477/TM).. Via: SIP/2.0/TCP 129.150.32.27:7685.. From: <sip:rao-toshiba@sipserver>; tag=6d5db818-3a2a-40b3-b919-5cd06b18d8e9.. To: "rao-sony@sipserver" <sip:rao-sony@sipserver>; tag=3b3b0bff72424892aa8e78d5bbf3a316;epid=8bb54d4c1b.. Call-ID: 72452f0ccee6437193a271e057d52725(a)129.146.85.163.. CSeq: 4 MESSAGE..Server: Sip EXpress router (0.8.12 (sparc64/solaris)).. Content-Length: 0.... # __________________________________ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers