<html><body><div style="font-family: lucida console,sans-serif; font-size: 12pt; color: #000000"><div data-marker="__QUOTED_TEXT__"><div style="font-family: lucida console,sans-serif; font-size: 12pt; color: #000000"><div>Hello Everyone,<br></div><div>In my case I am using Path and I asterisk generate NOTIFY with route based on path, then I see on kamailio side tries reach on client on public IP side and open new connection not follow ESTABLISHED/RELATED link then it times out.</div><br><br><div>Log: <br></div><div>Mar 23 11:00:17 canlvprx01 /usr/sbin/kamailio[20193]: INFO: <script>: [NOTIFY], Inbound connection from <10.18.130.51> <span style="background-color: rgb(255, 0, 0);"> traffic from Asterisk</span><br>Mar 23 11:00:17 canlvprx01 /usr/sbin/kamailio[20193]: INFO: <script>: [NOTIFY], Present Route: Client_public_IP.<br>Mar 23 11:00:28 canlvprx01 /usr/sbin/kamailio[20204]: ERROR: <core> [tcp_main.c:4338]: tcpconn_main_timeout(): connect Client_public_IP:5060 failed (timeout)<br></div><br><br><div>Here trace on kamailio side <br></div><br><div>http://fpaste.org/201813/15287114/</div><br><div>Here trace from soft phone client side.<br></div><br><div>http://fpaste.org/201814/14271530/</div><br><div>Slava.<br></div><br><br><br><hr id="zwchr"><div><b>From: </b>"Alex Balashov" <abalashov@evaristesys.com><br><b>To: </b>"sr-users" <sr-users@lists.sip-router.org><br><b>Sent: </b>Monday, March 23, 2015 6:42:59 PM<br><b>Subject: </b>Re: [SR-Users] kamailio asterisk NOTIFY<br></div><br><div>Anthony,<br><br>The Contact presented by the subscriber in the initial subscription is:<br><br> m: "Test User" <br><sip:172.16.4.7;line=sr-D8G7CE2.5PUeK-xuarl7NYDdNYDxNYlFUYoeUeQ8Cw.6DE2vDdyJDAa4TliwC84OC82LK-2ehwl7NYDdNYDxNYlFUAm6UYzm0gme>;+sip.ice<br><br>And the subsequent NOTIFY is correctly targeted to this RURI:<br><br> NOTIFY <br>sip:172.16.4.7;line=sr-D8G7CE2.5PUeK-xuarl7NYDdNYDxNYlFUYoeUeQ8Cw.6DE2vDdyJDAa4TliwC84OC82LK-2ehwl7NYDdNYDxNYlFUAm6UYzm0gme <br>SIP/2.0<br><br>The subscriber returns this Contact in the 200 OK response for the NOTIFY:<br><br> m: "Test User" <br><sip:172.16.4.7;line=sr-D8G7CE2.5PUeK-xuarl7NYDdNYDxNYlFUYoeUeQ8Cw.6DE2vDdyJDAa4TliwC84O>;+sip.ice<br><br>And subsequent NOTIFYs appear to use this RURI instead of the original <br>Contact of the subscriber:<br><br> NOTIFY <br>sip:172.16.4.7;line=sr-D8G7CE2.5PUeK-xuarl7NYDdNYDxNYlFUYoeUeQ8Cw.6DE2vDdyJDAa4TliwC84O <br>SIP/2.0<br><br> NOTIFY <br>sip:172.16.4.7;line=sr-D8G7CE2.5PUeK-xuarl7NYDdNYDxNYlFUYoeUeQ8Cw.6DE2vDdyJDAa4TliwC84O <br>SIP/2.0<br><br>etc.<br><br>A SUBSCRIBE is a dialog-creating event, so in-dialog messages (e.g. <br>NOTIFYs) should be targeted at a Request URI corresponding to the <br>Contact URI of the SUBSCRIBE-er. It seems to me that this is the problem <br>here, rather than truncation.<br><br>-- <br>Alex Balashov | Principal | Evariste Systems LLC<br>303 Perimeter Center North, Suite 300<br>Atlanta, GA 30346<br>United States<br><br>Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)<br>Web: http://www.evaristesys.com/, http://www.csrpswitch.com/<br><br>_______________________________________________<br>SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>sr-users@lists.sip-router.org<br>http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</div></div><br></div></div></body></html>