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
April 2016
- 51 participants
- 128 messages
Recommendations for high-cps SS7 OC-X gear?
by brandon@kamikos.com
Just curious: Is there a reason to avoid Metaswitch?
My main experience is in Metaswitch and Sonus, but in Metaswitch it was
limited to the 2510 and 3510 gateways and the accompanying servers up to
7.4 software and none of the newer blade platforms. At the time I would
have said that Metaswitch would have worked quite well for what is being
asked, especially if wanting to split across many smaller gateways and
geographically distributed. Is there something with the new hardware
and/or software I don't know about quality-wise?
Sonus killed off the GSX4000 which would have lent better to spreading
around a bunch of smaller boxes. They still have the GSX9000 which goes
up to single OC-3 cards (so you'd have to have a couple to split an
OC-48 still), but their main push seems to be the SBC5210 and SBC7000
which are IP only, no TDM. But spread across gateways the call
processing can easily do the 500 CPS.
On 4/21/2016 5:00 AM, Anthony Orlando via VoiceOps wrote:
> Avoid Meta at all cost.
>
> Sent from my iPhone
>
> On Apr 20, 2016, at 10:35 PM, Paul Timmins <paul at timmins.net
> <mailto:paul at timmins.net>> wrote:
>
>> You're going to handle 500CPS of legacy sonet based TDM and question
>> dropping 7 figures on the solution? *cringes*
>>
>> This is literally what platforms like metaswitch, sonus and many
>> others are made for. If you're looking for low cost, Taqua's solution
>> is decent, and if you need to take that entire OC-48, you're all but
>> eyeballs deep in Sonus or Metaswitch land.
>>
>> -Paul
>>
>>> On Apr 20, 2016, at 17:54, Brooks Bridges <bbridges at o1.com
>>> <mailto:bbridges at o1.com>> wrote:
>>>
>>> Looking for suggestions for NEBS compliant gear that can support
>>> SS7, handle OC-3 or higher levels of channels, and can support (in
>>> aggregate) up to around 500 cps through a **good** (key word) SIP
>>> interface. I?m willing to entertain the idea of a single larger
>>> device that can take a full OC-48 and support the full 500 cps, but
>>> I?d prefer spread the load across multiple devices and smaller
>>> interfaces for load balancing and redundancy.
>>> Any pointers? Obviously there are products out there by the really
>>> big players, but I?d really rather not have to drop 7 figures on
>>> this project unless I have to.
>>> Thanks!
>>> *Brooks Bridges |*Sr. Voice Services Engineer
>>> *O^1 Communications*
>>> 5190 Golden Foothill Pkwy
>>> El Dorado Hills, CA 95762
>>> *office:*916.235.2097 |*main:*888.444.1111, Option 2
>>> *email:*bbridges at o1.com <mailto:bbridges at o1.com>| *web:*www.o1.com
>>> <http://www.o1.com/>
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
>>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org <mailto: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
April 22, 2016
anyone here
by zavoid@gmail.com
work for voip innovations out of pittsburgh pa?
If so please contact me off list.
thanks
April 22, 2016
SS7
by marylou@backuptelecom.com
If you just want to route traffic to the PSTN network and you don't want to deal
with getting SS7 links, there are several large carriers that will provide a
host switch product. It's a cheaper way to go initially for those who don't
deliver tons of traffic to the PSTN. Right now it is only available in Verizon
territories as far as I know, but as soon as the process for the new
Interconnected VOIP carriers is established, you should be able to do it in any
major ILEC/RBOC area. Just a thought for those who don't want to put all the
money into becoming a full-fledged facilities-based CLEC.
Mary Lou Carey
BackUP Telecom Consulting
Marylou at backuptelecom.com
Office: 615-791-9969
Cell: 615-796-1111
> On April 21, 2016 at 5:35 PM Kidd Filby <kiddfilby at gmail.com> wrote:
>
> I purposely didn't even start down that road. But, Yes, they most certainly
> could, and for the most part would be easier. All of the same info rides the
> SigTran deployment as an SS7 A/E/F-Link, plus possibly more.... depending on
> what type of messaging you're talking about. However, it also lacks voice
> content, like the SS7 network.
>
> Kidd
>
> On Thu, Apr 21, 2016 at 4:27 PM, Jared Geiger <jared at compuwizz.net
> <mailto:jared at compuwizz.net> > wrote:
> > > I haven't used SS7 in the voice world, only touched briefly on the
> > > messaging side of it. Would hackers be able to do the same similar
> > > attack via SIGTRAN? I would think it would be easier to get access to a
> > > poorly managed SIGTRAN device which would then give you SS7 access.
> >
> > Or even an Asterisk box running SS7 trunks.
> >
> > On Thu, Apr 21, 2016 at 1:00 PM, Dan York <dyork at lodestar2.com
> > <mailto:dyork at lodestar2.com> > wrote:
> > > > > Joseph,
> > >
> > > I noticed that in Gmail (and perhaps other email systems), the longer
> > > reply I wrote for Kidd was hidden because it appeared after his text.
> > > Here's what I wrote...
> > >
> > > what's fascinating is the recent rise in end-to-end (e2e) encryption
> > > among IP-based communications platforms that include voice.
> > >
> > > WhatsApp, for instance, just completed the rollout of e2e encryption
> > > on April 5, and not just for messaging, but also for voice and video calls
> > > as well as file transfers (
> > > https://blog.whatsapp.com/10000618/end-to-end-encryption ). Just
> > > yesterday the team behind Viber announced that they will soon have e2e
> > > encryption for all clients. The app Wire ( http://wire.com ) also does
> > > e2e encryption for voice, video and group chats.
> > >
> > > In a US Congress hearing this week, a Congressman asked a Dept of
> > > Homeland Security representative if e2e encryption available in apps would
> > > have prevented this interception that happened via SS7. The DHS answer was
> > > that it would mitigate the interception of the content, although the
> > > location meta-data would still be available. (You can view the exchange
> > > via the link in this tweet:
> > > https://twitter.com/csoghoian/status/722854012567969794 )
> > >
> > > The end result is that we're definitely moving to a space where the
> > > communication over IP-based solutions will wind up being far more secure
> > > than what we had before.
> > >
> > > Interesting times,
> > > Dan
> > >
> > > On Thu, Apr 21, 2016 at 3:45 PM, Joseph Jackson
> > > <jjackson at aninetworks.net <mailto:jjackson at aninetworks.net> > wrote:
> > > > > > >
> > > > I don?t know many places that encrypt their voice traffic.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > From: VoiceOps [mailto:voiceops-bounces at voiceops.org
> > > > <mailto:voiceops-bounces at voiceops.org> ] On Behalf Of Dan York
> > > > Sent: Thursday, April 21, 2016 2:45 PM
> > > > To: Kidd Filby
> > > > Cc: voiceops at voiceops.org <mailto:voiceops at voiceops.org>
> > > > Subject: Re: [VoiceOps] SS7
> > > >
> > > >
> > > >
> > > > This is generally true if the calls are *unencrypted* on VoIP...
> > > >
> > > >
> > > >
> > > > On Thu, Apr 21, 2016 at 2:20 PM, Kidd Filby <kiddfilby at gmail.com
> > > > <mailto:kiddfilby at gmail.com> > wrote:
> > > >
> > > >
> > > >
> > > > Also folks, don't forget, the same outcome of recording someone's
> > > > call is MUCH easier to accomplish once it is VoIP. IMHO, of course.
> > > > ;-)
> > > >
> > > >
> > > >
> > > > ... BUT... what's fascinating is the recent rise in end-to-end
> > > > (e2e) encryption among IP-based communications platforms that include
> > > > voice.
> > > >
> > > >
> > > >
> > > > WhatsApp, for instance, just completed the rollout of e2e
> > > > encryption on April 5, and not just for messaging, but also for voice
> > > > and video calls as well as file transfers (
> > > > https://blog.whatsapp.com/10000618/end-to-end-encryption ). Just
> > > > yesterday the team behind Viber announced that they will soon have e2e
> > > > encryption for all clients. The app Wire ( http://wire.com ) also does
> > > > e2e encryption for voice, video and group chats.
> > > >
> > > >
> > > >
> > > > In a US Congress hearing this week, a Congressman asked a Dept of
> > > > Homeland Security representative if e2e encryption available in apps
> > > > would have prevented this interception that happened via SS7. The DHS
> > > > answer was that it would mitigate the interception of the content,
> > > > although the location meta-data would still be available. (You can view
> > > > the exchange via the link in this tweet:
> > > > https://twitter.com/csoghoian/status/722854012567969794 )
> > > >
> > > >
> > > >
> > > > The end result is that we're definitely moving to a space where
> > > > the communication over IP-based solutions will wind up being far more
> > > > secure than what we had before.
> > > >
> > > >
> > > >
> > > > Interesting times,
> > > >
> > > > Dan
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > >
> > > >
> > > > Dan York
> > > >
> > > > dyork at lodestar2.com <mailto:dyork at lodestar2.com>
> > > > +1-802-735-1624 Skype:danyork
> > > >
> > > > My writing -> http://www.danyork.me/
> > > >
> > > > http://www.danyork.com/ <http://www.danyork.com/>
> > > >
> > > > http://twitter.com/danyork <http://twitter.com/danyork>
> > > >
> > > > > > >
> > >
> > >
> > > --
> > >
> > > Dan York
> > > dyork at lodestar2.com <mailto:dyork at lodestar2.com> +1-802-735-1624
> > > Skype:danyork
> > > My writing -> http://www.danyork.me/
> > > http://www.danyork.com/
> > > http://<http://twitter.com/danyork>
> > > _______________________________________________
> > > VoiceOps mailing list
> > > VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
> > > https://puck.nether.net/mailman/listinfo/voiceops
> > >
> > > > >
> > _______________________________________________
> > VoiceOps mailing list
> > VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
> > https://puck.nether.net/mailman/listinfo/voiceops
> > >
>
>
> --
> Kidd Filby
> 661.557.5640 (C)
> http://www.linkedin.com/in/kiddfilby
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
April 22, 2016
SS7
by kiddfilby@gmail.com
I purposely didn't even start down that road. But, Yes, they most
certainly could, and for the most part would be easier. All of the same
info rides the SigTran deployment as an SS7 A/E/F-Link, plus possibly
more.... depending on what type of messaging you're talking about.
However, it also lacks voice content, like the SS7 network.
Kidd
On Thu, Apr 21, 2016 at 4:27 PM, Jared Geiger <jared at compuwizz.net> wrote:
> I haven't used SS7 in the voice world, only touched briefly on the
> messaging side of it. Would hackers be able to do the same similar attack
> via SIGTRAN? I would think it would be easier to get access to a poorly
> managed SIGTRAN device which would then give you SS7 access.
>
> Or even an Asterisk box running SS7 trunks.
>
> On Thu, Apr 21, 2016 at 1:00 PM, Dan York <dyork at lodestar2.com> wrote:
>
>> Joseph,
>>
>> I noticed that in Gmail (and perhaps other email systems), the longer
>> reply I wrote for Kidd was hidden because it appeared after his text.
>> Here's what I wrote...
>>
>> what's fascinating is the recent rise in end-to-end (e2e) encryption
>> among IP-based communications platforms that include voice.
>>
>> WhatsApp, for instance, just completed the rollout of e2e encryption on
>> April 5, and not just for messaging, but also for voice and video calls as
>> well as file transfers (
>> https://blog.whatsapp.com/10000618/end-to-end-encryption ). Just
>> yesterday the team behind Viber announced that they will soon have e2e
>> encryption for all clients. The app Wire ( http://wire.com ) also does
>> e2e encryption for voice, video and group chats.
>>
>> In a US Congress hearing this week, a Congressman asked a Dept of
>> Homeland Security representative if e2e encryption available in apps would
>> have prevented this interception that happened via SS7. The DHS answer was
>> that it would mitigate the interception of the content, although the
>> location meta-data would still be available. (You can view the exchange
>> via the link in this tweet:
>> https://twitter.com/csoghoian/status/722854012567969794 )
>>
>> The end result is that we're definitely moving to a space where the
>> communication over IP-based solutions will wind up being far more secure
>> than what we had before.
>>
>> Interesting times,
>> Dan
>>
>> On Thu, Apr 21, 2016 at 3:45 PM, Joseph Jackson <jjackson at aninetworks.net
>> > wrote:
>>
>>> I don?t know many places that encrypt their voice traffic.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *From:* VoiceOps [mailto:voiceops-bounces at voiceops.org] *On Behalf Of *Dan
>>> York
>>> *Sent:* Thursday, April 21, 2016 2:45 PM
>>> *To:* Kidd Filby
>>> *Cc:* voiceops at voiceops.org
>>> *Subject:* Re: [VoiceOps] SS7
>>>
>>>
>>>
>>> This is generally true if the calls are *unencrypted* on VoIP...
>>>
>>>
>>>
>>> On Thu, Apr 21, 2016 at 2:20 PM, Kidd Filby <kiddfilby at gmail.com> wrote:
>>>
>>>
>>>
>>> Also folks, don't forget, the same outcome of recording someone's call
>>> is MUCH easier to accomplish once it is VoIP. IMHO, of course. ;-)
>>>
>>>
>>>
>>> ... BUT... what's fascinating is the recent rise in end-to-end (e2e)
>>> encryption among IP-based communications platforms that include voice.
>>>
>>>
>>>
>>> WhatsApp, for instance, just completed the rollout of e2e encryption on
>>> April 5, and not just for messaging, but also for voice and video calls as
>>> well as file transfers (
>>> https://blog.whatsapp.com/10000618/end-to-end-encryption ). Just
>>> yesterday the team behind Viber announced that they will soon have e2e
>>> encryption for all clients. The app Wire ( http://wire.com ) also does
>>> e2e encryption for voice, video and group chats.
>>>
>>>
>>>
>>> In a US Congress hearing this week, a Congressman asked a Dept of
>>> Homeland Security representative if e2e encryption available in apps would
>>> have prevented this interception that happened via SS7. The DHS answer was
>>> that it would mitigate the interception of the content, although the
>>> location meta-data would still be available. (You can view the exchange
>>> via the link in this tweet:
>>> https://twitter.com/csoghoian/status/722854012567969794 )
>>>
>>>
>>>
>>> The end result is that we're definitely moving to a space where the
>>> communication over IP-based solutions will wind up being far more secure
>>> than what we had before.
>>>
>>>
>>>
>>> Interesting times,
>>>
>>> Dan
>>>
>>>
>>>
>>> --
>>>
>>>
>>>
>>> Dan York
>>>
>>> dyork at lodestar2.com +1-802-735-1624 Skype:danyork
>>>
>>> My writing -> http://www.danyork.me/
>>>
>>> http://www.danyork.com/
>>>
>>> http://twitter.com/danyork
>>>
>>
>>
>>
>> --
>>
>> Dan York
>> dyork at lodestar2.com +1-802-735-1624 Skype:danyork
>> My writing -> http://www.danyork.me/
>> http://www.danyork.com/
>> http://twitter.com/danyork
>>
>> _______________________________________________
>> 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
>
>
--
Kidd Filby
661.557.5640 (C)
http://www.linkedin.com/in/kiddfilby
April 21, 2016
SS7
by jared@compuwizz.net
I haven't used SS7 in the voice world, only touched briefly on the
messaging side of it. Would hackers be able to do the same similar attack
via SIGTRAN? I would think it would be easier to get access to a poorly
managed SIGTRAN device which would then give you SS7 access.
Or even an Asterisk box running SS7 trunks.
On Thu, Apr 21, 2016 at 1:00 PM, Dan York <dyork at lodestar2.com> wrote:
> Joseph,
>
> I noticed that in Gmail (and perhaps other email systems), the longer
> reply I wrote for Kidd was hidden because it appeared after his text.
> Here's what I wrote...
>
> what's fascinating is the recent rise in end-to-end (e2e) encryption among
> IP-based communications platforms that include voice.
>
> WhatsApp, for instance, just completed the rollout of e2e encryption on
> April 5, and not just for messaging, but also for voice and video calls as
> well as file transfers (
> https://blog.whatsapp.com/10000618/end-to-end-encryption ). Just
> yesterday the team behind Viber announced that they will soon have e2e
> encryption for all clients. The app Wire ( http://wire.com ) also does
> e2e encryption for voice, video and group chats.
>
> In a US Congress hearing this week, a Congressman asked a Dept of Homeland
> Security representative if e2e encryption available in apps would have
> prevented this interception that happened via SS7. The DHS answer was that
> it would mitigate the interception of the content, although the location
> meta-data would still be available. (You can view the exchange via the
> link in this tweet:
> https://twitter.com/csoghoian/status/722854012567969794 )
>
> The end result is that we're definitely moving to a space where the
> communication over IP-based solutions will wind up being far more secure
> than what we had before.
>
> Interesting times,
> Dan
>
> On Thu, Apr 21, 2016 at 3:45 PM, Joseph Jackson <jjackson at aninetworks.net>
> wrote:
>
>> I don?t know many places that encrypt their voice traffic.
>>
>>
>>
>>
>>
>>
>>
>> *From:* VoiceOps [mailto:voiceops-bounces at voiceops.org] *On Behalf Of *Dan
>> York
>> *Sent:* Thursday, April 21, 2016 2:45 PM
>> *To:* Kidd Filby
>> *Cc:* voiceops at voiceops.org
>> *Subject:* Re: [VoiceOps] SS7
>>
>>
>>
>> This is generally true if the calls are *unencrypted* on VoIP...
>>
>>
>>
>> On Thu, Apr 21, 2016 at 2:20 PM, Kidd Filby <kiddfilby at gmail.com> wrote:
>>
>>
>>
>> Also folks, don't forget, the same outcome of recording someone's call is
>> MUCH easier to accomplish once it is VoIP. IMHO, of course. ;-)
>>
>>
>>
>> ... BUT... what's fascinating is the recent rise in end-to-end (e2e)
>> encryption among IP-based communications platforms that include voice.
>>
>>
>>
>> WhatsApp, for instance, just completed the rollout of e2e encryption on
>> April 5, and not just for messaging, but also for voice and video calls as
>> well as file transfers (
>> https://blog.whatsapp.com/10000618/end-to-end-encryption ). Just
>> yesterday the team behind Viber announced that they will soon have e2e
>> encryption for all clients. The app Wire ( http://wire.com ) also does
>> e2e encryption for voice, video and group chats.
>>
>>
>>
>> In a US Congress hearing this week, a Congressman asked a Dept of
>> Homeland Security representative if e2e encryption available in apps would
>> have prevented this interception that happened via SS7. The DHS answer was
>> that it would mitigate the interception of the content, although the
>> location meta-data would still be available. (You can view the exchange
>> via the link in this tweet:
>> https://twitter.com/csoghoian/status/722854012567969794 )
>>
>>
>>
>> The end result is that we're definitely moving to a space where the
>> communication over IP-based solutions will wind up being far more secure
>> than what we had before.
>>
>>
>>
>> Interesting times,
>>
>> Dan
>>
>>
>>
>> --
>>
>>
>>
>> Dan York
>>
>> dyork at lodestar2.com +1-802-735-1624 Skype:danyork
>>
>> My writing -> http://www.danyork.me/
>>
>> http://www.danyork.com/
>>
>> http://twitter.com/danyork
>>
>
>
>
> --
>
> Dan York
> dyork at lodestar2.com +1-802-735-1624 Skype:danyork
> My writing -> http://www.danyork.me/
> http://www.danyork.com/
> http://twitter.com/danyork
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
April 21, 2016
SS7
by kiddfilby@gmail.com
Dan;
I totally agree with you on where the industry is headed and we will get
there. Encryption has definitely become a MUST-HAVE with the technology
change to connectionless vs. timeslot-oriented network. However, we are
not there yet. Where there is a will, there is a way... on both sides of
the coin, unfortunately.
Although some individuals are just seeing the light, security is king, in
communications, and it has been for a long time. I recall designing VSAT
systems for major corporations in the 80's, for both voice and data
applications. Their #1 priority was encryption on both. Along with this,
network isolation and ingress points MUST be key components to the design
of the deployment &/or service offering to protect both your customer and
YOUR network.
This has been a great discussion on a very important topic.
Kidd
On Thu, Apr 21, 2016 at 1:44 PM, Dan York <dyork at lodestar2.com> wrote:
> This is generally true if the calls are *unencrypted* on VoIP...
>
> On Thu, Apr 21, 2016 at 2:20 PM, Kidd Filby <kiddfilby at gmail.com> wrote:
>
>>
>> Also folks, don't forget, the same outcome of recording someone's call is
>> MUCH easier to accomplish once it is VoIP. IMHO, of course. ;-)
>>
>
> ... BUT... what's fascinating is the recent rise in end-to-end (e2e)
> encryption among IP-based communications platforms that include voice.
>
> WhatsApp, for instance, just completed the rollout of e2e encryption on
> April 5, and not just for messaging, but also for voice and video calls as
> well as file transfers (
> https://blog.whatsapp.com/10000618/end-to-end-encryption ). Just
> yesterday the team behind Viber announced that they will soon have e2e
> encryption for all clients. The app Wire ( http://wire.com ) also does
> e2e encryption for voice, video and group chats.
>
> In a US Congress hearing this week, a Congressman asked a Dept of Homeland
> Security representative if e2e encryption available in apps would have
> prevented this interception that happened via SS7. The DHS answer was that
> it would mitigate the interception of the content, although the location
> meta-data would still be available. (You can view the exchange via the
> link in this tweet:
> https://twitter.com/csoghoian/status/722854012567969794 )
>
> The end result is that we're definitely moving to a space where the
> communication over IP-based solutions will wind up being far more secure
> than what we had before.
>
> Interesting times,
> Dan
>
> --
>
> Dan York
> dyork at lodestar2.com +1-802-735-1624 Skype:danyork
> My writing -> http://www.danyork.me/
> http://www.danyork.com/
> http://twitter.com/danyork
>
--
Kidd Filby
661.557.5640 (C)
http://www.linkedin.com/in/kiddfilby
April 21, 2016
SS7
by dyork@lodestar2.com
Joseph,
I noticed that in Gmail (and perhaps other email systems), the longer reply
I wrote for Kidd was hidden because it appeared after his text. Here's
what I wrote...
what's fascinating is the recent rise in end-to-end (e2e) encryption among
IP-based communications platforms that include voice.
WhatsApp, for instance, just completed the rollout of e2e encryption on
April 5, and not just for messaging, but also for voice and video calls as
well as file transfers (
https://blog.whatsapp.com/10000618/end-to-end-encryption ). Just yesterday
the team behind Viber announced that they will soon have e2e encryption for
all clients. The app Wire ( http://wire.com ) also does e2e encryption for
voice, video and group chats.
In a US Congress hearing this week, a Congressman asked a Dept of Homeland
Security representative if e2e encryption available in apps would have
prevented this interception that happened via SS7. The DHS answer was that
it would mitigate the interception of the content, although the location
meta-data would still be available. (You can view the exchange via the
link in this tweet: https://twitter.com/csoghoian/status/722854012567969794
)
The end result is that we're definitely moving to a space where the
communication over IP-based solutions will wind up being far more secure
than what we had before.
Interesting times,
Dan
On Thu, Apr 21, 2016 at 3:45 PM, Joseph Jackson <jjackson at aninetworks.net>
wrote:
> I don?t know many places that encrypt their voice traffic.
>
>
>
>
>
>
>
> *From:* VoiceOps [mailto:voiceops-bounces at voiceops.org] *On Behalf Of *Dan
> York
> *Sent:* Thursday, April 21, 2016 2:45 PM
> *To:* Kidd Filby
> *Cc:* voiceops at voiceops.org
> *Subject:* Re: [VoiceOps] SS7
>
>
>
> This is generally true if the calls are *unencrypted* on VoIP...
>
>
>
> On Thu, Apr 21, 2016 at 2:20 PM, Kidd Filby <kiddfilby at gmail.com> wrote:
>
>
>
> Also folks, don't forget, the same outcome of recording someone's call is
> MUCH easier to accomplish once it is VoIP. IMHO, of course. ;-)
>
>
>
> ... BUT... what's fascinating is the recent rise in end-to-end (e2e)
> encryption among IP-based communications platforms that include voice.
>
>
>
> WhatsApp, for instance, just completed the rollout of e2e encryption on
> April 5, and not just for messaging, but also for voice and video calls as
> well as file transfers (
> https://blog.whatsapp.com/10000618/end-to-end-encryption ). Just
> yesterday the team behind Viber announced that they will soon have e2e
> encryption for all clients. The app Wire ( http://wire.com ) also does
> e2e encryption for voice, video and group chats.
>
>
>
> In a US Congress hearing this week, a Congressman asked a Dept of Homeland
> Security representative if e2e encryption available in apps would have
> prevented this interception that happened via SS7. The DHS answer was that
> it would mitigate the interception of the content, although the location
> meta-data would still be available. (You can view the exchange via the
> link in this tweet:
> https://twitter.com/csoghoian/status/722854012567969794 )
>
>
>
> The end result is that we're definitely moving to a space where the
> communication over IP-based solutions will wind up being far more secure
> than what we had before.
>
>
>
> Interesting times,
>
> Dan
>
>
>
> --
>
>
>
> Dan York
>
> dyork at lodestar2.com +1-802-735-1624 Skype:danyork
>
> My writing -> http://www.danyork.me/
>
> http://www.danyork.com/
>
> http://twitter.com/danyork
>
--
Dan York
dyork at lodestar2.com +1-802-735-1624 Skype:danyork
My writing -> http://www.danyork.me/
http://www.danyork.com/
http://twitter.com/danyork
April 21, 2016
SS7
by jjackson@aninetworks.net
I don?t know many places that encrypt their voice traffic.
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Dan York
Sent: Thursday, April 21, 2016 2:45 PM
To: Kidd Filby
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] SS7
This is generally true if the calls are *unencrypted* on VoIP...
On Thu, Apr 21, 2016 at 2:20 PM, Kidd Filby <kiddfilby at gmail.com<mailto:kiddfilby at gmail.com>> wrote:
Also folks, don't forget, the same outcome of recording someone's call is MUCH easier to accomplish once it is VoIP. IMHO, of course. ;-)
... BUT... what's fascinating is the recent rise in end-to-end (e2e) encryption among IP-based communications platforms that include voice.
WhatsApp, for instance, just completed the rollout of e2e encryption on April 5, and not just for messaging, but also for voice and video calls as well as file transfers ( https://blog.whatsapp.com/10000618/end-to-end-encryption ). Just yesterday the team behind Viber announced that they will soon have e2e encryption for all clients. The app Wire ( http://wire.com ) also does e2e encryption for voice, video and group chats.
In a US Congress hearing this week, a Congressman asked a Dept of Homeland Security representative if e2e encryption available in apps would have prevented this interception that happened via SS7. The DHS answer was that it would mitigate the interception of the content, although the location meta-data would still be available. (You can view the exchange via the link in this tweet: https://twitter.com/csoghoian/status/722854012567969794 )
The end result is that we're definitely moving to a space where the communication over IP-based solutions will wind up being far more secure than what we had before.
Interesting times,
Dan
--
Dan York
dyork at lodestar2.com<mailto:dyork at lodestar2.com> +1-802-735-1624 Skype:danyork
My writing -> http://www.danyork.me/
http://www.danyork.com/
http://twitter.com/danyork<http://twitter.com/danyork>
April 21, 2016
SS7
by dyork@lodestar2.com
This is generally true if the calls are *unencrypted* on VoIP...
On Thu, Apr 21, 2016 at 2:20 PM, Kidd Filby <kiddfilby at gmail.com> wrote:
>
> Also folks, don't forget, the same outcome of recording someone's call is
> MUCH easier to accomplish once it is VoIP. IMHO, of course. ;-)
>
... BUT... what's fascinating is the recent rise in end-to-end (e2e)
encryption among IP-based communications platforms that include voice.
WhatsApp, for instance, just completed the rollout of e2e encryption on
April 5, and not just for messaging, but also for voice and video calls as
well as file transfers (
https://blog.whatsapp.com/10000618/end-to-end-encryption ). Just yesterday
the team behind Viber announced that they will soon have e2e encryption for
all clients. The app Wire ( http://wire.com ) also does e2e encryption for
voice, video and group chats.
In a US Congress hearing this week, a Congressman asked a Dept of Homeland
Security representative if e2e encryption available in apps would have
prevented this interception that happened via SS7. The DHS answer was that
it would mitigate the interception of the content, although the location
meta-data would still be available. (You can view the exchange via the
link in this tweet: https://twitter.com/csoghoian/status/722854012567969794
)
The end result is that we're definitely moving to a space where the
communication over IP-based solutions will wind up being far more secure
than what we had before.
Interesting times,
Dan
--
Dan York
dyork at lodestar2.com +1-802-735-1624 Skype:danyork
My writing -> http://www.danyork.me/
http://www.danyork.com/
http://twitter.com/danyork
April 21, 2016
SS7
by peeip989@gmail.com
It's been a decade since I've touched SS7, and I barely remember what I had for breakfast, so it's like it's all new to me again.
>From what I read, it sounds like there may be a "proxy" function that can be injected which would bring both endpoints back to you so you can record both legs. The 60 Minutes piece shows exactly that. And, while it was done in seconds for TV, we all know there was a lot of prep work required ahead of time to make it that simple.
Question, though: does the proliferation of SMS gateway services open a security risk since they may be bridging IP to SS7?
On Apr 21, 2016, at 14:13, Paul Timmins <paul at timmins.net> wrote:
You could do it by saying "hey, this handset is roaming on me" then directing the call back to the handset in question, I figure. It would be inbound only intercept, but i could see that working.
-Paul
> On 04/21/2016 02:12 PM, Matthew Yaklin wrote:
>
> The part I was curious about and perhaps someone can clarify who has more knowledge than I is...
>
>
> It appears in order to record calls the attacker has to be in very close proximity to the target. Like radio/tower range.
>
> You cannot record a conversation half way across the world.
>
>
> Matt
>
>
>
>
> From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Matthew Yaklin <myaklin at firstlight.net>
> Sent: Thursday, April 21, 2016 2:09 PM
> To: Kidd Filby; Chris Aloi
> Cc: voiceops at voiceops.org
> Subject: Re: [VoiceOps] SS7
>
>
> Here is a paper that may shed some light on the discussion for the curious.
>
>
> https://www.sans.org/reading-room/whitepapers/critical/fall-ss7--critical-s…
>
> SANS Institute InfoSec Reading Room
> www.sans.org
> The Fall of SS7 ? How Can the Critical Security Controls Help? 4 " #$$#%!&'()#*+!"#$$#%,-')#*./-#01,2'-! area notices this registration and transfers to a Visitor ...
>
>
>
>
>
> From: Kidd Filby <kiddfilby at gmail.com>
> Sent: Thursday, April 21, 2016 2:01 PM
> To: Chris Aloi
> Cc: Matthew Yaklin; voiceops at voiceops.org
> Subject: Re: [VoiceOps] SS7
>
> In a strictly TDM world, or conversation... having access to the SS7 network gets you nothing but what and where the call traversed. NO audio is carried and without End Office controlling software for call routing, just dropping it into some IP connection is not going to afford you anything other than what you already have. You still need access to the audio carrying infrastructure of the network to get the audio.
>
> I cannot comment on CALEA
>
> Kidd
>
>> On Thu, Apr 21, 2016 at 10:56 AM, Chris Aloi <ctaloi at gmail.com> wrote:
>> It looked like they had access to SS7 links (likely A links terminated to a physical server) and were using FreeSWITCH to somehow fork the media from the call and record it. Just a guess based on the quick console recording.
>>
>> Correct, SS7 doesn't carry the actual voice it handles the signaling to bring up the voice channels (by identifying be point code and CICs) and various other signaling bits. Not sure if there are provisions for CALEA in SS7 that could fork a media stream or exactly how that would work.
>>
>> So I guess the barrier to entry would be access to the SS7 network, not as easy as hopping on the Internet, but certainly not much of a challenge.
>>
>> ---
>> Christopher Aloi
>> Sent from my iPhone
>>
>> On Apr 21, 2016, at 11:52 AM, Kidd Filby <kiddfilby at gmail.com> wrote:
>>
>>> There is no VOICE traversing the SS7 network, so you cannot possibly record a conversation by having access to the SS7 network only.
>>>
>>>> On Thu, Apr 21, 2016 at 9:36 AM, Matthew Yaklin <myaklin at firstlight.net> wrote:
>>>>
>>>> In other words the hacker has to have working SS7 trunks or access to someone who does? That is how I understood it.
>>>>
>>>> Not exactly a remote hack from mom's basement sort of thing.
>>>>
>>>> Matt
>>>>
>>>> ________________________________________
>>>> From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Peter Rad. <peter at 4isps.com>
>>>> Sent: Thursday, April 21, 2016 11:25 AM
>>>> To: voiceops at voiceops.org
>>>> Subject: [VoiceOps] SS7
>>>>
>>>> FYI...
>>>>
>>>> U.S. carriers mum on 60 Minutes report on vulnerability in SS7 -
>>>> http://www.fiercewireless.com/story/us-carriers-mum-60-minutes-report-vulne…
>>>>
>>>> Regards,
>>>>
>>>> Peter Radizeski
>>>> RAD-INFO, Inc.
>>>> 813.963.5884
>>>> http://rad-info.net
>>>> * Need bandwidth or colocation? call me
>>>> _______________________________________________
>>>> 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
>>>
>>>
>>>
>>> --
>>> Kidd Filby
>>> 661.557.5640 (C)
>>> http://www.linkedin.com/in/kiddfilby
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org
>>> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
> --
> Kidd Filby
> 661.557.5640 (C)
> http://www.linkedin.com/in/kiddfilby
>
>
> _______________________________________________
> 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
April 21, 2016