Hi everyone, Thank you all for your contributions to voiceops over the years, you quite literally make the voiceops distro what it is. With the coming of 2023, it's about time to pass the voiceops torch to the next generation. If you'd like to pick up the domain name and such, please contact me off list. Happy New Year to all, David Hiers David.hiers at cdk.com<mailto:David.hiers at cdk.com>
I was going to reach out to Jared Mauch, but it looks like he's already hosting mailman as it is. :-) ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com ----- Original Message ----- From: "David via VoiceOps Hiers" <voiceops at voiceops.org> To: "VoiceOps" <voiceops at voiceops.org> Sent: Monday, January 2, 2023 10:10:31 AM Subject: [VoiceOps] Passing the Voiceops torch Hi everyone, Thank you all for your contributions to voiceops over the years, you quite literally make the voiceops distro what it is. With the coming of 2023, it?s about time to pass the voiceops torch to the next generation. If you?d like to pick up the domain name and such, please contact me off list. Happy New Year to all, David Hiers David.hiers at cdk.com _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
And probably about half of the rest of the internet, too! From: Mike Hammett <voiceops at ics-il.net> Sent: Thursday, January 5, 2023 6:58 AM To: Hiers, David <David.Hiers at cdk.com> Cc: VoiceOps <voiceops at voiceops.org> Subject: [EXTERNAL] Re: [VoiceOps] Passing the Voiceops torch Caution: External email - Please use caution opening links and attachments from external senders I was going to reach out to Jared Mauch, but it looks like he's already hosting mailman as it is. :-) ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com ________________________________ From: "David via VoiceOps Hiers" <voiceops at voiceops.org<mailto:voiceops at voiceops.org>> To: "VoiceOps" <voiceops at voiceops.org<mailto:voiceops at voiceops.org>> Sent: Monday, January 2, 2023 10:10:31 AM Subject: [VoiceOps] Passing the Voiceops torch Hi everyone, Thank you all for your contributions to voiceops over the years, you quite literally make the voiceops distro what it is. With the coming of 2023, it?s about time to pass the voiceops torch to the next generation. If you?d like to pick up the domain name and such, please contact me off list. Happy New Year to all, David Hiers David.hiers at cdk.com<mailto:David.hiers at cdk.com> _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
Incidentally: as an elementary school-aged child, I learned Linux/UNIX thanks to Jared's public Linux server at nether.net <http://nether.net/>. I had an MS-DOS PC at home and no Internet access, but used the computers at the university library for a few hours a day. Nether.net <http://nether.net/> was one of the few places I could have a UNIX account despite being a nobody, so I could learn the shell folk traditions, and even compile some C code. I made great use of it and am deeply in his debt! Happy New Year to all! -- Alex -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800
On January 2, 2023, David Hiers wrote:
Hi everyone,
Thank you all for your contributions to voiceops over the years, you quite literally make the voiceops distro what it is.
With the coming of 2023, it?s about time to pass the voiceops torch to the next generation.? If you?d like to pick up the domain name and such, please contact me off list.
Happy New Year to all,
David Hiers
The torch has been passed. David has transferred the voiceops.org domain name over to me, and I am now hosting the DNS and landing page on $DAYJOB servers. The actual mailing list is still hosted at puck.nether.net. And thank you, David, for your years of work to the voiceops list. Much of what we do is so niche, it can be hard to find the resources we need anywhere else. Just look at the DTMF thread from yesterday! So let's all give a big thanks to David! I'll leave you with a few quotes from way way back in the archives. On July 30, 2009, David Hiers wrote:
"Mr. Watson -- come here -- I want to see you."
On August 5, 2009, Mark R Lindsey wrote:
At IPTComm a couple of years ago, Jonathan Rosenberg stood up and said the big problem was the walled gardens that are telcos and ITSPs. We carriers just aren't passing traffic via VoIP. Even Cisco customers aren't passing traffic within their own company; you'd have a BTS over here and a BTS over there, owned by the same Cable MSO, passing traffic via ISUP.
That was back in 2009. That is, sadly, still the case for many telcos, both large and small. And here are some excellent words from anorexicpoodle, written on October 21, 2009:
Since we, collectively, are steering one of the industries driving up individual utilization of the IPV4 address space as well as being one of the most sensitive to NAT which is the only way through which IPV4 has been sustained as long as it has; it seems like a worthy exercise to discuss our own, and the industries preparedness to adopt IPV6.
Has anyone out there had any experience using any of the open source platforms (OpenSIPS, Asterisk, SIPPY etc) with native IPV6? It seems like these projects are the best equipped right now to handle this move since they rely heavily on the network stack of the underlying OS.
Are there any endpoints or other CPE that anybody has had luck getting to work over native IPV6?
So far I am unaware of any carrier grade (meaning it costs a lot of money) softswtch platforms that are ready for this, or seem like they would be without a multi-year effort. Anybody out there that can enlighten us on this one?
Sincerely, Mike Johnston
Thanks for your leadership David. jj Sent from my iPhone
On Feb 14, 2023, at 5:02 PM, Mike Johnston via VoiceOps <voiceops at voiceops.org> wrote:
?On January 2, 2023, David Hiers wrote:
Hi everyone, Thank you all for your contributions to voiceops over the years, you quite literally make the voiceops distro what it is. With the coming of 2023, it?s about time to pass the voiceops torch to the next generation. If you?d like to pick up the domain name and such, please contact me off list. Happy New Year to all, David Hiers
The torch has been passed. David has transferred the voiceops.org domain name over to me, and I am now hosting the DNS and landing page on $DAYJOB servers. The actual mailing list is still hosted at puck.nether.net.
And thank you, David, for your years of work to the voiceops list. Much of what we do is so niche, it can be hard to find the resources we need anywhere else. Just look at the DTMF thread from yesterday!
So let's all give a big thanks to David!
I'll leave you with a few quotes from way way back in the archives.
On July 30, 2009, David Hiers wrote: "Mr. Watson -- come here -- I want to see you."
On August 5, 2009, Mark R Lindsey wrote: At IPTComm a couple of years ago, Jonathan Rosenberg stood up and said the big problem was the walled gardens that are telcos and ITSPs. We carriers just aren't passing traffic via VoIP. Even Cisco customers aren't passing traffic within their own company; you'd have a BTS over here and a BTS over there, owned by the same Cable MSO, passing traffic via ISUP.
That was back in 2009. That is, sadly, still the case for many telcos, both large and small.
And here are some excellent words from anorexicpoodle, written on October 21, 2009:
Since we, collectively, are steering one of the industries driving up individual utilization of the IPV4 address space as well as being one of the most sensitive to NAT which is the only way through which IPV4 has been sustained as long as it has; it seems like a worthy exercise to discuss our own, and the industries preparedness to adopt IPV6. Has anyone out there had any experience using any of the open source platforms (OpenSIPS, Asterisk, SIPPY etc) with native IPV6? It seems like these projects are the best equipped right now to handle this move since they rely heavily on the network stack of the underlying OS. Are there any endpoints or other CPE that anybody has had luck getting to work over native IPV6? So far I am unaware of any carrier grade (meaning it costs a lot of money) softswtch platforms that are ready for this, or seem like they would be without a multi-year effort. Anybody out there that can enlighten us on this one?
Sincerely, Mike Johnston _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Thanks David. Your work helped all us in large and small ways. ~Glen On 2/14/2023 17:45, jjones--- via VoiceOps wrote:
Thanks for your leadership David.
jj
Sent from my iPhone
On Feb 14, 2023, at 5:02 PM, Mike Johnston via VoiceOps<voiceops at voiceops.org> wrote:
?On January 2, 2023, David Hiers wrote:
Hi everyone, Thank you all for your contributions to voiceops over the years, you quite literally make the voiceops distro what it is. With the coming of 2023, it?s about time to pass the voiceops torch to the next generation. If you?d like to pick up the domain name and such, please contact me off list. Happy New Year to all, David Hiers The torch has been passed. David has transferred the voiceops.org domain name over to me, and I am now hosting the DNS and landing page on $DAYJOB servers. The actual mailing list is still hosted at puck.nether.net.
And thank you, David, for your years of work to the voiceops list. Much of what we do is so niche, it can be hard to find the resources we need anywhere else. Just look at the DTMF thread from yesterday!
So let's all give a big thanks to David!
I'll leave you with a few quotes from way way back in the archives.
On July 30, 2009, David Hiers wrote: "Mr. Watson -- come here -- I want to see you." On August 5, 2009, Mark R Lindsey wrote: At IPTComm a couple of years ago, Jonathan Rosenberg stood up and said the big problem was the walled gardens that are telcos and ITSPs. We carriers just aren't passing traffic via VoIP. Even Cisco customers aren't passing traffic within their own company; you'd have a BTS over here and a BTS over there, owned by the same Cable MSO, passing traffic via ISUP. That was back in 2009. That is, sadly, still the case for many telcos, both large and small.
And here are some excellent words from anorexicpoodle, written on October 21, 2009:
Since we, collectively, are steering one of the industries driving up individual utilization of the IPV4 address space as well as being one of the most sensitive to NAT which is the only way through which IPV4 has been sustained as long as it has; it seems like a worthy exercise to discuss our own, and the industries preparedness to adopt IPV6. Has anyone out there had any experience using any of the open source platforms (OpenSIPS, Asterisk, SIPPY etc) with native IPV6? It seems like these projects are the best equipped right now to handle this move since they rely heavily on the network stack of the underlying OS. Are there any endpoints or other CPE that anybody has had luck getting to work over native IPV6? So far I am unaware of any carrier grade (meaning it costs a lot of money) softswtch platforms that are ready for this, or seem like they would be without a multi-year effort. Anybody out there that can enlighten us on this one?
Sincerely, Mike Johnston _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
-- Glen Gerhard glen at cognexus.net 858.324.4536 Cognexus, LLC P.O.Box 12083 San Diego, CA 92039
participants (6)
-
abalashov＠evaristesys.com -
David.Hiers＠cdk.com -
glen＠cognexus.net -
jjones＠danrj.com -
mjohnston＠wiktel.com -
voiceops＠ics-il.net