[reSIProcate] Query regarding queuing mechanism for NOTIFYs (ClientSubscription)

["Parag" <papatel@xxxxxxxxxx>]

Hello,

According to current queuing mechanism for NOTIFY in ClientSubscription, 
if you application call end() to terminate subscription and at that time
ClintSubscription already have more then one queued NOTIFY. And after some
time DUM also getting NOTIFY with terminate state which will also queued in
NOTIFY queue.

In above case application never get callback "onTerminate or onUpdateActive"
for remaining queued NOTIFYs.

Am I right in above case?

Thanks,
Parag Patel