I am not sure if this is intentional but I noticed that presence subscription results in firing ContactChangeStatusEvent event. This seems not entirely correct, as subscription request does not really change contact status.
I am not even sure if this should trigger PresenceReceivedEvent as this is really subscription request. Perhaps it would be more efficient to have a separate SubscriptionReuqestEvent to be triggered for such packets.
I am not sure if this is intentional but I noticed that presence
subscriptionresults in firingContactChangeStatusEventevent. This seems not entirely correct, as subscription request does not really change contact status.I am not even sure if this should trigger
PresenceReceivedEventas this is really subscription request. Perhaps it would be more efficient to have a separateSubscriptionReuqestEventto be triggered for such packets.Taken from GitHub