Daniel Ferrer | 14 Aug 17:36
Favicon

Submitted bug #13027 needs comment!

Hi all,

Once a month ago, I've submitted a bug to the bug tracker.
It is a chan_zap/dahdi channel name bug, from my point of view Zap 
channel names are wrong when you make a hookflash event. This occurs 
since Asterisk 1.4.5, before that the "hookflashed" chan name was 
Zap/1-2 for example, now are Zap/1-1 always. There are more detailed 
info and also a patch in the bug report.

The problem is that nobody has taken a look at it, in the past I've 
wrote to the list and you said that someone will take it, sorry for the 
delay, etc. Now I think that maybe there's a problem, maybe because I 
posted the bug before signing the license agreement (license is ok, and 
I can see the files attached when not logged). What should I do? I must 
close an reopen it? Can somebody take a look at it?

Thanks to all
bye
daniel

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

(Continue reading)

Leif Madsen | 15 Aug 19:43

Re: Submitted bug #13027 needs comment!

Daniel Ferrer wrote:
> Hi all,
> 
> Once a month ago, I've submitted a bug to the bug tracker.
> It is a chan_zap/dahdi channel name bug, from my point of view Zap 
> channel names are wrong when you make a hookflash event. This occurs 
> since Asterisk 1.4.5, before that the "hookflashed" chan name was 
> Zap/1-2 for example, now are Zap/1-1 always. There are more detailed 
> info and also a patch in the bug report.
> 
> The problem is that nobody has taken a look at it, in the past I've 
> wrote to the list and you said that someone will take it, sorry for the 
> delay, etc. Now I think that maybe there's a problem, maybe because I 
> posted the bug before signing the license agreement (license is ok, and 
> I can see the files attached when not logged). What should I do? I must 
> close an reopen it? Can somebody take a look at it?

Looks like Tilghman already committed your changes (with modifications 
by him to compensate for both names).

This was done on August 14th.

Thanks!
Leif Madsen.

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net
(Continue reading)

Daniel Ferrer | 15 Aug 20:56
Favicon

Re: Submitted bug #13027 needs comment!

Yes, I saw it yesterday
Thanks for response

bye
daniel

Leif Madsen escribió:
> Daniel Ferrer wrote:
>> Hi all,
>>
>> Once a month ago, I've submitted a bug to the bug tracker.
>> It is a chan_zap/dahdi channel name bug, from my point of view Zap 
>> channel names are wrong when you make a hookflash event. This occurs 
>> since Asterisk 1.4.5, before that the "hookflashed" chan name was 
>> Zap/1-2 for example, now are Zap/1-1 always. There are more detailed 
>> info and also a patch in the bug report.
>>
>> The problem is that nobody has taken a look at it, in the past I've 
>> wrote to the list and you said that someone will take it, sorry for the 
>> delay, etc. Now I think that maybe there's a problem, maybe because I 
>> posted the bug before signing the license agreement (license is ok, and 
>> I can see the files attached when not logged). What should I do? I must 
>> close an reopen it? Can somebody take a look at it?
> 
> Looks like Tilghman already committed your changes (with modifications 
> by him to compensate for both names).
> 
> This was done on August 14th.
> 
> Thanks!
(Continue reading)


Gmane