diff options
| author | Matt Jordan <mjordan@digium.com> | 2015-12-24 12:19:51 -0600 |
|---|---|---|
| committer | Matt Jordan <mjordan@digium.com> | 2015-12-24 12:19:51 -0600 |
| commit | 0a9941de9d24093b5ff44096d1d7406f29d11e45 (patch) | |
| tree | 26c42e995537e94de20b46c9ad92e94acf9eeda6 | |
| parent | 15641cb6cdad4a115145fd4e7aa80ae4c5219b2d (diff) | |
res/res_pjsip_location: Delete contact_status object when contact is deleted
In 450579e908, a change was made that removed the deletion of the
'contact_status' object when a 'contact' object is deleted in sorcery.
This unfortunately means that the 'contact_status' object persists, even when
something has explicitly removed a contact. The result is that the state of
the contact will not be regenerated if that contact is re-created, and the
stale state will be reported/used for that contact. It also results in
no ContactStatusChanged events being generated for either ARI or AMI.
This patch restores the deletion logic that was removed. Doing so now
results in the expected events being generated again.
Change-Id: I28789a112e845072308b5b34522690e3faf58f07
| -rw-r--r-- | res/res_pjsip/location.c | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/res/res_pjsip/location.c b/res/res_pjsip/location.c index 2908f6f70..a34e5cdf3 100644 --- a/res/res_pjsip/location.c +++ b/res/res_pjsip/location.c @@ -322,6 +322,14 @@ int ast_sip_location_update_contact(struct ast_sip_contact *contact) int ast_sip_location_delete_contact(struct ast_sip_contact *contact) { + void *contact_status_obj; + + contact_status_obj = ast_sorcery_retrieve_by_id(ast_sip_get_sorcery(), CONTACT_STATUS, ast_sorcery_object_get_id(contact)); + if (contact_status_obj) { + ast_sorcery_delete(ast_sip_get_sorcery(), contact_status_obj); + ao2_ref(contact_status_obj, -1); + } + return ast_sorcery_delete(ast_sip_get_sorcery(), contact); } |