Summary:ASTERISK-15934: MeetMe Options S(10)L(10000)
Reporter:ChandrakantS (chandrakantsolanki)Labels:
Date Opened:2010-04-09 06:09:09Date Closed:2011-06-07 14:05:31
Versions:Frequency of

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.


Edit: Removed inline patch - pabelanger
Comments:By: Paul Belanger (pabelanger) 2010-04-09 10:42:37

Your report is lacking information, see below.  If you are supplying a patch, do not include it inline in your comments (again see below). Also, what version of Asterisk is this?  

Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "Asterisk Issue Guidelines" http://www.asterisk.org/developers/bug-guidelines. We'd be grateful if you would then provide a more complete description of the problem.

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

This likely includes output from the console with debug level logging, a SIP trace (if this is SIP related), and configuration information such as dialplan (e.g. extensions.conf) and channel configuration (e.g. sip.conf).


By: Leif Madsen (lmadsen) 2010-04-12 10:02:41

Additionally, if this is your first patch, please sign the electronic license agreement (link available at the top in the link bar) prior to uploading your patch. Thanks!

By: Paul Belanger (pabelanger) 2010-04-28 16:20:16

Ping!  Does the reporter want to update a patch for this?

By: Leif Madsen (lmadsen) 2010-05-13 09:09:53

Issue suspended. The reporter is welcome to reopen the issue if they are willing to attach the patch to this issue.

By: Leif Madsen (lmadsen) 2010-05-13 09:10:52

Actually on second thought the reporter at least states how the resolve the issue, so I'll import this into our internal queue and see if it bubbles up high enough on the priority scale.

By: Leif Madsen (lmadsen) 2010-05-13 09:11:13

It would of course still be ideal if the original reporter attached their patch.

By: Jonathan Rose (jrose) 2011-04-04 16:28:49

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.

It would be prudent though to provide some verbose messages related to the L option so that the operator can see that they have been set to avoid confusion like this in the future, so I'll be working on that tomorrow.