From: Jaco Kroon <jaco@uls.co.za>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] last-rite: net-voip/captagent
Date: Wed, 14 Dec 2022 14:33:55 +0200 [thread overview]
Message-ID: <1888f296-9d5f-a849-a0e0-939bc6db5cba@uls.co.za> (raw)
# Jaco Kroon <jaco@uls.co.za> (2022-12-14)
# Multiple open bugs (bug #870910, bug #877731, bug #884815), only one
of which
# is trivial to solve.
# With more and more SIP traffic using TLS rather than plaintext UDP or TCP
# this is fast becoming less and less useful. You should rather use
# asterisk's res_hep which can also report encrypted SIP and RTP to any HEP
# compatible reporting tool (including Homer).
# I'm no longer using this and don't recommend it's use, if you want
this to be
# unmasked again, please contact me so that we can figure out how to
approach
# maintenance thereof.
# Removal on 2023-01-31.
net-voip/captagent
reply other threads:[~2022-12-14 12:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1888f296-9d5f-a849-a0e0-939bc6db5cba@uls.co.za \
--to=jaco@uls.co.za \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox