On 06/09/24 17:27, Jonas Smedegaard wrote:
Please subscribe to our mailinglist and discuss more there, and please
join our Salsa team - see details athttps://wiki.debian.org/Teams/VoIP/
I'm a long time subscriber from your mailinglist... and I've just
applied for a Salsa account.
On 06/09/24 16:35, Jonas Smedegaard wrote:
I can do the task of releasing patches-applied updates, so you need not
be an official Debian developer to help. All you need is dedication to
keep an eye on stable and oldstable branches of Debian, and the ability
to*try* to apply patches. If you not
the unstable release).
Thank you and best regards,
José Miguel Gonçalves
Debian project, in the maintenance of
very stable systems that I use in my work and private life.
Going to a more specific question, are you considering packaging
Asterisk 20 for bookworm-backports?
Best regards,
José Miguel Gonçalves
On 06/09/24 14:10, Jonas Smedegaard wrote:
Hi José,
Quoting
use Debian packages (even if I need to backport them from
unstable to bookworm) or if I need to go in other direction (find some
alternative Debian packaging, or compile/package it myself).
Best regards,
José Miguel Gonçalves
Hi Jeremy,
On 13/07/23 23:01, Jeremy Davis wrote:
Can you confirm that the current default bookworm fail2ban
config/regex works with sshd with just this change (to 'backend' in
/etc/fail2ban/jail.conf)? Or are further adjustments required?
Yes, I can confirm that fail2ban sshd jail works fin
Hi,
As Debian opted by systemd journal as the default logging mechanism for
bookworm, maybe a better option would be to change the default
configuration in '/etc/fail2ban/jail.conf' to select journal as the
logging source, i.e., instead of setting 'backend = auto', set 'backend
= systemd'.
-backports.
Best regards,
José Miguel Gonçalves
-- System Information:
Debian Release: 11.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP
Any chance to enable this support soon (in bullseye or bullseye-backports)?
Best regards,
José Gonçalves
On 13/07/21 14:04, Chris Hofstaedtler wrote:
Control: tags -1 - confirmed
Hi Bernhard,
* Bernhard Schmidt [210428 15:41]:
hrm, Jose reported this issue appearing with the stable release only
(16.16.1 from his (back then) private backport fixing it), you tagged
the bug as still found in 16.16.
Hi,
I'm currently using the asterisk build from buster-backports (16.16.1)
and the leak does not happen on it.
Best regards,
José Gonçalves
Hi,
The following patch solves this issue for me:
--- a/mpath.c
+++ b/mpath.c
@@ -226,7 +226,7 @@
enum id_input id)
{
printf("DEST ADDR NEXT HOP IFACE\tSN\tMETRIC\tQLEN\t"
- "EXPTIME\t\tDTIM\tDRET\tFLAGS\tHOP_COUNT\tPATH_CHANGE\n");
+ "EXPTIME\tDTIM\tDRET\tFLAGS\
Will this be fixed in bullseye?
Best regards,
José Gonçalves
Hi,
Any updates regarding this bug ?
I'm currently building my own asterisk backport from testing sources in
order to "fix" this issue on my server.
If this bug is not to be fixed in buster, is there any chances in
providing asterisk 16.15 packages in buster-backports ?
Best regards,
José Gon
On 02/12/20 18:50, sergio wrote:
On 15/11/2020 16:55, Andrej Shadura wrote:
I’ve got reports it completely broke connectivity on certain drivers.
Could you provide a separate package then (hostapd-mesh for example)?
A separate package could be a solution to anyone that needs encrypted
Me
On 18/11/20 11:14, Paride Legovini wrote:
Could you perhaps test how the version of 'iw' currently in testing
behaves?
For sure. This is how it looks with testing:
$ iw --version
iw version 5.9
$ sudo iw dev mesh0 mpath dump
DEST ADDR NEXT HOP IFACE SN METRIC QLEN
Hi,
I would like to upvote this issue.
What's preventing Mesh support from being added to Debian's
wpasupplicant package?
Best regards,
José Gonçalves
Package: iw
Version: 5.0.1-1
Severity: minor
Dear Maintainer,
Using iw to display a list of Mesh paths leads to a wrongly formatted output:
$ sudo iw dev mesh0 mpath dump
DEST ADDR NEXT HOP IFACE SN METRIC QLENEXPTIME
DTIMDRETFLAGS
64:69:4e:XX:XX
Hi again,
Adding some more info on this issue.
Using FreePBX statistics dashboard, I've also noticed an increase on the
network traffic and CPU usage.
All of these drop drastically as soon I restart the Asterisk service.
I've backported asterisk testing version (1:16.10.0~dfsg-1) to buster
a
Package: asterisk
Version: 1:16.2.1~dfsg-1+deb10u1
Severity: important
Dear Maintainer,
* What led up to the situation?
Executing asterisk in a system configured with around 250 VoIP phones
using PJSIP, my 8 GB RAM's server rapidly (~ 2 days) rans out of memory.
The phones are confi
Hi,
The default '/etc/asterisk/modules.conf' packaged in "asterisk-config" has these
problems, and should be fixed for something that does not give 'undefined symbols'
out of the box.
After some experiments, what worked well for me in a Debian 8 installation with
FreePBX was this:
[modules
21 matches
Mail list logo
