Re: [VoiceOps] Three Digit Numbers

2020-03-25 Thread Andy Brezinsky
From what I've been able to gather, 711 tends to forward to unpublished 
numbers which I've struggled to track down.  I've gathered a few by 
capturing data from tariffs and included those as an initial list (with 
source links)



If any CLECs on the list have the numbers for their states I would 
appreciate you sending them to me directly so I can include them in the 
list.



On 03/25/2020 06:36 PM, Zilk, David wrote:


I like your data collection, but I would also add 711 as there is a 
FCC mandate to support the relay services for the deaf.


David

*From:*VoiceOps [mailto:voiceops-boun...@voiceops.org] *On Behalf Of 
*Andy Brezinsky

*Sent:* Wednesday, March 25, 2020 11:59 AM
*To:* voiceops@voiceops.org
*Subject:* Re: [VoiceOps] Three Digit Numbers

If anyone is looking to contribute, I created a Github project and 
seeded it with some information I know about 811. I'm open for 
suggestions on the file formats.


https://github.com/n11db/n11_database 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_n11db_n11-5Fdatabase=DwMDaQ=N13-TaG7c-EYAiUNohBk74oLRjUiBTwVm-KSnr4bPSc=VcRLyVxkyGds34uxiPM944HQvaWq-nynyZXfNpSfhOs=JJ4LNGa6QyagWcHVeH3DmwaxZn_EdWhISKWapaFjIoA=kjygvG9ad44uk4gGOokK3oL6FCv4SYW56cBkv14AHOE=>


On 3/25/20 12:29 PM, Andy Brezinsky wrote:

I've been looking for something like this for years.  It'd be
really nice to get it into a machine readable format to digest by
routing engines.  Maybe a Github repo would be best for tracking
the changes?

On 3/25/20 11:45 AM, Mike Hammett wrote:

Right. The "more details" is the part I'm looking to build a
library of.



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

<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ics-2Dil.com=DwMDaQ=N13-TaG7c-EYAiUNohBk74oLRjUiBTwVm-KSnr4bPSc=VcRLyVxkyGds34uxiPM944HQvaWq-nynyZXfNpSfhOs=JJ4LNGa6QyagWcHVeH3DmwaxZn_EdWhISKWapaFjIoA=nUkkFfp878e09orR5dmCH8DKXdU0KKf2AbkSWJvP3E8=>



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

<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.midwest-2Dix.com=DwMDaQ=N13-TaG7c-EYAiUNohBk74oLRjUiBTwVm-KSnr4bPSc=VcRLyVxkyGds34uxiPM944HQvaWq-nynyZXfNpSfhOs=JJ4LNGa6QyagWcHVeH3DmwaxZn_EdWhISKWapaFjIoA=KHP5YlRKw5_O7KjdjPiw6VwG4cp_VZROTqn6yzvN_-o=>




*From: *"Brandon Svec" 
<mailto:bs...@teamonesolutions.com>
*To: *"Mike Hammett" 
<mailto:voice...@ics-il.net>
*Cc: *"Paul Timmins" 
<mailto:p...@timmins.net>, "Voiceops.org"
 <mailto:voiceops@voiceops.org>
*Sent: *Wednesday, March 25, 2020 11:42:15 AM
*Subject: *Re: [VoiceOps] Three Digit Numbers

NANPA defines normal uses for Nxx and refers to local
regulators for more details:

https://nationalnanpa.com/number_resource_info/n11_codes.html

<https://urldefense.proofpoint.com/v2/url?u=https-3A__nationalnanpa.com_number-5Fresource-5Finfo_n11-5Fcodes.html=DwMDaQ=N13-TaG7c-EYAiUNohBk74oLRjUiBTwVm-KSnr4bPSc=VcRLyVxkyGds34uxiPM944HQvaWq-nynyZXfNpSfhOs=JJ4LNGa6QyagWcHVeH3DmwaxZn_EdWhISKWapaFjIoA=WGhQnEr7sSel9_9FAypeostzzBaVqKiGR2DsPDIgt9U=>

*Security Made Simple with Cisco Meraki:
*http://bit.ly/MerakiSecure

