[VoiceOps] Abandoned Ported Numbers

Nick Olsen Nick at 141networks.com
Fri Oct 14 15:41:13 EDT 2022


Depends on who/what you use for NPAC access, or if you use like LTI..etc.

We built our own SOA and LSMS XML platform so we didn't have to go through a third-party like Neustar or 10x..etc.

We get a notification (via our normal XML mechanized interface) when a TN is disconnected in the NPAC back to us for any of our SPID's. Likewise there is a SOA action you can call to disconnect/remove an SV for a given TN.

Not everyone does it. But most of the iLEC's ..etc do honor it and disconnect TN's back regularly.

If you use LTI, I'm not sure how it's presented there.
________________________________
From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Mike Hammett via VoiceOps <voiceops at voiceops.org>
Sent: Friday, October 14, 2022 11:19 AM
To: Jeff Shultz <jeffshultz at sctcweb.com>
Cc: voiceops at voiceops.org <voiceops at voiceops.org>
Subject: Re: [VoiceOps] Abandoned Ported Numbers

How would the original carrier know? I've never seen anything about numbers being returned to us. Maybe my employees are ignoring them, maybe the emails are lost, maybe we have to fetch it from somewhere.



-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com



Midwest Internet Exchange
http://www.midwest-ix.com



________________________________
From: "Jeff Shultz via VoiceOps" <voiceops at voiceops.org>
To: voiceops at voiceops.org
Sent: Friday, October 14, 2022 10:06:48 AM
Subject: Re: [VoiceOps] Abandoned Ported Numbers

I know the LNP coordinator in our company occasionally sends out "NPAC Disconnects" spreadsheets of numbers that have been returned to us, so presumably this is an NPAC process.

On Fri, Oct 14, 2022 at 8:03 AM Greg Stone via VoiceOps <voiceops at voiceops.org<mailto:voiceops at voiceops.org>> wrote:
It's been a long time since I've used NPAC personally but there is a cancel button if I recall correctly and it pushes the number back to the original pooling carrier.




Greg Stone
Senior Voice Network Engineer
Race Communications
E : greg.stone at race.com<mailto:greg.stone at race.com>

P : +1 8777223833<tel:+1%208777223833>

Web : Visit Race.com<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.race.com%2F&data=04%7C01%7CGreg.Stone%40race.com%7C20495d863c6a4cf1028108da0cf9d357%7Cc4f7941052bf4601be443afdc7670fe9%7C1%7C0%7C637836564377453172%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=JBEBRVE%2F9wwPKIHRUZRMAXtUHrDm2XBibbS%2ByqWAnPg%3D&reserved=0>



-------- Original message --------
From: Mike Hammett <voiceops at ics-il.net<mailto:voiceops at ics-il.net>>
Date: 10/14/22 7:49 AM (GMT-08:00)
To: Greg Stone <Greg.Stone at race.com<mailto:Greg.Stone at race.com>>
Cc: Mike Johnston <mjohnston at wiktel.com<mailto:mjohnston at wiktel.com>>, voiceops at voiceops.org<mailto:voiceops at voiceops.org>
Subject: Re: [VoiceOps] Abandoned Ported Numbers

You don't often get email from voiceops at ics-il.net<mailto:voiceops at ics-il.net>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
How does that work?



-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com



Midwest Internet Exchange
http://www.midwest-ix.com



________________________________
From: "Greg Stone via VoiceOps" <voiceops at voiceops.org<mailto:voiceops at voiceops.org>>
To: "Mike Johnston" <mjohnston at wiktel.com<mailto:mjohnston at wiktel.com>>, voiceops at voiceops.org<mailto:voiceops at voiceops.org>
Sent: Friday, October 14, 2022 9:47:28 AM
Subject: Re: [VoiceOps] Abandoned Ported Numbers

Common practice is to age them out and then push them back to the original block holder.




Greg Stone
Senior Voice Network Engineer
Race Communications
E : greg.stone at race.com<mailto:greg.stone at race.com>

P : +1 8777223833<tel:+1%208777223833>

Web : Visit Race.com<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.race.com%2F&data=05%7C01%7CGreg.Stone%40race.com%7C8158f613b4924658b09308daadf34b8a%7Cc4f7941052bf4601be443afdc7670fe9%7C1%7C1%7C638013557703973687%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=YJpbzcrOeLv8trP%2BK3Rr9ZWUZFsV4fFrjPg9fXKy2ds%3D&reserved=0>



-------- Original message --------
From: Mike Johnston via VoiceOps <voiceops at voiceops.org<mailto:voiceops at voiceops.org>>
Date: 10/14/22 7:37 AM (GMT-08:00)
To: voiceops at voiceops.org<mailto:voiceops at voiceops.org>
Subject: [VoiceOps] Abandoned Ported Numbers

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

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 the number be returned to the donor telco after aging?

Is it permissible for the recipient telco to add this number to their
inventory and then re-assign the number to a different subscriber?
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fvoiceops&data=05%7C01%7Cgreg.stone%40race.com%7Cbc900d0c35e74b76f34308daadf1aa95%7Cc4f7941052bf4601be443afdc7670fe9%7C1%7C0%7C638013550723280018%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8jxDiA2LWg3yPXDSnc5SbtsYYJ%2Bti3XcjX01bIohEFs%3D&reserved=0<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fvoiceops&data=05%7C01%7CGreg.Stone%40race.com%7C8158f613b4924658b09308daadf34b8a%7Cc4f7941052bf4601be443afdc7670fe9%7C1%7C1%7C638013557703973687%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=7y7cAUJAy7YiJgrBc%2FjpwXaGcz4zCEvGCKduyaaoV3c%3D&reserved=0>

_______________________________________________
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<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops


--
Jeff Shultz
Central Office Technician
SCTC
(503) 769-2125
Go Big  Ask for Gig

Like us on Social Media for News, Promotions, and other information!!

  [https://cdn0.iconfinder.com/data/icons/free-social-media-set/24/facebook-32.png] <https://www.facebook.com/SCTCWEB/>      [https://www.instagram.com/sctc_sctc/] <https://www.instagram.com/sctc_sctc/>      [https://cdn2.iconfinder.com/data/icons/social-media-2142/192/Yelp-32.png] <https://www.yelp.com/biz/sctc-stayton-3>      [https://cdn3.iconfinder.com/data/icons/free-social-icons/67/youtube_circle_color-32.png] <https://www.youtube.com/c/sctcvideos>







*** This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ***

_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20221014/83a8163e/attachment-0001.htm>


More information about the VoiceOps mailing list