Do not immediate terminate REFER subscription

[wakamoleguy]

This was requested in the mailing list.

When receiving a REFER, the SIP.js user agent replies with a NOTIFY request immediately terminating the subscription. This is valid as per RFC 3515 Section 2.4.4, but more complete information (see section 2.4.5 of the RFC) would be nice.

[klarrimore]

There's a similar but much more significant issue on the REFER request side in Session.refer. On a 2XX response to a REFER with replaces, the Session immediately terminates. The Session needs the ability to continue to stay up to respond and act on the actual NOTIFY. The original 202 response simply means it's subscribed. Should I break this out into another issue?

[wakamoleguy]

This has also been requested on the mailing list

[klarrimore]

I opened an Issue about it a few days ago with some code I'm using as a workaround here: #254

[egreenmachine]

Can you try out #459? I think that I have addressed this issue there.

• Due to the age of this issue, if we do not hear any feedback on this we will close it once we merge the pull request.