<https://urldefense.proofpoint.com/v2/url?u=http-3A__bit.ly_MerakiSecure=DwMDaQ=N13-TaG7c-EYAiUNohBk74oLRjUiBTwVm-KSnr4bPSc=VcRLyVxkyGds34uxiPM944HQvaWq-nynyZXfNpSfhOs=JJ4LNGa6QyagWcHVeH3DmwaxZn_EdWhISKWapaFjIoA=woabqnmtLJyVLb75qSBgbIF-VVdAWvfXn4z-Vm-Lx8g=>*

*Brandon Svec**
CA C-7 Lic. #822064

<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.cslb.ca.gov_OnlineServices_CheckLicenseII_LicenseDetail.aspx-3FLicNum-3D822064=DwMDaQ=N13-TaG7c-EYAiUNohBk74oLRjUiBTwVm-KSnr4bPSc=VcRLyVxkyGds34uxiPM944HQvaWq-nynyZXfNpSfhOs=JJ4LNGa6QyagWcHVeH3DmwaxZn_EdWhISKWapaFjIoA=79jnyUsvoJbgkFFKcSuzEZftaBujAz7DAfISdwuAogA=>
.ılı.ılı. Cisco Meraki CMNA
*15106862204  voice | sms
*teamonesolutions.com

<https://urldefense.proofpoint.com/v2/url?u=https-3A__teamonesolutions.com_=DwMDaQ=N13-TaG7c-EYAiUNohBk74oLRjUiBTwVm-KSnr4bPSc=VcRLyVxkyGds34uxiPM944HQvaWq-nynyZXfNpSfhOs=JJ4LNGa6QyagWcHVeH3DmwaxZn_EdWhISKWapaFjIoA=XEn3_8qgZBIj7hio9CkF3QdkAM8h_62Wjb6_r6w3NKs=>**

On Wed, Mar 25, 2020 at 6:25 AM Mike Hammett
mailto:voice...@ics-il.net>> wrote:

Other than voip-info.org

<https://urldefense.proofpoint.com/v2/url?u=http-3A__voip-2Dinfo.org=DwMDaQ=N13-TaG7c-EYAiUNohBk74oLRjUiBTwVm-KSnr4bPSc=VcRLyVxkyGds34uxiPM944HQvaWq-nynyZXfNpSfhOs=JJ4LNGa6QyagWcHVeH3DmwaxZn_EdWhISKWapaFjIoA=YedO7hf_Vc-i2lbnpqElvNHT9Kxh917FSD5wG3PayoE=>,
is there a voice-centric WIKI out there that we m

Re: [VoiceOps] Three Digit Numbers

2020-03-25 Thread Andy Brezinsky
If anyone is looking to contribute, I created a Github project and 
seeded it with some information I know about 811.  I'm open for 
suggestions on the file formats.



https://github.com/n11db/n11_database



On 3/25/20 12:29 PM, Andy Brezinsky wrote:


I've been looking for something like this for years.  It'd be really 
nice to get it into a machine readable format to digest by routing 
engines.  Maybe a Github repo would be best for tracking the changes?



On 3/25/20 11:45 AM, Mike Hammett wrote:

Right. The "more details" is the part I'm looking to build a library of.



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



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




*From: *"Brandon Svec" 
*To: *"Mike Hammett" 
*Cc: *"Paul Timmins" , "Voiceops.org" 


*Sent: *Wednesday, March 25, 2020 11:42:15 AM
*Subject: *Re: [VoiceOps] Three Digit Numbers

NANPA defines normal uses for Nxx and refers to local regulators for 
more details:

https://nationalnanpa.com/number_resource_info/n11_codes.html

*Security Made Simple with Cisco Meraki: *http://bit.ly/MerakiSecure*

Brandon Svec*
CA C-7 Lic. #822064 
<https://www.cslb.ca.gov/OnlineServices/CheckLicenseII/LicenseDetail.aspx?LicNum=822064>

.ılı.ılı. Cisco Meraki CMNA
*15106862204  voice | sms
**teamonesolutions.com <https://teamonesolutions.com/>*
*
*





On Wed, Mar 25, 2020 at 6:25 AM Mike Hammett <mailto:voice...@ics-il.net>> wrote:


