date:20200326

Re: [VoiceOps] Requirements for SHAKEN service providers

2020-03-26 Thread Mary Lou Carey

So connecting the dots between all the FCC statements we know of...I 
think the following statements are still true:


1. A company can attest all their TNs (whether leased or owned) if they 
have a STIR/SHAKEN certificate,

2. Only those companies with a STIR/SHAKEN certificate can attest calls.
3. Only those companies with a state certification or FCC License can 
get a STIR/SHAKEN certificate because only companies with a state 
certification or FCC License are able to obtain direct access to NANPA.


MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-

On 2020-03-26 02:48 PM, Kent Adams wrote:

I believe if you look at the footnote on the third point you will find
that they have realized the problems it will cause. I don't know of
anything providing a path around it yet, but at least they acknowledge
the rule is not perfect?

"While the access limitation is reasonable, signing a given call
should not be limited to only the pool of numbers available to the
provider via direct access. In other words, per ATIS-100074, 5.2.3,
under correct conditions a qualified service provider (SP) must be
allowed to sign leased numbers as well as other numbers belonging to
an OCN not assigned to that qualified SP insofar as the SP can
properly verify the customer's authorized use of that number."

On Thu, Mar 26, 2020 at 2:52 PM Zilk, David 
wrote:


There are three requirements for a Service Provider to be included
in the SHAKEN ecosystem:

1.   Service Provider must have an OCN

2.   Service Provider must have a current Form 499-A filed with
the FCC

3.   Service Provider must have direct access to telephone
numbers from the North American Number Plan Administrator (NANPA)
and National Pooling Administrator (NPA)

My company meets the first two requirements as we have an OCN as an
interconnected voice provider (IPES) and a current Form 499-A filed,
however we obtain telephone numbers from our carriers, and don’t
have our own numbers assigned from NANPA and NPA.  How do we
determine if we are eligible to obtain numbers and thus be qualified
to play in the SHAKEN ecosystem?

David
-
This message and any attachments are intended only for the use of
the addressee and may contain information that is privileged and
confidential. If the reader of the message is not the intended
recipient or an authorized representative of the intended recipient,
you are hereby notified that any dissemination of this communication
is strictly prohibited. If you have received this communication in
error, notify the sender immediately by return email and delete the
message and any attachments from your system.
___
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] Coronavirus Traffic Patterns

2020-03-26 Thread Carlos Alvarez

Obamacare tripled the staff at both of the billing companies we serve, and
doubled call volume.  It legally requires billing within a certain
timeframe, which also causes erroneous bills to go out, then they have to
call customers and say "no not really wait for your second bill with a
correction."

On Thu, Mar 26, 2020 at 12:37 PM Alex Balashov 
wrote:

> Oh yeah. Medical billing is the one thing this country will not forget or
> neglect under any circumstances. That’s one thing we do really well -
> medically bill. After the thermonuclear Armageddon, cockroaches will
> remain, along with medical billing.
>
> And the PHP programming language.
>
> —
> Sent from mobile, with due apologies for brevity and errors.
>
> On Mar 26, 2020, at 3:00 PM, Carlos Alvarez  wrote:
>
> 
> Medical billing--exactly the same.
>
> "Elective" medicine like dental and small doctor's office--totally dead.
>
> Manufacturing--dead.
>
> Professional offices--normal.
>
> We saw a spike in traffic very early on, and now we're well below normal.
>
> On Wed, Mar 25, 2020 at 6:00 PM Darren Schreiber 
> wrote:
>
>> We are in a similar boat. Almost 60% higher in traffic. We service
>> medical, police, fire and a lot of technical orgs. They are doing constant
>> conference calls. Big spikes in the morning.
>>
>>
>>
>> On the other hand we also service hotels. That traffic is literally
>> non-existent now.
>>
>>
>>
>> We are doubling our server count this week in anticipation and shifting
>> non-critical “data” side of the traffic to alternate paths.
>>
>>
>>
>> *From: *VoiceOps  on behalf of Ryan
>> Delgrosso 
>> *Date: *Wednesday, March 25, 2020 at 5:43 PM
>> *To: *"voiceops@voiceops.org" 
>> *Subject: *Re: [VoiceOps] Coronavirus Traffic Patterns
>>
>>
>>
>> We are +100% network traffic since the first lock-down happened. Its
>> worth noting we are a healthcare focused carrier so this isn't at all
>> surprising, and as more cities go into lock-down we expect this is going to
>> move around, and we will probably see net +200%-400% traffic over YoY
>> norms.
>>
>> We have also seen +400% customer intake rate as healthcare providers
>> scramble to be able to work remotely or rapidly scale staffing.
>>
>> We are seeing both in regional surges as well.
>>
>>
>>
>> On 3/23/2020 4:58 PM, Andrew Melton wrote:
>>
>> It would be interesting to hear what kind of traffic shifts this group
>> has observed over the past 2 weeks.  While certain variances are
>> predictable, i.e. Mother's Day, I have no idea what to expect with millions
>> of people in the US suddenly working from home every day and how that
>> informs metrics, planning, reporting, etc.
>>
>>
>>
>>
>>
>> -Andy
>>
>>
>>
>> ---
>>
>> Please wash your hands.
>>
>> ---
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ___
>>
>> 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
>
> ___
> 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] Coronavirus Traffic Patterns

