Re: [cisco-voip] E911 Address Incorrect

[Lelio Fulgenzi]

Interesting. If you're using default address information, then you'll have to 
arrange with your TSP that they coordinate address record updates with the 
local PSAP.

I know with my little experience that PSALI updates have to be precise. So if 
the PSALI database has RD instead of ROAD, if you use ROAD it will get 
rejected. Something like that.

---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | le...@uoguelph.ca<mailto:le...@uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

From: Jason Faraone 
Sent: Tuesday, July 9, 2019 12:38 PM
To: Lelio Fulgenzi ; cisco-voip@puck.nether.net
Subject: RE: E911 Address Incorrect

We're using the default address information - this TN is provided via SIP.us, 
and so I manually entered in the E911 information when I provisioned the line. 
I opened a ticket with them, and they verified that the address they have on 
hand is the correct one, which I believe as 933 is able to confirm this.

My confusion comes in with 911 receiving different information - slightly 
different, but enough to cause concern. I was always under the impression that 
933 and 911 pulled the same data when it comes to caller ID.

Jason Faraone
Sr. Network Engineer Bear

Build-A-Bear Workshop, Inc.
1954 Innerbelt Business Center Drive
St. Louis, MO  63114
US: 314.593.3244
UK: 01753560740
C: 314.308.9003

jas...@buildabear.com<mailto:jas...@buildabear.com>
www.buildabear.com<http://www.buildabear.com/>

Follow us: Facebook<https://www.facebook.com/Buildabear>, 
Twitter<https://twitter.com/buildabear>, 
YouTube<https://www.youtube.com/user/Buildabearworkshop1>, 
Pinterest<https://pinterest.com/buildabear/>

[cid:image002.jpg@01D5365C.ABC73CF0]<http://www.buildabear.com/>[cid:image003.jpg@01D5365C.ABC73CF0]<https://dashradio.com/buildabear>

From: cisco-voip 
mailto:cisco-voip-boun...@puck.nether.net>> 
On Behalf Of Lelio Fulgenzi
Sent: Tuesday, July 9, 2019 11:31 AM
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] E911 Address Incorrect

Hey Jason,

Do you subscribe to a PS-ALI type service? Or are you relying on default 
address information?

If you are relying on default address information - that will be difficult to 
change since it's likely going to be tied to the service address of the PSTN 
connection.

That being said, if it's actually incorrect, you should be able to reach out to 
your account team for starting point. First thing I'd do is check with whomever 
is getting the bills for that PSTN number to see what the billing information 
looks like. If they have equipment records, that might help too.

Lelio


---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | le...@uoguelph.ca<mailto:le...@uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

From: cisco-voip 
mailto:cisco-voip-boun...@puck.nether.net>> 
On Behalf Of Jason Faraone
Sent: Tuesday, July 9, 2019 12:09 PM
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: [cisco-voip] E911 Address Incorrect

I have a location that shows the correct physical address when I dial 933, but 
a slightly incorrect address when dialing 911. Has anyone encountered this 
before?

Dialing 933 shows Oakbrook Center, where 911 shows Oakbrook Road. Everything 
else is correct (State, CID, zip, street address). There is an Oakbrook road in 
the area, so I need to get this resolved so that there is no confusion in case 
of emergency.

Jason Faraone
Sr. Network Engineer Bear

Build-A-Bear Workshop, Inc.
1954 Innerbelt Business Center Drive
St. Louis, MO  63114


jas...@buildabear.com<mailto:jas...@buildabear.com>
www.buildabear.com<http://www.buildabear.com/>

Follow us: Facebook<https://www.facebook.com/Buildabear>, 
Twitter<https://twitter.com/buildabear>, 
YouTube<https://www.youtube.com/user/Buildabearworkshop1>, 
Pinterest<https://pinterest.com/buildabear/>

[cid:image002.jpg@01D5365C.ABC73CF0]<http://www.buildabear.com/>[cid:image003.jpg@01D5365C.ABC73CF0]<https://dashradio.com/buildabear>

The information in this message may be privileged, "confidential" and protected 
from disclosure and/or intended only for the addressee(s) named above. If the 
reader of this message is not the intended recipient, or an employee or agent 
responsible for delivering this m

Re: [cisco-voip] E911 Address Incorrect

[Brian Meade]

933 is usually just provided by the SIP carrier in my understanding.  A lot
of the circuits I've installed don't have 933 as an option.

On Tue, Jul 9, 2019 at 12:38 PM Jason Faraone  wrote:

> We’re using the default address information – this TN is provided via
> SIP.us, and so I manually entered in the E911 information when I
> provisioned the line. I opened a ticket with them, and they verified that
> the address they have on hand is the correct one, which I believe as 933 is
> able to confirm this.
>
>
>
> My confusion comes in with 911 receiving different information – slightly
> different, but enough to cause concern. I was always under the impression
> that 933 and 911 pulled the same data when it comes to caller ID.
>
>
>
>
> *Jason Faraone *Sr. Network Engineer Bear
>
> Build-A-Bear Workshop, Inc.
> 1954 Innerbelt Business Center Drive
> St. Louis, MO  63114
> US: 314.593.3244
> UK: 01753560740
> C: 314.308.9003
>
> *jas...@buildabear.com *
> www.buildabear.com
>
> *Follow us:* Facebook <https://www.facebook.com/Buildabear>, Twitter
> <https://twitter.com/buildabear>, YouTube
> <https://www.youtube.com/user/Buildabearworkshop1>, Pinterest
> <https://pinterest.com/buildabear/>
>
> <http://www.buildabear.com/> <https://dashradio.com/buildabear>
>
>
>
> *From:* cisco-voip  *On Behalf Of *Lelio
> Fulgenzi
> *Sent:* Tuesday, July 9, 2019 11:31 AM
> *To:* cisco-voip@puck.nether.net
> *Subject:* Re: [cisco-voip] E911 Address Incorrect
>
>
>
> Hey Jason,
>
>
>
> Do you subscribe to a PS-ALI type service? Or are you relying on default
> address information?
>
>
>
> If you are relying on default address information – that will be difficult
> to change since it’s likely going to be tied to the service address of the
> PSTN connection.
>
>
>
> That being said, if it’s actually incorrect, you should be able to reach
> out to your account team for starting point. First thing I’d do is check
> with whomever is getting the bills for that PSTN number to see what the
> billing information looks like. If they have equipment records, that might
> help too.
>
>
>
> Lelio
>
>
>
>
>
> ---
>
> *Lelio Fulgenzi, B.A.* | Senior Analyst
>
> Computing and Communications Services | University of Guelph
>
> Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON |
> N1G 2W1
>
> 519-824-4120 Ext. 56354 | le...@uoguelph.ca
>
>
>
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>
>
>
> [image: University of Guelph Cornerstone with Improve Life tagline]
>
>
>
> *From:* cisco-voip  *On Behalf Of *Jason
> Faraone
> *Sent:* Tuesday, July 9, 2019 12:09 PM
> *To:* cisco-voip@puck.nether.net
> *Subject:* [cisco-voip] E911 Address Incorrect
>
>
>
> I have a location that shows the correct physical address when I dial 933,
> but a slightly incorrect address when dialing 911. Has anyone encountered
> this before?
>
>
>
> Dialing 933 shows Oakbrook Center, where 911 shows Oakbrook Road.
> Everything else is correct (State, CID, zip, street address). There is an
> Oakbrook road in the area, so I need to get this resolved so that there is
> no confusion in case of emergency.
>
>
>
>
> *Jason Faraone *Sr. Network Engineer Bear
>
> Build-A-Bear Workshop, Inc.
> 1954 Innerbelt Business Center Drive
> St. Louis, MO  63114
>
>
> *jas...@buildabear.com *
> www.buildabear.com
>
> *Follow us:* Facebook <https://www.facebook.com/Buildabear>, Twitter
> <https://twitter.com/buildabear>, YouTube
> <https://www.youtube.com/user/Buildabearworkshop1>, Pinterest
> <https://pinterest.com/buildabear/>
>
> <http://www.buildabear.com/> <https://dashradio.com/buildabear>
>
>
>
> The information in this message may be privileged, "confidential" and
> protected from disclosure and/or intended only for the addressee(s) named
> above. If the reader of this message is not the intended recipient, or an
> employee or agent responsible for delivering this message to the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of the communication is strictly prohibited. If you have received
> this communication in error, please notify us immediately by replying to
> the message and deleting it from your computer. Please consider the
> environment before printing this email.
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] E911 Address Incorrect

[Jason Faraone]

We're using the default address information - this TN is provided via SIP.us, 
and so I manually entered in the E911 information when I provisioned the line. 
I opened a ticket with them, and they verified that the address they have on 
hand is the correct one, which I believe as 933 is able to confirm this.

My confusion comes in with 911 receiving different information - slightly 
different, but enough to cause concern. I was always under the impression that 
933 and 911 pulled the same data when it comes to caller ID.

Jason Faraone
Sr. Network Engineer Bear

Build-A-Bear Workshop, Inc.
1954 Innerbelt Business Center Drive
St. Louis, MO  63114
US: 314.593.3244
UK: 01753560740
C: 314.308.9003

jas...@buildabear.com
www.buildabear.com<http://www.buildabear.com/>

Follow us: Facebook<https://www.facebook.com/Buildabear>, 
Twitter<https://twitter.com/buildabear>, 
YouTube<https://www.youtube.com/user/Buildabearworkshop1>, 
Pinterest<https://pinterest.com/buildabear/>

[cid:image001.jpg@01D5364A.CD208D00]<http://www.buildabear.com/>[cid:image002.jpg@01D5364A.CD208D00]<https://dashradio.com/buildabear>

From: cisco-voip  On Behalf Of Lelio 
Fulgenzi
Sent: Tuesday, July 9, 2019 11:31 AM
To: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] E911 Address Incorrect

Hey Jason,

Do you subscribe to a PS-ALI type service? Or are you relying on default 
address information?

If you are relying on default address information - that will be difficult to 
change since it's likely going to be tied to the service address of the PSTN 
connection.

That being said, if it's actually incorrect, you should be able to reach out to 
your account team for starting point. First thing I'd do is check with whomever 
is getting the bills for that PSTN number to see what the billing information 
looks like. If they have equipment records, that might help too.

