[asterisk-bugs] [JIRA] (ASTERISK-28955) "setvar" doesn't work properly in dahdi-channels.conf

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-28955:
------------------------------------------

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.

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.

> "setvar" doesn't work properly in dahdi-channels.conf
> -----------------------------------------------------
>
>                 Key: ASTERISK-28955
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28955
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Configuration
>    Affects Versions: 16.11.0
>            Reporter: Marin Odrljin
>            Severity: Minor
>
> "setvar" works differently than in previous Asterisk versions, e.g. 16.4.1 or 13.11.2.
> I have following dahdi-channels.conf:
> {code}
> ; Span 1: TE8/0/1 "T8XXP (PCI) Card 0 Span 1" (MASTER) 
> ; Server X IN channels
> group = 11
> setvar = GROUP_NR=11
> context = from-pri
> switchtype = euroisdn
> signalling = pri_net
> channel => 1-15,17-21
> ; Server X OUT channels
> group = 12
> setvar = GROUP_NR=12
> context = from-pri
> switchtype = euroisdn
> signalling = pri_net
> channel => 22-31
> ; Span 2: TE8/0/2 "T8XXP (PCI) Card 0 Span 2"
> ; Asterisk .98
> group = 2
> setvar = GROUP_NR=2
> context = from-pri
> switchtype = euroisdn
> signalling = pri_net
> channel => 32-46,48-62
> ; ... other spans
> ; Span 8: TE8/0/8 "T8XXP (PCI) Card 0 Span 8" 
> ; Panasonic PBX
> group = 8
> setvar = GROUP_NR=8
> context = from-pri
> switchtype = euroisdn
> signalling = pri_net
> channel => 218-232,234-248
> {code}
> And extensions.conf:
> {code}
> [from-pri]
> exten => _X!,1,Stasis(AriStart,SPAN=${CHANNEL(dahdi_span)},CHANNEL=${CHANNEL(dahdi_channel)},GROUP=${GROUP_NR}, ...other parameters)
> {code}
> In every group I have "setvar = GROUP_NR=X". This is a convenient way how I can have only one entry in dialplan for context "from-pri" and to know from which group a call came in. In Asterisk 13 that works fine, but we have decided to slowly move toward newer Asterisk version 16 because of new features and LTS. We have started to test with Asterisk 16.4.1 when it came out and this part with "setvar" was working fine, but now we took a latest one for production server and "setvar" is not working properly anymore. In version 16.11 if call comes at span 8, variable GROUP_NR is set to value 11 (1st group and setvar from our config) and not to value 8 as defined in that group. It looks like either parsing of the config file has changed and it takes now the "setvar" entry from the first group where it occurs. If I remove all "setvar=GROUP_NR=..." except in the last group 8 then it is fine. In previous versions and the same config files GROUP_NR variable was always set to the value according to "setvar" directive from that group.



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