I'm afraid I am then not aware of any way how to make Messenger work the way it should (except asking the vendor to fix it).
given that interoperability in 5.0 is very questionable, and there are apparently some 5.0-to-5.0 issues [*], downgrading to 4.x may be a safer choice. (I'm serious.)
-jiri
[*] I have no slightest idea why the responding UA both agrees to have a session with 200 and terminates it with BYE. Did you apply the settings mentioned bellow on the recepient's side? Have you tried to turn modparam("rr", "enable_full_lr", ... on and off? (someone told me that 4.x love full_lr whereas 5.x hate it). If that does not help either, could you try turning record routing off (commenting the line with record_route() in SER config)? That's all just silly ideas how to make Messenger happy, the principal place to fix or replace with something else is Messenger.
At 02:08 AM 10/30/2003, Rork, Joseph (J.P.) wrote:
There is no 4.7 involved. The problem exists on strickly a 5.0 to 5.0 basis.
-----Original Message----- From: Jiri Kuthan [mailto:jiri@iptel.org] Sent: Wednesday, October 29, 2003 7:36 PM To: Rork, Joseph (J.P.); 'serusers@lists.iptel.org' Subject: Re: [Serusers] Messenger5.0 481 Error continued
That's a one-way trick to make 5.0 accept 4.7's instant messages. There is no way to make 4.7 or other standard-based implementation understand 5.0's proprietary messaing model (sending INVITEs to establish a messaging session).
-jiri
At 04:05 PM 10/28/2003, Rork, Joseph (J.P.) wrote:
I've followed the instructions: Attention: instant messaging model has changed from 4.7 to 5.0 dramatically and in a non-standard way. 5.0 takes session establishement using INVITE and drops out-of-dialog MESSAGEs on the floor, whereas sending "481 Call Leg/Transaction...". To permit them, apply the following registry setting: HighSecurityMode HKLM\Software\Policies\Microsoft\Messenger\Client{83D4679F-B6D7-11D2-BF36-0 0C04FB90A03}_Default\EnableSIPHighSecurityMode DWORD= 0 -- Low Security 1 -- High Security 2(Default, same as not set) --- Medium security You need set it to 0 in order to make peer-to-peer IM. Since WM4.7 client is not registered in the LCS server, I guess that WM5 treats it as peer-to-peer call.
And I'm still getting the following error: <<messenger5dump>>
Any ideas?
--joe
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
-- Jiri Kuthan http://iptel.org/~jiri/
Jiri Kuthan writes:
I'm afraid I am then not aware of any way how to make Messenger work the way it should (except asking the vendor to fix it).
also, i read yesterday that microsoft will pull windows messenger 5.0 out from xp in the next service pack. so i suggest that you don't waste your time with messenger or microsoft.
-- juha