Lelio


---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | le...@uoguelph.ca<mailto:le...@uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

From: cisco-voip 
mailto:cisco-voip-boun...@puck.nether.net>> 
On Behalf Of Jason Faraone
Sent: Tuesday, July 9, 2019 12:09 PM
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: [cisco-voip] E911 Address Incorrect

I have a location that shows the correct physical address when I dial 933, but 
a slightly incorrect address when dialing 911. Has anyone encountered this 
before?

Dialing 933 shows Oakbrook Center, where 911 shows Oakbrook Road. Everything 
else is correct (State, CID, zip, street address). There is an Oakbrook road in 
the area, so I need to get this resolved so that there is no confusion in case 
of emergency.

Jason Faraone
Sr. Network Engineer Bear

Build-A-Bear Workshop, Inc.
1954 Innerbelt Business Center Drive
St. Louis, MO  63114


jas...@buildabear.com<mailto:jas...@buildabear.com>
www.buildabear.com<http://www.buildabear.com/>

Follow us: Facebook<https://www.facebook.com/Buildabear>, 
Twitter<https://twitter.com/buildabear>, 
YouTube<https://www.youtube.com/user/Buildabearworkshop1>, 
Pinterest<https://pinterest.com/buildabear/>

[cid:image007.jpg@01D5364A.CD0EB2B0]<http://www.buildabear.com/>[cid:image008.jpg@01D5364A.CD0EB2B0]<https://dashradio.com/buildabear>

The information in this message may be privileged, "confidential" and protected 
from disclosure and/or intended only for the addressee(s) named above. If the 
reader of this message is not the intended recipient, or an employee or agent 
responsible for delivering this message to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of the 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by replying to the message and deleting 
it from your computer. Please consider the environment before printing this 
email.
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] E911 Address Incorrect

[Lelio Fulgenzi]

Hey Jason,

Do you subscribe to a PS-ALI type service? Or are you relying on default 
address information?

If you are relying on default address information - that will be difficult to 
change since it's likely going to be tied to the service address of the PSTN 
connection.

That being said, if it's actually incorrect, you should be able to reach out to 
your account team for starting point. First thing I'd do is check with whomever 
is getting the bills for that PSTN number to see what the billing information 
looks like. If they have equipment records, that might help too.

Lelio


---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | le...@uoguelph.ca<mailto:le...@uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

From: cisco-voip  On Behalf Of Jason Faraone
Sent: Tuesday, July 9, 2019 12:09 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] E911 Address Incorrect

I have a location that shows the correct physical address when I dial 933, but 
a slightly incorrect address when dialing 911. Has anyone encountered this 
before?

Dialing 933 shows Oakbrook Center, where 911 shows Oakbrook Road. Everything 
else is correct (State, CID, zip, street address). There is an Oakbrook road in 
the area, so I need to get this resolved so that there is no confusion in case 
of emergency.

Jason Faraone
Sr. Network Engineer Bear

Build-A-Bear Workshop, Inc.
1954 Innerbelt Business Center Drive
St. Louis, MO  63114


jas...@buildabear.com<mailto:jas...@buildabear.com>
www.buildabear.com<http://www.buildabear.com/>

Follow us: Facebook<https://www.facebook.com/Buildabear>, 
Twitter<https://twitter.com/buildabear>, 
YouTube<https://www.youtube.com/user/Buildabearworkshop1>, 
Pinterest<https://pinterest.com/buildabear/>

[cid:image002.jpg@01D53652.28AE56F0]<http://www.buildabear.com/>[cid:image003.jpg@01D53652.28AE56F0]<https://dashradio.com/buildabear>

The information in this message may be privileged, "confidential" and protected 
from disclosure and/or intended only for the addressee(s) named above. If the 
reader of this message is not the intended recipient, or an employee or agent 
responsible for delivering this message to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of the 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by replying to the message and deleting 
it from your computer. Please consider the environment before printing this 
email.
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] E911 Address Incorrect

[Jason Faraone]

I have a location that shows the correct physical address when I dial 933, but 
a slightly incorrect address when dialing 911. Has anyone encountered this 
before?

Dialing 933 shows Oakbrook Center, where 911 shows Oakbrook Road. Everything 
else is correct (State, CID, zip, street address). There is an Oakbrook road in 
the area, so I need to get this resolved so that there is no confusion in case 
of emergency.
Jason Faraone
Sr. Network Engineer Bear

Build-A-Bear Workshop, Inc.
1954 Innerbelt Business Center Drive
St. Louis, MO  63114


jas...@buildabear.com
www.buildabear.com

Follow us: Facebook, 
Twitter, 
YouTube, 
Pinterest

[cid:image002.jpg@01D53646.C284A060][cid:image004.jpg@01D53646.C284A060]

The information in this message may be privileged, "confidential" and protected 
from disclosure and/or intended only for the addressee(s) named above. If the 
reader of this message is not the intended recipient, or an employee or agent 
responsible for delivering this message to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of the 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by replying to the message and deleting 
it from your computer. Please consider the environment before printing this 
email.
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] E911 System

[Brian Meade]

West/Redsky are the 2 big players in this space.

On Wed, Mar 6, 2019 at 2:49 PM Lisa Notarianni 
wrote:

> Hello All,
>
> We are currently using SPOK as our E911 system in our Cisco VoIP
> environment.  We populate the data nightly through a provisioning tool
> called 2nd Nature.  SPOK also provides a desktop client to notify our
> police department of a 911 call plus a passive phone call for them to
> listen to and get a head start on the situation.
>
> Our current system is end of support in December 2020.  We are considering
> an RFP since we have time.  I am wondering if anyone out there has had a
> good experience with any other E911 systems.
>
> The downside to what we do today is probably the same in most cases -
> there is no redundancy because we cannot afford 2 systems and SPOK does not
> offer a full VM option since the dedicated 911 PRI runs through the server.
>
> I look forward to your valued input.
>
> Thank you,
>
> Lisa Notarianni
> Telecommunications Engineer
> The University of Scranton
> 570.941.4325
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] E911 System

[Lisa Notarianni]

Hello All,

We are currently using SPOK as our E911 system in our Cisco VoIP environment.  
We populate the data nightly through a provisioning tool called 2nd Nature.  
SPOK also provides a desktop client to notify our police department of a 911 
call plus a passive phone call for them to listen to and get a head start on 
the situation.

Our current system is end of support in December 2020.  We are considering an 
RFP since we have time.  I am wondering if anyone out there has had a good 
experience with any other E911 systems.

The downside to what we do today is probably the same in most cases - there is 
no redundancy because we cannot afford 2 systems and SPOK does not offer a full 
VM option since the dedicated 911 PRI runs through the server.

I look forward to your valued input.

Thank you,

Lisa Notarianni 
Telecommunications Engineer
The University of Scranton 
570.941.4325
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911

[Parker Pearson - Donoma]

If it helps to have another resource, our company’s OneView CDR & Analytics 
solution for Cisco Call Manager has a popularly implemented report for 
notifying of any 911 calls that happen.  It can be an alert triggered 
immediately – or it can be configured to run periodic reports one can tell who 
called 911 (accidentally or otherwise).

The two biggest use cases are actual 911 notification (911 is called, and HR 
wants to be notified, particularly if it happened at a remote site where they 
might not otherwise hear of an emergency immediately) or people needing a 
little training because of repeated fat fingering particular area codes that 
start with 91x. (There’s a couple around the country)

Cheers,

Parker Pearson
Donoma Software


[Donoma Software Web Page]<http://donomasoftware.com/>

Parker Pearson
Vice President, Marketing & Business Development

Donoma Software
1750 Kraft Dr. Suite 1200 Blacksburg, VA 24060
540.443.3577
par...@donomasoftware.com
www.donomasoftware.com<http://www.donomasoftware.com>
[Facebook]<https://www.facebook.com/DonomaSoftware> [Twitter] 
<https://twitter.com/donomasoftware>  [LinkedIn] 
<https://www.linkedin.com/company/donoma-software>


From: cisco-voip  on behalf of Matthew 
Loraditch 
Date: Wednesday, March 7, 2018 at 4:07 PM
To: NateCCIE , 'Ryan Huff' , 
"cisco-voip@puck.nether.net" 
Subject: Re: [cisco-voip] e911

As far as I know that feature doesn’t notify anyone internally.
The part of the law I’m referring to is this:

“A person engaged in the business of installing, managing, or operating 
multi-line telephone systems shall, in installing, managing, or operating such 
a system for use in the United States, configure the system to provide a 
notification to a central location at the facility where the system is 
installed or to another person or organization regardless of location, if the 
system is able to be configured to provide the notification without an 
improvement to the hardware or software of the system.”





Matthew Loraditch

Sr. Network Engineer


p: 443.541.1518



w: www.heliontechnologies.com<http://www.heliontechnologies.com/>

 |

e: mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>


[cid:image970315.png@0F1E6CCE.E3A950A8]


[Facebook]<https://facebook.com/heliontech>


[Twitter]<https://twitter.com/heliontech>


[LinkedIn]<https://www.linkedin.com/company/helion-technologies>












The information transmitted, including attachments, is intended only for the 
person(s) or entity to which it is addressed and may contain confidential 
and/or privileged material. Any review, retransmission, dissemination or other 
use of, or taking of any action in reliance upon this information by persons or 
entities other than the intended recipient is prohibited. If you received this 
in error, please contact the sender and destroy any copies of this information.
From: NateCCIE [mailto:natec...@gmail.com]
Sent: Wednesday, March 7, 2018 3:58 PM
To: Matthew Loraditch ; 'Ryan Huff' 
; cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] e911

Um, I thought it did.

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200452-Usage-of-Native-Emergency-Call-Routing-F.html


From: cisco-voip 
mailto:cisco-voip-boun...@puck.nether.net>> 
On Behalf Of Matthew Loraditch
Sent: Wednesday, March 7, 2018 1:36 PM
To: Ryan Huff mailto:ryanh...@outlook.com>>; 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] e911

To piggy back on this, while Cisco doesn’t have emergency notifications built 
in, as the law mentions, and thus they are not required, does anyone know of 
options beyond Singlewire that they are happy with? The installs would monitor 
up to 1000 or so handsets but the folks that would be notified would probably 
be fewer than 50.




