[asterisk-bugs] [Asterisk 0017158]: MeetMe Options S(10)L(10000)
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Apr 4 16:28:49 CDT 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17158
======================================================================
Reported By: chandrakantsolanki
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17158
Category: Core/General
Reproducibility: always
Severity: minor
Priority: normal
Status: acknowledged
Asterisk Version: I did not set the version :(
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-04-09 06:09 CDT
Last Modified: 2011-04-04 16:28 CDT
======================================================================
Summary: MeetMe Options S(10)L(10000)
Description:
Hi
I have tried to create conference using MeetMe say ConfNo. 1234567, with
MeetMe Option sdmAS(10)L(10000).
I have print MeetMe Option in conf_exec() function of app_meetme.c after
ast_app_parse_options() this function.
I have found proper MeetMe Option i.e. sdmAS(10)L(10000) before call
ast_app_parse_options(), but after this function MeetMe Option just print
this value only as MeetMe Option sdmAS(10.
When I am looking for code. I found problem in main/app.c in
ast_app_parse_options() function, when it found ')' character, it will
store '\0' in variable so L(10000) option will not print.
======================================================================
----------------------------------------------------------------------
(0133356) jrose (manager) - 2011-04-04 16:28
https://issues.asterisk.org/view.php?id=17158#c133356
----------------------------------------------------------------------
This isn't really a bug. The only thing going on here is that the reporter
set the boot time to the same amount of time as the conference duration and
mistook the fact that the parser mangles the input string as a sign that
the input string wasn't being read properly by the parser. This isn't the
case.
I've tested this sequence of values and others in 1.6.2, 1.8, and trunk
and the behavior in each case is exactly as expected.
It's notable that if there were a problem like what's being described by
the reporter with ast_app_parse_options then multiple options with
arguments wouldn't work for any application.
Issue History
Date Modified Username Field Change
======================================================================
2011-04-04 16:28 jrose Note Added: 0133356
======================================================================
More information about the asterisk-bugs
mailing list