2020-03-26 Thread Alex Balashov

Oh yeah. Medical billing is the one thing this country will not forget or 
neglect under any circumstances. That’s one thing we do really well - medically 
bill. After the thermonuclear Armageddon, cockroaches will remain, along with 
medical billing.

And the PHP programming language.

—
Sent from mobile, with due apologies for brevity and errors.

> On Mar 26, 2020, at 3:00 PM, Carlos Alvarez  wrote:
> 
> 
> Medical billing--exactly the same.
> 
> "Elective" medicine like dental and small doctor's office--totally dead.
> 
> Manufacturing--dead.
> 
> Professional offices--normal.
> 
> We saw a spike in traffic very early on, and now we're well below normal.
> 
>> On Wed, Mar 25, 2020 at 6:00 PM Darren Schreiber  wrote:
>> We are in a similar boat. Almost 60% higher in traffic. We service medical, 
>> police, fire and a lot of technical orgs. They are doing constant conference 
>> calls. Big spikes in the morning.
>> 
>>  
>> 
>> On the other hand we also service hotels. That traffic is literally 
>> non-existent now.
>> 
>>  
>> 
>> We are doubling our server count this week in anticipation and shifting 
>> non-critical “data” side of the traffic to alternate paths.
>> 
>>  
>> 
>> From: VoiceOps  on behalf of Ryan Delgrosso 
>> 
>> Date: Wednesday, March 25, 2020 at 5:43 PM
>> To: "voiceops@voiceops.org" 
>> Subject: Re: [VoiceOps] Coronavirus Traffic Patterns
>> 
>>  
>> 
>> We are +100% network traffic since the first lock-down happened. Its worth 
>> noting we are a healthcare focused carrier so this isn't at all surprising, 
>> and as more cities go into lock-down we expect this is going to move around, 
>> and we will probably see net +200%-400% traffic over YoY norms.
>> 
>> We have also seen +400% customer intake rate as healthcare providers 
>> scramble to be able to work remotely or rapidly scale staffing.
>> 
>> We are seeing both in regional surges as well.
>> 
>>  
>> 
>> On 3/23/2020 4:58 PM, Andrew Melton wrote:
>> 
>> It would be interesting to hear what kind of traffic shifts this group has 
>> observed over the past 2 weeks.  While certain variances are predictable, 
>> i.e. Mother's Day, I have no idea what to expect with millions of people in 
>> the US suddenly working from home every day and how that informs metrics, 
>> planning, reporting, etc.
>> 
>>  
>> 
>>  
>> 
>> -Andy
>> 
>>  
>> 
>> ---
>> 
>> Please wash your hands.
>> 
>> ---
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>> 
>> 
>> 
>> ___
>> 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
___
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

Re: [VoiceOps] Coronavirus Traffic Patterns

2020-03-26 Thread Carlos Alvarez

Medical billing--exactly the same.

"Elective" medicine like dental and small doctor's office--totally dead.

Manufacturing--dead.

Professional offices--normal.

We saw a spike in traffic very early on, and now we're well below normal.

On Wed, Mar 25, 2020 at 6:00 PM Darren Schreiber  wrote:

> We are in a similar boat. Almost 60% higher in traffic. We service
> medical, police, fire and a lot of technical orgs. They are doing constant
> conference calls. Big spikes in the morning.
>
>
>
> On the other hand we also service hotels. That traffic is literally
> non-existent now.
>
>
>
> We are doubling our server count this week in anticipation and shifting
> non-critical “data” side of the traffic to alternate paths.
>
>
>
> *From: *VoiceOps  on behalf of Ryan
> Delgrosso 
> *Date: *Wednesday, March 25, 2020 at 5:43 PM
> *To: *"voiceops@voiceops.org" 
> *Subject: *Re: [VoiceOps] Coronavirus Traffic Patterns
>
>
>
> We are +100% network traffic since the first lock-down happened. Its worth
> noting we are a healthcare focused carrier so this isn't at all surprising,
> and as more cities go into lock-down we expect this is going to move
> around, and we will probably see net +200%-400% traffic over YoY norms.
>
> We have also seen +400% customer intake rate as healthcare providers
> scramble to be able to work remotely or rapidly scale staffing.
>
> We are seeing both in regional surges as well.
>
>
>
> On 3/23/2020 4:58 PM, Andrew Melton wrote:
>
> It would be interesting to hear what kind of traffic shifts this group has
> observed over the past 2 weeks.  While certain variances are predictable,
> i.e. Mother's Day, I have no idea what to expect with millions of people in
> the US suddenly working from home every day and how that informs metrics,
> planning, reporting, etc.
>
>
>
>
>
> -Andy
>
>
>
> ---
>
> Please wash your hands.
>
> ---
>
>
>
>
>
>
>
>
>
> ___
>
> 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