Matthew Loraditch

Sr. Network Engineer


p: 443.541.1518



w: www.heliontechnologies.com<http://www.heliontechnologies.com/>

 |

e: mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>


[cid:image001.png@01D3B62D.FF2B55D0]


[Facebook]<https://facebook.com/heliontech>


[Twitter]<https://twitter.com/heliontech>


[LinkedIn]







From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan 
Huff
Sent: Wednesday, March 7, 2018 3:11 PM
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: [cisco-voip] e911

I wonder how cloud-based phone system like Cisco spark will answer this?


https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar
Sent from my iPhone
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911

[Bill Talley]

Great points Ryan.  

We have a standard 9-1-1 disclaimer in our scopes (as I’m sure many VARs do), 
though it primarily focuses on location and alerting versus access.  I would 
imagine it would now also need to include reference to this mandate prohibiting 
restrictions to direct access of 9-1-1 services... i.e. call it out BEFORE the 
sale to establish baseline notification to the customer.

We also use the Uplinx Reporting Tool (unpaid plug) to capture a snapshot of 
the CUCM configuration database during handoff to customers,  as well as 
pre-upgrade and post-upgrade snapshots during upgrades of existing systems.  
Something like Uplinx or AXL/SOAP exports, BAT exports, or anything with time 
stamps bound to the config data will be crucial for everyone going forward.

Sent from a mobile device with very tiny touchscreen input keys. Please excude 
my typtos.   

> On Mar 7, 2018, at 9:16 PM, Ryan Huff  wrote:
> 
> Legal language aside, I see this as a HUGE area for VARs to get into civil 
> torts with customers.
> 
> Ideally the end customer is the true owner and stakeholder of the MLTS 
> however; when levied with a government fine (presumably how it would be 
> handled), due to e911 malfeasance, who was the last one to touch it?
> 
> Document everything, get sign off on everything and proceed with caution :) 
> brothers and sisters.
> 
> Sent from my iPhone
> 
> On Mar 7, 2018, at 22:10, Anthony Holloway  
> wrote:
> 
>> I'd be cautious with this one.
>> 
>> 1) You penalize actual emergency calls from connecting as quickly as 
>> possible.  Do you really want to be the person responsible for that?
>> 
>> 2) You penalize the entire cluster by changing a global parameter, for the 
>> occasional accidental 911 call.
>> 
>> I think a better solution is to solve the human problem.  Just like we 
>> wouldn't tolerate our children playing on land lines or cell phones calling 
>> 911 (even my son has done it), we shouldn't tolerate adults doing it either.
>> 
>> Failing that, switch your PSTN trunk access code to another digit.  8 seems 
>> to be a popular second choice.
>> 
>>> On Wed, Mar 7, 2018 at 3:41 PM NateCCIE  wrote:
>>> This might be a good time to talk about my favorite way to enable 911.
>>> 
>>>  
>>> 
>>> Set the interdigit timeout to a small value, like 3-5 seconds.  Then create 
>>> a 911 route pattern, and a 911! Pattern, that does not route to 911.  If 
>>> the user dials 911 and stops, the call connects.  If they keep dialing 
>>> which usually what happens on a miss-dial, they get whatever your 911! 
>>> Pattern is configured to do, usually I like block this pattern.
>>> 
>>>  
>>> 
>>> -Nate
>>> 
>>>  
>>> 
>>> From: Bill Talley  
>>> Sent: Wednesday, March 7, 2018 2:22 PM
>>> To: Matthew Loraditch 
>>> Cc: NateCCIE ; Ryan Huff ; 
>>> cisco-voip@puck.nether.net
>>> Subject: Re: [cisco-voip] e911
>>> 
>>>  
>>> 
>>> Seems like there's two key aspects we need to be concerned with.  1) As I 
>>> think Matthew is pointing out, notifications are only required if 
>>> notifications are a native feature available "without improvement", i.e. 
>>> add-on components.  2)  We now MUST configure direct 911 access without 
>>> regard to customer complaints or PSAP complaints about accidental 911 calls.
>>> 
>>>  
>>> 
>>> To answer your question Matthew, I have only ever used CER and Singlewire 
>>> for notifications, sorry I can't provide more feedback.
>>> 
>>>  
>>> 
>>> On Wed, Mar 7, 2018 at 3:06 PM, Matthew Loraditch 
>>>  wrote:
>>> 
>>> As far as I know that feature doesn’t notify anyone internally.
>>> 
>>> The part of the law I’m referring to is this:
>>> 
>>>  
>>> 
>>> “A person engaged in the business of installing, managing, or operating 
>>> multi-line telephone systems shall, in installing, managing, or operating 
>>> such a system for use in the United States, configure the system to provide 
>>> a notification to a central location at the facility where the system is 
>>> installed or to another person or organization regardless of location, if 
>>> the system is able to be configured to provide the notification without an 
>>> improvement to the hardware or software of the system.”
>>> 
>>>  
>>> 
>>>  
>>> 
>>>  
>>> 
>>>  
>>> 
>>> 

Re: [cisco-voip] e911

[Ryan Huff]

It would be the PSTN carrier the Spark customer is using, that would ultimately 
provide the PSAP routing.

https://www.cisco.com/c/en/us/solutions/collateral/unified-communications/hosted-collaboration-solution-hcs/datasheet-c78-736823.html

My thought is, what if anything, will this change for Spark. The data sheet 
seems to suggest (although I have no experience with it) that Spark does have 
an ELAN service.

I just see this as the catalyst to a licensing model change. Who knows I 
suppose.

Thanks,

Ryan

On Mar 7, 2018, at 22:26, Anthony Holloway 
mailto:avholloway+cisco-v...@gmail.com>> wrote:

Oh I see.  Yeah, government ignorance aside, I would say it is.

So, Spark does support 911 calls today?

If so, what's there to change?  The law seems to be written such that, as long 
as the system is configured for direct 911 access, before being "installed,"  
you're fine.  The "installed" word might be confusing for some, but I read that 
as being the same as "in production."  Then of course you have to define "in 
production,"  which, does that include training room phones, pilot users, beta 
testers, etc.

On Wed, Mar 7, 2018 at 9:17 PM Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:
If this is to apply to multi line telephone systems at large, is the Spark 
Cloud not a MLTS?

Sent from my iPhone

On Mar 7, 2018, at 22:12, Anthony Holloway 
mailto:avholloway+cisco-v...@gmail.com>> wrote:

Can you not call 911 from Spark?  Or did I miss what "this" is in your context?

On Wed, Mar 7, 2018 at 2:11 PM Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:
I wonder how cloud-based phone system like Cisco spark will answer this?


https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar

Sent from my iPhone
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911

[Anthony Holloway]

Oh I see.  Yeah, government ignorance aside, I would say it is.

So, Spark does support 911 calls today?

If so, what's there to change?  The law seems to be written such that, as
long as the system is configured for direct 911 access, before being
"installed,"  you're fine.  The "installed" word might be confusing for
some, but I read that as being the same as "in production."  Then of course
you have to define "in production,"  which, does that include training room
phones, pilot users, beta testers, etc.

On Wed, Mar 7, 2018 at 9:17 PM Ryan Huff  wrote:

> If this is to apply to multi line telephone systems at large, is the Spark
> Cloud not a MLTS?
>
> Sent from my iPhone
>
> On Mar 7, 2018, at 22:12, Anthony Holloway <
> avholloway+cisco-v...@gmail.com> wrote:
>
> Can you not call 911 from Spark?  Or did I miss what "this" is in your
> context?
>
> On Wed, Mar 7, 2018 at 2:11 PM Ryan Huff  wrote:
>
>> I wonder how cloud-based phone system like Cisco spark will answer this?
>>
>>
>> https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar
>>
>> Sent from my iPhone
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911

[Ryan Huff]

If this is to apply to multi line telephone systems at large, is the Spark 
Cloud not a MLTS?

Sent from my iPhone

On Mar 7, 2018, at 22:12, Anthony Holloway 
mailto:avholloway+cisco-v...@gmail.com>> wrote:

Can you not call 911 from Spark?  Or did I miss what "this" is in your context?

On Wed, Mar 7, 2018 at 2:11 PM Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:
I wonder how cloud-based phone system like Cisco spark will answer this?


https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar

Sent from my iPhone
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911

[Ryan Huff]

Legal language aside, I see this as a HUGE area for VARs to get into civil 
torts with customers.

Ideally the end customer is the true owner and stakeholder of the MLTS however; 
when levied with a government fine (presumably how it would be handled), due to 
e911 malfeasance, who was the last one to touch it?

Document everything, get sign off on everything and proceed with caution :) 
brothers and sisters.

Sent from my iPhone

On Mar 7, 2018, at 22:10, Anthony Holloway 
mailto:avholloway+cisco-v...@gmail.com>> wrote:

I'd be cautious with this one.

1) You penalize actual emergency calls from connecting as quickly as possible.  
Do you really want to be the person responsible for that?

2) You penalize the entire cluster by changing a global parameter, for the 
occasional accidental 911 call.

I think a better solution is to solve the human problem.  Just like we wouldn't 
tolerate our children playing on land lines or cell phones calling 911 (even my 
son has done it), we shouldn't tolerate adults doing it either.

Failing that, switch your PSTN trunk access code to another digit.  8 seems to 
be a popular second choice.

On Wed, Mar 7, 2018 at 3:41 PM NateCCIE 
mailto:natec...@gmail.com>> wrote:
This might be a good time to talk about my favorite way to enable 911.

Set the interdigit timeout to a small value, like 3-5 seconds.  Then create a 
911 route pattern, and a 911! Pattern, that does not route to 911.  If the user 
dials 911 and stops, the call connects.  If they keep dialing which usually 
what happens on a miss-dial, they get whatever your 911! Pattern is configured 
to do, usually I like block this pattern.

-Nate

From: Bill Talley mailto:btal...@gmail.com>>
Sent: Wednesday, March 7, 2018 2:22 PM
To: Matthew Loraditch 
mailto:mloradi...@heliontechnologies.com>>
Cc: NateCCIE mailto:natec...@gmail.com>>; Ryan Huff 
mailto:ryanh...@outlook.com>>; 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] e911

