On 23 Mar 2015, at 23:42, Alex Balashov abalashov@evaristesys.com wrote:
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.
I think that changed recently. The NOTIFY is a dialog-creating event, since a SUBSCRIBE can fork to many destinations.
/O