Summary:ASTERISK-06639: Join/Leave (i) option, notifies the leaves with incorrect name.
Reporter:dp (dp)Labels:
Date Opened:2006-03-28 10:46:31.000-0600Date Closed:2006-05-24 15:08:08
Versions:Frequency of
Environment:Attachments:( 0) as
Description:When 'i' option is selected, the name of the person who joined last in the conference will be announced as the name of the person who leaves first from the conference.
ex:- If A, B and C joins the conf in that order. No matter who leaves the conference first, the announcement will be C left the conference. The announcement when the second person leaves will be B left the conference.
Comments:By: vortex_0_o (vortex_0_o) 2006-03-28 11:09:31.000-0600

I can't seem to duplicate this with current 1.2 branch - can you check using the current version

By: dp (dp) 2006-03-28 13:46:17.000-0600

I could reproduce this issue with 1.2.4 also.

By: BJ Weschke (bweschke) 2006-03-29 22:40:28.000-0600

1.2.4 isn't current. We're at 1.2.6 now and will probably be at 1.2.7 shortly. Pls test with that and if you're still having the problem, let's get a trace so we can track down the problem and get it fixed. Thanks.

By: dp (dp) 2006-03-30 08:00:46.000-0600

Look like it is fixed in Asterisk 1.2.6, I coudn't reproduce this problem in that release. Thank you.

By: BJ Weschke (bweschke) 2006-03-30 08:08:44.000-0600

Fixed with previous commits prior to 1.2.6.

By: dp (dp) 2006-05-23 14:47:34

This issue is back in 1.2.7.  In this release, for the first person who leaves the conference the announcement says the name of the last person who joined the conference has left, when  all other people leave the conference the announcement says " has left the conference" with out identifying the person.

By: BJ Weschke (bweschke) 2006-05-23 15:37:24

ok. can we can a DEBUG / VERBOSE trace of what's going on?

By: dp (dp) 2006-05-24 11:00:21

Attaching the log.

By: Matt O'Gorman (mogorman) 2006-05-24 15:08:07

Committed revision 30037. into 1.2
Committed revision 30068. into trunk

app_meetme was using ast_max_exten and not path_max for the length of the path creation this should solve your problem.