<br><font size=2 face="sans-serif">I haven't got this narrowed down enough
yet to put a report up in the bug reporter, but I thought I'd relate the
info I have here in case others are seeing similar. Also, I'm pretty
new to working on core asterisk code and don't want to step on toes if
I'm doing something incorrectly.</font>
<br>
<br><font size=2 face="sans-serif">I have patched my own app_meetme.c with
some functionality I'm testing and its working fine. Before submitting
it however, I wanted to follow the directions so I cleared the build tree
on my machine, pulled the latest trunk, and went to apply the same changes.
That way I could submit my proposed patch based on the most current
trunk as described by the doc on the developers site.</font>
<br>
<br><font size=2 face="sans-serif">There were significant changes in the
recordthread() part of the app, so clearly someone is working in there.
The problem is the same code that's working for me in my own patched
2.7.1 is having just a series of bizarre problems that I can't account
for. In particular, the code runs fine the first time through, but
if I hang up and reenter the conference several things go wrong. It
almost seems as if some of the conference structure members are scrambled
or half initialized. Since my use of the app involves starting and
stopping the same conference number frequently, it may be that I'm testing
something others don't do. At one point, I seemed to be getting
the wrong values in some channel variables -- getting the values of other
channel variables instead. Very odd.</font>
<br>
<br><font size=2 face="sans-serif">The other issue I've had is that even
building the current trunk from svn (yesterday) after installation the
apps/app_hasnewvoicemail module was crashing on load. Surely that
means something about my build environment isn't quite the same because
I can't imagine it would have made the trunk build that way. </font>
<br>
<br><font size=2 face="sans-serif">I'm not entirely sure what's up. I
can't 100% rule out my own code changes yet so I'm not declaring it a bug
so much as asking of there are others with known issues here, or if something
significant has changed that I'm unaware of. Clearly the conference
structure itself has changed and now uses lists instead of next record
pointers. That seems to be something done in many cases throughout
the code. Perhaps the issue has to do with how lists are handled?</font>
<br>
<br><font size=2 face="sans-serif">Any thoughts?</font>
<br>
<br><font size=2 face="sans-serif">I've gone back to 2.7.1 and seem to
be having no trouble with the source as provided or with my own patch to
app_MeetMe.</font>
<br>
<br>
<br><font size=2 face="sans-serif"> ----------------------------------------------------<br>
Andrew Pollack<br>
President, Northern Collaborative Technologies<br>
http://www.thenorth.com/apblog<br>
Free World Dialup: 713144<br>
----------------------------------------------------<br>
</font>