{"push_id":785062212,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"820b9dc13810929d7280178c9cf0c5f08709d59b","before":"d2106c0b21e2e4d53eb177d1d271c30c362700f1","commits":[{"sha":"ef3358d0c0a75ac19f91195716560226cb734f97","author":{"email":"317a993f1126881a6019d7e476a07af7fa3e05fe@digium.com","name":"Matt Jordan"},"message":"res/res_pjsip: Purge contacts when an AoR is deleted\n\nWhen an AoR is deleted by an external mechanism, such as through ARI, we\ncurrently do not remove dynamic contacts that were created for that AoR as a\nresult of a received REGISTER request. As a result, re-creating the AoR will\ncause the dynamic contact to be interpreted as a persistent contact, leading\nto some rather strange state being created for the contacts/endpoints.\n\nThis patch adds a sorcery observer for the 'aor' object. When a delete is\nissued on the underlying sorcery object, the observer is called, and all\ncontacts created and persisted in sorcery for that AoR are also removed. Note\nthat we don't want to perform this action when an AO2 object that is an AoR is\ndestroyed, as the AoR can still exist in the backing storage (and we would\nthus be removing valid contacts from an AoR that still \"exists\".)\n\nASTERISK-25381 #close\n\nChange-Id: I6697e51ef6b2858b5d63401f35dc378bb0f90328","distinct":true,"url":"https://api.github.com/repos/asterisk/asterisk/commits/ef3358d0c0a75ac19f91195716560226cb734f97"},{"sha":"820b9dc13810929d7280178c9cf0c5f08709d59b","author":{"email":"e7bf676187195e47c70a931cb0e87f318fea16b3@digium.com","name":"Joshua Colp"},"message":"Merge \"res/res_pjsip: Purge contacts when an AoR is deleted\"","distinct":true,"url":"https://api.github.com/repos/asterisk/asterisk/commits/820b9dc13810929d7280178c9cf0c5f08709d59b"}]}