Other than voip-info.org <http://voip-info.org>, is there a
voice-centric WIKI out there that we may be able to crowd-source
this information? I'd be up for contributing the information I
collect for my coverage area to some central repository.



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



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




*From: *"Paul Timmins" mailto:p...@timmins.net>>
*To: *"Mike Hammett" mailto:voice...@ics-il.net>>
*Cc: *"Ken Mix" mailto:ken@clearfly.net>>, voiceops@voiceops.org
<mailto:voiceops@voiceops.org>
*Sent: *Wednesday, March 25, 2020 8:15:39 AM
*Subject: *Re: Three Digit Numbers

Definitely not. Especially with stuff like 2-1-1 which (at least
in Michigan) routes on the county level.

On Mar 25, 2020, at 8:06 AM, Mike Hammett
mailto:voice...@ics-il.net>> wrote:

I take it there's no authoritative list of what geographies
need to send what N11 calls where?



-
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:*"Ken Mix" mailto:ken@clearfly.net>>
*To:*"Mike Hammett" mailto:voice...@ics-il.net>>, "Paul Timmins"
mailto:p...@timmins.net>>
*Cc:*voiceops@voiceops.org <mailto:voiceops@voiceops.org>
*Sent:*Tuesday, March 24, 2020 11:29:59 AM
*Subject:*RE: Three Digit Numbers

If there's something standardized out there, I’d love to see
a link to it. We have a nationwide US footprint and had to
build an internal system to handle routing to 211, 311, 511,
711 & 811 based on calling number. It was a real pain
tracking down all of the numbers we need to translate to, though.

We’re a pretty small business-only carrier, and volume to
non-911 N11 numbers is low, but not insignificant. Current
N11 call counts in 2020:

211 - 270
311 - 82
511 - 67
711 - 34
811 - 323

*From:*VoiceOps mailto:voiceops-boun...@voiceops.org>>*On Behalf Of*Mike Hammett
*Sent:*Tuesday, March 24, 2020 09:25
*To:*Paul Timmins mailto:p...@timmins.net>>
*Cc:*voiceops@voiceops.org <mailto:voiceops@voiceops.org>
*Subject:*Re: [VoiceOps] Three Digit Numbers

Are we supposed to be providing the intelligence in how to
route those calls? IE: Customer is in the City of Chicago, so
route it to the city's Digger 10 digit, whereas if the
customer is anywhere else in Illinois, route it to the
state's JULIE 10 digit?



-
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/>


---

Re: [VoiceOps] Three Digit Numbers

2020-03-25 Thread Andy Brezinsky
I've been looking for something like this for years.  It'd be really 
nice to get it into a machine readable format to digest by routing 
engines.  Maybe a Github repo would be best for tracking the changes?



On 3/25/20 11:45 AM, Mike Hammett wrote:

Right. The "more details" is the part I'm looking to build a library of.



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



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




*From: *"Brandon Svec" 
*To: *"Mike Hammett" 
*Cc: *"Paul Timmins" , "Voiceops.org" 


*Sent: *Wednesday, March 25, 2020 11:42:15 AM
*Subject: *Re: [VoiceOps] Three Digit Numbers

NANPA defines normal uses for Nxx and refers to local regulators for 
more details:

https://nationalnanpa.com/number_resource_info/n11_codes.html

*Security Made Simple with Cisco Meraki: *http://bit.ly/MerakiSecure*

Brandon Svec*
CA C-7 Lic. #822064 


.ılı.ılı. Cisco Meraki CMNA
*15106862204  voice | sms
**teamonesolutions.com *
*
*





On Wed, Mar 25, 2020 at 6:25 AM Mike Hammett > wrote:


Other than voip-info.org , is there a
voice-centric WIKI out there that we may be able to crowd-source
this information? I'd be up for contributing the information I
collect for my coverage area to some central repository.



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



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




*From: *"Paul Timmins" mailto:p...@timmins.net>>
*To: *"Mike Hammett" mailto:voice...@ics-il.net>>
*Cc: *"Ken Mix" mailto:ken@clearfly.net>>, voiceops@voiceops.org