Seems like there's two key aspects we need to be concerned with.  1) As I think 
Matthew is pointing out, notifications are only required if notifications are a 
native feature available "without improvement", i.e. add-on components.  2)  We 
now MUST configure direct 911 access without regard to customer complaints or 
PSAP complaints about accidental 911 calls.

To answer your question Matthew, I have only ever used CER and Singlewire for 
notifications, sorry I can't provide more feedback.

On Wed, Mar 7, 2018 at 3:06 PM, Matthew Loraditch 
mailto:mloradi...@heliontechnologies.com>> 
wrote:
As far as I know that feature doesn’t notify anyone internally.
The part of the law I’m referring to is this:

“A person engaged in the business of installing, managing, or operating 
multi-line telephone systems shall, in installing, managing, or operating such 
a system for use in the United States, configure the system to provide a 
notification to a central location at the facility where the system is 
installed or to another person or organization regardless of location, if the 
system is able to be configured to provide the notification without an 
improvement to the hardware or software of the system.”





Matthew Loraditch

Sr. Network Engineer


p: 443.541.1518



w: www.heliontechnologies.com<http://www.heliontechnologies.com/>

 |

e: mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>





<https://facebook.com/heliontech>



<https://twitter.com/heliontech>



<https://www.linkedin.com/company/helion-technologies>








From: NateCCIE [mailto:natec...@gmail.com<mailto:natec...@gmail.com>]
Sent: Wednesday, March 7, 2018 3:58 PM
To: Matthew Loraditch 
mailto:mloradi...@heliontechnologies.com>>; 
'Ryan Huff' mailto:ryanh...@outlook.com>>; 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: RE: [cisco-voip] e911

Um, I thought it did.

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200452-Usage-of-Native-Emergency-Call-Routing-F.html


From: cisco-voip 
mailto:cisco-voip-boun...@puck.nether.net>> 
On Behalf Of Matthew Loraditch
Sent: Wednesday, March 7, 2018 1:36 PM
To: Ryan Huff mailto:ryanh...@outlook.com>>; 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] e911

To piggy back on this, while Cisco doesn’t have emergency notifications built 
in, as the law mentions, and thus they are not required, does anyone know of 
options beyond Singlewire that they are happy with? The installs would monitor 
up to 1000 or so handsets but the folks that would be notified would probably 
be fewer than 50.




Matthew Loraditch

Sr. Network Engineer


p: 443.541.1518



w: www.heliontechnologies.com<http://www.heliontechnologies.com/>

 |

e: mloradi.

Re: [cisco-voip] e911

[Anthony Holloway]

Can you not call 911 from Spark?  Or did I miss what "this" is in your
context?

On Wed, Mar 7, 2018 at 2:11 PM Ryan Huff  wrote:

> I wonder how cloud-based phone system like Cisco spark will answer this?
>
>
> https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar
>
> Sent from my iPhone
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911

[Anthony Holloway]

I'd be cautious with this one.

1) You penalize actual emergency calls from connecting as quickly as
possible.  Do you really want to be the person responsible for that?

2) You penalize the entire cluster by changing a global parameter, for the
occasional accidental 911 call.

I think a better solution is to solve the human problem.  Just like we
wouldn't tolerate our children playing on land lines or cell phones calling
911 (even my son has done it), we shouldn't tolerate adults doing it either.

Failing that, switch your PSTN trunk access code to another digit.  8 seems
to be a popular second choice.

On Wed, Mar 7, 2018 at 3:41 PM NateCCIE  wrote:

> This might be a good time to talk about my favorite way to enable 911.
>
>
>
> Set the interdigit timeout to a small value, like 3-5 seconds.  Then
> create a 911 route pattern, and a 911! Pattern, that does not route to
> 911.  If the user dials 911 and stops, the call connects.  If they keep
> dialing which usually what happens on a miss-dial, they get whatever your
> 911! Pattern is configured to do, usually I like block this pattern.
>
>
>
> -Nate
>
>
>
> *From:* Bill Talley 
> *Sent:* Wednesday, March 7, 2018 2:22 PM
> *To:* Matthew Loraditch 
> *Cc:* NateCCIE ; Ryan Huff ;
> cisco-voip@puck.nether.net
> *Subject:* Re: [cisco-voip] e911
>
>
>
> Seems like there's two key aspects we need to be concerned with.  1) As I
> think Matthew is pointing out, notifications are only required if
> notifications are a native feature available "without improvement", i.e.
> add-on components.  2)  We now MUST configure direct 911 access without
> regard to customer complaints or PSAP complaints about accidental 911 calls.
>
>
>
> To answer your question Matthew, I have only ever used CER and Singlewire
> for notifications, sorry I can't provide more feedback.
>
>
>
> On Wed, Mar 7, 2018 at 3:06 PM, Matthew Loraditch <
> mloradi...@heliontechnologies.com> wrote:
>
> As far as I know that feature doesn’t notify anyone internally.
>
> The part of the law I’m referring to is this:
>
>
>
> *“A person engaged in the business of installing, managing, or operating
> multi-line telephone systems shall, in installing, managing, or operating
> such a system for use in the United States, configure the system to provide
> a notification to a central location at the facility where the system is
> installed or to another person or organization regardless of location, if
> the system is able to be configured to provide the notification without an
> improvement to the hardware or software of the system.”*
>
>
>
>
>
>
>
>
>
> *Matthew Loraditch*
>
> *Sr. Network Engineer*
>
> p: *443.541.1518* <443.541.1518>
>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>
>
>  |
>
> e: *mloradi...@heliontechnologies.com* 
>
> [image: image001.png]
>
> <https://facebook.com/heliontech>
> [image: image002.png]
>
> <https://twitter.com/heliontech>
> [image: image003.png]
>
> <https://www.linkedin.com/company/helion-technologies>
> [image: image004.png]
>
>
>
> *From:* NateCCIE [mailto:natec...@gmail.com]
> *Sent:* Wednesday, March 7, 2018 3:58 PM
> *To:* Matthew Loraditch ; 'Ryan Huff' <
> ryanh...@outlook.com>; cisco-voip@puck.nether.net
> *Subject:* RE: [cisco-voip] e911
>
>
>
> Um, I thought it did.
>
>
>
>
> https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200452-Usage-of-Native-Emergency-Call-Routing-F.html
>
>
>
>
>
> *From:* cisco-voip  *On Behalf Of *Matthew
> Loraditch
> *Sent:* Wednesday, March 7, 2018 1:36 PM
> *To:* Ryan Huff ; cisco-voip@puck.nether.net
> *Subject:* Re: [cisco-voip] e911
>
>
>
> To piggy back on this, while Cisco doesn’t have emergency notifications
> built in, as the law mentions, and thus they are not required, does anyone
> know of options beyond Singlewire that they are happy with? The installs
> would monitor up to 1000 or so handsets but the folks that would be
> notified would probably be fewer than 50.
>
>
>
>
>
>
>
> *Matthew Loraditch*
>
> *Sr. Network Engineer*
>
> p: *443.541.1518* <443.541.1518>
>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>
>
>  |
>
> e: *mloradi...@heliontechnologies.com* 
>
> [image: image001.png]
>
> <https://facebook.com/heliontech>
> [image: image002.png]
>
> <https://twitter.com/heliontech>
> [image: image003.png]
>
> <https://www.linkedin.com/company/helion-technologies>

Re: [cisco-voip] e911

[Tim Kenyon]

That's pretty close to accurate Matt. When we first started working on Kari's 
Law, the main priority was to remove the necessity of dialing any trunk access 
code in order to get to 911. That all started due to the death of Kari Hunt in 
Texas when she was being stabbed by her soon to be ex husband and Kari's 9 year 
old daughter was trying to dial 911 from the hotel phone and did not know she 
needed to dial 9 first to get out. She tried 4 times and finally grabbed her 
siblings and ran for help.


The onsite notification piece was written so that if someone in a hotel dialed 
911, the call would go directly to 911, but alert the front desk that "hey, 
room 301 just dialed 911" type of events. A lot of hotels used to tell people 
to dial something internally instead of dialing 911 and that call would go to 
theo hotel operator or the front desk instead of 911. Problem was, smaller 
hotels, middle of the night, one guy working the front desk and steps away from 
the desk. This requirement obviously extended to any MLTS system to provide on 
site notification.


And the third point of the law was basically to avoid that similar front desk 
experience. If someone dials 911, the calls should go to a fully trained and 
certified 911 call handler, not the dude at the front desk.


My company spent quite a bit of time working on and promoting Kari's law. The 
Hunt family are now very dear personal friends of ours.


Since we are on this topic of 911, if anyone would like to have a discussion 
with me on what some of the other vendors are trying to get into law that would 
end up costing every customer out there TONS of money to support, please reach 
out to me. I think it is important that everyone understand what some of these 
guys are trying to do that is only going to end up costing the customers a TON 
of money to implement.


Regards,

Tim



Tim Kenyon, ENP
President
Conveyant Systems, Inc.
Suwanee, GA 30043
770-339-1085
tken...@conveyant.com<mailto:kk...@conveyant.com>


This Email and any documents accompanying this Email contain information from 
Conveyant Systems, Inc. which is confidential and/or privileged. The 
information is intended only for the use of the individual or entity named on 
this Email. If you are not the intended recipient; you are hereby notified that 
any disclosure, copying, distribution or the taking of any action in reliance 
on the contents of this Email information is strictly prohibited.




From: cisco-voip  on behalf of Matthew 
Loraditch 
Sent: Wednesday, March 7, 2018 4:37 PM
To: Bill Talley; Ryan Huff
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] e911


It refers to just subsection a which is the part that requires Cisco and other 
manufacturers and resellers to not build or sell a system unless it’s 
preconfigured to allow this when setup properly.



At least that’s how I read it.




Matthew Loraditch
Sr. Network Engineer

p: 443.541.1518


w: www.heliontechnologies.com<http://www.heliontechnologies.com/>|  
e: mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>

[cid:image136887.png@FC71AD9B.2F65509D]

[Facebook]<https://facebook.com/heliontech>

[Twitter]<https://twitter.com/heliontech>

[LinkedIn]<https://www.linkedin.com/company/helion-technologies>





 From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Bill 
