[asterisk-bugs] [JIRA] (ASTERISK-26645) res_pjsip_endpoint_identifier_ip: Does not check for updates in realtime database

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-26645:
------------------------------------------

This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.

> res_pjsip_endpoint_identifier_ip: Does not check for updates in realtime database
> ---------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26645
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26645
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_endpoint_identifier_ip
>    Affects Versions: 13.12.2
>         Environment: Fedora 23
>            Reporter: Ross Beer
>
> When storing endpoint identifier entries in a realtime backend, entries are not checked for updates.
> I would have expected the table to either be queried periodically or when a SIP device tries to send messages to Asterisk.
> If changes are made to the database, the only way for these to be pulled into the asterisk config is to manually run a show command to load it.
> The sorcery config is as follows:
> {noformat}
> [res_pjsip_endpoint_identifier_ip]
> identify=config,pjsip.conf,criteria=type=identify
> identify/cache=memory_cache,expire_on_reload=yes,full_backend_cache=yes
> identify=realtime,ps_endpoint_id_ips
> {noformat}
> The command used to fetch the data from the database is:
> {noformat}
> pjsip show identify <ENDPOINT>
> {noformat}
> Once the command has been run, devices are successfully authenticated via IP.
> As this table could be hammered by attempted hackers, I would suggest a periodic check be put in place or negative caching.



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