Hello Everyone, 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.
Log: Mar 23 11:00:17 canlvprx01 /usr/sbin/kamailio[20193]: INFO: <script>: [NOTIFY], Inbound connection from <10.18.130.51> traffic from Asterisk Mar 23 11:00:17 canlvprx01 /usr/sbin/kamailio[20193]: INFO: <script>: [NOTIFY], Present Route: Client_public_IP. 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)
Here trace on kamailio side
http://fpaste.org/201813/15287114/
Here trace from soft phone client side.
http://fpaste.org/201814/14271530/
Slava.
From: "Alex Balashov" abalashov@evaristesys.com To: "sr-users" sr-users@lists.sip-router.org Sent: Monday, March 23, 2015 6:42:59 PM Subject: Re: [SR-Users] kamailio asterisk NOTIFY
Anthony,
The Contact presented by the subscriber in the initial subscription is:
m: "Test User" sip:172.16.4.7;line=sr-D8G7CE2.5PUeK-xuarl7NYDdNYDxNYlFUYoeUeQ8Cw.6DE2vDdyJDAa4TliwC84OC82LK-2ehwl7NYDdNYDxNYlFUAm6UYzm0gme;+sip.ice
And the subsequent NOTIFY is correctly targeted to this RURI:
NOTIFY sip:172.16.4.7;line=sr-D8G7CE2.5PUeK-xuarl7NYDdNYDxNYlFUYoeUeQ8Cw.6DE2vDdyJDAa4TliwC84OC82LK-2ehwl7NYDdNYDxNYlFUAm6UYzm0gme SIP/2.0
The subscriber returns this Contact in the 200 OK response for the NOTIFY:
m: "Test User" sip:172.16.4.7;line=sr-D8G7CE2.5PUeK-xuarl7NYDdNYDxNYlFUYoeUeQ8Cw.6DE2vDdyJDAa4TliwC84O;+sip.ice
And subsequent NOTIFYs appear to use this RURI instead of the original Contact of the subscriber:
NOTIFY sip:172.16.4.7;line=sr-D8G7CE2.5PUeK-xuarl7NYDdNYDxNYlFUYoeUeQ8Cw.6DE2vDdyJDAa4TliwC84O SIP/2.0
NOTIFY sip:172.16.4.7;line=sr-D8G7CE2.5PUeK-xuarl7NYDdNYDxNYlFUYoeUeQ8Cw.6DE2vDdyJDAa4TliwC84O SIP/2.0
etc.
A SUBSCRIBE is a dialog-creating event, so in-dialog messages (e.g. NOTIFYs) should be targeted at a Request URI corresponding to the Contact URI of the SUBSCRIBE-er. It seems to me that this is the problem here, rather than truncation.