Talley
Sent: Wednesday, March 7, 2018 4:32 PM
To: Ryan Huff 
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] e911



Digging further, does this mean the law doesn't go into affect until Feb, 2020?



(b) Effective Date.—The amendment made by subsection (a) shall apply with 
respect to a multi-line telephone system that is manufactured, imported, 
offered for first sale or lease, first sold or leased, or installed after the 
date that is 2 years after the date of the enactment of this Act.



On Wed, Mar 7, 2018 at 2:11 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:

I wonder how cloud-based phone system like Cisco spark will answer this?





https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar

Sent from my iPhone

___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip


___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911

[NateCCIE]

This might be a good time to talk about my favorite way to enable 911.

 

Set the interdigit timeout to a small value, like 3-5 seconds.  Then create a 
911 route pattern, and a 911! Pattern, that does not route to 911.  If the user 
dials 911 and stops, the call connects.  If they keep dialing which usually 
what happens on a miss-dial, they get whatever your 911! Pattern is configured 
to do, usually I like block this pattern.

 

-Nate

 

From: Bill Talley  
Sent: Wednesday, March 7, 2018 2:22 PM
To: Matthew Loraditch 
Cc: NateCCIE ; Ryan Huff ; 
cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] e911

 

Seems like there's two key aspects we need to be concerned with.  1) As I think 
Matthew is pointing out, notifications are only required if notifications are a 
native feature available "without improvement", i.e. add-on components.  2)  We 
now MUST configure direct 911 access without regard to customer complaints or 
PSAP complaints about accidental 911 calls.

 

To answer your question Matthew, I have only ever used CER and Singlewire for 
notifications, sorry I can't provide more feedback.

 

On Wed, Mar 7, 2018 at 3:06 PM, Matthew Loraditch 
mailto:mloradi...@heliontechnologies.com> > 
wrote:

As far as I know that feature doesn’t notify anyone internally.

The part of the law I’m referring to is this:

 

“A person engaged in the business of installing, managing, or operating 
multi-line telephone systems shall, in installing, managing, or operating such 
a system for use in the United States, configure the system to provide a 
notification to a central location at the facility where the system is 
installed or to another person or organization regardless of location, if the 
system is able to be configured to provide the notification without an 
improvement to the hardware or software of the system.”

 

 

 



 


Matthew Loraditch



Sr. Network Engineer




p:   443.541.1518



w:  <http://www.heliontechnologies.com/> www.heliontechnologies.com

 | 

e:  <mailto:mloradi...@heliontechnologies.com> mloradi...@heliontechnologies.com









 <https://facebook.com/heliontech> 


 <https://twitter.com/heliontech> 


 <https://www.linkedin.com/company/helion-technologies> 

 

From: NateCCIE [mailto:natec...@gmail.com <mailto:natec...@gmail.com> ] 
Sent: Wednesday, March 7, 2018 3:58 PM
To: Matthew Loraditch mailto:mloradi...@heliontechnologies.com> >; 'Ryan Huff' mailto:ryanh...@outlook.com> >; cisco-voip@puck.nether.net 
<mailto:cisco-voip@puck.nether.net> 
Subject: RE: [cisco-voip] e911

 

Um, I thought it did.

 

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200452-Usage-of-Native-Emergency-Call-Routing-F.html

 

 

From: cisco-voip mailto:cisco-voip-boun...@puck.nether.net> > On Behalf Of Matthew Loraditch
Sent: Wednesday, March 7, 2018 1:36 PM
To: Ryan Huff mailto:ryanh...@outlook.com> >; 
cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net> 
Subject: Re: [cisco-voip] e911

 

To piggy back on this, while Cisco doesn’t have emergency notifications built 
in, as the law mentions, and thus they are not required, does anyone know of 
options beyond Singlewire that they are happy with? The installs would monitor 
up to 1000 or so handsets but the folks that would be notified would probably 
be fewer than 50.

 

 



 


Matthew Loraditch



Sr. Network Engineer




p:   443.541.1518



w:  <http://www.heliontechnologies.com/> www.heliontechnologies.com

 | 

e:  <mailto:mloradi...@heliontechnologies.com> mloradi...@heliontechnologies.com









 <https://facebook.com/heliontech> 


 <https://twitter.com/heliontech> 


 <https://www.linkedin.com/company/helion-technologies> 

 

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan 
Huff
Sent: Wednesday, March 7, 2018 3:11 PM
To: cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net> 
Subject: [cisco-voip] e911

 

I wonder how cloud-based phone system like Cisco spark will answer this?

 

 

https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar

Sent from my iPhone


___
cisco-voip mailing list
cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net> 
https://puck.nether.net/mailman/listinfo/cisco-voip

 

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911

[Matthew Loraditch]

It refers to just subsection a which is the part that requires Cisco and other 
manufacturers and resellers to not build or sell a system unless it’s 
preconfigured to allow this when setup properly.

At least that’s how I read it.


Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: mloradi...@heliontechnologies.com
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Bill 
Talley
Sent: Wednesday, March 7, 2018 4:32 PM
To: Ryan Huff 
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] e911

Digging further, does this mean the law doesn't go into affect until Feb, 2020?

(b) Effective Date.—The amendment made by subsection (a) shall apply with 
respect to a multi-line telephone system that is manufactured, imported, 
offered for first sale or lease, first sold or leased, or installed after the 
date that is 2 years after the date of the enactment of this Act.

On Wed, Mar 7, 2018 at 2:11 PM, Ryan Huff 
mailto:ryanh...@outlook.com>> wrote:
I wonder how cloud-based phone system like Cisco spark will answer this?


https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar
Sent from my iPhone

___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911

[Bill Talley]

Digging further, does this mean the law doesn't go into affect until Feb,
2020?

(b) Effective Date.—The amendment made by subsection (a) shall apply with
respect to a multi-line telephone system that is manufactured, imported,
offered for first sale or lease, first sold or leased, or installed after
the date that is 2 years after the date of the enactment of this Act.

On Wed, Mar 7, 2018 at 2:11 PM, Ryan Huff  wrote:

> I wonder how cloud-based phone system like Cisco spark will answer this?
>
>
> https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar
>
> Sent from my iPhone
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911

[Matthew Loraditch]

And with Number 2, I believe that to be effective immediately, it’s also 
written fairly broadly as to who is responsible. I’d imagine there will be a 
ramp up before actual enforcement, but we are going through and verifying all 
clients and changing immediately, if need be.

Here’s the whole thing: 
https://www.congress.gov/bill/115th-congress/house-bill/582/text For something 
legal it’s pretty plain English.

CYA!



Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: mloradi...@heliontechnologies.com
From: Bill Talley [mailto:btal...@gmail.com]
Sent: Wednesday, March 7, 2018 4:22 PM
To: Matthew Loraditch 
Cc: NateCCIE ; Ryan Huff ; 
cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] e911

Seems like there's two key aspects we need to be concerned with.  1) As I think 
Matthew is pointing out, notifications are only required if notifications are a 
native feature available "without improvement", i.e. add-on components.  2)  We 
now MUST configure direct 911 access without regard to customer complaints or 
PSAP complaints about accidental 911 calls.

To answer your question Matthew, I have only ever used CER and Singlewire for 
notifications, sorry I can't provide more feedback.

On Wed, Mar 7, 2018 at 3:06 PM, Matthew Loraditch 
mailto:mloradi...@heliontechnologies.com>> 
wrote:
As far as I know that feature doesn’t notify anyone internally.
The part of the law I’m referring to is this:

“A person engaged in the business of installing, managing, or operating 
multi-line telephone systems shall, in installing, managing, or operating such 
a system for use in the United States, configure the system to provide a 
notification to a central location at the facility where the system is 
installed or to another person or organization regardless of location, if the 
system is able to be configured to provide the notification without an 
improvement to the hardware or software of the system.”





Matthew Loraditch

Sr. Network Engineer


p: 443.541.1518



w: www.heliontechnologies.com<http://www.heliontechnologies.com/>

 |

e: mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>


[cid:image001.png@01D3B631.5163BCE0]


[Facebook]<https://facebook.com/heliontech>


[Twitter]<https://twitter.com/heliontech>


[LinkedIn]<https://www.linkedin.com/company/helion-technologies>







From: NateCCIE [mailto:natec...@gmail.com<mailto:natec...@gmail.com>]
Sent: Wednesday, March 7, 2018 3:58 PM
To: Matthew Loraditch 
mailto:mloradi...@heliontechnologies.com>>; 
'Ryan Huff' mailto:ryanh...@outlook.com>>; 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: RE: [cisco-voip] e911

Um, I thought it did.

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200452-Usage-of-Native-Emergency-Call-Routing-F.html


From: cisco-voip 
mailto:cisco-voip-boun...@puck.nether.net>> 
On Behalf Of Matthew Loraditch
Sent: Wednesday, March 7, 2018 1:36 PM
To: Ryan Huff mailto:ryanh...@outlook.com>>; 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] e911

To piggy back on this, while Cisco doesn’t have emergency notifications built 
in, as the law mentions, and thus they are not required, does anyone know of 
options beyond Singlewire that they are happy with? The installs would monitor 
up to 1000 or so handsets but the folks that would be notified would probably 
be fewer than 50.




Matthew Loraditch

Sr. Network Engineer


p: 443.541.1518



w: www.heliontechnologies.com<http://www.heliontechnologies.com/>

 |

e: mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>


[cid:image001.png@01D3B631.5163BCE0]


[Facebook]<https://facebook.com/heliontech>


[Twitter]<https://twitter.com/heliontech>


[LinkedIn]<https://www.linkedin.com/company/helion-technologies>







From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan 
Huff
Sent: Wednesday, March 7, 2018 3:11 PM
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: [cisco-voip] e911

I wonder how cloud-based phone system like Cisco spark will answer this?


https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar
Sent from my iPhone

___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911

[Bill Talley]

Seems like there's two key aspects we need to be concerned with.  1) As I
think Matthew is pointing out, notifications are only required if
notifications are a native feature available "without improvement", i.e.
add-on components.  2)  We now MUST configure direct 911 access without
regard to customer complaints or PSAP complaints about accidental 911 calls.