[VoiceOps] Requirements for SHAKEN service providers

2020-03-26 Thread Zilk, David

There are three requirements for a Service Provider to be included in the 
SHAKEN ecosystem:


1.   Service Provider must have an OCN

2.   Service Provider must have a current Form 499-A filed with the FCC

3.   Service Provider must have direct access to telephone numbers from the 
North American Number Plan Administrator (NANPA) and National Pooling 
Administrator (NPA)

My company meets the first two requirements as we have an OCN as an 
interconnected voice provider (IPES) and a current Form 499-A filed, however we 
obtain telephone numbers from our carriers, and don't have our own numbers 
assigned from NANPA and NPA.  How do we determine if we are eligible to obtain 
numbers and thus be qualified to play in the SHAKEN ecosystem?

David

--
This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, notify the sender immediately by return email and delete the message 
and any attachments from your system.
___
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

Re: [VoiceOps] Three Digit Numbers

2020-03-26 Thread Zilk, David

The vast majority of states obtain their Telecommunications Relay Services from 
one of two providers: Sprint and Hamilton Relay, with only a couple of states 
providing their own services.

Sprint provides service to 36 states and has provided this list of the numbers 
that 7-1-1 should translate to:

TX

800-735-1805 (711 vru)

MO

800-735-2466 (711 v)

NH

800-735-2964 (711 v)

NV

800-326-6888  711

SC

800-735-2905 (711 v)

OR

800-735-2900 (711 v)

SD

800-877-1113 (711 v)

WY

877-711-9982 711

IL

877-283-4187 (711 v)

IN

877-711-7704 (711 v)

CT

800-842-9710 (711 v)

ND

800-366-6889 (711 v)

OK

800-722-0353 (711 v)

MN

866-711-2526 (711 v)

NY

877-711-1944  711

OH

800-750-0750 (711 v)

AZ

877-711-1618 711

PR

866-280-2053 t  711

AK

800-770-8973 (711 v)

VT

877-368-6276 (711 v)

MS

866-305-1342 (711 v)

HI

877-447-1101 (711 v)

AR

866-692-7460 (711 v)

AL

866-305-1341 (711 v)

UT

800-346-4128  711

FL

800-955-8771  711

DE

800-509-2245 (711 v)

KS

800-743-8435  711

NE

888-952-7103  711

NJ

800-229-5751   711

RI

877-368-6274  711

WV

877-368-4890  711

MI

888-609-3829  711

WI

888-350-2565  711

TN

866-305-1340  711

ME

877-593-3253  711


I am still requesting the same info from the other providers.

David

From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of Zilk, David
Sent: Thursday, March 26, 2020 7:02 AM
To: Andy Brezinsky ; voiceops@voiceops.org
Subject: Re: [VoiceOps] Three Digit Numbers

The FCC provides this list of all the state relay service numbers.
https://www.fcc.gov/general/telecommunications-relay-services-directory

David

From: Andy Brezinsky [mailto:a...@mbrez.com]
Sent: Wednesday, March 25, 2020 8:40 PM
To: Zilk, David mailto:david.z...@cdk.com>>; 
voiceops@voiceops.org
Subject: Re: [VoiceOps] Three Digit Numbers


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




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:

Re: [VoiceOps] Three Digit Numbers

2020-03-26 Thread Zilk, David

The FCC provides this list of all the state relay service numbers.
https://www.fcc.gov/general/telecommunications-relay-services-directory

David

From: Andy Brezinsky [mailto:a...@mbrez.com]
Sent: Wednesday, March 25, 2020 8:40 PM
To: Zilk, David ; voiceops@voiceops.org
Subject: Re: [VoiceOps] Three Digit Numbers

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

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
[http://www.teamonesolutions.com/wp-content/uploads/header_logo.png]
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 
mailto:voice...@ics-il.net>> 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

Re: [VoiceOps] Requirements for SHAKEN service providers

Re: [VoiceOps] Coronavirus Traffic Patterns

Re: [VoiceOps] Coronavirus Traffic Patterns

Re: [VoiceOps] Coronavirus Traffic Patterns

[VoiceOps] Requirements for SHAKEN service providers

Re: [VoiceOps] Three Digit Numbers

Re: [VoiceOps] Three Digit Numbers

7 matches

Site Navigation

Mail list logo

Footer information