[asterisk-bugs] [JIRA] (ASTERISK-28563) Additional configuration [extName](+) not always working

[Kevin Harwell (JIRA)]

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

Kevin Harwell commented on ASTERISK-28563:
------------------------------------------

According to [~rmudgett] this could be due to the way pjsip configuration uses "type" parameters for its sections, and then using the same name for a section. So for instance:
{noformat}
[101]
type=aor

[101]
type=endpoint

[101](+)
{noformat}
Which one does it choose to append? The first one it finds?

> Additional configuration [extName](+) not always working
> --------------------------------------------------------
>
>                 Key: ASTERISK-28563
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28563
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Configuration
>    Affects Versions: 16.5.0
>         Environment: CentOS 7
>            Reporter: Michael Maier
>            Severity: Minor
>              Labels: pjsip
>
> There is a problem regarding the configuration options, provided by FreePBX, which should be supported by asterisk. I'm referring to the possibility, to add additional options not supported by FreePBX using special config files like pjsip.registration_custom_post.conf or pjsip.aor_custom_post.conf and pjsip.endpoint_custom_post.conf or pjsip.transports_custom_post.conf. The last two files are working pretty fine as expected, but the first two just don't work.
> I'm configuring in pjsip.registration_custom_post.conf for example:
> {noformat}
> [extName](+)
> key=value
> {noformat}
> Asterisk reads it (asterisk complains if it doesn't know the key), but asterisk doesn't apply the provided value for a known key - it's always the default value.



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