To answer your question Matthew, I have only ever used CER and Singlewire
for notifications, sorry I can't provide more feedback.

On Wed, Mar 7, 2018 at 3:06 PM, Matthew Loraditch <
mloradi...@heliontechnologies.com> wrote:

> As far as I know that feature doesn’t notify anyone internally.
>
> The part of the law I’m referring to is this:
>
>
>
> *“A person engaged in the business of installing, managing, or operating
> multi-line telephone systems shall, in installing, managing, or operating
> such a system for use in the United States, configure the system to provide
> a notification to a central location at the facility where the system is
> installed or to another person or organization regardless of location, if
> the system is able to be configured to provide the notification without an
> improvement to the hardware or software of the system.”*
>
>
>
>
>
>
>
> Matthew Loraditch
> Sr. Network Engineer
> p: *443.541.1518* <443.541.1518>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>  |
> e: *mloradi...@heliontechnologies.com* 
> [image: Facebook] <https://facebook.com/heliontech>
> [image: Twitter] <https://twitter.com/heliontech>
> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>
>
> *From:* NateCCIE [mailto:natec...@gmail.com]
> *Sent:* Wednesday, March 7, 2018 3:58 PM
> *To:* Matthew Loraditch ; 'Ryan Huff' <
> ryanh...@outlook.com>; cisco-voip@puck.nether.net
> *Subject:* RE: [cisco-voip] e911
>
>
>
> Um, I thought it did.
>
>
>
> https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-
> communications-manager-callmanager/200452-Usage-of-
> Native-Emergency-Call-Routing-F.html
>
>
>
>
>
> *From:* cisco-voip  *On Behalf Of *Matthew
> Loraditch
> *Sent:* Wednesday, March 7, 2018 1:36 PM
> *To:* Ryan Huff ; cisco-voip@puck.nether.net
> *Subject:* Re: [cisco-voip] e911
>
>
>
> To piggy back on this, while Cisco doesn’t have emergency notifications
> built in, as the law mentions, and thus they are not required, does anyone
> know of options beyond Singlewire that they are happy with? The installs
> would monitor up to 1000 or so handsets but the folks that would be
> notified would probably be fewer than 50.
>
>
>
>
>
>
>
> *Matthew Loraditch*
>
> *Sr. Network Engineer*
>
> p: *443.541.1518* <443.541.1518>
>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>
>
>  |
>
> e: *mloradi...@heliontechnologies.com* 
>
> [image: Facebook] <https://facebook.com/heliontech>
>
> [image: Twitter] <https://twitter.com/heliontech>
>
> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net
> ] *On Behalf Of *Ryan Huff
> *Sent:* Wednesday, March 7, 2018 3:11 PM
> *To:* cisco-voip@puck.nether.net
> *Subject:* [cisco-voip] e911
>
>
>
> I wonder how cloud-based phone system like Cisco spark will answer this?
>
>
>
>
>
> https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar
>
> Sent from my iPhone
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911

[Brian Meade]

That allows you to route calls using basic ELIN support but doesn't really
do any notifications like CER/InformaCast do.

On Wed, Mar 7, 2018 at 3:58 PM, NateCCIE  wrote:

> Um, I thought it did.
>
>
>
> https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-
> communications-manager-callmanager/200452-Usage-of-
> Native-Emergency-Call-Routing-F.html
>
>
>
>
>
> *From:* cisco-voip  *On Behalf Of *Matthew
> Loraditch
> *Sent:* Wednesday, March 7, 2018 1:36 PM
> *To:* Ryan Huff ; cisco-voip@puck.nether.net
> *Subject:* Re: [cisco-voip] e911
>
>
>
> To piggy back on this, while Cisco doesn’t have emergency notifications
> built in, as the law mentions, and thus they are not required, does anyone
> know of options beyond Singlewire that they are happy with? The installs
> would monitor up to 1000 or so handsets but the folks that would be
> notified would probably be fewer than 50.
>
>
>
>
>
>
>
> *Matthew Loraditch*
>
> *Sr. Network Engineer*
>
> p: *443.541.1518* <443.541.1518>
>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>
>
>  |
>
> e: *mloradi...@heliontechnologies.com* 
>
> [image: Facebook] <https://facebook.com/heliontech>
>
> [image: Twitter] <https://twitter.com/heliontech>
>
> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net
> ] *On Behalf Of *Ryan Huff
> *Sent:* Wednesday, March 7, 2018 3:11 PM
> *To:* cisco-voip@puck.nether.net
> *Subject:* [cisco-voip] e911
>
>
>
> I wonder how cloud-based phone system like Cisco spark will answer this?
>
>
>
>
>
> https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar
>
> Sent from my iPhone
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911

[Matthew Loraditch]

As far as I know that feature doesn’t notify anyone internally.
The part of the law I’m referring to is this:

“A person engaged in the business of installing, managing, or operating 
multi-line telephone systems shall, in installing, managing, or operating such 
a system for use in the United States, configure the system to provide a 
notification to a central location at the facility where the system is 
installed or to another person or organization regardless of location, if the 
system is able to be configured to provide the notification without an 
improvement to the hardware or software of the system.”




Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: mloradi...@heliontechnologies.com
From: NateCCIE [mailto:natec...@gmail.com]
Sent: Wednesday, March 7, 2018 3:58 PM
To: Matthew Loraditch ; 'Ryan Huff' 
; cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] e911

Um, I thought it did.

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200452-Usage-of-Native-Emergency-Call-Routing-F.html


From: cisco-voip 
mailto:cisco-voip-boun...@puck.nether.net>> 
On Behalf Of Matthew Loraditch
Sent: Wednesday, March 7, 2018 1:36 PM
To: Ryan Huff mailto:ryanh...@outlook.com>>; 
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] e911

To piggy back on this, while Cisco doesn’t have emergency notifications built 
in, as the law mentions, and thus they are not required, does anyone know of 
options beyond Singlewire that they are happy with? The installs would monitor 
up to 1000 or so handsets but the folks that would be notified would probably 
be fewer than 50.




Matthew Loraditch

Sr. Network Engineer


p: 443.541.1518



w: www.heliontechnologies.com<http://www.heliontechnologies.com/>

 |

e: mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>


[cid:image001.png@01D3B62D.FF2B55D0]


[Facebook]<https://facebook.com/heliontech>


[Twitter]<https://twitter.com/heliontech>


[LinkedIn]<https://www.linkedin.com/company/helion-technologies>







From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan 
Huff
Sent: Wednesday, March 7, 2018 3:11 PM
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: [cisco-voip] e911

I wonder how cloud-based phone system like Cisco spark will answer this?


https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar
Sent from my iPhone
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911

[NateCCIE]

Um, I thought it did.

 

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200452-Usage-of-Native-Emergency-Call-Routing-F.html

 

 

From: cisco-voip  On Behalf Of Matthew 
Loraditch
Sent: Wednesday, March 7, 2018 1:36 PM
To: Ryan Huff ; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] e911

 

To piggy back on this, while Cisco doesn’t have emergency notifications built 
in, as the law mentions, and thus they are not required, does anyone know of 
options beyond Singlewire that they are happy with? The installs would monitor 
up to 1000 or so handsets but the folks that would be notified would probably 
be fewer than 50.

 

 



 


Matthew Loraditch



Sr. Network Engineer




p:   443.541.1518



w:  <http://www.heliontechnologies.com/> www.heliontechnologies.com

 | 

e:  <mailto:mloradi...@heliontechnologies.com> mloradi...@heliontechnologies.com









 <https://facebook.com/heliontech> 


 <https://twitter.com/heliontech> 


 <https://www.linkedin.com/company/helion-technologies> 

 

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan 
Huff
Sent: Wednesday, March 7, 2018 3:11 PM
To: cisco-voip@puck.nether.net <mailto:cisco-voip@puck.nether.net> 
Subject: [cisco-voip] e911

 

I wonder how cloud-based phone system like Cisco spark will answer this?

 

 

https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar

Sent from my iPhone

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911

[Brian Meade]

CER is still good for 911 notifications.

IPCelerate IPSession is another big player in the emergency notification
space.

On Wed, Mar 7, 2018 at 3:35 PM, Matthew Loraditch <
mloradi...@heliontechnologies.com> wrote:

> To piggy back on this, while Cisco doesn’t have emergency notifications
> built in, as the law mentions, and thus they are not required, does anyone
> know of options beyond Singlewire that they are happy with? The installs
> would monitor up to 1000 or so handsets but the folks that would be
> notified would probably be fewer than 50.
>
>
>
>
>
> Matthew Loraditch
> Sr. Network Engineer
> p: *443.541.1518* <443.541.1518>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>  |
> e: *mloradi...@heliontechnologies.com* 
> [image: Facebook] <https://facebook.com/heliontech>
> [image: Twitter] <https://twitter.com/heliontech>
> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>
>
> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf
> Of *Ryan Huff
> *Sent:* Wednesday, March 7, 2018 3:11 PM
> *To:* cisco-voip@puck.nether.net
> *Subject:* [cisco-voip] e911
>
>
>
> I wonder how cloud-based phone system like Cisco spark will answer this?
>
>
>
>
>
> https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar
>
> Sent from my iPhone
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911

[Matthew Loraditch]

To piggy back on this, while Cisco doesn’t have emergency notifications built 
in, as the law mentions, and thus they are not required, does anyone know of 
options beyond Singlewire that they are happy with? The installs would monitor 
up to 1000 or so handsets but the folks that would be notified would probably 
be fewer than 50.



Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: mloradi...@heliontechnologies.com
From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan 
Huff
Sent: Wednesday, March 7, 2018 3:11 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] e911

I wonder how cloud-based phone system like Cisco spark will answer this?


https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar
Sent from my iPhone
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] e911

[Ryan Huff]

I wonder how cloud-based phone system like Cisco spark will answer this?


https://www.linkedin.com/pulse/karis-law-you-compliant-edgar-salazar

Sent from my iPhone
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911, CER, wireless and soft phones?

[Nick Barnett]

ok, that's interesting for a whole lot of reasons right now. We are looking
at our next upgrade for next year and right now, we are a 100% cisco shop.

On Thu, Jun 1, 2017 at 12:28 AM, Ankur Srivastava via cisco-voip <
cisco-voip@puck.nether.net> wrote:

