Ketil Vestby wrote:
Thursday 26 June 2008, Moritz Muehlenhoff wrote:
..
What's the status? Shall we push the fix in the upcoming r4 release?
The status: The patch did not do its job, instead it did open up for a rather
huge set of instability problems in addition to the original problem. I have
Thursday 26 June 2008, Moritz Muehlenhoff wrote:
..
>What's the status? Shall we push the fix in the upcoming r4 release?
Not unless you want to break the asterisk in the r4 release badly.
The status: The patch did not do its job, instead it did open up for a rather
huge set of instability probl
On Tue, May 27, 2008 at 09:08:52PM +0300, Faidon Liambotis wrote:
> Florian Weimer wrote:
>> * Faidon Liambotis:
>>
>>> security team, what do you think?
>>> Should I prepare a new version with these changes and upload it to
>>> security-proposed-updates?
>>
>> Do you mean stable-proposed-updates?
Florian Weimer wrote:
* Faidon Liambotis:
security team, what do you think?
Should I prepare a new version with these changes and upload it to
security-proposed-updates?
Do you mean stable-proposed-updates? That's up to the stable release
managers.
I don't like uploading such a change as a
* Faidon Liambotis:
> security team, what do you think?
> Should I prepare a new version with these changes and upload it to
> security-proposed-updates?
Do you mean stable-proposed-updates? That's up to the stable release
managers.
I don't like uploading such a change as a security update if w
tags 482997 + confirmed
thanks
Torgeir Skjøtskift wrote:
When making calls involving IAX2 channels, sound is extremely choppy
and CPU usage spikes.
Messages on the CLI indicate problems while channels are active:
WARNING[12301]: File chan_iax2.c, Line 4436 (socket_read): Received
mini frame bef
6 matches
Mail list logo
