[asterisk-bugs] [JIRA] (ASTERISK-29525) PJSIP remove_existing unavailable contacts

[George Joseph (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-29525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255661#comment-255661 ] 

George Joseph commented on ASTERISK-29525:
------------------------------------------

We also can't really delete unavailable contacts if their registration hasn't timed out yet.  They may be temporarily unavailable because of a network issue blocking OPTIONS requests and come back a short while later.  If their registration hasn't expired, their contact needs to remain in place.


> PJSIP remove_existing unavailable contacts
> ------------------------------------------
>
>                 Key: ASTERISK-29525
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29525
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 16.19.0, 18.5.0
>            Reporter: Joe
>
> The current behavior of remove_existing is:
> 1. If enabled, the contact that will expire soonest will be removed
> 2. If disabled, no contacts will be removed.
> This doesn't take into account contacts that have gone offline and are now unavailable.  There doesn't seem to be any use case for maintaining unavailable contacts.  Perhaps, a more intelligent process would work like this instead:
> 1. If enabled, first remove unavailable contacts, and if there aren't any, remove expiring soonest
> 2. If disabled, remove only unavailable contacts.
> If changing the behavior of 'no' is unwanted, then add a 3rd option of:
> remove_existing=unavailable
> to create the behavior of 2 above.



--
This message was sent by Atlassian JIRA
(v6.2#6252)