[asterisk-bugs] [JIRA] (ASTERISK-30396) Improper use of regex in res_pjsip/location.c, Regression from ASTERISK-26151

Asterisk Team (JIRA) noreply at issues.asterisk.org
Thu Jan 12 13:25:05 CST 2023


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

Asterisk Team commented on ASTERISK-30396:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> Improper use of regex in res_pjsip/location.c, Regression from ASTERISK-26151
> -----------------------------------------------------------------------------
>
>                 Key: ASTERISK-30396
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30396
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 16.28.0
>         Environment: Debian x64, IPv6 only.
>            Reporter: erebus
>            Severity: Major
>
> Greetings programs!
> I got the following use case:
> Asterisk server with 2 SIP Clients registered to the same AOR and same endpoint. AOR identifier and extension number match the E123-formatted E164 number of the participant which is why the AOR and the extension begin with a + sign.
> My Asterisk is now suffering from contact amnesia. I. e. pjsip show endpoints will sometimes list either of the two phones and rarely even both will show up. But in most cases, either phone or even both are forgotten by the software. This means that my 2 phones aren't ringing reliably. Sometimes only 1 phone rings, sometimes neither rings.
> I managed to work around this bug by resurrecting an old work-around that I developed for bug ASTERISK-26151:
> For each AOR I want to have in pjsip.conf, I create a second which has the + sign escaped with a backslash.
> [aor_dynamic](!)
> type=aor
> max_contacts=15
> qualify_frequency=1
> qualify_timeout=1000
> [+12345](aor_dynamic)
> [\+12345](aor_dynamic) ; <==== WORKAROUND
> This made Asterisk work for me.
> I think that one of the changes that was made to location.c in the past years introduced this issue and that it is again caused by improper use of ast_sorcery_retrieve_by_regex() in lines 887 and/or 1051.



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



More information about the asterisk-bugs mailing list