[asterisk-bugs] [Asterisk 0016646]: [patch] Its not possible to pass more than one agrument in custom features.
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Apr 14 17:57:38 CDT 2010
The following issue has been RESOLVED.
======================================================================
https://issues.asterisk.org/view.php?id=16646
======================================================================
Reported By: pinga-fogo
Assigned To: tilghman
======================================================================
Project: Asterisk
Issue ID: 16646
Category: Resources/res_features
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
Target Version: 1.4.32
Asterisk Version: SVN
JIRA: SWP-758
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2010-01-19 04:46 CST
Last Modified: 2010-04-14 17:57 CDT
======================================================================
Summary: [patch] Its not possible to pass more than one
agrument in custom features.
Description:
Is not possible to pass mor than one argument in a custon features, if i
use the pipe | to separate the arguments, this downt work in dialplan, and
if i use "," to separate the arguments the feature accept the first
argument only,
example:
testfeature => *25,peer/callee,goto,tstfax|s|1
(in execution the dialplan not recognise the pipe separator (deprecated))
testfeature => *25,peer/callee,goto,tstfax,s,1
(the parameters are parsed incorrect, MOH_Class = s)
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
duplicate of 0016984 impossible to pass more than one argume...
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-04-14 17:57 svnbot Status ready for testing =>
assigned
2010-04-14 17:57 svnbot Status assigned => resolved
2010-04-14 17:57 svnbot Resolution open => fixed
======================================================================
More information about the asterisk-bugs
mailing list