> In 11.5 Cisco has released a feature that helps you isolate the particular
> user, but this only works for Cisco WLC. I tried testing this with Aruba in
> our environment but cucm is not synching with it. I raised this with Cisco
> to open this feature up to other Third-party vendors. But I guess if more
> people raise the noise they will listen. All they are doing is sharing info
> over SNMP , but its currently programmed to not respond to any other box
> that doesn’t say Cisco
>
>
>
> Regards,
>
> Ankur
>
>
>
> *From: *cisco-voip  on behalf of
> Lelio Fulgenzi 
> *Date: *Wednesday, May 31, 2017 at 4:53 PM
> *To: *Brian Meade 
> *Cc: *voip puck 
> *Subject: *Re: [cisco-voip] e911, CER, wireless and soft phones?
>
>
>
> Can any of these solutions do anything better than tell me what AP I'm on?
>
>
>
> And that includes telling me my location based on the location of the AP.
>
>
>
> I'd hope that there'd be some type of triangulation based on proximity to
> several APs. Or some sort of partnership with the BU that handles
> rfid/beacons.
>
>
>
>
>
>
>
> Sent from my iPhone
>
>
> On May 31, 2017, at 4:54 PM, Brian Meade  wrote:
>
> Yea, but most people are deploying their entire campus wireless as a
> single /16 for better roaming.
>
>
>
> On Wed, May 31, 2017 at 4:46 PM, Ben Amick  wrote:
>
> Doesn't CER have the ability to track by subnet?
>
> Ben Amick
> Telecom Analyst
>
>
> > On May 31, 2017, at 3:59 PM, Nick Barnett 
> wrote:
> >
> > I'm looking into options to properly track softphones with CER. Our CER
> is 100% Intrado right now, but we're looking at ditching hard phones and
> need to figure out tracking of softphones, especially when connected
> wirelessly.
> >
> > What are people using out there?
> >
> > Thanks,
> > Nick
>
> > ___
> > cisco-voip mailing list
> > cisco-voip@puck.nether.net
> > http://cp.mcafee.com/d/k-Kr6h0SyMqen4TbzDSjtPqabbXaoUsy
> qejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS
> 6NJOVICSHIdzrBPtPhPtdRcQsLZvAXKcff9ZuVtdBZDCm4QrIIth5dqWqJSk
> -l3PWApmU6CQjq9K_nhh7ec3HLCzATsSjDdqymoIToHMd9_
> 7wrwCHIcfBisEeROQGmGncRAIrJaBGBPdpb5O5mUm-wamrIlU6A_
> zMddI6zCVEVdCBKQGmGncRAIqnjh1VEVhh0cQg2gQ2M3d41ykvf-
> B3h1I43h1iHIPh0IjH3W4zr1EVdMMln8SHR
>
>
> Confidentiality Note: This message is intended for use only by the
> individual or entity to which it is addressed and may contain information
> that is privileged, confidential, and exempt from disclosure under
> applicable law. If the reader of this message is not the intended recipient
> or the employee or agent responsible for delivering the message to the
> intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited. If
> you have received this communication in error, please contact the sender
> immediately and destroy the material in its entirety, whether electronic or
> hard copy. Thank you
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911, CER, wireless and soft phones?

[Nick Barnett]

Yep, we are wireless on /16, makes roaming a heck of a lot easier, but is
worthless for subnet e911 tracking.  We also have RedSky's cloud service.
I've reached out to them to try and get a demo of their warez.

On Wed, May 31, 2017 at 3:54 PM, Brian Meade  wrote:

> Yea, but most people are deploying their entire campus wireless as a
> single /16 for better roaming.
>
> On Wed, May 31, 2017 at 4:46 PM, Ben Amick  wrote:
>
>> Doesn't CER have the ability to track by subnet?
>>
>> Ben Amick
>> Telecom Analyst
>>
>> > On May 31, 2017, at 3:59 PM, Nick Barnett 
>> wrote:
>> >
>> > I'm looking into options to properly track softphones with CER. Our CER
>> is 100% Intrado right now, but we're looking at ditching hard phones and
>> need to figure out tracking of softphones, especially when connected
>> wirelessly.
>> >
>> > What are people using out there?
>> >
>> > Thanks,
>> > Nick
>> > ___
>> > cisco-voip mailing list
>> > cisco-voip@puck.nether.net
>> > http://cp.mcafee.com/d/k-Kr6h0SyMqen4TbzDSjtPqabbXaoUsyqejqa
>> bbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrB
>> PtPhPtdRcQsLZvAXKcff9ZuVtdBZDCm4QrIIth5dqWqJSk-
>> l3PWApmU6CQjq9K_nhh7ec3HLCzATsSjDdqymoIToHMd9_7wrwCHIcfBisEe
>> ROQGmGncRAIrJaBGBPdpb5O5mUm-wamrIlU6A_zMddI6zCVEVdCBKQGmGn
>> cRAIqnjh1VEVhh0cQg2gQ2M3d41ykvf-B3h1I43h1iHIPh0IjH3W4zr1EVdMMln8SHR
>>
>>
>> Confidentiality Note: This message is intended for use only by the
>> individual or entity to which it is addressed and may contain information
>> that is privileged, confidential, and exempt from disclosure under
>> applicable law. If the reader of this message is not the intended recipient
>> or the employee or agent responsible for delivering the message to the
>> intended recipient, you are hereby notified that any dissemination,
>> distribution or copying of this communication is strictly prohibited. If
>> you have received this communication in error, please contact the sender
>> immediately and destroy the material in its entirety, whether electronic or
>> hard copy. Thank you
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911, CER, wireless and soft phones?

[Ankur Srivastava via cisco-voip]

In 11.5 Cisco has released a feature that helps you isolate the particular 
user, but this only works for Cisco WLC. I tried testing this with Aruba in our 
environment but cucm is not synching with it. I raised this with Cisco to open 
this feature up to other Third-party vendors. But I guess if more people raise 
the noise they will listen. All they are doing is sharing info over SNMP , but 
its currently programmed to not respond to any other box that doesn’t say Cisco

Regards,
Ankur

From: cisco-voip  on behalf of Lelio 
Fulgenzi 
Date: Wednesday, May 31, 2017 at 4:53 PM
To: Brian Meade 
Cc: voip puck 
Subject: Re: [cisco-voip] e911, CER, wireless and soft phones?

Can any of these solutions do anything better than tell me what AP I'm on?

And that includes telling me my location based on the location of the AP.

I'd hope that there'd be some type of triangulation based on proximity to 
several APs. Or some sort of partnership with the BU that handles rfid/beacons.



Sent from my iPhone

On May 31, 2017, at 4:54 PM, Brian Meade 
mailto:bmead...@vt.edu>> wrote:
Yea, but most people are deploying their entire campus wireless as a single /16 
for better roaming.

On Wed, May 31, 2017 at 4:46 PM, Ben Amick 
mailto:bam...@humanarc.com>> wrote:
Doesn't CER have the ability to track by subnet?

Ben Amick
Telecom Analyst

> On May 31, 2017, at 3:59 PM, Nick Barnett 
> mailto:nicksbarn...@gmail.com>> wrote:
>
> I'm looking into options to properly track softphones with CER. Our CER is 
> 100% Intrado right now, but we're looking at ditching hard phones and need to 
> figure out tracking of softphones, especially when connected wirelessly.
>
> What are people using out there?
>
> Thanks,
> Nick
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
> http://cp.mcafee.com/d/k-Kr6h0SyMqen4TbzDSjtPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPtPhPtdRcQsLZvAXKcff9ZuVtdBZDCm4QrIIth5dqWqJSk-l3PWApmU6CQjq9K_nhh7ec3HLCzATsSjDdqymoIToHMd9_7wrwCHIcfBisEeROQGmGncRAIrJaBGBPdpb5O5mUm-wamrIlU6A_zMddI6zCVEVdCBKQGmGncRAIqnjh1VEVhh0cQg2gQ2M3d41ykvf-B3h1I43h1iHIPh0IjH3W4zr1EVdMMln8SHR


Confidentiality Note: This message is intended for use only by the individual 
or entity to which it is addressed and may contain information that is 
privileged, confidential, and exempt from disclosure under applicable law. If 
the reader of this message is not the intended recipient or the employee or 
agent responsible for delivering the message to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited. If you have received this communication 
in error, please contact the sender immediately and destroy the material in its 
entirety, whether electronic or hard copy. Thank you
___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911, CER, wireless and soft phones?

[Tim Kenyon]

Or Conveyant Systems.



Tim Kenyon ENP
President
Conveyant Systems, Inc.

Sent via cell phone. Please excuse any typos or obvious autocorrect changes I 
may miss, lol.


 Original message 
From: Christopher Lamer 
Date: 5/31/17 8:46 PM (GMT-05:00)
To: Brian Meade , Lelio Fulgenzi 
Cc: Cisco VoIP Group 
Subject: Re: [cisco-voip] e911, CER, wireless and soft phones?

A 911 solution just by itself would not do this. You need something like the 
Cisco MSE along with Cisco Prime and a 911 solution like 911 Enable by West

Christopher


On Wed, May 31, 2017 at 6:53 PM Lelio Fulgenzi 
mailto:le...@uoguelph.ca>> wrote:
Can any of these solutions do anything better than tell me what AP I'm on?

And that includes telling me my location based on the location of the AP.

I'd hope that there'd be some type of triangulation based on proximity to 
several APs. Or some sort of partnership with the BU that handles rfid/beacons.



Sent from my iPhone

On May 31, 2017, at 4:54 PM, Brian Meade 
mailto:bmead...@vt.edu>> wrote:

Yea, but most people are deploying their entire campus wireless as a single /16 
for better roaming.

On Wed, May 31, 2017 at 4:46 PM, Ben Amick 
mailto:bam...@humanarc.com>> wrote:
Doesn't CER have the ability to track by subnet?

Ben Amick
Telecom Analyst

