That is because of WM dealing with loose routing. It does not like only lr parameter ... you have to set enable_full_lr parameter of RR module to 1. See readme for rr module: http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/rr/README?r...
Try again.
Daniel
Igor Boguslavsky wrote:
Daniel,
I changed the timeouts as per your suggestion. When I send the message from JAM -> WM I still get no messages (the ngrep output is below). First off, there is obviously a duplicate message being send there. Then, the 400 comes back from WM client. What gives?
Igor
U 144.14.255.145:5060 -> 144.14.62.75:12157 MESSAGE sip:144.14.62.75:12157 SIP/2.0..Record-Route: <sip:igorb@144.14.255.145;ftag=a5a3ce0e783e6e6de506638e4c2bc736-20 4a;lr>..Via: SIP/2.0/UDP 144.14.255.145;branch=z9hG4bK8dcb.214ce0e2.0..Via: SIP/2.0/UDP 144.14.255.145;branch=z9hG4bK7e1 7.0bd7c7b5.0..To: sip:igorb@piias12.ms.com..From: sip:igorb*jamny1@sait661;tag=a5a3ce0e783e6e6de506638e4c2bc736-204a.. CSeq: 10 MESSAGE..Call-ID: 5fbc9eb5-11089@144.14.255.145..Content-Length: 3..User-Agent: Sip EXpress router(0.8.12dev-t1 1 (i386/linux))..Content-Type: text/plain..Contact: sip:igorb*jamny1@sait661....zxc # U 144.14.255.145:5060 -> 144.14.62.75:12157 MESSAGE sip:144.14.62.75:12157 SIP/2.0..Record-Route: <sip:igorb@144.14.255.145;ftag=a5a3ce0e783e6e6de506638e4c2bc736-20 4a;lr>..Via: SIP/2.0/UDP 144.14.255.145;branch=z9hG4bK8dcb.214ce0e2.0..Via: SIP/2.0/UDP 144.14.255.145;branch=z9hG4bK7e1 7.0bd7c7b5.0..To: sip:igorb@piias12.ms.com..From: sip:igorb*jamny1@sait661;tag=a5a3ce0e783e6e6de506638e4c2bc736-204a.. CSeq: 10 MESSAGE..Call-ID: 5fbc9eb5-11089@144.14.255.145..Content-Length: 3..User-Agent: Sip EXpress router(0.8.12dev-t1 1 (i386/linux))..Content-Type: text/plain..Contact: sip:igorb*jamny1@sait661....zxc # U 144.14.62.75:1555 -> 144.14.255.145:5060 SIP/2.0 400 Bad Request..Via: SIP/2.0/UDP 144.14.255.145;branch=z9hG4bK8dcb.214ce0e2.0..Via: SIP/2.0/UDP 144.14.255.145; branch=z9hG4bK7e17.0bd7c7b5.0..From: sip:igorb*jamny1@sait661;tag=a5a3ce0e783e6e6de506638e4c2bc736-204a..To: sip:igorb @piias12.ms.com;tag=6810f81b-2264-4a2a-8c11-f4002710fb62..Call-ID: 5fbc9eb5-11089@144.14.255.145..CSeq: 10 MESSAGE..User -Agent: Windows RTC/1.0..Content-Length: 0....
Daniel-Constantin Mierla wrote:
When that value is 1 the Jabber connection is going to be closed, it has expired. The cache_time specifies the time to keep a jabber connection open if there is no traffic through it, when that time expires the connection is closed. Otherwise, if a message is not successfully delivered to SIP user then the jabber connection is closed, too. Watch your network traffic (using ngrep, tcpdump or ethereal) to see if any SIP request from Jabber gateway is launched on wire and whether it gets a non 2xx reply code or not.
Best regards, Daniel
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers