Re: [VoiceOps] Nortel Equipment

Maybe check with the Connections Museum in Seattle?  With their recent acquisition of a DMS-10, they might be interested. https://www.telcomhistory.org/connections-museum-seattle/ On 2024-02-26 15:34, Ronald Loneker via VoiceOps wrote: Hi Everyone - Not sure where to find a home for this,

Re: [VoiceOps] Spike in customers numbers showing SPAM?

We had two reports on 2024-01-25.  Both were reporting that Verizon cellphone recipients would see "Potential Spam" if they called from their main number. One is a manufacturer in one of our ILEC exchanges, OCN 1505. The other is a school in one of our CLEC exchanges, OCN 914F. These are A

Re: [VoiceOps] troubleshooting RTP loss - and does anyone use webair/opti9?

mtr https://en.wikipedia.org/wiki/MTR_(software) It isn't specific to VoIP. But it is still a very good first step in troubleshooting which hop the packet loss begins at. Unlike the basic traceroute tools that come with Linux or Windows, it can run continuously for however long you need,

Re: [VoiceOps] Voice Peering

Who can source email from a domain is more-or-less a solved problem by using DNS SPF records. An SPF record is a list of IP addresses[1] that is allowed to send email for a domain. When an email server receives an email, best practice is to do a DNS lookup for the SPF of the alleged sender

Re: [VoiceOps] SS7 Landscape

On 2023-10-24 15:11, Mike Hammett wrote: Recommend\don't recommend? Anything to watch out for? The offer I got was attractive, but not everything that's attractive is what it seems. We used to have Onvoy/Inteliquent SS7 via TDM, which was reliable.  Two A-Links, to two geographically

Re: [VoiceOps] SS7 Landscape

Yes.  Any particular questions? On 2023-10-24 08:18, Mike Hammett via VoiceOps wrote: Any experience with Inteliquent for SS7\SIGTRAN services? - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com

Re: [VoiceOps] A2P-aaS

That's what we use for automated notifications to on-call techs of P1 tickets. We wrote code to email a short message to the appropriate domain. This list we use is Inteliquent's: https://help.inteliquent.com/sending-emails-to-sms-or-mms For example: AT: num...@txt.att.net (SMS),

Re: [VoiceOps] Directory Listings

On 2023-08-21 17:16, Mike Hammett via VoiceOps wrote: We've come across some legacy customers that have directory listings through us (or, well, at least we're paying Frontier for them). 1. Are those a thing in the VoIP space? Can I go to {insert SIP provider here} and they can place

Re: [VoiceOps] Carriers that support cic codes

On 2023-08-04 09:37, Jeff Anderson via VoiceOps wrote: If a SIP carrier wanted to support equal access, is there anything like a SIP tandem provider that can accept any Carrier Identification Code (cic=) and route to the appropriate LD carrier? The TDM equivalent might be something like

Re: [VoiceOps] Call term misrouting?

On 2023-07-26 17:43, Paul Timmins via VoiceOps wrote: I wouldn't be surprised to see carriers dumping these calls via a GSM gateway, this is really common in europe with gray routes. It'd explain why you get weird cellular voicemail, if they sent the number to the cell phone wrong to actually

Re: [VoiceOps] Call term misrouting?

I serve a rural area. I do the technical "make it work" stuff. I'm generally only involved in the business dealings insofar as determining technical incompatibilities (draw 7 red lines, all perpendicular, some with green ink and some with transparent). That said, please forgive any errors

Re: [VoiceOps] No-commit international calling

On 2023-07-13 14:34, Ross Tajvar via VoiceOps wrote: Looks like voip.ms is one option. Does anyone have any other suggestions? I use voip.ms for my personal tinkering.  I don't have much of a /need/ for them, since I operate an entire telephone company of my own (my

Re: [VoiceOps] STIR/SHAKEN warning!

On 2023-07-12 16:37, Nathan Anderson via VoiceOps wrote: By the way, love your test tool service.  Thanks for putting it together and maintaining it...what a gift to the community. There are a handful of S/S testing tools out there, but yours is easily the most comprehensive...most just

Re: [VoiceOps] dynect oracle end of life

Wherever possible, we use RFC 2136, to the primary authoritative name server. pfSense firewalls, for example, support RFC 2136 for Dynamic DNS (tracking the WAN IP when DHCP changes it) and for Acme Certificates (demonstrate control of the FQDN). RFC 2136 is also a nice method for internal

Re: [VoiceOps] 911 Records of Inbound-Only TNs

A maybe simpler example to what you are asking would be TEEN lines, where calling the TEEN number makes the parent station ring with a distinctive pattern. The subscriber has no way of making an outbound call with that TEEN number. Should we bother setting up a 911 record for that TEEN

Re: [VoiceOps] Rate Center Geodata

Nice work, Paul!  I spot checked a few that are in my area.  The coordinates are not perfect, but are close.  In general, the coordinates are within a mile of the central office. ___ VoiceOps mailing list VoiceOps@voiceops.org

Re: [VoiceOps] Call recording and single party versus all party consent states

Good question! I would love to see some sort of matrix (calling state/called state). It might also depend on which side is the originator. For example, AZ->CA might be different than CA->AZ. Everything will get even more complicated if a call involves a transfer, or a conference bridge. I

Re: [VoiceOps] Neustar SOA Archives

On 2023-02-22 17:28, Paul Timmins via VoiceOps wrote: Ask to get a BDD set up from the NPAC and you'll have a copy of the regional LNP database every morning, piping fresh. You'l want to write a script or something because the files are a lot too big for something like excel, but a comparison

Re: [VoiceOps] Passing the Voiceops torch

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

Re: [VoiceOps] test

DNS test looks good. ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

Re: [VoiceOps] Abandoned Ported Numbers

Can anybody reference any regulations that would /require/ such numbers be returned?  Something from say, the FCC's website? I'm looking to provide for something more than just, "common practice". I appreciate everybody's help! ___ VoiceOps mailing

[VoiceOps] Abandoned Ported Numbers

Say a subscriber ports a number to/from a different telco. Then, after some time, the subscriber decides they no longer want the phone number (or phone service in general). What should be done with this abandoned number? Should the number immediately be returned to the donor telco? Should

Re: [VoiceOps] Lack of Sandbox

I wish more 911 systems had a 933 number. I've made actual 911 calls for testing purposes more times than I can remember. I always call the Sheriff's Office admin line first, asking if this is an alright time. But sometimes my 911 call is routed to a different county than I expected, and