*Sent: *Wednesday, March 25, 2020 8:15:39 AM
*Subject: *Re: Three Digit Numbers

Definitely not. Especially with stuff like 2-1-1 which (at least
in Michigan) routes on the county level.

On Mar 25, 2020, at 8:06 AM, Mike Hammett mailto:voice...@ics-il.net>> wrote:

I take it there's no authoritative list of what geographies
need to send what N11 calls where?



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



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




*From:*"Ken Mix" mailto:ken@clearfly.net>>
*To:*"Mike Hammett" mailto:voice...@ics-il.net>>, "Paul Timmins"
mailto:p...@timmins.net>>
*Cc:*voiceops@voiceops.org 
*Sent:*Tuesday, March 24, 2020 11:29:59 AM
*Subject:*RE: Three Digit Numbers

If there's something standardized out there, I’d love to see a
link to it. We have a nationwide US footprint and had to build
an internal system to handle routing to 211, 311, 511, 711 &
811 based on calling number. It was a real pain tracking down
all of the numbers we need to translate to, though.

We’re a pretty small business-only carrier, and volume to
non-911 N11 numbers is low, but not insignificant. Current N11
call counts in 2020:

211 - 270
311 - 82
511 - 67
711 - 34
811 - 323

*From:*VoiceOps mailto:voiceops-boun...@voiceops.org>>*On Behalf Of*Mike Hammett
*Sent:*Tuesday, March 24, 2020 09:25
*To:*Paul Timmins mailto:p...@timmins.net>>
*Cc:*voiceops@voiceops.org 
*Subject:*Re: [VoiceOps] Three Digit Numbers

Are we supposed to be providing the intelligence in how to
route those calls? IE: Customer is in the City of Chicago, so
route it to the city's Digger 10 digit, whereas if the
customer is anywhere else in Illinois, route it to the state's
JULIE 10 digit?



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



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



*From:*"Paul Timmins" mailto:p...@timmins.net>>
*To:*"Carlos Alvarez" mailto:caalva...@gmail.com>>
*Cc:*voiceops@voiceops.org 
*Sent:*Tuesday, March 24, 2020 10:14:18 AM
*Subject:*Re: [VoiceOps] Three Digit Numbers

711 and 811 have federal mandates to go to telecommunications
relay service and one call facilities flagging services
respectively. Be careful about working like 

Re: [VoiceOps] Hotel Phone

2019-04-05 Thread Andy Brezinsky
There are a number of ways to do this without having a DID assigned to 
each device with address information.  A number of systems also assign a 
callback number to anyone that dials 911 which tacks up a translation 
for that number for a period of time so they can call back the user 
directly.


Example onfiguration details for AudioCodes and Sonus with skype can be 
seen here: 
https://ucvnext.org/2016/03/enhanced-911-in-skype4b-server-and-lync-server-part-4/



On 4/5/19 1:22 AM, Matthew Yaklin wrote:
That is correct. A DID for every phone and listed by e911. For example 
in NH it is law schools have it now days to get their special erate 
funding. When they call 911 they see very detailed information about 
floor, room, etc.. and the phone can be called back directly. We do it 
for every customer that has that specific need.


Matthew Yaklin
Network Engineer
FirstLight
359 Corporate Drive │ Portsmouth, NH 03801
Mobile 603-845-5031
myak...@firstlight.net | www.firstlight.net
This email may contain FirstLight confidential and/or privileged 
information. If you are not the intended recipient, you are directed
not to read, disclose or otherwise use this transmission and to 
immediately delete same. Delivery of this message is not intended

to waive any applicable privileges.


*From:* Colton Conor 
*Sent:* Thursday, April 4, 2019 8:40:11 PM
*To:* Matthew Yaklin
*Cc:* Jason Kuylen; VoiceOps@voiceops.org
*Subject:* Re: [VoiceOps] Hotel Phone
So if you had e911 per room, that would be quite a bit of e911 
charges. Most hotels I have seen have a 10 to 1 ratio for rooms to 
phone lines. So a 100 room hotel gets 10 phone lines from the LEC. Are 
you saying we would have to pay bandwidth.com  
or whomever we got our e911 from a separate e911 charge per room? 
Isn't e911 tied to DID? In that case you would need a DID per hotel 
room? To actuately say room 302 is on floor 3, and room 302 for example.




