Reverse logic during subscription persistence recreation.
authorMark Michelson <mmichelson@digium.com>
Mon, 30 Jun 2014 18:39:56 +0000 (18:39 +0000)
committerMark Michelson <mmichelson@digium.com>
Mon, 30 Jun 2014 18:39:56 +0000 (18:39 +0000)
In the abstraction effort, this bit of logic got messed up. We
want to recreate the persistence if things go well, not if things
fail.

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@417663 65c4cc65-6c06-0410-ace0-fbb531ad65f3

res/res_pjsip_pubsub.c

index 9032bd3..cfda0ae 100644 (file)
@@ -566,7 +566,7 @@ static int subscription_persistence_recreate(void *obj, void *arg, int flags)
                        pubsub_module.id, MOD_DATA_PERSISTENCE, persistence);
 
        resp = handler->notifier->new_subscribe(endpoint, resource);
-       if (!PJSIP_IS_STATUS_IN_CLASS(resp, 200)) {
+       if (PJSIP_IS_STATUS_IN_CLASS(resp, 200)) {
                sub = notifier_create_subscription(handler, endpoint, &rdata, resource, generator);
                sub->persistence = ao2_bump(persistence);
                subscription_persistence_update(sub, &rdata);