Re: [reSIProcate-users] Any way to kill a DUM subscription in case of deregistration?
Brody, Chris - Acision wrote:
Hello,
We are implementing a third-party registration system over DUM where upon an
incoming registration, we subscribe to the reg event for the user and keep some
information in a subclass of AppDialogSet. In case a deregistration event comes
in, we would like to stop the subscription. We can do this by calling
AppDialogSet::end() which in turn calls DialogSet::end(), ending the dialog by
sending a SUBSCRIBE message with a zero expiration time.
Normally, it is a good idea to indicate dialog cleanup to a peer. However, our
idea is that when a user device had already deregistered, that indicates an
application shutdown and we would rather not send the extra zero-expiration
SUBSCRIBE message.
I'm not certain I completely understand what you're trying to
accomplish, but what you're proposing to do is pretty well outside of
what's allowed by RFC 3265.
In fact, it sounds like you might be doing things a bit backwards to
start with -- could you put together a sequence diagram to show the use
case you're trying to handle?
/a