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
CALEA for the small fry operator
by nathana@fsr.com
You're probably right, but I'm just laying out the facts as I see/read them. The rules seem to state that you aren't granted "safe harbor" unless you adhere to standard industry-adopted protocols.
-- Nathan
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Alex Balashov
Sent: Saturday, January 19, 2013 5:16 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] CALEA for the small fry operator
On 01/19/2013 07:57 PM, Nathan Anderson wrote:
> It is sounding more and more like we are either expected to adhere to
> these industry standards or are going to be expected to at some
> point, depending on what the DoJ has actually filed in response to
> these standards and how section 107(b) of the CALEA of 1994 is to be
> interpreted.
Practically speaking, this is impossible, and will continue to be
impossible.
It's just too expensive.
--
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. 20, 2013
CALEA for the small fry operator
by carlos@race.com
Hey Nathan,
I'm sure every agency is different the method that we have used and seems
to be pretty standard with the lea's is CDC collection function (call data
channel) we setup a vpn with them they give us the ip and port of where to
send the info. What actual data is being sent I will have to dig up as I
do not have access to that remotely to show a sample. I'll tell you this
our soft switch vendor keeps the calea manual under lock and key we had to
ask for it as it did not come with the standard docs and or there portal.
Note we are a clec and do have all our local interconnects ect so we do
function a little bit different then a normal itsp. I know with talking
with the lea's they have always asked us to make sure that our switch can
handle the lea portions even when someone does a transfer disconnect as
that is a method people have used to get around calea.
Carlos Alcantar
Race Communications / Race Team Member
1325 Howard Ave. #604, Burlingame, CA. 94010
Phone: +1 415 376 3314 / carlos at race.com / http://www.race.com
-----Original Message-----
From: Nathan Anderson <nathana at fsr.com>
Date: Saturday, January 19, 2013 3:17 PM
To: Carlos Alcantar <carlos at race.com>, "'ryandelgrosso at gmail.com'"
<ryandelgrosso at gmail.com>, VoiceOps <voiceops at voiceops.org>
Subject: RE: [VoiceOps] CALEA for the small fry operator
What format was the live call data in? Is it just the SIP signalling in
real-time? Are they just concerned about DTMF? Is there any reason why
they would not accept having the DTMF put back in-band and including it in
the audio fork?
If they just want the SIP signalling mirrored across the VPN connection
but also want to keep the DTMF out-of-band, could I take the RTP DTMF and
convert it to SIP INFO and send it to them that way?
-- Nathan
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Carlos Alcantar
Sent: Saturday, January 19, 2013 2:30 PM
To: ryandelgrosso at gmail.com; voiceops at voiceops.org
Subject: Re: [VoiceOps] CALEA for the small fry operator
Every calea request that we have had to deal with we have had a setup like
the one described below where we would basically fork the call to an
external # for the audio as well as we setup a vpn connection with the
requesting agency to send them the live call data. Eg. Touch tones
pressed ect.
Carlos Alcantar
Race Communications / Race Team Member
1325 Howard Ave. #604, Burlingame, CA. 94010
Phone: +1 415 376 3314 / carlos at race.com / http://www.race.com
From: Ryan Delgrosso <ryandelgrosso at gmail.com>
Reply-To: "ryandelgrosso at gmail.com" <ryandelgrosso at gmail.com>
Date: Friday, January 18, 2013 3:59 PM
To: VoiceOps <voiceops at voiceops.org>
Subject: Re: [VoiceOps] CALEA for the small fry operator
Well in our case we were provided with a destination that signaling was to
be sent to at Quantico, and a phone number that would be dialed to collect
the audio (forked in the network). This is of course the fancy way. I'm
sure any call recording solution that can associate signaling and media in
a neat package would probably suffice, presuming its local and not
federal. Again IANAL so you might want to consult with one before taking
anything I say as gospel.
-Ryan
On 01/18/2013 03:50 PM, Carlos Alvarez wrote:
On Fri, Jan 18, 2013 at 4:44 PM, Ryan Delgrosso <ryandelgrosso at gmail.com>
wrote:
I would respectfully disagree. We are most certainly not a CLEC, but we
have received warrants for wire taps, and have complied. Fortunately we do
use a commercial softswitch that can provide this.
When you say "provide this" can you tell us exactly how? It seems like a
simple ability to listen in to calls may or may not be compliant.
--
Carlos Alvarez
TelEvolve
602-889-3003
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.orghttps://puck.nether.net/mailman/listinfo/voiceops
Jan. 20, 2013
911 address policy for company phones at home
by nathana@fsr.com
!!!
Thanks for this. Very interesting.
Perhaps I should be asking my E911 provider if they plan to have VPC capability any time soon, or even consider a switch to 911Enable.
-- Nathan
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Frank Bulk
Sent: Saturday, January 19, 2013 5:10 PM
To: 'Mary Lou Carey'; 'Jay Hennigan'; 'VoiceOps'
Subject: Re: [VoiceOps] 911 address policy for company phones at home
It looks like there are vendors that make it possible for PSAPs to access
near-realtime info:
http://www1.911enable.com/resource-center/faq (see "What is a VoIP
Positioning Center?")
Frank
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Mary Lou Carey
Sent: Saturday, January 19, 2013 8:17 AM
To: 'Jay Hennigan'; 'VoiceOps'
Subject: Re: [VoiceOps] 911 address policy for company phones at home
PBXs can associate a single line for one location or have multiple lines,
one for each location so that there is an address in the ALI database for
each location. These lines are all fixed though so it's very different from
VOIP because the end user can move their phone to any location that has
internet access and use it without the switch being re-programmed. That's
why there is a requirement for the CLEC to offer a way for the customer to
update their information in the ALI database themselves.
Someone asked me about who provides the VOIP ALI update solution and I
couldn't find a provider, but in researching it I did find that there
appears to be an issue with this method because the ALI database doesn't
update in real time and since users could plug their phone in and update the
address, it didn't mean that the ALI database identified the location
correctly. YMAX commented to the FCC in November 2011 (see the link below)
that they had a solution that could work. It involved attaching a GSM
cellular transceiver to their MagicJack device so the location could be
identified but it also relied on having some type of database with customer
locations to help it identify which PSAP needed to be contacted so it
doesn't appear that is totally thought out either. It appears to me that
even though there are some requirements that the FCC put out about updating
the ALI database, the details of exactly how that will work aren't totally
worked out because of the issue with the ALI database. To me......that seems
like a great business opportunity for someone! If you could figure out how
to get a VOIP phone to automatically identify the exact location of the
phone whenever its plugged in and transmit that location to a VOIP ALI
database (which you'd need to create), then you could sell the service to
both PSAPs AND VOIP providers!
http://apps.fcc.gov/ecfs/document/view;jsessionid=c1M1QZvLvW9XfyYDpTwlMGN1QK
T7yhs21npc4ThYvwR61R6JK4yv!-56284754!-224088840?id=7021744691
Mary Lou Carey
BackUP Telecom Consulting
marylou at backuptelecom.com
Office: 615-791-9969 x 2001
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Jay Hennigan
Sent: Friday, January 18, 2013 6:33 PM
To: VoiceOps
Subject: Re: [VoiceOps] 911 address policy for company phones at home
On 1/18/13 3:46 PM, Mike Ray wrote:
> The difference here is the demarcation point. If you're handing off
> analog lines, there are two important differences:
>
> 1. You're not providing the PBX functionality as part of the telephone
> service and, 2. You're using a technology that is incapable of sending
> a different ANI than what's in your switch for each line.
An extension-only SIP phone doesn't have a unique ANI.
> So the requirement here is that the e911 ALI address must match the
> physical location where you have those lines installed.
But there are no "lines" for DID-less extensions or for that matter an
"installation" in the case of softphones.
The company HQ where the main ANI is answered is the ALI address. Call it
and talk to the receptionist. Drive there in a police car and visit the
same receptionist.
> If you are looking to protect yourself from the customer moving to a
> new location, ATA, PBX and all, you just use a contract provision
> requiring them to notify you of address changes. You could also
> require them to have you move the service to the new location for more
security there.
Yes, and you should.
> So, different animal that the hosted PBX question...
ATA, PBX and all is indeed a different animal than an extension-only remote
phone.
The problem, and I don't know if there is a full solution, is that PSTN
telephone numbers have always been used to identify the destination of a
call. 9-1-1 assumes that this identifier of a destination positively and
unequivocally also identifies the origin.
Think in terms of laptops with softphones. There is no way to make that
work with the present 9-1-1 infrastructure.
--
Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net Impulse
Internet Service - http://www.impulse.net/ Your local telephone and
internet company - 805 884-6323 - WB6RDV
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 20, 2013
CALEA for the small fry operator
by abalashov@evaristesys.com
On 01/19/2013 07:57 PM, Nathan Anderson wrote:
> It is sounding more and more like we are either expected to adhere to
> these industry standards or are going to be expected to at some
> point, depending on what the DoJ has actually filed in response to
> these standards and how section 107(b) of the CALEA of 1994 is to be
> interpreted.
Practically speaking, this is impossible, and will continue to be
impossible.
It's just too expensive.
--
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/
Jan. 20, 2013
911 address policy for company phones at home
by frnkblk@iname.com
It looks like there are vendors that make it possible for PSAPs to access
near-realtime info:
http://www1.911enable.com/resource-center/faq (see "What is a VoIP
Positioning Center?")
Frank
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Mary Lou Carey
Sent: Saturday, January 19, 2013 8:17 AM
To: 'Jay Hennigan'; 'VoiceOps'
Subject: Re: [VoiceOps] 911 address policy for company phones at home
PBXs can associate a single line for one location or have multiple lines,
one for each location so that there is an address in the ALI database for
each location. These lines are all fixed though so it's very different from
VOIP because the end user can move their phone to any location that has
internet access and use it without the switch being re-programmed. That's
why there is a requirement for the CLEC to offer a way for the customer to
update their information in the ALI database themselves.
Someone asked me about who provides the VOIP ALI update solution and I
couldn't find a provider, but in researching it I did find that there
appears to be an issue with this method because the ALI database doesn't
update in real time and since users could plug their phone in and update the
address, it didn't mean that the ALI database identified the location
correctly. YMAX commented to the FCC in November 2011 (see the link below)
that they had a solution that could work. It involved attaching a GSM
cellular transceiver to their MagicJack device so the location could be
identified but it also relied on having some type of database with customer
locations to help it identify which PSAP needed to be contacted so it
doesn't appear that is totally thought out either. It appears to me that
even though there are some requirements that the FCC put out about updating
the ALI database, the details of exactly how that will work aren't totally
worked out because of the issue with the ALI database. To me......that seems
like a great business opportunity for someone! If you could figure out how
to get a VOIP phone to automatically identify the exact location of the
phone whenever its plugged in and transmit that location to a VOIP ALI
database (which you'd need to create), then you could sell the service to
both PSAPs AND VOIP providers!
http://apps.fcc.gov/ecfs/document/view;jsessionid=c1M1QZvLvW9XfyYDpTwlMGN1QK
T7yhs21npc4ThYvwR61R6JK4yv!-56284754!-224088840?id=7021744691
Mary Lou Carey
BackUP Telecom Consulting
marylou at backuptelecom.com
Office: 615-791-9969 x 2001
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Jay Hennigan
Sent: Friday, January 18, 2013 6:33 PM
To: VoiceOps
Subject: Re: [VoiceOps] 911 address policy for company phones at home
On 1/18/13 3:46 PM, Mike Ray wrote:
> The difference here is the demarcation point. If you're handing off
> analog lines, there are two important differences:
>
> 1. You're not providing the PBX functionality as part of the telephone
> service and, 2. You're using a technology that is incapable of sending
> a different ANI than what's in your switch for each line.
An extension-only SIP phone doesn't have a unique ANI.
> So the requirement here is that the e911 ALI address must match the
> physical location where you have those lines installed.
But there are no "lines" for DID-less extensions or for that matter an
"installation" in the case of softphones.
The company HQ where the main ANI is answered is the ALI address. Call it
and talk to the receptionist. Drive there in a police car and visit the
same receptionist.
> If you are looking to protect yourself from the customer moving to a
> new location, ATA, PBX and all, you just use a contract provision
> requiring them to notify you of address changes. You could also
> require them to have you move the service to the new location for more
security there.
Yes, and you should.
> So, different animal that the hosted PBX question...
ATA, PBX and all is indeed a different animal than an extension-only remote
phone.
The problem, and I don't know if there is a full solution, is that PSTN
telephone numbers have always been used to identify the destination of a
call. 9-1-1 assumes that this identifier of a destination positively and
unequivocally also identifies the origin.
Think in terms of laptops with softphones. There is no way to make that
work with the present 9-1-1 infrastructure.
--
Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net Impulse
Internet Service - http://www.impulse.net/ Your local telephone and
internet company - 805 884-6323 - WB6RDV
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 20, 2013
CALEA for the small fry operator
by nathana@fsr.com
Replying to myself here (but still seeking comments from others...). Apologies in advance for the length.
The CALEA law states in section 107(a)(2): "COMPLIANCE UNDER ACCEPTED STANDARDS - A telecommunications carrier shall be found to be in compliance with the assistance capability requirements under section 103 [...] if the carrier, manufacturer, or support service provider is in compliance with publicly available technical requirements or standards adopted by an industry association or standard-setting organization..."
This would seem to state that the industry is responsible for helping to set standards that can be used to deliver the required information (section 103) to LEA, and so the very existence of standards such as J-STD-025-A/B and T1.678 (both headed by ATIS) and their adoption by the industry I take as an indication that whatever solution we come up with *has to adhere to these technical standards and protocols*, by law.
Now, in section 107(b), it is stated that (summarizing here...you can read a copy for yourself that I found @ http://cdn.ientry.com/sites/webpronews/pdf/calea.pdf) if the industry fails to come up with standards, OR if an agency finds the standards to be "deficient", then they can petition the FCC to come up with and enforce a different standard. INTERESTINGLY, at http://en.wikipedia.org/wiki/Lawful_interception there is a comment at the end of the "Technical description" section that mentions that "all of these standards have been challenged as 'deficient' by the U.S. Dept of Justice pursuant to CALEA." I don't know if that means we are currently off-the-hook and in some state of "limbo" right now where any reasonable attempt on a carrier's part to deliver a tap or CDRs pursuant to a court order is considered acceptable, whether or not it adheres to any of the ATIS-led and ANSI-adopted standards released to-date.
As far as the standards themselves go, Sid Rao contacted me off-list to inform me that the live signalling format I was asking about earlier is in fact expected to adhere to J-STD-025, transmitted over a VPN, while the live call audio is forked to a PSTN destination. This is interesting, because I did some digging and ran into a product by IP Fabrics (http://www.ipfabrics.com/) called the "DeepSweep." They have a CALEA-for-VoIP edition. The manual (http://www.ipfabrics.com/pdf/VoIP_SM_users_manual.pdf) states that their product adheres to T1.678, which was specifically developed for interconnected VoIP providers (whereas J-STD-025(-A/B) was developed before interconnected VoIP was really a "thing" in the industry and is meant for circuit-switched voice traffic). Perhaps not all agencies know how to deal with T1.678-encapsulated messages yet, or perhaps preference of delivery method varies on an agency-by-agency basis.
In any case, section 2.5 of the DeepSweep manual says this:
"T1.678 gives the implementer a basic choice in CII messages (section 6.4). One choice is to map SIP (and H.323, if one is providing that, which DeepSweep does not) into J-STD-025 messages defined for circuit-switched telephony. This is called mapped signaling information, or mapped. The other choice is DSR (direct signal reporting), where most of the signaling is delivered on the CII interface by encapsulating the SIP message. DeepSweep implements DSR. Thus the T1.678 message types that are generated are the DSR and DialedDigitExtraction messages, and, if content intercept is authorized, the CCOpen, CCClose, and CCChange. DialedDigitExtraction comes from the VoIP content SM; the others come from the VoIP controller SM."
I take this to mean that T1.678 gives you the option of either translating the SIP signalling into J-STD-025 format, OR simply sending the raw SIP dialogs themselves. In either case, it does sound like T1.678 defines some kind of encapsulation protocol that either signalling format needs to be stuffed into before transmission to the LEA's off-site data collector; you can't just mirror the IP or ethernet frames containing the SIP signalling and throw those at them.
It is sounding more and more like we are either expected to adhere to these industry standards or are going to be expected to at some point, depending on what the DoJ has actually filed in response to these standards and how section 107(b) of the CALEA of 1994 is to be interpreted.
*sigh*
Anybody know anything about these DeepSweep appliances?
--
Nathan Anderson
First Step Internet, LLC
nathana at fsr.com
-----Original Message-----
From: Nathan Anderson
Sent: Saturday, January 19, 2013 3:26 PM
To: 'Carlos Alvarez'; 'voiceops at voiceops.org'
Subject: RE: [VoiceOps] CALEA for the small fry operator
Carlos, thanks for doing that legwork. A few questions come to mind:
1) What is the "one allowed data standard", and where did you find it referenced?
2) Is there any reference copy of the data standard publicly available? Is it in fact the T1.678 that http://askcalea.fbi.gov/ mentions?
3) What signalling information do they require be recorded and/or streamed in real-time?
4) One might wonder if the concession made to operators not being required to completely redesign their networks was specifically made for those who had networks operating before CALEA compliance was made mandatory. Is there any reason to believe that those of us who have started up networks in the last year or two, well after the CALEA requirements were put in place, cannot use this excuse? It seems to me they could try to argue that we should have known at the outset that this would be required of us, and should have planned our network accordingly.
--
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: Saturday, January 19, 2013 8:13 AM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] CALEA for the small fry operator
I'm trimming all previous replies because this isn't in reply to any one thing. I spent several hours last night reading FCC docs, FBI stuff, and whatever I could find on this topic. There are a few bullet points that stuck in my mind. These are according to my interpretation, and while I've been reading FCC and other legal stuff for a very long time, I'm not a lawyer and my expertise isn't in law.
It seems that there is one allowed data standard, but repeatedly I saw that the FCC refused to limit delivery methods, particularly for packet-switched networks. It seems to me that a meetme in Asterisk is almost compliant, though missing some of the signaling stuff. There is in fact an option on the FCC compliance form for "proprietary/home-grown" solution.
On that topic however, I repeatedly saw "if reasonably available." The FCC says that you must provide all the signaling requested "if reasonably available" at the network intercept point. They specifically said they don't expect operators to completely redesign their networks. This of course is rather unclear. From our perspective, as a tiny company, it would be easy to argue that it's not reasonable for us to spend 50% of a year's profit changing our network. I may be crazy and that may not work, I don't know.
You can charge any time you get a request for records or intercept. Actually a lot. As a comparative number, Comcast charges $1k to set up an intercept and provide a month of service, $750/mo thereafter. They charge $200/mo for weekly call record delivery.
--
Carlos Alvarez
TelEvolve
602-889-3003
Jan. 20, 2013
CALEA for the small fry operator
by nathana@fsr.com
Carlos, thanks for doing that legwork. A few questions come to mind:
1) What is the "one allowed data standard", and where did you find it referenced?
2) Is there any reference copy of the data standard publicly available? Is it in fact the T1.678 that http://askcalea.fbi.gov/ mentions?
3) What signalling information do they require be recorded and/or streamed in real-time?
4) One might wonder if the concession made to operators not being required to completely redesign their networks was specifically made for those who had networks operating before CALEA compliance was made mandatory. Is there any reason to believe that those of us who have started up networks in the last year or two, well after the CALEA requirements were put in place, cannot use this excuse? It seems to me they could try to argue that we should have known at the outset that this would be required of us, and should have planned our network accordingly.
--
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: Saturday, January 19, 2013 8:13 AM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] CALEA for the small fry operator
I'm trimming all previous replies because this isn't in reply to any one thing. I spent several hours last night reading FCC docs, FBI stuff, and whatever I could find on this topic. There are a few bullet points that stuck in my mind. These are according to my interpretation, and while I've been reading FCC and other legal stuff for a very long time, I'm not a lawyer and my expertise isn't in law.
It seems that there is one allowed data standard, but repeatedly I saw that the FCC refused to limit delivery methods, particularly for packet-switched networks. It seems to me that a meetme in Asterisk is almost compliant, though missing some of the signaling stuff. There is in fact an option on the FCC compliance form for "proprietary/home-grown" solution.
On that topic however, I repeatedly saw "if reasonably available." The FCC says that you must provide all the signaling requested "if reasonably available" at the network intercept point. They specifically said they don't expect operators to completely redesign their networks. This of course is rather unclear. From our perspective, as a tiny company, it would be easy to argue that it's not reasonable for us to spend 50% of a year's profit changing our network. I may be crazy and that may not work, I don't know.
You can charge any time you get a request for records or intercept. Actually a lot. As a comparative number, Comcast charges $1k to set up an intercept and provide a month of service, $750/mo thereafter. They charge $200/mo for weekly call record delivery.
--
Carlos Alvarez
TelEvolve
602-889-3003
Jan. 19, 2013
CALEA for the small fry operator
by nathana@fsr.com
What format was the live call data in? Is it just the SIP signalling in real-time? Are they just concerned about DTMF? Is there any reason why they would not accept having the DTMF put back in-band and including it in the audio fork?
If they just want the SIP signalling mirrored across the VPN connection but also want to keep the DTMF out-of-band, could I take the RTP DTMF and convert it to SIP INFO and send it to them that way?
-- Nathan
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Carlos Alcantar
Sent: Saturday, January 19, 2013 2:30 PM
To: ryandelgrosso at gmail.com; voiceops at voiceops.org
Subject: Re: [VoiceOps] CALEA for the small fry operator
Every calea request that we have had to deal with we have had a setup like the one described below where we would basically fork the call to an external # for the audio as well as we setup a vpn connection with the requesting agency to send them the live call data. Eg. Touch tones pressed ect.
Carlos Alcantar
Race Communications / Race Team Member
1325 Howard Ave. #604, Burlingame, CA. 94010
Phone: +1 415 376 3314 / carlos at race.com / http://www.race.com
From: Ryan Delgrosso <ryandelgrosso at gmail.com>
Reply-To: "ryandelgrosso at gmail.com" <ryandelgrosso at gmail.com>
Date: Friday, January 18, 2013 3:59 PM
To: VoiceOps <voiceops at voiceops.org>
Subject: Re: [VoiceOps] CALEA for the small fry operator
Well in our case we were provided with a destination that signaling was to be sent to at Quantico, and a phone number that would be dialed to collect the audio (forked in the network). This is of course the fancy way. I'm sure any call recording solution that can associate signaling and media in a neat package would probably suffice, presuming its local and not federal. Again IANAL so you might want to consult with one before taking anything I say as gospel.
-Ryan
On 01/18/2013 03:50 PM, Carlos Alvarez wrote:
On Fri, Jan 18, 2013 at 4:44 PM, Ryan Delgrosso <ryandelgrosso at gmail.com> wrote:
I would respectfully disagree. We are most certainly not a CLEC, but we have received warrants for wire taps, and have complied. Fortunately we do use a commercial softswitch that can provide this.
When you say "provide this" can you tell us exactly how? It seems like a simple ability to listen in to calls may or may not be compliant.
--
Carlos Alvarez
TelEvolve
602-889-3003
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.orghttps://puck.nether.net/mailman/listinfo/voiceops
Jan. 19, 2013
CALEA for the small fry operator
by carlos@race.com
Every calea request that we have had to deal with we have had a setup like
the one described below where we would basically fork the call to an
external # for the audio as well as we setup a vpn connection with the
requesting agency to send them the live call data. Eg. Touch tones pressed
ect.
Carlos Alcantar
Race Communications / Race Team Member
1325 Howard Ave. #604, Burlingame, CA. 94010
Phone: +1 415 376 3314 / carlos at race.com / http://www.race.com
From: Ryan Delgrosso <ryandelgrosso at gmail.com>
Reply-To: "ryandelgrosso at gmail.com" <ryandelgrosso at gmail.com>
Date: Friday, January 18, 2013 3:59 PM
To: VoiceOps <voiceops at voiceops.org>
Subject: Re: [VoiceOps] CALEA for the small fry operator
Well in our case we were provided with a destination that signaling was to
be sent to at Quantico, and a phone number that would be dialed to collect
the audio (forked in the network). This is of course the fancy way. I'm sure
any call recording solution that can associate signaling and media in a neat
package would probably suffice, presuming its local and not federal. Again
IANAL so you might want to consult with one before taking anything I say as
gospel.
-Ryan
On 01/18/2013 03:50 PM, Carlos Alvarez wrote:
> On Fri, Jan 18, 2013 at 4:44 PM, Ryan Delgrosso <ryandelgrosso at gmail.com>
> wrote:
>> I would respectfully disagree. We are most certainly not a CLEC, but we have
>> received warrants for wire taps, and have complied. Fortunately we do use a
>> commercial softswitch that can provide this.
>
> When you say "provide this" can you tell us exactly how? It seems like a
> simple ability to listen in to calls may or may not be compliant.
>
>
> --
> Carlos Alvarez
> TelEvolve
> 602-889-3003
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.orghttps://puck.nether.net/mailman/listinfo/voiceops
Jan. 19, 2013
911 address policy for company phones at home
by abalashov@evaristesys.com
Does the FCC narrative specifically parameterise the 911 requirement in
terms of end-users?
What about wholesale VoIP orig+term providers?
--
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/
Jan. 19, 2013