Date: Sun, 27 Jan 2019 11:07:36 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 235236] net/asterisk15 improvement: force setvar to override previous value in chan_sip, chan_iax2 Message-ID: <bug-235236-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235236 Bug ID: 235236 Summary: net/asterisk15 improvement: force setvar to override previous value in chan_sip, chan_iax2 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: madpilot@FreeBSD.org Reporter: pfduch@yandex.ru Flags: maintainer-feedback?(madpilot@FreeBSD.org) Assignee: madpilot@FreeBSD.org Created attachment 201436 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D201436&action= =3Dedit patch for chan_sip and chan_iax2 In chan_sip and chan_iax2, variable set by setvar option cannot be overriden later. E.g.: [tmpl](!) setvar=3Dfoo=3Dbar [some-peer](tmpl) setvar=3Dfoo=3Dbaz ; no chance: "${SIPPEER(some-peer,chanvar[foo])}" in dia= lplan still returns "bar" Actually, second setvar appends an attribute-value pair to a list, but only= the first one is always read. A ticket in asterisk JIRA is still open for a long long time: https://issues.asterisk.org/jira/browse/ASTERISK-23756 Unlike chan_sip and chan_iax2, chan_dahdi, for example, was already fixed f= or that. I use the attached patch for a several years without any problems on versio= ns 11.x, 13.x, 15.x, both i386 and amd64. It would be nice to include it to mainstream. Maybe it makes sense even to enable it by default. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235236-7788>