[asterisk-bugs] [JIRA] (ASTERISK-25811) Unable to delete object from sorcery cache

[Asterisk Team (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-25811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asterisk Team updated ASTERISK-25811:
-------------------------------------

    Target Release Version/s: 13.8.0

> Unable to delete object from sorcery cache
> ------------------------------------------
>
>                 Key: ASTERISK-25811
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25811
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Sorcery
>    Affects Versions: 13.7.2
>         Environment: Centos 7
>            Reporter: Ross Beer
>            Assignee: Unassigned
>      Target Release: 13.8.0
>
>
> Sorcery cache throws an error on unregister:
> {quote}
> [2016-02-25 13:47:02] ERROR[17353]: res_sorcery_memory_cache.c:1559 sorcery_memory_cache_delete: Unable to delete object '<ENDPOINT>;@115bb1375dae1799c68048e7abef7e05' from sorcery cache
>  Contact <ENDPOINT>/sip:<ENDPOINT>@<IP Address>:39212;transport=TLS has been deleted
>     -- Added contact 'sip:<ENDPOINT>@<IP Address>:39212;transport=TLS' to AOR '<ENDPOINT>' with expiration of 60 seconds
>  Contact <ENDPOINT>/sip:<ENDPOINT>@<IP Address>:39212;transport=TLS has been created
>  Contact <ENDPOINT>/sip:<ENDPOINT>@<IP Address>:39212;transport=TLS is now Unknown.  RTT: 0.000 msec
> {quote}
> The device had previously registered and therefore the device should have been in the cache. When this issue occurs it blocks the registration of an endpoint causing it to go offline. I can replicate this issue by pressing 'Re-register' within the Snom interface.
> Sourcery is configured in the following way:
> {quote}
> contact/cache=memory_cache,object_lifetime_stale=3600,object_lifetime_maximum=28800,expire_on_reload=yes,full_backend_cache=yes
> contact=config,pjsip.conf,criteria=type=contact
> contact=realtime,ps_contacts
> {quote}
> Looking at the real-time database the ID is present, all be it encoded with <ENDPOINT>^3B which is the encoding for a semicolon. Therefore it looks like the cache isn't matching the object correctly or not being inserted in the first place. 



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