The best way would be to fix the user agent. SER would not know where to
forward the reply if it does not contain Via.
Jan.
On 02-06-2005 10:58, Dominik Schulte wrote:
Hi,
I am struggling with a problem where I have a UA that responds to invites but
does not preserve the original request Via fields. see ngrep capture below.
I can see that SER receives the reply, but drops it because it cannot correlate any
transaction with this response.
I tried to write a module that uses the tm modules callbacks, but it seems that response
messages are dropped by the core.
Is there any way I can validate responses that fall outside any transaction??
#
U 172.17.26.19:5060 -> 172.17.26.178:5060
INVITE sip:dschulte@heat.callsuite.tellumat.co.za SIP/2.0.
Via: SIP/2.0/UDP
172.17.26.19:5060;rport;branch=z9hG4bKE2FD4189B717447BB8192445A851777B.
From: DOMINIKS PC SIP PHONE
<sip:1200@heat.callsuite.tellumat.co.za>;tag=859273871.
To: <sip:dschulte@heat.callsuite.tellumat.co.za>.
Contact: <sip:1200@172.17.26.19:5060>.
Call-ID: AF0EF5B2-5850-4573-A2FF-F1D50A6B2B65(a)172.17.26.19.
CSeq: 656 INVITE.
Max-Forwards: 70.
Content-Type: application/sdp.
User-Agent: X-Lite release 1103m.
Content-Length: 293.
#
U 172.17.26.178:5060 -> 172.17.26.19:5060
SIP/2.0 100 trying -- your call is important to us.
Via: SIP/2.0/UDP
172.17.26.19:5060;rport=5060;branch=z9hG4bKE2FD4189B717447BB8192445A851777B.
From: DOMINIKS PC SIP PHONE
<sip:1200@heat.callsuite.tellumat.co.za>;tag=859273871.
To: <sip:dschulte@heat.callsuite.tellumat.co.za>.
Call-ID: AF0EF5B2-5850-4573-A2FF-F1D50A6B2B65(a)172.17.26.19.
CSeq: 656 INVITE.
Server: Sip EXpress router (0.8.14 (i386/linux)).
Content-Length: 0.
Warning: 392 172.17.26.178:5060 "Noisy feedback tells: pid=17762
req_src_ip=172.17.26.19 req_src_port=5060
in_uri=sip:dschulte@heat.callsuite.tellumat.co.za out_uri=sip:94099:1001@172.17.1.31
via_cnt==1".
.
#
U 172.17.26.178:5060 -> 172.17.1.31:5060
INVITE sip:94099:1001@172.17.1.31 SIP/2.0.
Record-Route: <sip:dschulte@172.17.26.178;ftag=859273871;lr=on>.
Via: SIP/2.0/UDP 172.17.26.178;branch=z9hG4bK33ab.6f0be065.0.
Via: SIP/2.0/UDP
172.17.26.19:5060;rport=5060;branch=z9hG4bKE2FD4189B717447BB8192445A851777B.
From: DOMINIKS PC SIP PHONE
<sip:1200@heat.callsuite.tellumat.co.za>;tag=859273871.
To: <sip:94099@172.17.1.31>>.
Contact: <sip:1200@172.17.26.19:5060>.
Call-ID: AF0EF5B2-5850-4573-A2FF-F1D50A6B2B65(a)172.17.26.19.
CSeq: 656 INVITE.
Max-Forwards: 69.
Content-Type: application/sdp.
User-Agent: X-Lite release 1103m.
Content-Length: 293.
#
U 172.17.1.31:5060 -> 172.17.26.178:5060
SIP/2.0 100 Trying.
Via: SIP/2.0/UDP 172.17.26.178.
`From: DOMINIKS PC SIP PHONE
<sip:1200@heat.callsuite.tellumat.co.za>;tag=859273871.
To: <sip:94099@172.17.1.31>;tag=viper94099.
Call-ID: AF0EF5B2-5850-4573-A2FF-F1D50A6B2B65(a)172.17.26.19.
CSeq: 656 INVITE.
Content-Length: 0.
.
#
U 172.17.1.31:5060 -> 172.17.26.178:5060
SIP/2.0 180 Ringing.
Via: SIP/2.0/UDP 172.17.26.178.
From: DOMINIKS PC SIP PHONE
<sip:1200@heat.callsuite.tellumat.co.za>;tag=859273871.
To: "" <sip:94099@172.17.1.31>;tag=viper94099.
Call-ID: AF0EF5B2-5850-4573-A2FF-F1D50A6B2B65(a)172.17.26.19.
CSeq: 656 INVITE.
Content-Length: 0.
.
#
U 172.17.26.178:5060 -> 172.17.1.31:5060
INVITE sip:94099:1001@172.17.1.31 SIP/2.0.
Record-Route: <sip:dschulte@172.17.26.178;ftag=859273871;lr=on>.
Via: SIP/2.0/UDP 172.17.26.178;branch=z9hG4bK33ab.6f0be065.0.
Via: SIP/2.0/UDP
172.17.26.19:5060;rport=5060;branch=z9hG4bKE2FD4189B717447BB8192445A851777B.
From: DOMINIKS PC SIP PHONE
<sip:1200@heat.callsuite.tellumat.co.za>;tag=859273871.
To: <sip:94099@172.17.1.31>>.
Contact: <sip:1200@172.17.26.19:5060>.
Call-ID: AF0EF5B2-5850-4573-A2FF-F1D50A6B2B65(a)172.17.26.19.
CSeq: 656 INVITE.
Max-Forwards: 69.
Content-Type: application/sdp.
User-Agent: X-Lite release 1103m.
Content-Length: 293.
**********************************************************************
Relevant company disclaimers are available at the following addresses:
Tellumat (Pty) Ltd e-mail: mailto:disclaimer@tellumat.com?Subject=Tellumat_Disclaimer
Web:
http://www.tellumat.com/email.aspx
**********************************************************************
_______________________________________________
Serdev mailing list
serdev(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serdev