From what I could tell from the documentation:
Full is a snapshot of what the status is of everything at this moment. Delta is what changed between two specified points in time, regardless if it's current or not. Is that right? Neither would get me a complete history of any particular number, right? I'd have to use someone like 10XPeople (suggested to me offlist) to get a complete history? I'm assuming they just collected the day to day changes from the beginning of time to have a complete record. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com ----- Original Message ----- From: "Paul Timmins" <ptimmins at clearrate.com> To: "Mike Hammett" <voiceops at ics-il.net> Cc: "VoiceOps" <voiceops at voiceops.org> Sent: Wednesday, February 22, 2023 6:17:46 PM Subject: Re: [VoiceOps] Neustar SOA Archives I enjoyed it. You also get the last SV date and version as some of the fields if you want to know how long it's been on-net (or ported out). Handy. On Feb 22, 2023, at 7:11 PM, Mike Hammett <voiceops at ics-il.net> wrote: Oooh, that sounds fun for my dev guys to work with. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com ----- Original Message ----- From: "Paul Timmins" <ptimmins at clearrate.com> To: "Mike Hammett" <voiceops at ics-il.net> Cc: "VoiceOps" <voiceops at voiceops.org> Sent: Wednesday, February 22, 2023 5:28:06 PM Subject: Re: [VoiceOps] Neustar SOA Archives 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 is easy at that point. <blockquote> On Feb 22, 2023, at 6:18 PM, Mike Hammett via VoiceOps <voiceops at voiceops.org> wrote: How many of you are still using Neustar SOA? Any better ways of getting this information? After some personnel changes, we're cleaning up our systems. Things haven't been maintained properly over the years. We're going through disabled (but not ported away or deleted) numbers in Metaswitch to see what their fate should be. I ran an SV search for all ported out numbers, exported to Excel, and then had my staff compare that to what we had configured in Metaswitch, along with seeking their recommendation as to whether we set it to ported out, keep it as-is, or delete the entry entirely. That recommendation would be with our guidance as to when to do what. I spot checked their recommendations and found some messes. One of which is that the SOA export just managed to skip one line from 2018, so that was fun. Another is that a number that a former customer had doesn't show up on that list for ported out, but does show up on the ported in list. When I do an SV Query, it shows up as someone else. How can that be congruent? Is there a way to get more that current and 1st prior? Is the SV search supposed to include everyone that ported away from us, or just those that had us as their first prior carrier? I'd like to not have them issue an SV query for each potentially ported away number. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops </blockquote>