> On May 31, 2017, at 3:59 PM, Nick Barnett 
> mailto:nicksbarn...@gmail.com>> wrote:
>
> I'm looking into options to properly track softphones with CER. Our CER is 
> 100% Intrado right now, but we're looking at ditching hard phones and need to 
> figure out tracking of softphones, especially when connected wirelessly.
>
> What are people using out there?
>
> Thanks,
> Nick
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
> http://cp.mcafee.com/d/k-Kr6h0SyMqen4TbzDSjtPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPtPhPtdRcQsLZvAXKcff9ZuVtdBZDCm4QrIIth5dqWqJSk-l3PWApmU6CQjq9K_nhh7ec3HLCzATsSjDdqymoIToHMd9_7wrwCHIcfBisEeROQGmGncRAIrJaBGBPdpb5O5mUm-wamrIlU6A_zMddI6zCVEVdCBKQGmGncRAIqnjh1VEVhh0cQg2gQ2M3d41ykvf-B3h1I43h1iHIPh0IjH3W4zr1EVdMMln8SHR


Confidentiality Note: This message is intended for use only by the individual 
or entity to which it is addressed and may contain information that is 
privileged, confidential, and exempt from disclosure under applicable law. If 
the reader of this message is not the intended recipient or the employee or 
agent responsible for delivering the message to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited. If you have received this communication 
in error, please contact the sender immediately and destroy the material in its 
entirety, whether electronic or hard copy. Thank you
___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911, CER, wireless and soft phones?

[Christopher Lamer]

A 911 solution just by itself would not do this. You need something like
the Cisco MSE along with Cisco Prime and a 911 solution like 911 Enable by
West

Christopher


On Wed, May 31, 2017 at 6:53 PM Lelio Fulgenzi  wrote:

> Can any of these solutions do anything better than tell me what AP I'm on?
>
> And that includes telling me my location based on the location of the AP.
>
> I'd hope that there'd be some type of triangulation based on proximity to
> several APs. Or some sort of partnership with the BU that handles
> rfid/beacons.
>
>
>
> Sent from my iPhone
>
> On May 31, 2017, at 4:54 PM, Brian Meade  wrote:
>
> Yea, but most people are deploying their entire campus wireless as a
> single /16 for better roaming.
>
> On Wed, May 31, 2017 at 4:46 PM, Ben Amick  wrote:
>
>> Doesn't CER have the ability to track by subnet?
>>
>> Ben Amick
>> Telecom Analyst
>>
>> > On May 31, 2017, at 3:59 PM, Nick Barnett 
>> wrote:
>> >
>> > I'm looking into options to properly track softphones with CER. Our CER
>> is 100% Intrado right now, but we're looking at ditching hard phones and
>> need to figure out tracking of softphones, especially when connected
>> wirelessly.
>> >
>> > What are people using out there?
>> >
>> > Thanks,
>> > Nick
>> > ___
>> > cisco-voip mailing list
>> > cisco-voip@puck.nether.net
>> >
>> http://cp.mcafee.com/d/k-Kr6h0SyMqen4TbzDSjtPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPtPhPtdRcQsLZvAXKcff9ZuVtdBZDCm4QrIIth5dqWqJSk-l3PWApmU6CQjq9K_nhh7ec3HLCzATsSjDdqymoIToHMd9_7wrwCHIcfBisEeROQGmGncRAIrJaBGBPdpb5O5mUm-wamrIlU6A_zMddI6zCVEVdCBKQGmGncRAIqnjh1VEVhh0cQg2gQ2M3d41ykvf-B3h1I43h1iHIPh0IjH3W4zr1EVdMMln8SHR
>>
>>
>> Confidentiality Note: This message is intended for use only by the
>> individual or entity to which it is addressed and may contain information
>> that is privileged, confidential, and exempt from disclosure under
>> applicable law. If the reader of this message is not the intended recipient
>> or the employee or agent responsible for delivering the message to the
>> intended recipient, you are hereby notified that any dissemination,
>> distribution or copying of this communication is strictly prohibited. If
>> you have received this communication in error, please contact the sender
>> immediately and destroy the material in its entirety, whether electronic or
>> hard copy. Thank you
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911, CER, wireless and soft phones?

[Lelio Fulgenzi]

Can any of these solutions do anything better than tell me what AP I'm on?

And that includes telling me my location based on the location of the AP.

I'd hope that there'd be some type of triangulation based on proximity to 
several APs. Or some sort of partnership with the BU that handles rfid/beacons.



Sent from my iPhone

On May 31, 2017, at 4:54 PM, Brian Meade 
mailto:bmead...@vt.edu>> wrote:

Yea, but most people are deploying their entire campus wireless as a single /16 
for better roaming.

On Wed, May 31, 2017 at 4:46 PM, Ben Amick 
mailto:bam...@humanarc.com>> wrote:
Doesn't CER have the ability to track by subnet?

Ben Amick
Telecom Analyst

> On May 31, 2017, at 3:59 PM, Nick Barnett 
> mailto:nicksbarn...@gmail.com>> wrote:
>
> I'm looking into options to properly track softphones with CER. Our CER is 
> 100% Intrado right now, but we're looking at ditching hard phones and need to 
> figure out tracking of softphones, especially when connected wirelessly.
>
> What are people using out there?
>
> Thanks,
> Nick
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> http://cp.mcafee.com/d/k-Kr6h0SyMqen4TbzDSjtPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPtPhPtdRcQsLZvAXKcff9ZuVtdBZDCm4QrIIth5dqWqJSk-l3PWApmU6CQjq9K_nhh7ec3HLCzATsSjDdqymoIToHMd9_7wrwCHIcfBisEeROQGmGncRAIrJaBGBPdpb5O5mUm-wamrIlU6A_zMddI6zCVEVdCBKQGmGncRAIqnjh1VEVhh0cQg2gQ2M3d41ykvf-B3h1I43h1iHIPh0IjH3W4zr1EVdMMln8SHR


Confidentiality Note: This message is intended for use only by the individual 
or entity to which it is addressed and may contain information that is 
privileged, confidential, and exempt from disclosure under applicable law. If 
the reader of this message is not the intended recipient or the employee or 
agent responsible for delivering the message to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited. If you have received this communication 
in error, please contact the sender immediately and destroy the material in its 
entirety, whether electronic or hard copy. Thank you
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911, CER, wireless and soft phones?

[Brian Meade]

Yea, but most people are deploying their entire campus wireless as a single
/16 for better roaming.

On Wed, May 31, 2017 at 4:46 PM, Ben Amick  wrote:

> Doesn't CER have the ability to track by subnet?
>
> Ben Amick
> Telecom Analyst
>
> > On May 31, 2017, at 3:59 PM, Nick Barnett 
> wrote:
> >
> > I'm looking into options to properly track softphones with CER. Our CER
> is 100% Intrado right now, but we're looking at ditching hard phones and
> need to figure out tracking of softphones, especially when connected
> wirelessly.
> >
> > What are people using out there?
> >
> > Thanks,
> > Nick
> > ___
> > cisco-voip mailing list
> > cisco-voip@puck.nether.net
> > http://cp.mcafee.com/d/k-Kr6h0SyMqen4TbzDSjtPqabbXaoUsy
> qejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS
> 6NJOVICSHIdzrBPtPhPtdRcQsLZvAXKcff9ZuVtdBZDCm4QrIIth5dqWqJSk
> -l3PWApmU6CQjq9K_nhh7ec3HLCzATsSjDdqymoIToHMd9_
> 7wrwCHIcfBisEeROQGmGncRAIrJaBGBPdpb5O5mUm-wamrIlU6A_
> zMddI6zCVEVdCBKQGmGncRAIqnjh1VEVhh0cQg2gQ2M3d41ykvf-
> B3h1I43h1iHIPh0IjH3W4zr1EVdMMln8SHR
>
>
> Confidentiality Note: This message is intended for use only by the
> individual or entity to which it is addressed and may contain information
> that is privileged, confidential, and exempt from disclosure under
> applicable law. If the reader of this message is not the intended recipient
> or the employee or agent responsible for delivering the message to the
> intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited. If
> you have received this communication in error, please contact the sender
> immediately and destroy the material in its entirety, whether electronic or
> hard copy. Thank you
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911, CER, wireless and soft phones?

[Ben Amick]

Doesn't CER have the ability to track by subnet? 

Ben Amick
Telecom Analyst

> On May 31, 2017, at 3:59 PM, Nick Barnett  wrote:
> 
> I'm looking into options to properly track softphones with CER. Our CER is 
> 100% Intrado right now, but we're looking at ditching hard phones and need to 
> figure out tracking of softphones, especially when connected wirelessly.
> 
> What are people using out there? 
> 
> Thanks,
> Nick
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> http://cp.mcafee.com/d/k-Kr6h0SyMqen4TbzDSjtPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPtPhPtdRcQsLZvAXKcff9ZuVtdBZDCm4QrIIth5dqWqJSk-l3PWApmU6CQjq9K_nhh7ec3HLCzATsSjDdqymoIToHMd9_7wrwCHIcfBisEeROQGmGncRAIrJaBGBPdpb5O5mUm-wamrIlU6A_zMddI6zCVEVdCBKQGmGncRAIqnjh1VEVhh0cQg2gQ2M3d41ykvf-B3h1I43h1iHIPh0IjH3W4zr1EVdMMln8SHR


Confidentiality Note: This message is intended for use only by the individual 
or entity to which it is addressed and may contain information that is 
privileged, confidential, and exempt from disclosure under applicable law. If 
the reader of this message is not the intended recipient or the employee or 
agent responsible for delivering the message to the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited. If you have received this communication 
in error, please contact the sender immediately and destroy the material in its 
entirety, whether electronic or hard copy. Thank you
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] e911, CER, wireless and soft phones?

[Brian Meade]

Redsky is the big player in this field.

On Wed, May 31, 2017 at 3:58 PM, Nick Barnett 
wrote:

> I'm looking into options to properly track softphones with CER. Our CER is
> 100% Intrado right now, but we're looking at ditching hard phones and need
> to figure out tracking of softphones, especially when connected wirelessly.
>
> What are people using out there?
>
> Thanks,
> Nick
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] e911, CER, wireless and soft phones?

[Nick Barnett]

I'm looking into options to properly track softphones with CER. Our CER is
100% Intrado right now, but we're looking at ditching hard phones and need
to figure out tracking of softphones, especially when connected wirelessly.

What are people using out there?

Thanks,
Nick
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip