VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
January 2013
- 57 participants
- 176 messages
911 address policy for company phones at home
by ian@blenke.com
On Fri, Jan 18, 2013 at 5:13 PM, Nathan Anderson <nathana at fsr.com> wrote:
> This is all predicated on the notion that the only way that most E911 services work is by binding an address to a telephone number in a database on their end. Are there any E911 providers that you can transmit an address to in the call signalling, in real-time during call set-up? That would solve the problem entirely.
MSAG validation and ALI publishing is mostly how things are done
today. Route your E911 through a selective router and have them find
the correct PSAP.
Intrado has (or had) GRISIP for passing GIS information as a
proprietary SIP extension header. I'm not sure if this worked outside
of their ECRC, however.
How would such GIS information get relayed to the > 9000 PSAPs all
over the US? Many of them are still rural TDM.
There has been talk about relaying GIS information in NG911, but I
haven't stumbled on the standard whitepaper on that much less an
implementation.
As someone working in the Video Relay Service industry for the deaf
and hard of hearing, there is work now in the SIP Forum VRS working
group attempting to deal with passing video, text, and audio from our
customer mobile and video phones. There is only beginning debate in
the FCC working group regarding implementation and staffing of NG911
video interpreters.
The sheer number of ancient TDM based PSAPs, funding, and regulation,
is really the core problem there.
--
- Ian Blenke <ian at blenke.com> http://ian.blenke.com
Jan. 18, 2013
CALEA for the small fry operator
by j@2600hz.com
From: http://transition.fcc.gov/pshs/services/calea/
CALEA Compliance for Packet Equipment, And Equipment for Facilities-Based Broadband Internet Access Providers and Providers of Interconnected VoIP
All facilities-based broadband Internet access providers and providers of interconnected VoIP service must ensure that their services comply with CALEA upon launch. In the May 12, 2006 Commission order, the Commission found that section 107(c)(1) may not be used by entities seeking extensions for equipment, facilities, and services deployed on or after October 25, 1998 (the effective date of the CALEA section 103 and 105 requirements).
I believe you aren't subject to CALEA unless you're a facilities-based CLEC/ILEC. I am not a lawyer, this is not legal advice, but I don't think this applies to you. (Someone please correct me if I'm mistaken).
Joshua Goldbard
VP of Marketing, 2600hz
116 Natoma Street, Floor 2
San Francisco, CA, 94104
415.886.7923 | j at 2600hz.com<mailto:j at 2600hz.com>
[cid:A04A0B25-B1C5-459F-BDCE-0E90D89EA979 at 2600hz.com]
On Jan 18, 2013, at 2:16 PM, Nathan Anderson <nathana at fsr.com<mailto:nathana at fsr.com>>
wrote:
Nope.
-- Nathan
-----Original Message-----
From: Joshua Goldbard [mailto:j at 2600hz.com<http://2600hz.com>]
Sent: Friday, January 18, 2013 2:03 PM
To: Nathan Anderson
Cc: voiceops at voiceops.org<mailto:voiceops at voiceops.org>
Subject: Re: [VoiceOps] CALEA for the small fry operator
Are you a CLEC?
Cheers,
Joshua
Joshua Goldbard
VP of Marketing, 2600hz
116 Natoma Street, Floor 2
San Francisco, CA, 94104
415.886.7923 | j at 2600hz.com<mailto:j at 2600hz.com>
On Jan 18, 2013, at 1:54 PM, Nathan Anderson <nathana at fsr.com<mailto:nathana at fsr.com>>
wrote:
We are a small-ish, regional broadband ISP in the U.S. (inland Washington and Idaho) that has also rolled out an interconnected VoIP product over the past year. I'm trying to wrestle through and understand what our responsibilities and obligations are with regards to CALEA compliance at both the legal and technical levels.
Confession time: we did not purchase a commercial softswitch product. We built our own solution on top of Asterisk. (I can already hear the groans and feel the tangible disapproval.) We went this route for cost reasons, yes, but more importantly we did it because with a custom-engineered solution, we were able to seamlessly integrate our new voice offering with our other existing products when it comes to both provisioning and billing, and this (I believe) leads to a better and more uniform experience for our customers. For better or worse, we are an ISP first and foremost, and an ITSP second, and provisioning for the new product needed to conform to existing practices rather than be an island unto itself, as so many "turn-key" offerings are.
But I recognize that going down this path has brought with it a distinct disadvantage when it comes to solving the CALEA complaince problem. Notably, there are no known CALEA solutions for Asterisk of any stripe that I have been able to find, and any discussion about Asterisk and CALEA seems to have peaked around the time (2006-2007) that the feds announced VoIP providers were going to have to bring themselves into compliance, and then quickly faded after that.
Sure, I could easily come up with something that would allow for live or recorded call interception and/or delivery of CDR/CPNI to law enforcement using existing tools already available to me. What is unclear to me, though, is whether there is any particular format or delivery mechanism for this data that the law stipulates we follow. I know that there is an ANSI standard, T1.678v2 (and the subsequent supplements), but of course I have no access to that (200+ page) document without paying the publisher hundreds of dollars for a copy. And even if we got our hands on a copy, it sounds like it would be prohibitively difficult to implement by ourselves.
Does the law actually stipulate that T1.678 be followed, and are you not in compliance with CALEA regulations unless you specifically use a solution that is T1.678-compatible? Or is the T1.678 standard simply recommended and preferred by LEAs? I have seen discussion threads where other people have talked about their "creative" solutions to CALEA compliance, which include things such as proxying the RTP stream and having a bank of E&M channels at the ready to mirror the audio to (http://fonality.com/trixbox/forums/trixbox-forums/open-discussion/what-i-ne…) Do these people actually know if their solution gets a passing grade, or are they taking a gamble?
Thanks,
--
Nathan Anderson
First Step Internet, LLC
nathana at fsr.com<mailto:nathana at fsr.com>
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 18, 2013
911 address policy for company phones at home
by j@2600hz.com
Great questions :).
So since we can override on a per device basis, you'll notice that I didn't put an actual address, I put ($Address). This is an important distinction.
Suppose we could sense a users physical position (IE via GPS on their SIP-enabled smartphone). We could then insert the lat-long and approximate address instead of transmitting the HQ address. In practice, most users will set their office devices to default to the HQ Emergency info, but on their home devices, they can set a different address (typically tied to their direct DID instead of the main number).
I don't believe you can send an address in real-time to a 911 service (if I'm wrong I'd be thrilled to learn of one). It's always a db lookup, which sort of negates the idea I proposed in my previous paragraph. In short, 911 is complex, antiquated and difficult. Even though we could EASILY provide live lat-long and address information to e911 the infrastructure isn't setup to support it and I think we're in agreement on this point.
BTW, It's also not kludgey if I know the difference between a direct dial and a main number (which I'd wager most people do since it's printed on most business cards).
Cheers,
Joshua
Joshua Goldbard
VP of Marketing, 2600hz
116 Natoma Street, Floor 2
San Francisco, CA, 94104
415.886.7923 | j at 2600hz.com<mailto:j at 2600hz.com>
[cid:A04A0B25-B1C5-459F-BDCE-0E90D89EA979 at 2600hz.com]
On Jan 18, 2013, at 2:13 PM, Nathan Anderson <nathana at fsr.com<mailto:nathana at fsr.com>>
wrote:
Kinda/sorta. So you are doing (in essence) what I proposed in my last paragraph: transmitting a different CLID to the PSAP than you transmit to all other called parties for that station.
The thing is that this doesn't seem to solve the original poster's problem. In your example, the station in question has a DID: 415-886-7923, and it (presumably) uses that DID for all external outbound calls, but uses the main switchboard number as the CLID when dialing emergency services (911). That works great if all of the stations are at the same address as what is provisioned in E911 for the switchboard number. If that station isn't at that address, I take it your solution is to "override" this so that the emergency CLID matches the external CLID, and then to provision that DID in E911 with the right address.
The way I understood it, though, the original question dealt with a scenario like this:
My internal Caller ID is: 330 (THE MARKETING GUY)
My external Caller ID is: 415.886.7900 (no DID! You call the switchboard and ask for 330.)
My emergency Caller ID is: 415.886.7900
...so the company in question -- for whatever reason, I presume they have a good one and it's not my position to ask or judge -- does not hand out DIDs to stations and wants all outbound calls to look like they are coming from HQ regardless, and station 330 is physically at MARKETING GUY's residence (since he telecommutes), not company HQ.
So, the question is, how do you transmit the correct address to the dispatcher for MARKETING GUY's residence in this scenario, instead of company HQ's address? My proposed solution was this:
My internal Caller ID is: 330 (THE MARKETING GUY)
My external Caller ID is: 415.886.7900 (no DID! You call the switchboard and ask for 330.)
My emergency Caller ID is: 415.886.7923 ("throwaway" number)
...then you provision the dude's residential address on the 7923 number. But MARKETING GUY has no clue that this number exists, and in fact dialing that number will not lead you to his station, thus the "throwaway" label. (In addition to confusing MARKETING GUY when PSAP asks him if he is calling from 7923, if the call drops and PSAP tries to get hold of him again, that will fail. Another reason why this kludgey solution is not great.)
This is all predicated on the notion that the only way that most E911 services work is by binding an address to a telephone number in a database on their end. Are there any E911 providers that you can transmit an address to in the call signalling, in real-time during call set-up? That would solve the problem entirely.
--
Nathan Anderson
First Step Internet, LLC
nathana at fsr.com<mailto:nathana at fsr.com>
-----Original Message-----
From: Joshua Goldbard [mailto:j at 2600hz.com]
Sent: Friday, January 18, 2013 1:47 PM
To: Nathan Anderson
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] 911 address policy for company phones at home
Nathan,
CLID as it applies to the PSTN is inherently outbound. That being said, a number of switches (PBXs) have the capability of modifying the caller ID of a user. You see this with internal Caller IDs and external caller ID (extension versus CNAM). Some providers (2600hz included) have introduced a third caller ID classification: emergency.
Let me give you a practical example.
My Internal Caller ID is: 7923 (THE MARKETING GUY)
My external Caller ID is: 415.886.7923 2600hz
My emergency Caller ID is: 415.886.7900 2600hz ($Address)
The purpose here is to take our block of 100 DIDs and only support emergency services in a single uniform fashion. We can override this on a user by user or per-device basis, but the point is to simplify emergency calling.
Does that help clarify what we're doing?
Cheers,
Joshua
P.S. I previously sent this email only to Nathan. Adding voiceops onto the chain just in case there's interest.
Joshua Goldbard
VP of Marketing, 2600hz
116 Natoma Street, Floor 2
San Francisco, CA, 94104
415.886.7923 | j at 2600hz.com
On Jan 18, 2013, at 1:04 PM, Nathan Anderson <nathana at fsr.com>
wrote:
I'm confused, and I apologize to those who have already been involved in this discussion thread for a while since I am just now jumping in. CLID is inherently outbound, so I am not sure what you mean by "inbound vs. outbound caller IDs". Perhaps by "inbound CLID" you mean DID, or DNIS?
I'm also not sure how you propose to bind E911 details to a device instead of a telephone number. The few E911 services I've looked at all only give you the option to provision E911 information via TN. So if you propose a set-up such as what is being discussed here, where each company phone only has an internal extension # and no DID, and CLID is uniformly set to a single number for all outbound calls from any phone whether it is located in the office building or at an employee's residence, then there can only be a single E911 address for all of those phones. That seems inescapable. Are you saying that there are E911 companies that can provision differently, and not use the CLID as the "key" to looking up an address? What do they use/how do they work, and can you name some names?
The only other kludgey workaround I can think of that might pass muster would be to assign unique "throwaway" TNs to each individual extension that you would use as the CLID for outbound from that extension *only* when 911 is dialed, and continue to use the global office TN as CLID across all extensions for all other outbound calls. It's not a perfect solution, since if the individuals using those phones have no clue about those numbers, they might get confused when asked to verify their own telephone number by the PSAP and the dispatcher reads some number back to them that isn't their main office number. At that point, you might as well let the customer know that these numbers exist and give them the option of using them as DIDs for the extensions/devices they've been assigned to.
--
Nathan Anderson
First Step Internet, LLC
nathana at fsr.com
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Carlos Alvarez
Sent: Friday, January 18, 2013 11:49 AM
To: Joshua Goldbard
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] 911 address policy for company phones at home
On Fri, Jan 18, 2013 at 12:46 PM, Joshua Goldbard <j at 2600hz.com> wrote:
Yeah, but you're talking about inbound.
In many corporate environments, the outbound caller ID is uniform for a location (and even if it's not, most systems support uniform caller ID for emergencies). E911 is an outbound service and the inbound and outbound caller IDs can certainly be different.
Does that help clarify my viewpoint?
Ah, yes. We very rarely get anyone who wants to do that, so it didn't cross my mind.
We do have special 911 CLID/DID settings and special processing for those calls. However we bind them to a device, since the device is what has location, in most of our installations.
--
Carlos Alvarez
TelEvolve
602-889-3003
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 18, 2013
CALEA for the small fry operator
by nathana@fsr.com
Nope.
-- Nathan
-----Original Message-----
From: Joshua Goldbard [mailto:j at 2600hz.com]
Sent: Friday, January 18, 2013 2:03 PM
To: Nathan Anderson
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] CALEA for the small fry operator
Are you a CLEC?
Cheers,
Joshua
Joshua Goldbard
VP of Marketing, 2600hz
116 Natoma Street, Floor 2
San Francisco, CA, 94104
415.886.7923 | j at 2600hz.com
On Jan 18, 2013, at 1:54 PM, Nathan Anderson <nathana at fsr.com>
wrote:
We are a small-ish, regional broadband ISP in the U.S. (inland Washington and Idaho) that has also rolled out an interconnected VoIP product over the past year. I'm trying to wrestle through and understand what our responsibilities and obligations are with regards to CALEA compliance at both the legal and technical levels.
Confession time: we did not purchase a commercial softswitch product. We built our own solution on top of Asterisk. (I can already hear the groans and feel the tangible disapproval.) We went this route for cost reasons, yes, but more importantly we did it because with a custom-engineered solution, we were able to seamlessly integrate our new voice offering with our other existing products when it comes to both provisioning and billing, and this (I believe) leads to a better and more uniform experience for our customers. For better or worse, we are an ISP first and foremost, and an ITSP second, and provisioning for the new product needed to conform to existing practices rather than be an island unto itself, as so many "turn-key" offerings are.
But I recognize that going down this path has brought with it a distinct disadvantage when it comes to solving the CALEA complaince problem. Notably, there are no known CALEA solutions for Asterisk of any stripe that I have been able to find, and any discussion about Asterisk and CALEA seems to have peaked around the time (2006-2007) that the feds announced VoIP providers were going to have to bring themselves into compliance, and then quickly faded after that.
Sure, I could easily come up with something that would allow for live or recorded call interception and/or delivery of CDR/CPNI to law enforcement using existing tools already available to me. What is unclear to me, though, is whether there is any particular format or delivery mechanism for this data that the law stipulates we follow. I know that there is an ANSI standard, T1.678v2 (and the subsequent supplements), but of course I have no access to that (200+ page) document without paying the publisher hundreds of dollars for a copy. And even if we got our hands on a copy, it sounds like it would be prohibitively difficult to implement by ourselves.
Does the law actually stipulate that T1.678 be followed, and are you not in compliance with CALEA regulations unless you specifically use a solution that is T1.678-compatible? Or is the T1.678 standard simply recommended and preferred by LEAs? I have seen discussion threads where other people have talked about their "creative" solutions to CALEA compliance, which include things such as proxying the RTP stream and having a bank of E&M channels at the ready to mirror the audio to (http://fonality.com/trixbox/forums/trixbox-forums/open-discussion/what-i-ne…) Do these people actually know if their solution gets a passing grade, or are they taking a gamble?
Thanks,
--
Nathan Anderson
First Step Internet, LLC
nathana at fsr.com
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 18, 2013
911 address policy for company phones at home
by nathana@fsr.com
Kinda/sorta. So you are doing (in essence) what I proposed in my last paragraph: transmitting a different CLID to the PSAP than you transmit to all other called parties for that station.
The thing is that this doesn't seem to solve the original poster's problem. In your example, the station in question has a DID: 415-886-7923, and it (presumably) uses that DID for all external outbound calls, but uses the main switchboard number as the CLID when dialing emergency services (911). That works great if all of the stations are at the same address as what is provisioned in E911 for the switchboard number. If that station isn't at that address, I take it your solution is to "override" this so that the emergency CLID matches the external CLID, and then to provision that DID in E911 with the right address.
The way I understood it, though, the original question dealt with a scenario like this:
My internal Caller ID is: 330 (THE MARKETING GUY)
My external Caller ID is: 415.886.7900 (no DID! You call the switchboard and ask for 330.)
My emergency Caller ID is: 415.886.7900
...so the company in question -- for whatever reason, I presume they have a good one and it's not my position to ask or judge -- does not hand out DIDs to stations and wants all outbound calls to look like they are coming from HQ regardless, and station 330 is physically at MARKETING GUY's residence (since he telecommutes), not company HQ.
So, the question is, how do you transmit the correct address to the dispatcher for MARKETING GUY's residence in this scenario, instead of company HQ's address? My proposed solution was this:
My internal Caller ID is: 330 (THE MARKETING GUY)
My external Caller ID is: 415.886.7900 (no DID! You call the switchboard and ask for 330.)
My emergency Caller ID is: 415.886.7923 ("throwaway" number)
...then you provision the dude's residential address on the 7923 number. But MARKETING GUY has no clue that this number exists, and in fact dialing that number will not lead you to his station, thus the "throwaway" label. (In addition to confusing MARKETING GUY when PSAP asks him if he is calling from 7923, if the call drops and PSAP tries to get hold of him again, that will fail. Another reason why this kludgey solution is not great.)
This is all predicated on the notion that the only way that most E911 services work is by binding an address to a telephone number in a database on their end. Are there any E911 providers that you can transmit an address to in the call signalling, in real-time during call set-up? That would solve the problem entirely.
--
Nathan Anderson
First Step Internet, LLC
nathana at fsr.com
-----Original Message-----
From: Joshua Goldbard [mailto:j at 2600hz.com]
Sent: Friday, January 18, 2013 1:47 PM
To: Nathan Anderson
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] 911 address policy for company phones at home
Nathan,
CLID as it applies to the PSTN is inherently outbound. That being said, a number of switches (PBXs) have the capability of modifying the caller ID of a user. You see this with internal Caller IDs and external caller ID (extension versus CNAM). Some providers (2600hz included) have introduced a third caller ID classification: emergency.
Let me give you a practical example.
My Internal Caller ID is: 7923 (THE MARKETING GUY)
My external Caller ID is: 415.886.7923 2600hz
My emergency Caller ID is: 415.886.7900 2600hz ($Address)
The purpose here is to take our block of 100 DIDs and only support emergency services in a single uniform fashion. We can override this on a user by user or per-device basis, but the point is to simplify emergency calling.
Does that help clarify what we're doing?
Cheers,
Joshua
P.S. I previously sent this email only to Nathan. Adding voiceops onto the chain just in case there's interest.
Joshua Goldbard
VP of Marketing, 2600hz
116 Natoma Street, Floor 2
San Francisco, CA, 94104
415.886.7923 | j at 2600hz.com
On Jan 18, 2013, at 1:04 PM, Nathan Anderson <nathana at fsr.com>
wrote:
I'm confused, and I apologize to those who have already been involved in this discussion thread for a while since I am just now jumping in. CLID is inherently outbound, so I am not sure what you mean by "inbound vs. outbound caller IDs". Perhaps by "inbound CLID" you mean DID, or DNIS?
I'm also not sure how you propose to bind E911 details to a device instead of a telephone number. The few E911 services I've looked at all only give you the option to provision E911 information via TN. So if you propose a set-up such as what is being discussed here, where each company phone only has an internal extension # and no DID, and CLID is uniformly set to a single number for all outbound calls from any phone whether it is located in the office building or at an employee's residence, then there can only be a single E911 address for all of those phones. That seems inescapable. Are you saying that there are E911 companies that can provision differently, and not use the CLID as the "key" to looking up an address? What do they use/how do they work, and can you name some names?
The only other kludgey workaround I can think of that might pass muster would be to assign unique "throwaway" TNs to each individual extension that you would use as the CLID for outbound from that extension *only* when 911 is dialed, and continue to use the global office TN as CLID across all extensions for all other outbound calls. It's not a perfect solution, since if the individuals using those phones have no clue about those numbers, they might get confused when asked to verify their own telephone number by the PSAP and the dispatcher reads some number back to them that isn't their main office number. At that point, you might as well let the customer know that these numbers exist and give them the option of using them as DIDs for the extensions/devices they've been assigned to.
--
Nathan Anderson
First Step Internet, LLC
nathana at fsr.com
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Carlos Alvarez
Sent: Friday, January 18, 2013 11:49 AM
To: Joshua Goldbard
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] 911 address policy for company phones at home
On Fri, Jan 18, 2013 at 12:46 PM, Joshua Goldbard <j at 2600hz.com> wrote:
Yeah, but you're talking about inbound.
In many corporate environments, the outbound caller ID is uniform for a location (and even if it's not, most systems support uniform caller ID for emergencies). E911 is an outbound service and the inbound and outbound caller IDs can certainly be different.
Does that help clarify my viewpoint?
Ah, yes. We very rarely get anyone who wants to do that, so it didn't cross my mind.
We do have special 911 CLID/DID settings and special processing for those calls. However we bind them to a device, since the device is what has location, in most of our installations.
--
Carlos Alvarez
TelEvolve
602-889-3003
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 18, 2013
911 address policy for company phones at home
by jra@baylink.com
Before I get into my reply, I will point out that the OP is inquiring
about this stuff specifically as it regards *extensions on a PBX which
his company hosts as a vendor to/agent of the end user whose employees'
phones are in question here. I think that materially affects the answers,
but IANAL.
Anyway...
----- Original Message -----
> From: "Nathan Anderson" <nathana at fsr.com>
> I'm also not sure how you propose to bind E911 details to a device
> instead of a telephone number. The few E911 services I've looked at
> all only give you the option to provision E911 information via TN. So
> if you propose a set-up such as what is being discussed here, where
> each company phone only has an internal extension # and no DID, and
> CLID is uniformly set to a single number for all outbound calls from
> any phone whether it is located in the office building or at an
> employee's residence, then there can only be a single E911 address for
> all of those phones.
And indeed, there used to be such an exemption for office PBX type
installations; I do not remember whether it's expired, but I think
so. There was quite a bit of third party activity in the "patching
around your PBX to send remote extension building locations to the
PSAP" space at the time...
> The only other kludgey workaround I can think of that might pass
> muster would be to assign unique "throwaway" TNs to each individual
> extension that you would use as the CLID for outbound from that
> extension *only* when 911 is dialed, and continue to use the global
> office TN as CLID across all extensions for all other outbound calls.
> It's not a perfect solution, since if the individuals using those
> phones have no clue about those numbers, they might get confused when
> asked to verify their own telephone number by the PSAP and the
> dispatcher reads some number back to them that isn't their main office
> number. At that point, you might as well let the customer know that
> these numbers exist and give them the option of using them as DIDs for
> the extensions/devices they've been assigned to.
The "Emergency CNID", yes; FreePBX has this, and can be taught what are
emergency calls; when it recognizes one, it sends a different CNID out on
the "trunk".
I believe that PSAPs have a protocol for dealing with this sort of
situation, where a note can be put in the LIDB saying that this ANI is
at a physical location and the phone may be labeled with a different
number, but I am not a PSAP operator, so I might be wrong on this.
Cheers,
-- jra
--
Jay R. Ashworth Baylink jra at baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA #natog +1 727 647 1274
Jan. 18, 2013
CALEA for the small fry operator
by j@2600hz.com
Are you a CLEC?
Cheers,
Joshua
Joshua Goldbard
VP of Marketing, 2600hz
116 Natoma Street, Floor 2
San Francisco, CA, 94104
415.886.7923 | j at 2600hz.com<mailto:j at 2600hz.com>
[cid:A04A0B25-B1C5-459F-BDCE-0E90D89EA979 at 2600hz.com]
On Jan 18, 2013, at 1:54 PM, Nathan Anderson <nathana at fsr.com<mailto:nathana at fsr.com>>
wrote:
We are a small-ish, regional broadband ISP in the U.S. (inland Washington and Idaho) that has also rolled out an interconnected VoIP product over the past year. I'm trying to wrestle through and understand what our responsibilities and obligations are with regards to CALEA compliance at both the legal and technical levels.
Confession time: we did not purchase a commercial softswitch product. We built our own solution on top of Asterisk. (I can already hear the groans and feel the tangible disapproval.) We went this route for cost reasons, yes, but more importantly we did it because with a custom-engineered solution, we were able to seamlessly integrate our new voice offering with our other existing products when it comes to both provisioning and billing, and this (I believe) leads to a better and more uniform experience for our customers. For better or worse, we are an ISP first and foremost, and an ITSP second, and provisioning for the new product needed to conform to existing practices rather than be an island unto itself, as so many "turn-key" offerings are.
But I recognize that going down this path has brought with it a distinct disadvantage when it comes to solving the CALEA complaince problem. Notably, there are no known CALEA solutions for Asterisk of any stripe that I have been able to find, and any discussion about Asterisk and CALEA seems to have peaked around the time (2006-2007) that the feds announced VoIP providers were going to have to bring themselves into compliance, and then quickly faded after that.
Sure, I could easily come up with something that would allow for live or recorded call interception and/or delivery of CDR/CPNI to law enforcement using existing tools already available to me. What is unclear to me, though, is whether there is any particular format or delivery mechanism for this data that the law stipulates we follow. I know that there is an ANSI standard, T1.678v2 (and the subsequent supplements), but of course I have no access to that (200+ page) document without paying the publisher hundreds of dollars for a copy. And even if we got our hands on a copy, it sounds like it would be prohibitively difficult to implement by ourselves.
Does the law actually stipulate that T1.678 be followed, and are you not in compliance with CALEA regulations unless you specifically use a solution that is T1.678-compatible? Or is the T1.678 standard simply recommended and preferred by LEAs? I have seen discussion threads where other people have talked about their "creative" solutions to CALEA compliance, which include things such as proxying the RTP stream and having a bank of E&M channels at the ready to mirror the audio to (http://fonality.com/trixbox/forums/trixbox-forums/open-discussion/what-i-ne…) Do these people actually know if their solution gets a passing grade, or are they taking a gamble?
Thanks,
--
Nathan Anderson
First Step Internet, LLC
nathana at fsr.com<mailto:nathana at fsr.com>
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 18, 2013
911 address policy for company phones at home
by mike@astrocompanies.com
We handle this by programming our OSS to remind subscriber to verify their
911 information annually via email and if they login to our portal. That
way, if they don't, we not only didn't know about the move but we did remind
them...
Mike Ray, MBA, CNE, CTE
Astro Companies, LLC
11523 Palm Brush Trail #401
Lakewood Ranch, FL 34202
DIRECT: 941 600-0207
http://www.astrocompanies.com
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Alex Balashov
Sent: Friday, January 18, 2013 2:57 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] 911 address policy for company phones at home
On 01/18/2013 02:27 PM, Carlos Alvarez wrote:
> This is a good point, and a fine line. I'd say at least 50% of our
> customers move phones. Almost none of them tell us. I suppose
> knowing that they do puts us in a tougher legal situation than having
> plausible deniability.
Which is why this paragraph should have been written as:
"It occurs to me that conceivably, at least 50% of our customers could,
hypothetically, in principle, be moving their phones, and possibly without
telling us, perhaps maybe."
:-)
--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
United States
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 18, 2013
CALEA for the small fry operator
by nathana@fsr.com
We are a small-ish, regional broadband ISP in the U.S. (inland Washington and Idaho) that has also rolled out an interconnected VoIP product over the past year. I'm trying to wrestle through and understand what our responsibilities and obligations are with regards to CALEA compliance at both the legal and technical levels.
Confession time: we did not purchase a commercial softswitch product. We built our own solution on top of Asterisk. (I can already hear the groans and feel the tangible disapproval.) We went this route for cost reasons, yes, but more importantly we did it because with a custom-engineered solution, we were able to seamlessly integrate our new voice offering with our other existing products when it comes to both provisioning and billing, and this (I believe) leads to a better and more uniform experience for our customers. For better or worse, we are an ISP first and foremost, and an ITSP second, and provisioning for the new product needed to conform to existing practices rather than be an island unto itself, as so many "turn-key" offerings are.
But I recognize that going down this path has brought with it a distinct disadvantage when it comes to solving the CALEA complaince problem. Notably, there are no known CALEA solutions for Asterisk of any stripe that I have been able to find, and any discussion about Asterisk and CALEA seems to have peaked around the time (2006-2007) that the feds announced VoIP providers were going to have to bring themselves into compliance, and then quickly faded after that.
Sure, I could easily come up with something that would allow for live or recorded call interception and/or delivery of CDR/CPNI to law enforcement using existing tools already available to me. What is unclear to me, though, is whether there is any particular format or delivery mechanism for this data that the law stipulates we follow. I know that there is an ANSI standard, T1.678v2 (and the subsequent supplements), but of course I have no access to that (200+ page) document without paying the publisher hundreds of dollars for a copy. And even if we got our hands on a copy, it sounds like it would be prohibitively difficult to implement by ourselves.
Does the law actually stipulate that T1.678 be followed, and are you not in compliance with CALEA regulations unless you specifically use a solution that is T1.678-compatible? Or is the T1.678 standard simply recommended and preferred by LEAs? I have seen discussion threads where other people have talked about their "creative" solutions to CALEA compliance, which include things such as proxying the RTP stream and having a bank of E&M channels at the ready to mirror the audio to (http://fonality.com/trixbox/forums/trixbox-forums/open-discussion/what-i-ne…) Do these people actually know if their solution gets a passing grade, or are they taking a gamble?
Thanks,
--
Nathan Anderson
First Step Internet, LLC
nathana at fsr.com
Jan. 18, 2013
911 address policy for company phones at home
by j@2600hz.com
Nathan,
CLID as it applies to the PSTN is inherently outbound. That being said, a number of switches (PBXs) have the capability of modifying the caller ID of a user. You see this with internal Caller IDs and external caller ID (extension versus CNAM). Some providers (2600hz included) have introduced a third caller ID classification: emergency.
Let me give you a practical example.
My Internal Caller ID is: 7923 (THE MARKETING GUY)
My external Caller ID is: 415.886.7923 2600hz
My emergency Caller ID is: 415.886.7900 2600hz ($Address)
The purpose here is to take our block of 100 DIDs and only support emergency services in a single uniform fashion. We can override this on a user by user or per-device basis, but the point is to simplify emergency calling.
Does that help clarify what we're doing?
Cheers,
Joshua
P.S. I previously sent this email only to Nathan. Adding voiceops onto the chain just in case there's interest.
Joshua Goldbard
VP of Marketing, 2600hz
116 Natoma Street, Floor 2
San Francisco, CA, 94104
415.886.7923 | j at 2600hz.com<mailto:j at 2600hz.com>
[cid:A04A0B25-B1C5-459F-BDCE-0E90D89EA979 at 2600hz.com]
On Jan 18, 2013, at 1:04 PM, Nathan Anderson <nathana at fsr.com<mailto:nathana at fsr.com>>
wrote:
I'm confused, and I apologize to those who have already been involved in this discussion thread for a while since I am just now jumping in. CLID is inherently outbound, so I am not sure what you mean by "inbound vs. outbound caller IDs". Perhaps by "inbound CLID" you mean DID, or DNIS?
I'm also not sure how you propose to bind E911 details to a device instead of a telephone number. The few E911 services I've looked at all only give you the option to provision E911 information via TN. So if you propose a set-up such as what is being discussed here, where each company phone only has an internal extension # and no DID, and CLID is uniformly set to a single number for all outbound calls from any phone whether it is located in the office building or at an employee's residence, then there can only be a single E911 address for all of those phones. That seems inescapable. Are you saying that there are E911 companies that can provision differently, and not use the CLID as the "key" to looking up an address? What do they use/how do they work, and can you name some names?
The only other kludgey workaround I can think of that might pass muster would be to assign unique "throwaway" TNs to each individual extension that you would use as the CLID for outbound from that extension *only* when 911 is dialed, and continue to use the global office TN as CLID across all extensions for all other outbound calls. It's not a perfect solution, since if the individuals using those phones have no clue about those numbers, they might get confused when asked to verify their own telephone number by the PSAP and the dispatcher reads some number back to them that isn't their main office number. At that point, you might as well let the customer know that these numbers exist and give them the option of using them as DIDs for the extensions/devices they've been assigned to.
--
Nathan Anderson
First Step Internet, LLC
nathana at fsr.com<mailto:nathana at fsr.com>
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Carlos Alvarez
Sent: Friday, January 18, 2013 11:49 AM
To: Joshua Goldbard
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] 911 address policy for company phones at home
On Fri, Jan 18, 2013 at 12:46 PM, Joshua Goldbard <j at 2600hz.com> wrote:
Yeah, but you're talking about inbound.
In many corporate environments, the outbound caller ID is uniform for a location (and even if it's not, most systems support uniform caller ID for emergencies). E911 is an outbound service and the inbound and outbound caller IDs can certainly be different.
Does that help clarify my viewpoint?
Ah, yes. We very rarely get anyone who wants to do that, so it didn't cross my mind.
We do have special 911 CLID/DID settings and special processing for those calls. However we bind them to a device, since the device is what has location, in most of our installations.
--
Carlos Alvarez
TelEvolve
602-889-3003
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 18, 2013