<DIV id=RTEContent>I have two window messenger 5.1 clients on the same subnet as the SER server w/ pa module. They subscribe/notify to each other ok. HOwever they cannot IM each other. The callee, after receiveing INVITE, sent back a 100 trying, then 200 OK, and then immediately BYE. </DIV>  <DIV>&nbsp;</DIV>  <DIV>I searched thru archives and looks like this is a known issue with wm. What is the solution or workaround to this?</DIV>  <DIV>&nbsp;</DIV>  <DIV>Here is the messages I captured:</DIV>  <DIV>&nbsp;</DIV>  <DIV>U 10.1.104.251:1172 -&gt; 10.1.104.254:5060<BR>&nbsp; INVITE sip:104pc1@10.1.104.254 SIP/2.0..Via: SIP/2.0/UDP 10.1.104.251:8053<BR>&nbsp; ..Max-Forwards: 70..From: "<A href="mailto:104pc2@10.1.104.254">104pc2@10.1.104.254</A>" &lt;sip:104pc2@10.1.104.254&gt;;<BR>&nbsp; tag=d46c61cfc8bf4ae4942b0e9c2a2f38d7;epid=69200d1362..To: &lt;sip:104pc1@10.1<BR>&nbsp; .104.254&gt;..Call-ID: 7dc26db0eb374cedbfa098d8fb7e2796..CSeq: 1 INVITE..Cont<BR>&nbsp; act:
 &lt;sip:10.1.104.251:8053&gt;..User-Agent: RTC/1.3..Content-Type: applicati<BR>&nbsp; on/sdp..Content-Length: 119....v=0..o=- 0 0 IN IP4 10.1.104.251..s=session<BR>&nbsp; ..c=IN IP4 10.1.104.251..t=0 0..m=message 5060 sip sip:104pc2@10.1.104.254<BR>&nbsp; ..<BR>#<BR>U 10.1.104.254:5060 -&gt; 10.1.104.251:8053<BR>&nbsp; SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 10.1.<BR>&nbsp; 104.251:8053..From: "<A href="mailto:104pc2@10.1.104.254">104pc2@10.1.104.254</A>" &lt;sip:104pc2@10.1.104.254&gt;;tag=d4<BR>&nbsp; 6c61cfc8bf4ae4942b0e9c2a2f38d7;epid=69200d1362..To: &lt;sip:104pc1@10.1.104.2<BR>&nbsp; 54&gt;..Call-ID: 7dc26db0eb374cedbfa098d8fb7e2796..CSeq: 1 INVITE..Server: Si<BR>&nbsp; p EXpress router (0.10.99-dev30-tm-timers-pa-3 (i386/linux))..Content-Leng<BR>&nbsp; th: 0..Warning: 392 10.1.104.254:5060 "Noisy feedback tells:&nbsp; pid=23866 re<BR>&nbsp; q_src_ip=10.1.104.251 req_src_port=1172 in_uri=sip:104pc1@10.1.104.254 out<BR>&nbsp;
 _uri=sip:10.1.104.248:13018 via_cnt==1"....<BR>#<BR>U 10.1.104.254:5060 -&gt; 10.1.104.248:13018<BR>&nbsp; INVITE sip:10.1.104.248:13018 SIP/2.0..Record-Route: &lt;sip:10.1.104.254;fta<BR>&nbsp; g=d46c61cfc8bf4ae4942b0e9c2a2f38d7;lr=on&gt;..Via: SIP/2.0/UDP 10.1.104.254;b<BR>&nbsp; ranch=z9hG4bK2216.fea17c01.0..Via: SIP/2.0/UDP 10.1.104.251:8053..Max-Forw<BR>&nbsp; ards: 16..From: "<A href="mailto:104pc2@10.1.104.254">104pc2@10.1.104.254</A>" &lt;sip:104pc2@10.1.104.254&gt;;tag=d46c61<BR>&nbsp; cfc8bf4ae4942b0e9c2a2f38d7;epid=69200d1362..To: &lt;sip:104pc1@10.1.104.254&gt;.<BR>&nbsp; .Call-ID: 7dc26db0eb374cedbfa098d8fb7e2796..CSeq: 1 INVITE..Contact: &lt;sip:<BR>&nbsp; 10.1.104.251:8053&gt;..User-Agent: RTC/1.3..Content-Type: application/sdp..Co<BR>&nbsp; ntent-Length: 119..P-hint: usrloc applied....v=0..o=- 0 0 IN IP4 10.1.104.<BR>&nbsp; 251..s=session..c=IN IP4 10.1.104.251..t=0 0..m=message 5060 sip sip:104pc<BR>&nbsp; <A
 href="mailto:2@10.1.104.254">2@10.1.104.254</A>..<BR>#<BR>U 10.1.104.248:1334 -&gt; 10.1.104.254:5060<BR>&nbsp; SIP/2.0 100 Trying..Via: SIP/2.0/UDP 10.1.104.254;branch=z9hG4bK2216.fea17<BR>&nbsp; c01.0..Via: SIP/2.0/UDP 10.1.104.251:8053..From: "<A href="mailto:104pc2@10.1.104.254">104pc2@10.1.104.254</A>" &lt;si<BR>&nbsp; p:104pc2@10.1.104.254&gt;;tag=d46c61cfc8bf4ae4942b0e9c2a2f38d7;epid=69200d136<BR>&nbsp; 2..To: &lt;sip:104pc1@10.1.104.254&gt;;tag=36f889ef11354d12890edd7a068dc893..Cal<BR>&nbsp; l-ID: 7dc26db0eb374cedbfa098d8fb7e2796..CSeq: 1 INVITE..User-Agent: RTC/1.<BR>&nbsp; 3..Content-Length: 0....<BR>#<BR>U 10.1.104.248:1334 -&gt; 10.1.104.254:5060<BR>&nbsp; SIP/2.0 200 OK..Via: SIP/2.0/UDP 10.1.104.254;branch=z9hG4bK2216.fea17c01.<BR>&nbsp; 0..Via: SIP/2.0/UDP 10.1.104.251:8053..From: "<A href="mailto:104pc2@10.1.104.254">104pc2@10.1.104.254</A>" &lt;sip:10<BR>&nbsp; <A
 href="mailto:4pc2@10.1.104.254>;tag=d46c61cfc8bf4ae4942b0e9c2a2f38d7;epid=69200d1362..T">4pc2@10.1.104.254&gt;;tag=d46c61cfc8bf4ae4942b0e9c2a2f38d7;epid=69200d1362..T</A><BR>&nbsp; o: &lt;sip:104pc1@10.1.104.254&gt;;tag=36f889ef11354d12890edd7a068dc893..Call-ID<BR>&nbsp; : 7dc26db0eb374cedbfa098d8fb7e2796..CSeq: 1 INVITE..Record-Route: &lt;sip:10.<BR>&nbsp; 1.104.254;ftag=d46c61cfc8bf4ae4942b0e9c2a2f38d7;lr=on&gt;..Contact: &lt;sip:10.1<BR>&nbsp; .104.248:13018&gt;..User-Agent: RTC/1.3..Content-Type: application/sdp..Conte<BR>&nbsp; nt-Length: 119....v=0..o=- 0 0 IN IP4 10.1.104.248..s=session..c=IN IP4 10<BR>&nbsp; .1.104.248..t=0 0..m=message 5060 sip sip:104pc1@10.1.104.254..<BR>#<BR>U 10.1.104.248:1334 -&gt; 10.1.104.254:5060<BR>&nbsp; BYE sip:10.1.104.254;ftag=d46c61cfc8bf4ae4942b0e9c2a2f38d7;lr=on SIP/2.0..<BR>&nbsp; Via: SIP/2.0/UDP 10.1.104.248:13018..Max-Forwards: 70..From: &lt;sip:104pc1@1<BR>&nbsp; 0.1.104.254&gt;;tag=36f889ef11354d12890edd7a068dc893..To: "<A
 href="mailto:104pc2@10.1.104.25">104pc2@10.1.104.25</A><BR>&nbsp; 4" &lt;sip:104pc2@10.1.104.254&gt;;tag=d46c61cfc8bf4ae4942b0e9c2a2f38d7;epid=692<BR>&nbsp; 00d1362..Call-ID: 7dc26db0eb374cedbfa098d8fb7e2796..CSeq: 1 BYE..Route: &lt;s<BR>&nbsp; ip:10.1.104.251:8053&gt;..User-Agent: RTC/1.3..Content-Length: 0....<BR>##<BR></DIV>