VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
February 2023
- 23 participants
- 55 messages
Wireless Canada Porting, the CRTC, and the Stupid Process
by beckman@angryox.com
Excellent detail, thank you Denver!
On Fri, 24 Feb 2023, Denver Gingerich wrote:
> On Thu, Feb 23, 2023 at 02:59:05PM -0500, Peter Beckman via VoiceOps wrote:
>> Add to this what happens when the End User is NOT PHYSICALLY in Canada.
>>
>> - MAYBE the Canada Carrier is able to indicate when they send the Port
>> Request to the Losing Carrier
>> - Customer must be notified to start calling the Losing Carrier, but we
>> all might not know when the 90 minute clock starts/started
>> - Customer MUST call LSP to approve Port
>> - Sometimes they are on hold longer than the 90 minute window
>> - The SMS is sent from a Canada-only Short Code, so even if they can
>> receive it while roaming, the roaming carrier does not know how to
>> route the SMS destination back to the LSP for approval
>
> I'm not sure about this last part - my experience suggests that SMS
> routing is based on the user's "SIM carrier", not whoever they're roaming
> on (unlike voice routing). In particular, this means you can't use local
> short codes if you're roaming, which is what I've noticed anecdotally in
> my own travelling. So in theory the short code message should make it to
> you, and your reply should succeed (though who knows how much that will
> cost you).
>
> Anyway, it sounds like you do have some contrary experience, and I don't
> wish to dispute that. I guess we haven't run into many people who are
> roaming but want to port out at the same time.
Huh, this would explain a handful of customers who are roaming who have
said they replied and it got approved. It definitely seems to depend on
what country they are roaming in, and may even depend on the carrier they
are roaming on, because I also have a handful of cases where they replied
to the SMS and it did NOT go through, as the request was rejected as no
response.
>> Overall I give the CRTC an F for this process.
>
> Due to my customers' experiences, I would make it more of a D. While I
> agree there are huge problems, especially for operators like you and me
> that can't control the LNP submission time, customers of mine do like
> this verification step, esp. versus the US carriers they're aware of,
> which are much more prone to unauthorized port outs.
It would be much better if customers who are OUTSIDE of Canada had a
better, online-based process to approve a Port Out request. It is fine if
customers are in Canada, but far harder when outside of Canada.
> I'm not aware of one. We have an account with one Canadian carrier,
> which we've repeatedly asked this question (i.e. about API access for
> port-ins), and they still don't have it. However, we haven't tried all
> of them. The usual suspects you could ask would be Distributel (aka
> ThinkTel, for business), Fibernetics, ISP Telecom, and Iristel.
Fibernetics bulk-submits port requests at 10am EST daily. This is an
annoying legacy-feeling delay, but at least it is predictable. ThinkTel
and IrisTel CAN submit ports in an automated fashion, but the feedback
loop is very slow. And like you said, through a US party like Bandwidth,
we do not get a very good/reliable signal for when the LSP receives the
Port Out request, and thus, if the customer is outside of Canada, and does
not have their SIM, we do not have a way to communicate WHEN they need to
call the LSP to approve the Port Out.
>> Is it just exponentially more expensive when the End User cannot gain
>> approval on the first Request?
>
> I don't know about exponential, but more expensive for sure.
Argh!
>> I'm also finding that getting a webhook or notification when the request is
>> actually sent to the LSP is also difficult, and so notifying the End User
>> of when to call is also difficult/impossible.
>
> Yeah, this is tricky, since most big carriers don't handle Canadian ports
> themselves, and so it's a human poking at the real carrier's system, who
> then reports back to your porting request manually. It seems that this
> causes the actual port request to be sent 24-48 hours after we submit it,
> which isn't super helpful for telling the customer when they should start
> looking at their phone for that 90-minute-expiry SMS.
>
> While it's not perfect, we do appear to get a notification closely
> correlated with this event from Bandwidth. In particular, when
> subscribed to porting updates by email (which are also available via
> webhook), we receive an email like the following approximately 5 minutes
> before the SMS is sent from the LSP:
Agreed. Bandwidth is consistent. The challenge is that they use IrisTel,
ThinkTel, AND NOW Fibernetics. While the BW Notes was mostly reliable for
IrisTel (PON IRISxxx) and ThinkTel (PON PORTSxxx), they rolled out
Fibernetics (0Xxxx) without anyone in the BW Porting Team seeming to know
how to handle resubmits, nor when Fibernetics submitted ports (IrisTel &
ThinkTel are within 5-30 minutes of the below notice; Fibernetics is once
a day at 10am EST; Sometimes challenging to write code to automate this
process!!!).
Bandwidth also requests FOC for 5 biz days out (won't do it any sooner,
maybe a THinkTel Restriction?), whereas Iristel through Inteliquent allows
for 1 biz day FOC Requested for Wireless.
> I confirmed this today actually, as I had a friendly customer who was
> informing me about each step of the process, and I matched up the
> timestamps to see which events corresponded to their SMS receipt.
>
> Anyway, I don't know if this helps, and can't say for sure that it
> happens every time with Bandwidth, but anecdotally it seems like it may
> be close to what you want (or as close as you'll get anyway).
>
> FWIW, we know that Bandwidth normally uses Distributel (ThinkTel) for
> their Canadian ports, though it seems occasionally they use Iristel
> instead. So this may be a(n API?) service you could get direct from
> either of those two.
>
> In any case, we are very interested to know if you get anywhere with
> this, as we'd really like to improve the situation for our customers with
> Canadian numbers too.
It is absolutely useful and much appreciated. I have a call with Iristel
later today to find out if going direct is a better value and would
provide us with faster service.
Cancelations of the underlying Canada port seem to take 24 hours and
really slow down the whole process.
Beckman
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com https://www.angryox.com/
---------------------------------------------------------------------------
Feb. 24, 2023
Wireless Canada Porting, the CRTC, and the Stupid Process
by denver@ossguy.com
On Thu, Feb 23, 2023 at 02:59:05PM -0500, Peter Beckman via VoiceOps wrote:
> In November 2021, without much notice to the industry AFAICT, the CRTC
> changed the process for Wireless Canada Ports:
>
> - Upon receiving a Port Out Request, the Losing Carrier sends an SMS to
> the End User
> - The End User has 90 minutes to reply affirmatively to the SMS
> - If they fail to do so, the Port Request is automatically canceled
This matches what we have experienced. This has caused us to have to re-submit several orders because the user wasn't aware of this requirement and wasn't watching their phone in that 90-minute window (whose start time we can't control, per below).
> For most Canada carriers I can find, they seem to charge you both to submit
> the Port Request, and then to Cancel the Port Request.
I am unaware of cancellation charges we pay, but new port requests (including re-submits, as often required per above) do cost us. More on that below.
> Add to this what happens when the End User is NOT PHYSICALLY in Canada.
>
> - MAYBE the Canada Carrier is able to indicate when they send the Port
> Request to the Losing Carrier
> - Customer must be notified to start calling the Losing Carrier, but we
> all might not know when the 90 minute clock starts/started
> - Customer MUST call LSP to approve Port
> - Sometimes they are on hold longer than the 90 minute window
> - The SMS is sent from a Canada-only Short Code, so even if they can
> receive it while roaming, the roaming carrier does not know how to
> route the SMS destination back to the LSP for approval
I'm not sure about this last part - my experience suggests that SMS routing is based on the user's "SIM carrier", not whoever they're roaming on (unlike voice routing). In particular, this means you can't use local short codes if you're roaming, which is what I've noticed anecdotally in my own travelling. So in theory the short code message should make it to you, and your reply should succeed (though who knows how much that will cost you).
Anyway, it sounds like you do have some contrary experience, and I don't wish to dispute that. I guess we haven't run into many people who are roaming but want to port out at the same time.
> Overall I give the CRTC an F for this process.
Due to my customers' experiences, I would make it more of a D. While I agree there are huge problems, especially for operators like you and me that can't control the LNP submission time, customers of mine do like this verification step, esp. versus the US carriers they're aware of, which are much more prone to unauthorized port outs.
> What are others here doing for Canada Ports? Are the costs similar to what
> I'm finding, USD$3-6 per TN, USD$3-6 to cancel the order, then another
> USD$3-6 to resubmit?
We pay US$4 per TN, plus US$4 to re-submit, but AFAICT $0 to cancel. We normally do these through Bandwidth, which charges us US$3 for our other (i.e. US) ports, as a point of comparison.
> Is there a carrier that does this extremely well? Must be automated too.
I'm not aware of one. We have an account with one Canadian carrier, which we've repeatedly asked this question (i.e. about API access for port-ins), and they still don't have it. However, we haven't tried all of them. The usual suspects you could ask would be Distributel (aka ThinkTel, for business), Fibernetics, ISP Telecom, and Iristel.
> Is it just exponentially more expensive when the End User cannot gain
> approval on the first Request?
I don't know about exponential, but more expensive for sure.
> I'm also finding that getting a webhook or notification when the request is
> actually sent to the LSP is also difficult, and so notifying the End User
> of when to call is also difficult/impossible.
Yeah, this is tricky, since most big carriers don't handle Canadian ports themselves, and so it's a human poking at the real carrier's system, who then reports back to your porting request manually. It seems that this causes the actual port request to be sent 24-48 hours after we submit it, which isn't super helpful for telling the customer when they should start looking at their phone for that 90-minute-expiry SMS.
While it's not perfect, we do appear to get a notification closely correlated with this event from Bandwidth. In particular, when subscribed to porting updates by email (which are also available via webhook), we receive an email like the following approximately 5 minutes before the SMS is sent from the LSP:
From: dashboard-updatenotification at bandwidth.com
Subject: Note has been added. Customer Order ID: [order_id]
*** Replies above this line will be appended as notes to the order if applicable ***
*** Please limit replies to 10 lines of text or less ***
Note Added
port_in: [UUID]
Last Modified Date: [current time]
Note: Hi Team! Your order (PORTS[digits]) has been submitted to our vendor and has a requested port date of MM/DD. Updates to follow in 2-3 business days. Thanks!
I confirmed this today actually, as I had a friendly customer who was informing me about each step of the process, and I matched up the timestamps to see which events corresponded to their SMS receipt.
Anyway, I don't know if this helps, and can't say for sure that it happens every time with Bandwidth, but anecdotally it seems like it may be close to what you want (or as close as you'll get anyway).
FWIW, we know that Bandwidth normally uses Distributel (ThinkTel) for their Canadian ports, though it seems occasionally they use Iristel instead. So this may be a(n API?) service you could get direct from either of those two.
In any case, we are very interested to know if you get anywhere with this, as we'd really like to improve the situation for our customers with Canadian numbers too.
Denver
https://jmp.chat/
Feb. 24, 2023
Wireless Canada Porting, the CRTC, and the Stupid Process
by beckman@angryox.com
I'm finding that Canada Ports, due to the CRTC actions, are increasingly
costly.
In November 2021, without much notice to the industry AFAICT, the CRTC
changed the process for Wireless Canada Ports:
- Upon receiving a Port Out Request, the Losing Carrier sends an SMS to
the End User
- The End User has 90 minutes to reply affirmatively to the SMS
- If they fail to do so, the Port Request is automatically canceled
For most Canada carriers I can find, they seem to charge you both to submit
the Port Request, and then to Cancel the Port Request.
Add to this what happens when the End User is NOT PHYSICALLY in Canada.
- MAYBE the Canada Carrier is able to indicate when they send the Port
Request to the Losing Carrier
- Customer must be notified to start calling the Losing Carrier, but we
all might not know when the 90 minute clock starts/started
- Customer MUST call LSP to approve Port
- Sometimes they are on hold longer than the 90 minute window
- The SMS is sent from a Canada-only Short Code, so even if they can
receive it while roaming, the roaming carrier does not know how to
route the SMS destination back to the LSP for approval
Overall I give the CRTC an F for this process.
What are others here doing for Canada Ports? Are the costs similar to what
I'm finding, USD$3-6 per TN, USD$3-6 to cancel the order, then another
USD$3-6 to resubmit?
Is there a carrier that does this extremely well? Must be automated too.
Is it just exponentially more expensive when the End User cannot gain
approval on the first Request?
I'm also finding that getting a webhook or notification when the request is
actually sent to the LSP is also difficult, and so notifying the End User
of when to call is also difficult/impossible.
Beckman
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com https://www.angryox.com/
---------------------------------------------------------------------------
Feb. 23, 2023
Neustar SOA Archives
by mjohnston@wiktel.com
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 is easy at that point.
I didn't know that was a thing.? Today I learned.? That will help us
with all sorts of automated processes.? Thank you!
Feb. 23, 2023
Neustar SOA Archives
by voiceops@ics-il.net
There's stuff in there that's probably ten years old.
-----
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: "Paul Timmins" <ptimmins at clearrate.com>
Cc: "Mike Hammett" <voiceops at ics-il.net>, "VoiceOps" <voiceops at voiceops.org>
Sent: Thursday, February 23, 2023 9:30:23 AM
Subject: Re: [VoiceOps] Neustar SOA Archives
Well, more clearly - You can tell when they ported last. Ideally if you have cleaned up the switch recently, there would not be more than one port between now and then.
If you waited so long that the customer has changed carriers more than once, well...
On Feb 23, 2023, at 10:28 AM, Paul Timmins via VoiceOps <voiceops at voiceops.org> wrote:
Correct. I can't imagine much why it matters when they left if you're just trying to clean up the meta, but I'd talk to the NPAC because they have the historical data and may have some other way to share it.
<blockquote>
On Feb 23, 2023, at 9:10 AM, Mike Hammett <voiceops at ics-il.net> wrote:
>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.
<blockquote>
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>
</blockquote>
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
</blockquote>
Feb. 23, 2023
Neustar SOA Archives
by ptimmins@clearrate.com
Well, more clearly - You can tell when they ported last. Ideally if you have cleaned up the switch recently, there would not be more than one port between now and then.
If you waited so long that the customer has changed carriers more than once, well...
On Feb 23, 2023, at 10:28 AM, Paul Timmins via VoiceOps <voiceops at voiceops.org> wrote:
Correct. I can't imagine much why it matters when they left if you're just trying to clean up the meta, but I'd talk to the NPAC because they have the historical data and may have some other way to share it.
On Feb 23, 2023, at 9:10 AM, Mike Hammett <voiceops at ics-il.net> wrote:
>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<http://www.ics-il.com/>
Midwest Internet Exchange
http://www.midwest-ix.com<http://www.midwest-ix.com/>
________________________________
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<http://www.ics-il.com/>
Midwest Internet Exchange
http://www.midwest-ix.com<http://www.midwest-ix.com/>
________________________________
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.
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<http://www.ics-il.com/>
Midwest Internet Exchange
http://www.midwest-ix.com<http://www.midwest-ix.com/>
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto: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
Feb. 23, 2023
Neustar SOA Archives
by ptimmins@clearrate.com
Correct. I can't imagine much why it matters when they left if you're just trying to clean up the meta, but I'd talk to the NPAC because they have the historical data and may have some other way to share it.
On Feb 23, 2023, at 9:10 AM, Mike Hammett <voiceops at ics-il.net> wrote:
>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<http://www.ics-il.com/>
Midwest Internet Exchange
http://www.midwest-ix.com<http://www.midwest-ix.com/>
________________________________
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<http://www.ics-il.com/>
Midwest Internet Exchange
http://www.midwest-ix.com<http://www.midwest-ix.com/>
________________________________
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.
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<http://www.ics-il.com/>
Midwest Internet Exchange
http://www.midwest-ix.com<http://www.midwest-ix.com/>
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
Feb. 23, 2023
Neustar SOA Archives
by voiceops@ics-il.net
>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>
Feb. 23, 2023
Neustar SOA Archives
by ptimmins@clearrate.com
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<http://www.ics-il.com/>
Midwest Internet Exchange
http://www.midwest-ix.com<http://www.midwest-ix.com/>
________________________________
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.
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<http://www.ics-il.com/>
Midwest Internet Exchange
http://www.midwest-ix.com<http://www.midwest-ix.com/>
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
Feb. 23, 2023
Neustar SOA Archives
by voiceops@ics-il.net
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.
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
Feb. 23, 2023