On Thu, Apr 4, 2019 at 11:21 AM Matthew Yaklin > wrote:


I imagine you want to make sure E911 information is super accurate
with actual floors and room numbers. Physical address and call
back number is correct. By making that accurate and having the
customer sign that phones cannot move you cover a serious base.
Perhaps even a sticker on the phone saying such would be great to.


*Matthew Yaklin*
Network Engineer
*FirstLight*
359 Corporate Drive │ Portsmouth, NH 03801
Mobile 603-845-5031
myak...@firstlight.net  |
www.firstlight.net 
/This email may contain FirstLight confidential and/or privileged
information. If you are not the intended recipient, you are directed/
/not to read, disclose or otherwise use this transmission and to
immediately delete same. Delivery of this message is not intended/
/to waive any applicable privileges./


*From:* VoiceOps mailto:voiceops-boun...@voiceops.org>> on behalf of Jason Kuylen
mailto:kuyl...@eastex.com>>
*Sent:* Thursday, April 4, 2019 12:08:32 PM
*To:* VoiceOps@voiceops.org 
*Subject:* Re: [VoiceOps] Hotel Phone

I’ve never heard of any other 911 requirement for hotel or
business phones outside of not have to dial 9 to dial 911, ie
9911. Kari’s Law.

Can anyone provide a link with more information?

Thanks.


Important/Confidential: This communication and any files or
documents attached to it are intended only for the use of the
person(s) or entity to which it is addressed. It contains
information that may be confidential and exempt from disclosure
under applicable law. If you are not the intended recipient of
this communication, you are hereby notified that the copying,
disclosure, distribution, storage, retransmission or other use of
this communication is strictly prohibited. If you have received
this communication by mistake, please notify the sender
immediately and destroy all forms of this communication
(electronic or paper).
___
VoiceOps mailing list
VoiceOps@voiceops.org 
https://puck.nether.net/mailman/listinfo/voiceops


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


Re: [VoiceOps] Level 3 Outage

2015-12-15 Thread Andy Brezinsky
Check the outa...@outages.org list.  Lots of people reporting L3 
internet issues in Chicago.  We dropped our BGP session with them and 
things are doing better.


On 12/15/15 1:26 PM, Michael Jacobs wrote:

Anyone having Level 3 internet issues?


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


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


Re: [VoiceOps] Preventing calls to cell phones with guaranteed accuracy

2015-08-18 Thread Andy Brezinsky
We've used DNC.com in the past which gets data from 
http://www.tcpacompliance.us/.  That's run by Neustar directly and:


Specifically, qualified users can now subscribe and receive the most 
up-to-date files (the Intermodal Ported Telephone Number Identification 
Service) consisting of nationwide ported telephone numbers that have 
been moved from wire line to wireless and vice versa, enabling users to 
avoid using auto-dialers or pre-recorded messages to call wireless numbers.


They will also offer an indemnification clause if you use their service 
and the number was on the list to protect you.  Prices were pretty 
reasonable and they both bulk interfaces and real time.



On 08/18/2015 03:30 PM, Carlos Alvarez wrote:
I have a customer in market research who is legally required to 
manually dial calls to cell phones.  Right now they are considering 
abandoning all of their auto/predictive dialer software and going to 
manual dial for everything, because the list-scrubbing services have 
been shown to be inaccurate.  There are extreme penalties for 
auto-dialing a cell phone, and best effort is NOT a defense to this, 
at all.  For example, Gallup just settle a claim for $12M.


So they need a totally accurate way to prevent a cell phone call from 
originating from their dialer.  The only thing I can think of is some 
sort of LRN dip + LRN-to-carrier-type response.  One of their people 
talked to Neustar, but didn't get great answers because he doesn't 
really understand telephony.  Before I get in touch with Neustar, I 
thought I'd see if people here have some ideas.


If you provide a commercial product for this, please feel free to tell 
me so on or off list, the customer is willing to pay for the service 
and we're open to all options.  I don't have a budget number yet but 
manual dialing is going to cost them quite a bit for some types of 
studies.




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


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