<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
not sure you mean transaction as used inside kamailio (tm module),
but a SIP transaction doesn't have anything to do with routing.
Kamailio will be able to route requests/replies even when not
creating transactions (i.e., when it is stateless forwarding).<br>
<br>
It looks like you get the sip packets from the asterisk box. Use
ngrep on kamailio server to see what happens there, like:<br>
<br>
ngrep -d any -qt -W byline port 5060 or port 5062<br>
<br>
You will see if the packets get to kamailio and if they are
attempted to be sent further.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 23/03/15 13:43, Slava Bendersky
wrote:<br>
</div>
<blockquote
cite="mid:1965093803.41486821.1427114592070.JavaMail.zimbra@skillsearch.ca"
type="cite">
<div style="font-family: lucida console,sans-serif; font-size:
12pt; color: #000000">
<div>Hello Daniel,<br>
</div>
<div>Look like transactions are not match when it send reply for
NOTIFY. I think it should reuse connection.<br
data-mce-bogus="1">
</div>
<div>Here SDP output where cseq are match and asterisk does
retransmissions until time out.<br data-mce-bogus="1">
</div>
<div>Also I wonder where Path route is reused I see %* instead
; as delimiter between transport and port.<br
data-mce-bogus="1">
</div>
<div><br data-mce-bogus="1">
</div>
<div><br data-mce-bogus="1">
</div>
<div>Retransmitting #8 (NAT) to 10.18.130.46:5060:<br>
NOTIFY <a class="moz-txt-link-freetext" href="sip:191@192.168.88.246:5062;transport=tcp">sip:191@192.168.88.246:5062;transport=tcp</a> SIP/2.0<br>
Via: SIP/2.0/UDP
10.18.130.51:5060;branch=z9hG4bK6939f20d;rport<br>
Max-Forwards: 70<br>
Route:
<a class="moz-txt-link-rfc2396E" href="sip:inbound@10.18.130.46;lr;received=sip:client_public_ip:5062%3Btransport%3Dtcp"><sip:inbound@10.18.130.46;lr;received=sip:client_public_ip:5062%3Btransport%3Dtcp></a><br>
From: "canlpbx02"
<a class="moz-txt-link-rfc2396E" href="sip:canlpbx02@10.18.130.51"><sip:canlpbx02@10.18.130.51></a>;tag=as4b212049<br>
To: <a class="moz-txt-link-rfc2396E" href="sip:191@192.168.88.246:5062;transport=tcp"><sip:191@192.168.88.246:5062;transport=tcp></a><br>
Contact: <a class="moz-txt-link-rfc2396E" href="sip:canlpbx02@10.18.130.51:5060"><sip:canlpbx02@10.18.130.51:5060></a><br>
Call-ID: <a class="moz-txt-link-abbreviated" href="mailto:14c7c8cc7335adf60f2be634132d3b2f@10.18.130.51:5060">14c7c8cc7335adf60f2be634132d3b2f@10.18.130.51:5060</a><br>
CSeq: 102 NOTIFY<br>
User-Agent: FPBX-12.0.43(12.8.1)<br>
Event: message-summary<br>
Content-Type: application/simple-message-summary<br>
Content-Length: 89<br>
<br>
Messages-Waiting: yes<br>
Message-Account: <a class="moz-txt-link-freetext" href="sip:*97@10.18.130.51">sip:*97@10.18.130.51</a><br>
Voice-Message: 24/0 (0/0)<br>
<br>
---<br>
Retransmitting #9 (NAT) to 10.18.130.46:5060:<br>
NOTIFY <a class="moz-txt-link-freetext" href="sip:191@192.168.88.246:5062;transport=tcp">sip:191@192.168.88.246:5062;transport=tcp</a> SIP/2.0<br>
Via: SIP/2.0/UDP
10.18.130.51:5060;branch=z9hG4bK6939f20d;rport<br>
Max-Forwards: 70<br>
Route:
<a class="moz-txt-link-rfc2396E" href="sip:inbound@10.18.130.46;lr;received=sip:99.251.238.38:5062%3Btransport%3Dtcp"><sip:inbound@10.18.130.46;lr;received=sip:99.251.238.38:5062%3Btransport%3Dtcp></a>
<span data-mce-style="color: #ff0000;" style="color: rgb(255,
0, 0);">right here</span><br>
From: "canlpbx02"
<a class="moz-txt-link-rfc2396E" href="sip:canlpbx02@10.18.130.51"><sip:canlpbx02@10.18.130.51></a>;tag=as4b212049<br>
To: <a class="moz-txt-link-rfc2396E" href="sip:191@192.168.88.246:5062;transport=tcp"><sip:191@192.168.88.246:5062;transport=tcp></a><br>
Contact: <a class="moz-txt-link-rfc2396E" href="sip:canlpbx02@10.18.130.51:5060"><sip:canlpbx02@10.18.130.51:5060></a><br>
Call-ID: <a class="moz-txt-link-abbreviated" href="mailto:14c7c8cc7335adf60f2be634132d3b2f@10.18.130.51:5060">14c7c8cc7335adf60f2be634132d3b2f@10.18.130.51:5060</a><br>
CSeq: 102 NOTIFY<br>
User-Agent: FPBX-12.0.43(12.8.1)<br>
Event: message-summary<br>
Content-Type: application/simple-message-summary<br>
Content-Length: 89<br>
<br>
Messages-Waiting: yes<br>
Message-Account: <a class="moz-txt-link-freetext" href="sip:*97@10.18.130.51">sip:*97@10.18.130.51</a><br>
Voice-Message: 24/0 (0/0)<br>
<br>
---<br>
<br>
<--- SIP read from UDP:10.18.130.46:5060 ---><br>
SIP/2.0 408 Request Timeout<br>
Via: SIP/2.0/UDP
10.18.130.51:5060;branch=z9hG4bK6939f20d;rport=5060;received=10.18.130.51<br>
From: "canlpbx02"
<a class="moz-txt-link-rfc2396E" href="sip:canlpbx02@10.18.130.51"><sip:canlpbx02@10.18.130.51></a>;tag=as4b212049<br>
To:
<a class="moz-txt-link-rfc2396E" href="sip:191@192.168.88.246:5062;transport=tcp"><sip:191@192.168.88.246:5062;transport=tcp></a>;tag=dc299d9ac16f3377ac0b8dfa22eaf0a6-2fe2<br>
Call-ID: <a class="moz-txt-link-abbreviated" href="mailto:14c7c8cc7335adf60f2be634132d3b2f@10.18.130.51:5060">14c7c8cc7335adf60f2be634132d3b2f@10.18.130.51:5060</a><br>
CSeq: 102 NOTIFY<br>
Server: kamailio (4.2.3 (x86_64/linux))<br>
Content-Length: 0<br>
<br>
<-------------><br>
</div>
<div><br>
</div>
<div>Mar 23 08:45:47 canlvprx01 /usr/sbin/kamailio[20143]:
ERROR: <core> [tcp_main.c:4338]: tcpconn_main_timeout():
connect client_pub_ip:5063 failed (timeout)</div>
<div><br data-mce-bogus="1">
</div>
<div><br data-mce-bogus="1">
</div>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Kamailio World Conference, May 27-29, 2015
Berlin, Germany - <a class="moz-txt-link-freetext" href="http://www.kamailioworld.com">http://www.kamailioworld.com</a></pre>
</body>
</html>