I would just put a different spin on this without changing the facts:
If you *don't* terminate the subscription with your NOTIFY, then by
definition it is not the last NOTIFY, because the subscription still has
to be terminated sometime, and that will entail a NOTIFY.
So, if you sent a NOTIFY a
according to RFC 3515
.4.7 Using the Subscription-State Header Field with Event Refer
Each NOTIFY must contain a Subscription-State header field as defined
in [2]. The final NOTIFY sent in response to a REFER MUST indicate
the subscription has been "terminated" with a reason of "noresou
When getting an in-dialog REFER we get a new SUBSCRIBE-dialog. I wonder if
it is mandatory to explisitly terminate (by means of "noresource") this
latter dialog from the transfer target once it sends the last NOTIFY (the
one with a sipfrag of 200 OK), or that it is equivaliently alright to have
th
