[asterisk-bugs] [Asterisk 0015338]: AstApplicationData when called with several arguments escapes comma with backslash
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Oct 21 08:01:19 CDT 2010
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=15338
======================================================================
Reported By: nito
Assigned To: suretec
======================================================================
Project: Asterisk
Issue ID: 15338
Category: Core/Configuration
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-06-16 19:59 CDT
Last Modified: 2010-10-21 08:01 CDT
======================================================================
Summary: AstApplicationData when called with several
arguments escapes comma with backslash
Description:
In my configuration we use LDAP as our database repository
With entries like this
dn: uid=jsalonen,ou=People,
AstApplication: Macro
AstExtension: 5035
AstPriority: 1
AstApplicationData: sipdial,SIP/nito,+3400012345
There is a macro in the dialplan
[macro-sipdial]
exten => ... ${ARG1} ...
and so on
on version 1.0.6-beta9 the macro was correctly called as:
Macro(sipdial,SIP/nito,+3400012345)
but since version 1.0.6.9 the macro is called as:
Macro(sipdial\,SIP/nito\,+3400012345)
That is setting a backslash for any comma that appears,
======================================================================
----------------------------------------------------------------------
(0128275) lmadsen (administrator) - 2010-10-21 08:01
https://issues.asterisk.org/view.php?id=15338#c128275
----------------------------------------------------------------------
I don't believe this really has anything to do with LDAP and is probably a
functionality of how things are escaped in the Asterisk dialplan more
generally. It just happens you're using res_config_ldap.
Issue History
Date Modified Username Field Change
======================================================================
2010-10-21 08:01 lmadsen Note Added: 0128275
2010-10-21 08:01 lmadsen Severity tweak => minor
2010-10-21 08:01 lmadsen Category
Resources/res_config_ldap => Core/Configuration
2010-10-21 08:01 lmadsen Additional Information Updated
======================================================================
More information about the asterisk-bugs
mailing list