Hello,

Me and other user are both on-line as seen from the output of the serctl showdb command:

[root@messenger src]# serctl showdb

+----------+-----------------------+-----------------------------------------------------+

| username | email_address | callid |

+----------+-----------------------+-----------------------------------------------------+

| gpd | gpd@maltanet.net | d165527c67a94651b99abc963c7778f2@194.158.38.175 |

| wilhelm | wilhelm@maltanet.net | ad0daa7e6e14410eb54485249c17c262@194.158.38.149 |

+----------+-----------------------+-----------------------------------------------------+

Note: Due to usage of cache, server's list may differ from DB list.

However when I try to send a message I get:

The following message could not be delivered to all recipients

The following is the output log using ngrep.

U 194.158.38.149:3458 -> 194.158.35.3:5060

INVITE sip:gpd@maltanet.net SIP/2.0..Via: SIP/2.0/UDP 194.158.38.149:10450..Max-Forwards: 70..From: "wilhelm@maltanet.net" <sip

:wilhelm@maltanet.net>;tag=57fc9d1e5a314be5a0f6d306f7acdc4a;epid=7a0b198ecd..To: <sip:gpd@maltanet.net>..Call-ID: 86b56c443a1e4

decb9523580851bda50@194.158.38.149..CSeq: 1 INVITE..Contact: <sip:194.158.38.149:10450>..User-Agent: RTC/1.2..Content-Type: app

lication/sdp..Content-Length: 109....v=0..o=- 0 0 IN IP4 194.158.38.149..s=session..c=IN IP4 194.158.38.149..t=0 0..m=x-ms-mess

age 5060 sip null..

U 194.158.35.3:5060 -> 194.158.38.149:10450

SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 194.158.38.149:10450..From: "wilhelm@maltanet.net" <sip:wi

lhelm@maltanet.net>;tag=57fc9d1e5a314be5a0f6d306f7acdc4a;epid=7a0b198ecd..To: <sip:gpd@maltanet.net>..Call-ID: 86b56c443a1e4dec

b9523580851bda50@194.158.38.149..CSeq: 1 INVITE..Server: Sip EXpress router (0.8.12 (i386/linux))..Content-Length: 0..Warning:

392 194.158.35.3:5060 "Noisy feedback tells: pid=15398 req_src_ip=194.158.38.149 req_src_port=3458 in_uri=sip:gpd@maltanet.net

out_uri=sip:194.158.38.175:14487 via_cnt==1"....

U 194.158.35.3:5060 -> 194.158.38.175:14487

INVITE sip:194.158.38.175:14487 SIP/2.0..Via: SIP/2.0/UDP 194.158.35.3;branch=z9hG4bKcbaa.ead71c41.0..Via: SIP/2.0/UDP 194.158.

38.149:10450..Max-Forwards: 69..From: "wilhelm@maltanet.net" <sip:wilhelm@maltanet.net>;tag=57fc9d1e5a314be5a0f6d306f7acdc4a;ep

id=7a0b198ecd..To: <sip:gpd@maltanet.net>..Call-ID: 86b56c443a1e4decb9523580851bda50@194.158.38.149..CSeq: 1 INVITE..Contact: <

sip:194.158.38.149:10450>..User-Agent: RTC/1.2..Content-Type: application/sdp..Content-Length: 109....v=0..o=- 0 0 IN IP4 194.1

58.38.149..s=session..c=IN IP4 194.158.38.149..t=0 0..m=x-ms-message 5060 sip null..

U 194.158.38.175:1703 -> 194.158.35.3:5060

SIP/2.0 100 Trying..Via: SIP/2.0/UDP 194.158.35.3;branch=z9hG4bKcbaa.ead71c41.0..Via: SIP/2.0/UDP 194.158.38.149:10450..From: "

wilhelm@maltanet.net" <sip:wilhelm@maltanet.net>;tag=57fc9d1e5a314be5a0f6d306f7acdc4a;epid=7a0b198ecd..To: <sip:gpd@maltanet.ne

t>;tag=fb29a56813ed466eb8a67d41f16a7deb..Call-ID: 86b56c443a1e4decb9523580851bda50@194.158.38.149..CSeq: 1 INVITE..User-Agent:

RTC/1.2..Content-Length: 0....

U 194.158.38.175:1703 -> 194.158.35.3:5060

SIP/2.0 200 OK..Via: SIP/2.0/UDP 194.158.35.3;branch=z9hG4bKcbaa.ead71c41.0..Via: SIP/2.0/UDP 194.158.38.149:10450..From: "wilh

elm@maltanet.net" <sip:wilhelm@maltanet.net>;tag=57fc9d1e5a314be5a0f6d306f7acdc4a;epid=7a0b198ecd..To: <sip:gpd@maltanet.net>;t

ag=fb29a56813ed466eb8a67d41f16a7deb..Call-ID: 86b56c443a1e4decb9523580851bda50@194.158.38.149..CSeq: 1 INVITE..Contact: <sip:19

4.158.38.175:14487>..User-Agent: RTC/1.2..Content-Type: application/sdp..Content-Length: 109....v=0..o=- 0 0 IN IP4 194.158.38.

175..s=session..c=IN IP4 194.158.38.175..t=0 0..m=x-ms-message 5060 sip null..

U 194.158.35.3:5060 -> 194.158.38.149:10450

SIP/2.0 200 OK..Via: SIP/2.0/UDP 194.158.38.149:10450..From: "wilhelm@maltanet.net" <sip:wilhelm@maltanet.net>;tag=57fc9d1e5a31

4be5a0f6d306f7acdc4a;epid=7a0b198ecd..To: <sip:gpd@maltanet.net>;tag=fb29a56813ed466eb8a67d41f16a7deb..Call-ID: 86b56c443a1e4de

cb9523580851bda50@194.158.38.149..CSeq: 1 INVITE..Contact: <sip:194.158.38.175:14487>..User-Agent: RTC/1.2..Content-Type: appli

cation/sdp..Content-Length: 109....v=0..o=- 0 0 IN IP4 194.158.38.175..s=session..c=IN IP4 194.158.38.175..t=0 0..m=x-ms-messag

e 5060 sip null..

When using Windows Messenger 4.7.2009 I was working fine, however now that I installed SP2 you cannot work using 4.7.2009, you must install messenger 5.

From a google search it seems that there are a number of users who experience the same problem, one particular links states difference between messenger 4.7 and 5.

http://www.mail-archive.com/sip-implementors@cs.columbia.edu/msg05848.html

I have noticed that the Windows Messenger 5.0 client expects to receive an INVITE message before it will accept a MESSAGE message from another client. This is a bit problematic, as it is not how many other clients behave (even Windows Messenger 4.7 does not do this). However, in lieu of just complaining about it, I'm trying to get around this behaviour.

By the way the strange thing is that sometimes I manage to send messages.

Also it seems that I experience presence problems as well. Contacts who are registered to the server are not seen on-line.

Thank you,

Wil