19 Dec
2009
19 Dec
'09
5:54 a.m.
andrei,
i made the exactly same test with kamailio 1.5 and it does send the ack
to 200 ok to the same ip/port as invite. i don't know how that is
possible when you say you have read the code and there is no difference,
but that is what is happening.
wireshark output is below.
but as i told in my previous reply, the new tm module param would be
fine with me. i don't care how it is made to work as long as it works.
-- juha
----------------------------------------------------------------------------
No. Time Source Destination Protocol Info
1 12:37:47.970568 192.98.101.34 192.98.100.132 SIP/SDP Request:
INVITE sip:jh@192.168.0.169:5074, with session description
Frame 1 (594 bytes on wire, 594 bytes captured)
Ethernet II, Src: Micro-St_12:9c:1f (00:0c:76:12:9c:1f), Dst: D-Link_a1:05:85
(00:1b:11:a1:05:85)
Internet Protocol, Src: 192.98.101.34 (192.98.101.34), Dst: 192.98.100.132
(192.98.100.132)
User Datagram Protocol, Src Port: sip (5060), Dst Port: 65023 (65023)
Session Initiation Protocol
Request-Line: INVITE sip:jh@192.168.0.169:5074 SIP/2.0
Message Header
Via: SIP/2.0/UDP 192.98.101.34;branch=z9hG4bKe9f7.475deca2.0
To: <sip:jh@openxg.com>
From: <sip:click2dial@openxg.com>;tag=4b2cacfbec47f
CSeq: 1 INVITE
Call-ID: 4b2cacfbec47f(a)openxg.com
Content-Length: 131
User-Agent: Kamailio (1.5.3-tls (i386/linux))
Contact: <sip:click2dial@192.98.101.34:5060>
Reject-Contact: *;automata="YES"
Content-Type: application/sdp
Message Body
No. Time Source Destination Protocol Info
5 12:37:56.154785 192.98.100.132 192.98.101.34 SIP/SDP Status: 200
OK, with session description
Frame 5 (694 bytes on wire, 694 bytes captured)
Ethernet II, Src: D-Link_a1:05:85 (00:1b:11:a1:05:85), Dst: Micro-St_12:9c:1f
(00:0c:76:12:9c:1f)
Internet Protocol, Src: 192.98.100.132 (192.98.100.132), Dst: 192.98.101.34
(192.98.101.34)
User Datagram Protocol, Src Port: 65023 (65023), Dst Port: sip (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 200 OK
Message Header
Via: SIP/2.0/UDP 192.98.101.34;branch=z9hG4bKe9f7.475deca2.0
To: <sip:jh@openxg.com>;tag=tnemc
From: <sip:click2dial@openxg.com>;tag=4b2cacfbec47f
Call-ID: 4b2cacfbec47f(a)openxg.com
CSeq: 1 INVITE
Contact: <sip:jh@192.168.0.169:5074>
Content-Type: application/sdp
Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE
Server: Twinkle/1.3.2
Supported: replaces,norefersub
Content-Length: 208
Message Body
No. Time Source Destination Protocol Info
6 12:37:56.154959 192.98.101.34 192.98.100.132 SIP Request: ACK
sip:jh@192.168.0.169:5074
Frame 6 (354 bytes on wire, 354 bytes captured)
Ethernet II, Src: Micro-St_12:9c:1f (00:0c:76:12:9c:1f), Dst: D-Link_a1:05:85
(00:1b:11:a1:05:85)
Internet Protocol, Src: 192.98.101.34 (192.98.101.34), Dst: 192.98.100.132
(192.98.100.132)
User Datagram Protocol, Src Port: sip (5060), Dst Port: 65023 (65023)
Session Initiation Protocol
Request-Line: ACK sip:jh@192.168.0.169:5074 SIP/2.0
Message Header
Via: SIP/2.0/UDP 192.98.101.34;branch=z9hG4bKe9f7.475deca2.0
From: <sip:click2dial@openxg.com>;tag=4b2cacfbec47f
Call-ID: 4b2cacfbec47f(a)openxg.com
To: <sip:jh@openxg.com>;tag=tnemc
CSeq: 1 ACK
User-Agent: Kamailio (1.5.3-tls (i386/linux))
Content-Length: 0