A test recently uncovered that running an ill-timed AMI command to show
inbound subscriptions could cause a crash since Asterisk will try to
operate on a freed subscription.
The fix for this is to remove the subscription tree from the list of
subscriptions at the time that we are sending our final NOTIFY request
out. This way, as the subscription is in the process of dying, it is
inaccessible from AMI.
Change-Id: Ic0239003d8d73e04c47c12dd2a7e23867e5b5b23
(cherry picked from commit
b073244c511f9634de57ea401ab9dbebcf2390e8)
ast_debug(3, "Destroying subscription tree %p\n", sub_tree);
- remove_subscription(sub_tree);
-
ao2_cleanup(sub_tree->endpoint);
destroy_subscriptions(sub_tree->root);
}
}
+ remove_subscription(sub_tree);
pjsip_evsub_set_mod_data(evsub, pubsub_module.id, NULL);
sub_tree->evsub = NULL;
ast_sip_dialog_set_serializer(sub_tree->dlg, NULL);