This is the problem of incompatible Windows Messenger versions. You send a MESSAGE which is accepted (200 OK) but WM does not display it, it sends a BYE instead. This happens when you send a message from WM 4.7 (or serweb) to WM 5.0.
Jan.
On 19-02 13:22, Dee Lowndes wrote:
Update I just realised msn messenger doesn't update to 5 by default but instead goes to 4.7 so I have rectified this.
Users still show as online on the server and offline on clients but when sending message from server it says its sent it but nothing arrives at the client now.
Btw I am putting the server url in messenger as sip:url
Here is the new ngrep output messaging from server to end user.
root@Dev:~# ngrep -qd eth1
U 192.168.0.1:5060 -> 192.168.0.2:7143 MESSAGE sip:192.168.0.2:7143 SIP/2.0..Max-Forwards: 10..Record-Route: <sip:sonko@192.168.0.1;ftag=533cb9e91f4b999cf76861cbb9ed5 4ed-5fb9;lr=on>..Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bKee2d.bf40ee56.0..Via: SIP/2.0/UDP 82.45.234.141;branch=z9hG4bK9448. 1ba3f692.0..To: sip:sonko@dev.asyouneed.com..From: sip:asyouneed@Dev.asyouneed.com;tag=533cb9e91f4b999cf76861cbb9ed54ed-5fb 9. .CSeq: 10 MESSAGE..Call-ID: 47ec783f-19484@127.0.0.1..Content-Length: 6..User-Agent: Sip EXpress router(0.8.12 (i386/linux))..p -version: Web_interface_Karel_Kozlik-0.9..Contact: sip:daemon@192.168.0.1..Content-Type: text/plain; charset=UTF-8....test..
U 192.168.0.2:1333 -> 192.168.0.1:5060 SIP/2.0 100 Trying..Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bKee2d.bf40ee56.0..Via: SIP/2.0/UDP 82.45.234.141;branch=z9hG4bK94 48.1ba3f692.0..From: sip:asyouneed@Dev.asyouneed.com;tag=533cb9e91f4b999cf76861cbb9ed54ed-5fb 9..To: <sip:sonko@dev.asyouneed.co m>;tag=7035a5f245c74540a5eb88c3b0dbc60f..Call-ID: 47ec783f-19484@127.0.0.1..CSeq: 10 MESSAGE..User-Agent: RTC/1.2..Content-Leng th: 0....
U 192.168.0.2:1333 -> 192.168.0.1:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bKee2d.bf40ee56.0..Via: SIP/2.0/UDP 82.45.234.141;branch=z9hG4bK9448.1 ba3f692.0..From: sip:asyouneed@Dev.asyouneed.com;tag=533cb9e91f4b999cf76861cbb9ed54ed-5fb 9..To: sip:sonko@dev.asyouneed.com;t ag=7035a5f245c74540a5eb88c3b0dbc60f..Call-ID: 47ec783f-19484@127.0.0.1..CSeq: 10 MESSAGE..Record-Route: <sip:sonko@192.168.0.1; ftag=533cb9e91f4b999cf76861cbb9ed54ed-5fb9;lr=on>..Contact: sip:192.168.0.2:7143..User-Agent: RTC/1.2..Content-Length: 0....
U 192.168.0.2:1333 -> 192.168.0.1:5060 BYE sip:sonko@192.168.0.1;ftag=533cb9e91f4b999cf76861cbb9ed54ed-5fb9;lr=on SIP/2.0..Via: SIP/2.0/UDP 192.168.0.2:7143..Max-Forw ards: 70..From: sip:sonko@dev.asyouneed.com;tag=7035a5f245c74540a5eb88c3b0dbc60f..To: sip:asyouneed@Dev.asyouneed.com;tag=533 cb9e91f4b999cf76861cbb9ed54ed-5fb9..Call-ID: 47ec783f-19484@127.0.0.1..CSeq: 1 BYE..Route: sip:daemon@192.168.0.1..User-Agent : RTC/1.2..Content-Length: 0....
U 192.168.0.1:5060 -> 192.168.0.2:7143 BYE sip:192.168.0.2:7143 SIP/2.0..Record-Route: sip:sonko@192.168.0.1;ftag=7035a5f245c74540a5eb88c3b0dbc60f;lr=on..Via : SIP/2 .0/UDP 192.168.0.1;branch=z9hG4bK60c9.6994f496.0..Via: SIP/2.0/UDP 192.168.0.2:7143..Max-Forwards: 69..From: <sip:sonko@dev.asy ouneed.com>;tag=7035a5f245c74540a5eb88c3b0dbc60f..To: sip:asyouneed@Dev.asyouneed.com;tag=533cb9e91f4b999cf76861cbb9ed54ed-5fb 9 ..Call-ID: 47ec783f-19484@127.0.0.1..CSeq: 1 BYE..User-Agent: RTC/1.2..Content-Length: 0....
U 192.168.0.2:1333 -> 192.168.0.1:5060 SIP/2.0 481 Call Leg/Transaction Does Not Exist..Via: SIP/2.0/UDP 192.168.0.1;branch=z9hG4bK60c9.6994f496.0..Via: SIP/2.0/UDP 1 92.168.0.2:7143..From: sip:sonko@dev.asyouneed.com;tag=7035a5f245c74540a5eb88c3b0dbc60f..To: sip:asyouneed@Dev.asyouneed.com; tag=533cb9e91f4b999cf76861cbb9ed54ed-5fb9..Call-ID: 47ec783f-19484@127.0.0.1..CSeq: 1 BYE..User-Agent: RTC/1.2..Content-Length: 0....
U 192.168.0.1:5060 -> 192.168.0.2:7143 SIP/2.0 481 Call Leg/Transaction Does Not Exist..Via: SIP/2.0/UDP 192.168.0.2:7143..From: sip:sonko@dev.asyouneed.com;tag=703 5a5f245c74540a5eb88c3b0dbc60f..To: sip:asyouneed@Dev.asyouneed.com;tag=533cb9e91f4b999cf76861cbb9ed54ed-5fb 9..Call-ID: 47ec783f -19484@127.0.0.1..CSeq: 1 BYE..User-Agent: RTC/1.2..Content-Length: 0....
U 192.168.0.2:1245 -> 192.168.0.1:1900 M-SEARCH * HTTP/1.1..HOST: 239.255.255.250:1900..MAN: "ssdp:discover"..MX: 3..ST: urn:schemas-upnp-org:service:WANIPConnection: 1....
I 192.168.0.1 -> 192.168.0.2 3:3 ....E...|.....<............l....M-SEARCH * HTTP/1.1..HOST: 239.255.255.250:1900..MAN: "ssdp:discover"..MX: 3..ST: urn:schemas-u pnp-org:service:WANIPConnection:1....
U 192.168.0.2:1245 -> 192.168.0.1:1900 M-SEARCH * HTTP/1.1..HOST: 239.255.255.250:1900..MAN: "ssdp:discover"..MX: 3..ST: urn:schemas-upnp-org:service:WANPPPConnection :1....
Thanks again,
Dee
-----Original Message----- From: serusers-bounces@iptel.org [mailto:serusers-bounces@lists.iptel.org]
On
Behalf Of Jan Janak Sent: 19 February 2004 11:46 To: Dee Lowndes Cc: serusers@lists.iptel.org Subject: Re: [Serusers] Newbie to Ser
Create SIP message dumps on the server (using ngrep) and send them to us.
Jan.
On 19-02 01:17, Dee Lowndes wrote:
Hi All,
I have been working on this Ser installation for awhile and now have it setup with mysql and ser-web. I am able to instant message
from
the server to the end users but the end users show up as unavailable when trying to message between them.
This is setup on a local (192.168.0.1/24 192.168.1.1/24) network
using
MS Messenger for XP to keep it all simple.
I am now a bit stuck or too tired anyone now of a good link to get
me
further or have an idea where I've gone wrong.
Thanks in advance, Dee
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers