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
- 14 participants
- 10512 messages
SS7 Landscape
by voiceops@ics-il.net
*nods* We take SIGTRAN over IPSec over the public Internet, then convert to SS7 over DS1s in some old Ciscos.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
----- Original Message -----
From: "Nick Olsen" <nick at 141networks.com>
To: "Mike Hammett" <voiceops at ics-il.net>
Cc: "Mary Lou Carey" <marylou at backuptelecom.com>, "voiceops" <voiceops at voiceops.org>
Sent: Wednesday, October 11, 2023 6:04:03 PM
Subject: Re: [VoiceOps] SS7 Landscape
We use them at $DAYJOB. We've had no issues with syniverse themselves in the recent years while I've been at the company. But plenty of issues with the transport providers to reach them. Luckily never both at the same time. Including a number of instances of flapping. Note, these are A-Links over TDM, not SIGTRAN at this time.
On Wed, Oct 11, 2023 at 4:22 PM Mike Hammett via VoiceOps < voiceops at voiceops.org > wrote:
Anyone in here using Syniverse for these services and can speak to their reliability?
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
From: "Mary Lou Carey" < marylou at backuptelecom.com >
To: "Mike Hammett" < voiceops at ics-il.net >
Cc: "voiceops" < voiceops at voiceops.org >
Sent: Tuesday, January 25, 2022 11:59:14 AM
Subject: Re: [VoiceOps] SS7 Landscape
There are pros and cons to everything. It sounds like in your case you
may just want to keep your ISUP trunks and SS7 links, but maybe look at
another provider for SS7. Syniverse is also an option but I'm not sure
if their service has gone downhill like TNS' apparently has.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2022-01-25 10:38 AM, Mike Hammett wrote:
> Right, but as I said earlier, I'm already in the same building as the
> tandem, so I'm just adding points of failure for moving an existing
> operation somewhere else.
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
> Midwest Internet Exchange
> http://www.midwest-ix.com
>
> -------------------------
>
> From: "Mary Lou Carey" < marylou at backuptelecom.com >
> To: "Mike Hammett" < voiceops at ics-il.net >
> Cc: "Paul Timmins" < paul at timmins.net >, "voiceops"
> < voiceops at voiceops.org >
> Sent: Monday, January 24, 2022 10:42:22 PM
> Subject: Re: [VoiceOps] SS7 Landscape
>
> When you use a PSTN connection provider you route your traffic to them
>
> via SIP and they handle all the SS7 so you can eliminate your direct
> LIS
> trunks with the LEC and your SS7 Links.
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
> On 2022-01-23 05:33 AM, Mike Hammett wrote:
>> Well right, but wouldn't I still need all of the same stuff (perhaps
> a
>> few less trunks to specific switches, only now I have fewer minutes
> to
>> spread the costs over?
>>
>> -----
>> Mike Hammett
>> Intelligent Computing Solutions
>> http://www.ics-il.com
>>
>> Midwest Internet Exchange
>> http://www.midwest-ix.com
>>
>> -------------------------
>>
>> From: "Paul Timmins" < paul at timmins.net >
>> To: "Mike Hammett" < voiceops at ics-il.net >
>> Cc: "voiceops" < voiceops at voiceops.org >
>> Sent: Sunday, January 23, 2022 12:01:01 AM
>> Subject: Re: [VoiceOps] SS7 Landscape
>>
>> Even without IPES you can switch your feature group D to voip
> through
>> these aggregators and get rid of basically everything that isn't the
>> local LEC's legacy network.
>>
>>> On Jan 22, 2022, at 7:03 PM, Mike Hammett < voiceops at ics-il.net >
>>> wrote:
>>>
>>> Sure, but then I just transfer the problem to someone else, until
>>> the traditional PSTN goes away or modernizes. I am working on IPES
>>> for expansion markets, though.
>>>
>>> Also, for my home LATA, I'm needing to be in the same building as
>>> the primary tandem, so it's kind of a selling point for large
>>> customers in that area that I would have fewer opportunities for
>>> failures. I don't have to go to Chicago and back to get to the
>>> operator in the next row of racks over. Though, I suppose my SS7
>>> diversity and availability is the weakness, not the actual call
>>> path.
>>>
>>> -----
>>> Mike Hammett
>>> Intelligent Computing Solutions
>>> http://www.ics-il.com [1]
>>>
>>> Midwest Internet Exchange
>>> http://www.midwest-ix.com [2]
>>>
>>> -------------------------
>>>
>>> From: "Paul Timmins" < paul at timmins.net >
>>> To: "Mike Hammett" < voiceops at ics-il.net >
>>> Cc: "voiceops" < voiceops at voiceops.org >
>>> Sent: Saturday, January 22, 2022 1:46:46 PM
>>> Subject: Re: [VoiceOps] SS7 Landscape
>>>
>>> Reduce your reliance on it more and more. Switch to IP tandems
>>> (Inteliquent/Peerless/etc) and ip interconnect. The people who make
>>> and support SS7 equipment are in a dying market, the brain drain on
>>> it is immense as people retire, and the longer you rely on it, the
>>> worse it's gonna get.
>>>
>>> TNS is a big dog in the space. But that's not saying much anymore.
>>>
>>>> On Jan 22, 2022, at 10:00 AM, Mike Hammett < voiceops at ics-il.net >
>>>> wrote:
>>>>
>>>> We currently get our SS7 via TNS. I (maybe incorrectly) understand
>>>> them to be a big dog in that space.
>>>>
>>>> I've had two major problems with them in six months.
>>>>
>>>> What are my alternatives? Are they less pleasant?
>>>>
>>>> -----
>>>> Mike Hammett
>>>> Intelligent Computing Solutions
>>>> http://www.ics-il.com [1]
>>>>
>>>> Midwest Internet Exchange
>>>> http://www.midwest-ix.com [2]
>>>>
>>>> _______________________________________________
>>>> VoiceOps mailing list
>>>> VoiceOps at voiceops.org
>>>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
>>
>> Links:
>> ------
>> [1] http://www.ics-il.com/
>> [2] http://www.midwest-ix.com/
>> _______________________________________________
>> 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
Oct. 12, 2023
SS7 Landscape
by nick@141networks.com
We use them at $DAYJOB. We've had no issues with syniverse themselves in
the recent years while I've been at the company. But plenty of issues with
the transport providers to reach them. Luckily never both at the same time.
Including a number of instances of flapping. Note, these are A-Links over
TDM, not SIGTRAN at this time.
On Wed, Oct 11, 2023 at 4:22?PM Mike Hammett via VoiceOps <
voiceops at voiceops.org> wrote:
> Anyone in here using Syniverse for these services and can speak to their
> reliability?
>
>
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
>
>
> Midwest Internet Exchange
> http://www.midwest-ix.com
>
>
>
> ------------------------------
> *From: *"Mary Lou Carey" <marylou at backuptelecom.com>
> *To: *"Mike Hammett" <voiceops at ics-il.net>
> *Cc: *"voiceops" <voiceops at voiceops.org>
> *Sent: *Tuesday, January 25, 2022 11:59:14 AM
> *Subject: *Re: [VoiceOps] SS7 Landscape
>
> There are pros and cons to everything. It sounds like in your case you
> may just want to keep your ISUP trunks and SS7 links, but maybe look at
> another provider for SS7. Syniverse is also an option but I'm not sure
> if their service has gone downhill like TNS' apparently has.
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
> On 2022-01-25 10:38 AM, Mike Hammett wrote:
> > Right, but as I said earlier, I'm already in the same building as the
> > tandem, so I'm just adding points of failure for moving an existing
> > operation somewhere else.
> >
> > -----
> > Mike Hammett
> > Intelligent Computing Solutions
> > http://www.ics-il.com
> >
> > Midwest Internet Exchange
> > http://www.midwest-ix.com
> >
> > -------------------------
> >
> > From: "Mary Lou Carey" <marylou at backuptelecom.com>
> > To: "Mike Hammett" <voiceops at ics-il.net>
> > Cc: "Paul Timmins" <paul at timmins.net>, "voiceops"
> > <voiceops at voiceops.org>
> > Sent: Monday, January 24, 2022 10:42:22 PM
> > Subject: Re: [VoiceOps] SS7 Landscape
> >
> > When you use a PSTN connection provider you route your traffic to them
> >
> > via SIP and they handle all the SS7 so you can eliminate your direct
> > LIS
> > trunks with the LEC and your SS7 Links.
> >
> > MARY LOU CAREY
> > BackUP Telecom Consulting
> > Office: 615-791-9969
> > Cell: 615-796-1111
> >
> > On 2022-01-23 05:33 AM, Mike Hammett wrote:
> >> Well right, but wouldn't I still need all of the same stuff (perhaps
> > a
> >> few less trunks to specific switches, only now I have fewer minutes
> > to
> >> spread the costs over?
> >>
> >> -----
> >> Mike Hammett
> >> Intelligent Computing Solutions
> >> http://www.ics-il.com
> >>
> >> Midwest Internet Exchange
> >> http://www.midwest-ix.com
> >>
> >> -------------------------
> >>
> >> From: "Paul Timmins" <paul at timmins.net>
> >> To: "Mike Hammett" <voiceops at ics-il.net>
> >> Cc: "voiceops" <voiceops at voiceops.org>
> >> Sent: Sunday, January 23, 2022 12:01:01 AM
> >> Subject: Re: [VoiceOps] SS7 Landscape
> >>
> >> Even without IPES you can switch your feature group D to voip
> > through
> >> these aggregators and get rid of basically everything that isn't the
> >> local LEC's legacy network.
> >>
> >>> On Jan 22, 2022, at 7:03 PM, Mike Hammett <voiceops at ics-il.net>
> >>> wrote:
> >>>
> >>> Sure, but then I just transfer the problem to someone else, until
> >>> the traditional PSTN goes away or modernizes. I am working on IPES
> >>> for expansion markets, though.
> >>>
> >>> Also, for my home LATA, I'm needing to be in the same building as
> >>> the primary tandem, so it's kind of a selling point for large
> >>> customers in that area that I would have fewer opportunities for
> >>> failures. I don't have to go to Chicago and back to get to the
> >>> operator in the next row of racks over. Though, I suppose my SS7
> >>> diversity and availability is the weakness, not the actual call
> >>> path.
> >>>
> >>> -----
> >>> Mike Hammett
> >>> Intelligent Computing Solutions
> >>> http://www.ics-il.com [1]
> >>>
> >>> Midwest Internet Exchange
> >>> http://www.midwest-ix.com [2]
> >>>
> >>> -------------------------
> >>>
> >>> From: "Paul Timmins" <paul at timmins.net>
> >>> To: "Mike Hammett" <voiceops at ics-il.net>
> >>> Cc: "voiceops" <voiceops at voiceops.org>
> >>> Sent: Saturday, January 22, 2022 1:46:46 PM
> >>> Subject: Re: [VoiceOps] SS7 Landscape
> >>>
> >>> Reduce your reliance on it more and more. Switch to IP tandems
> >>> (Inteliquent/Peerless/etc) and ip interconnect. The people who make
> >>> and support SS7 equipment are in a dying market, the brain drain on
> >>> it is immense as people retire, and the longer you rely on it, the
> >>> worse it's gonna get.
> >>>
> >>> TNS is a big dog in the space. But that's not saying much anymore.
> >>>
> >>>> On Jan 22, 2022, at 10:00 AM, Mike Hammett <voiceops at ics-il.net>
> >>>> wrote:
> >>>>
> >>>> We currently get our SS7 via TNS. I (maybe incorrectly) understand
> >>>> them to be a big dog in that space.
> >>>>
> >>>> I've had two major problems with them in six months.
> >>>>
> >>>> What are my alternatives? Are they less pleasant?
> >>>>
> >>>> -----
> >>>> Mike Hammett
> >>>> Intelligent Computing Solutions
> >>>> http://www.ics-il.com [1]
> >>>>
> >>>> Midwest Internet Exchange
> >>>> http://www.midwest-ix.com [2]
> >>>>
> >>>> _______________________________________________
> >>>> VoiceOps mailing list
> >>>> VoiceOps at voiceops.org
> >>>> https://puck.nether.net/mailman/listinfo/voiceops
> >>
> >>
> >>
> >> Links:
> >> ------
> >> [1] http://www.ics-il.com/
> >> [2] http://www.midwest-ix.com/
> >> _______________________________________________
> >> 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
>
Oct. 11, 2023
SS7 Landscape
by voiceops@ics-il.net
Anyone in here using Syniverse for these services and can speak to their reliability?
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
----- Original Message -----
From: "Mary Lou Carey" <marylou at backuptelecom.com>
To: "Mike Hammett" <voiceops at ics-il.net>
Cc: "voiceops" <voiceops at voiceops.org>
Sent: Tuesday, January 25, 2022 11:59:14 AM
Subject: Re: [VoiceOps] SS7 Landscape
There are pros and cons to everything. It sounds like in your case you
may just want to keep your ISUP trunks and SS7 links, but maybe look at
another provider for SS7. Syniverse is also an option but I'm not sure
if their service has gone downhill like TNS' apparently has.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2022-01-25 10:38 AM, Mike Hammett wrote:
> Right, but as I said earlier, I'm already in the same building as the
> tandem, so I'm just adding points of failure for moving an existing
> operation somewhere else.
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
> Midwest Internet Exchange
> http://www.midwest-ix.com
>
> -------------------------
>
> From: "Mary Lou Carey" <marylou at backuptelecom.com>
> To: "Mike Hammett" <voiceops at ics-il.net>
> Cc: "Paul Timmins" <paul at timmins.net>, "voiceops"
> <voiceops at voiceops.org>
> Sent: Monday, January 24, 2022 10:42:22 PM
> Subject: Re: [VoiceOps] SS7 Landscape
>
> When you use a PSTN connection provider you route your traffic to them
>
> via SIP and they handle all the SS7 so you can eliminate your direct
> LIS
> trunks with the LEC and your SS7 Links.
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
> On 2022-01-23 05:33 AM, Mike Hammett wrote:
>> Well right, but wouldn't I still need all of the same stuff (perhaps
> a
>> few less trunks to specific switches, only now I have fewer minutes
> to
>> spread the costs over?
>>
>> -----
>> Mike Hammett
>> Intelligent Computing Solutions
>> http://www.ics-il.com
>>
>> Midwest Internet Exchange
>> http://www.midwest-ix.com
>>
>> -------------------------
>>
>> From: "Paul Timmins" <paul at timmins.net>
>> To: "Mike Hammett" <voiceops at ics-il.net>
>> Cc: "voiceops" <voiceops at voiceops.org>
>> Sent: Sunday, January 23, 2022 12:01:01 AM
>> Subject: Re: [VoiceOps] SS7 Landscape
>>
>> Even without IPES you can switch your feature group D to voip
> through
>> these aggregators and get rid of basically everything that isn't the
>> local LEC's legacy network.
>>
>>> On Jan 22, 2022, at 7:03 PM, Mike Hammett <voiceops at ics-il.net>
>>> wrote:
>>>
>>> Sure, but then I just transfer the problem to someone else, until
>>> the traditional PSTN goes away or modernizes. I am working on IPES
>>> for expansion markets, though.
>>>
>>> Also, for my home LATA, I'm needing to be in the same building as
>>> the primary tandem, so it's kind of a selling point for large
>>> customers in that area that I would have fewer opportunities for
>>> failures. I don't have to go to Chicago and back to get to the
>>> operator in the next row of racks over. Though, I suppose my SS7
>>> diversity and availability is the weakness, not the actual call
>>> path.
>>>
>>> -----
>>> Mike Hammett
>>> Intelligent Computing Solutions
>>> http://www.ics-il.com [1]
>>>
>>> Midwest Internet Exchange
>>> http://www.midwest-ix.com [2]
>>>
>>> -------------------------
>>>
>>> From: "Paul Timmins" <paul at timmins.net>
>>> To: "Mike Hammett" <voiceops at ics-il.net>
>>> Cc: "voiceops" <voiceops at voiceops.org>
>>> Sent: Saturday, January 22, 2022 1:46:46 PM
>>> Subject: Re: [VoiceOps] SS7 Landscape
>>>
>>> Reduce your reliance on it more and more. Switch to IP tandems
>>> (Inteliquent/Peerless/etc) and ip interconnect. The people who make
>>> and support SS7 equipment are in a dying market, the brain drain on
>>> it is immense as people retire, and the longer you rely on it, the
>>> worse it's gonna get.
>>>
>>> TNS is a big dog in the space. But that's not saying much anymore.
>>>
>>>> On Jan 22, 2022, at 10:00 AM, Mike Hammett <voiceops at ics-il.net>
>>>> wrote:
>>>>
>>>> We currently get our SS7 via TNS. I (maybe incorrectly) understand
>>>> them to be a big dog in that space.
>>>>
>>>> I've had two major problems with them in six months.
>>>>
>>>> What are my alternatives? Are they less pleasant?
>>>>
>>>> -----
>>>> Mike Hammett
>>>> Intelligent Computing Solutions
>>>> http://www.ics-il.com [1]
>>>>
>>>> Midwest Internet Exchange
>>>> http://www.midwest-ix.com [2]
>>>>
>>>> _______________________________________________
>>>> VoiceOps mailing list
>>>> VoiceOps at voiceops.org
>>>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
>>
>> Links:
>> ------
>> [1] http://www.ics-il.com/
>> [2] http://www.midwest-ix.com/
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
Oct. 11, 2023
SS7 Landscape
by voiceops@ics-il.net
Has anyone in here done this with Frontier? They're our ILEC and tandem operator.
Is that aspect of Frontier reliable?
Is that aspect of Frontier any less money than what I'd be paying now?
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
----- Original Message -----
From: "Matthew Crocker" <matthew at corp.crocker.com>
To: "Mike Hammett" <voiceops at ics-il.net>
Cc: "Mary Lou Carey" <marylou at backuptelecom.com>, "voiceops" <voiceops at voiceops.org>
Sent: Tuesday, January 25, 2022 1:01:44 PM
Subject: Re: [VoiceOps] SS7 Landscape
Can you order SS7 links directly to the tandem (f-links?). Should just be a internal cross connect in the building. Then you build ISUP routes for the tandem point code over the direct links with backups over your current A- links
On Jan 25, 2022, at 1:15 PM, Mike Hammett <voiceops at ics-il.net> wrote:
<blockquote>
CAUTION: This email originated from outside of Crocker. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Oh, sure. Pros and cons to everything.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
----- Original Message -----
From: "Mary Lou Carey" <marylou at backuptelecom.com>
To: "Mike Hammett" <voiceops at ics-il.net>
Cc: "voiceops" <voiceops at voiceops.org>
Sent: Tuesday, January 25, 2022 11:59:14 AM
Subject: Re: [VoiceOps] SS7 Landscape
There are pros and cons to everything. It sounds like in your case you
may just want to keep your ISUP trunks and SS7 links, but maybe look at
another provider for SS7. Syniverse is also an option but I'm not sure
if their service has gone downhill like TNS' apparently has.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2022-01-25 10:38 AM, Mike Hammett wrote:
> Right, but as I said earlier, I'm already in the same building as the
> tandem, so I'm just adding points of failure for moving an existing
> operation somewhere else.
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
> Midwest Internet Exchange
> http://www.midwest-ix.com
>
> -------------------------
>
> From: "Mary Lou Carey" <marylou at backuptelecom.com>
> To: "Mike Hammett" <voiceops at ics-il.net>
> Cc: "Paul Timmins" <paul at timmins.net>, "voiceops"
> <voiceops at voiceops.org>
> Sent: Monday, January 24, 2022 10:42:22 PM
> Subject: Re: [VoiceOps] SS7 Landscape
>
> When you use a PSTN connection provider you route your traffic to them
>
> via SIP and they handle all the SS7 so you can eliminate your direct
> LIS
> trunks with the LEC and your SS7 Links.
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
> On 2022-01-23 05:33 AM, Mike Hammett wrote:
>> Well right, but wouldn't I still need all of the same stuff (perhaps
> a
>> few less trunks to specific switches, only now I have fewer minutes
> to
>> spread the costs over?
>>
>> -----
>> Mike Hammett
>> Intelligent Computing Solutions
>> http://www.ics-il.com
>>
>> Midwest Internet Exchange
>> http://www.midwest-ix.com
>>
>> -------------------------
>>
>> From: "Paul Timmins" <paul at timmins.net>
>> To: "Mike Hammett" <voiceops at ics-il.net>
>> Cc: "voiceops" <voiceops at voiceops.org>
>> Sent: Sunday, January 23, 2022 12:01:01 AM
>> Subject: Re: [VoiceOps] SS7 Landscape
>>
>> Even without IPES you can switch your feature group D to voip
> through
>> these aggregators and get rid of basically everything that isn't the
>> local LEC's legacy network.
>>
>>> On Jan 22, 2022, at 7:03 PM, Mike Hammett <voiceops at ics-il.net>
>>> wrote:
>>>
>>> Sure, but then I just transfer the problem to someone else, until
>>> the traditional PSTN goes away or modernizes. I am working on IPES
>>> for expansion markets, though.
>>>
>>> Also, for my home LATA, I'm needing to be in the same building as
>>> the primary tandem, so it's kind of a selling point for large
>>> customers in that area that I would have fewer opportunities for
>>> failures. I don't have to go to Chicago and back to get to the
>>> operator in the next row of racks over. Though, I suppose my SS7
>>> diversity and availability is the weakness, not the actual call
>>> path.
>>>
>>> -----
>>> Mike Hammett
>>> Intelligent Computing Solutions
>>> http://www.ics-il.com [1]
>>>
>>> Midwest Internet Exchange
>>> http://www.midwest-ix.com [2]
>>>
>>> -------------------------
>>>
>>> From: "Paul Timmins" <paul at timmins.net>
>>> To: "Mike Hammett" <voiceops at ics-il.net>
>>> Cc: "voiceops" <voiceops at voiceops.org>
>>> Sent: Saturday, January 22, 2022 1:46:46 PM
>>> Subject: Re: [VoiceOps] SS7 Landscape
>>>
>>> Reduce your reliance on it more and more. Switch to IP tandems
>>> (Inteliquent/Peerless/etc) and ip interconnect. The people who make
>>> and support SS7 equipment are in a dying market, the brain drain on
>>> it is immense as people retire, and the longer you rely on it, the
>>> worse it's gonna get.
>>>
>>> TNS is a big dog in the space. But that's not saying much anymore.
>>>
>>>> On Jan 22, 2022, at 10:00 AM, Mike Hammett <voiceops at ics-il.net>
>>>> wrote:
>>>>
>>>> We currently get our SS7 via TNS. I (maybe incorrectly) understand
>>>> them to be a big dog in that space.
>>>>
>>>> I've had two major problems with them in six months.
>>>>
>>>> What are my alternatives? Are they less pleasant?
>>>>
>>>> -----
>>>> Mike Hammett
>>>> Intelligent Computing Solutions
>>>> http://www.ics-il.com [1]
>>>>
>>>> Midwest Internet Exchange
>>>> http://www.midwest-ix.com [2]
>>>>
>>>> _______________________________________________
>>>> VoiceOps mailing list
>>>> VoiceOps at voiceops.org
>>>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
>>
>> Links:
>> ------
>> [1] http://www.ics-il.com/
>> [2] http://www.midwest-ix.com/
>> _______________________________________________
>> 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
</blockquote>
Oct. 11, 2023
CSR Best Practices
by caalvarez@gmail.com
I am not a lawyer, and our legal advice on this is old, but it?s the model
we follow. A CSR only goes to the authorized contact on our account
records. We only had one or two requests from another vendor, and just
said that we only give this to the customer due to CPNI, and they were good
with that. I just have a template PDF for each of our upstreams that gives
the customer instructions on what to put on the porting form, and then a
list of numbers they own is pasted in.
On Oct 10, 2023 at 9:49:46?AM, Mike Hammett via VoiceOps <
voiceops at voiceops.org> wrote:
> We recently received a CSR request. I was asked how we're supposed to
> respond. Looking through what we had sent out in the past was... less than
> satisfactory to me. It seemed too simplistic.
>
> Unfortunately, when I Googled for additional input, I got a range of:
>
> "Ask your provider, they'll know" I am the provider and I don't know,
> which is why I'm searching
> Some companies only send CSRs to customers
> Some companies only send CSRs to carriers
> Some companies don't send CSRs at all
>
>
> Are there any best practices out there regarding what should be sent to
> whom and what authorization is checked before sending?
>
>
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
>
>
> Midwest Internet Exchange
> http://www.midwest-ix.com
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
Oct. 10, 2023
CSR Best Practices
by marylou@backuptelecom.com
With the ILECs, CSRs can be provided to customers and carriers that have
an LOA from the customer. The ILEC CSRs include the following
information:
Address of service location
Address of billing location
List of all services with circuit identifiers
Breakdown of the billing components that make up the price for each
service.
List of all TNs associated with each service (if applicable)
Associated circuits connected to that service (if applicable)
If the CSR uses industry codes, the definition of the industry code
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2023-10-10 11:49 AM, Mike Hammett via VoiceOps wrote:
> We recently received a CSR request. I was asked how we're supposed to
> respond. Looking through what we had sent out in the past was... less
> than satisfactory to me. It seemed too simplistic.
>
> Unfortunately, when I Googled for additional input, I got a range of:
>
> "Ask your provider, they'll know" I am the provider and I don't know,
> which is why I'm searching
> Some companies only send CSRs to customers
> Some companies only send CSRs to carriers
> Some companies don't send CSRs at all
>
> Are there any best practices out there regarding what should be sent
> to whom and what authorization is checked before sending?
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
> Midwest Internet Exchange
> http://www.midwest-ix.com
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Oct. 10, 2023
CSR Best Practices
by voiceops@ics-il.net
We recently received a CSR request. I was asked how we're supposed to respond. Looking through what we had sent out in the past was... less than satisfactory to me. It seemed too simplistic.
Unfortunately, when I Googled for additional input, I got a range of:
"Ask your provider, they'll know" I am the provider and I don't know, which is why I'm searching
Some companies only send CSRs to customers
Some companies only send CSRs to carriers
Some companies don't send CSRs at all
Are there any best practices out there regarding what should be sent to whom and what authorization is checked before sending?
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
Oct. 10, 2023
IPAWS/FEMA National Test - VoWIFI
by jared@compuwizz.net
The alert was also not received on my DISH phone, a Project Genesis device
that was on native DISH 5G.
On Wed, Oct 4, 2023 at 4:33?PM Nathan Anderson via VoiceOps <
voiceops at voiceops.org> wrote:
> ...huh.
>
>
> https://cacm.acm.org/magazines/2021/10/255719-securing-the-wireless-emergen…
>
> Guess it is delivered over a separate interface to the MME than SMS would
> be.
>
> Kinda boggles the mind that "WEA over IMS" isn't a thing.
>
> Perhaps it's an issue of scalability? WEA messages over NAS presumably
> doesn't require that much overhead: MME sends the message out to all eNBs,
> who in turn I'd guess would just indiscriminately transmit it to all
> attached UEs. More broadcast-y than unicast-y. Whereas I guess an
> IMS-based solution would require the CSCF to enumerate all active
> registrations and then transmit a SIP message individually to each
> subscriber, one-by-one.
>
> Still, the lack of at least some IP-based way of accomplishing this seems
> like a huge oversight, especially in an age where it seems like more people
> (especially in more rural areas) are more reliant on VoWiFi than ever
> before in order to have any use whatsoever of their mobile voice service
> while at home.
>
> -- Nathan
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Nathan
> Anderson via VoiceOps
> Sent: Wednesday, October 4, 2023 3:53 PM
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] IPAWS/FEMA National Test - VoWIFI
>
> Darn...it actually had occurred to me to test this very thing by forcing
> airplane mode and then enabling WiFi, but then spaced it and didn't manage
> to do that before the broadcast went out!
>
> Assuming I'd actually managed to run the test, I was actually fully
> prepared to be surprised if I had NOT gotten the test broadcast while
> exclusively on WiFi Calling. It seems bizarre to me to learn that WEAs are
> dependent on the same NAS CP messages that non-IP-based SMS over LTE is
> also dependent on...can this really be true?? This is strange because it
> would require that all mobile carriers continue to run and maintain a 2G
> core, since (as far as I know) SMS can only be encapsulated within LTE NAS
> by way of the SGs interface. (Perhaps there is some separate interface
> over which WEA payloads specifically are sent to the MME?)
>
> Some months ago -- but well after the 3G UMTS shutdown had taken place --
> I found that my ability to use SMS on the AT&T network had suddenly broken
> in a weird way, and ONLY worked over WiFi. Which was naturally a *wee* bit
> inconvenient. After digging into it over a few days, I figured out that
> the SMS over IP (IMS) setting in my (non-5G) handset's baseband was
> disabled. And apparently this setting is ignored when you are on VoWiFi,
> since IMS is literally the only way to deliver SMS over ePDG. I enabled it
> & that fixed my problem with SMS over LTE. I did some back-and-forth
> testing and every time I re-disabled that baseband setting, SMS over LTE
> broke again. I took this all as a sign that AT&T was probably looking to
> retire their entire 2G/3G core, though admittedly I haven't tried forcing
> the same handset back to SMS-over-SGs since then in order to see if maybe
> this was just a temporary (yet prolonged) glitch on their side.
>
> -- Nathan
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Jay R.
> Ashworth via VoiceOps
> Sent: Wednesday, October 4, 2023 2:08 PM
> To: jra
> Cc: VoiceOps
> Subject: Re: [VoiceOps] IPAWS/FEMA National Test - VoWIFI
>
> I now have a counter report that the Cellular Control Channel necessary to
> get
> these alerts to a cellphone *is not proxied by carrier WIFI-connect*, by
> design.
>
> I'm familiar with his credentials, and I'll assume he knows what he's
> talking about,
> cause *I* know what he's talking about, and he sounds like he's talking
> sense. :-)
>
> Thanks to everyone who responded.
>
> If you *did* get an alert, *and you know you were not in range of ANY cell
> network*,
> only WIFI proxy, that wasn't supposed to be possible and I would still
> like to hear
> about that.
>
> Cheers,
> -- jr 'just zis guy, you know?' a
>
> ----- Original Message -----
> > From: "Jay R. Ashworth via VoiceOps" <voiceops at voiceops.org>
> > To: "VoiceOps" <voiceops at voiceops.org>
> > Sent: Wednesday, October 4, 2023 3:25:04 PM
> > Subject: [VoiceOps] IPAWS/FEMA National Test - VoWIFI
>
> > I have a report from a usually reliable source that he did not receive
> today's
> > IPAWS/CMAS/WEA test message, and he surmises this might be because his
> phone
> > handset is forced to VoWIFI. I have a number of other reports, mostly
> though
> > not all, from the broadcast engineering community; nobody reported
> expecting
> > a CMAS and not getting it, so that's not data here.
> >
> > Is anyone on the list involved with the FEMA/IPAWS/CMAS link, or knows
> someone
> > who is, and has a channel to clear this query up through?
> >
> > I could be unsurprised to find that the carrier VoWIFI proxies missed
> out on
> > proxying SMS Cell Broadcast, which I gather provides the underlying PHY
> for
> > CMAS.
> >
> > Cheers,
> > -- jra
> >
> > --
> > Jay R. Ashworth Baylink
> jra at baylink.com
> > Designer The Things I Think
> RFC 2100
> > Ashworth & Associates http://www.bcp38.info 2000 Land
> Rover DII
> > St Petersburg FL USA BCP38: Ask For It By Name! +1 727
> 647 1274
> > _______________________________________________
> > VoiceOps mailing list
> > VoiceOps at voiceops.org
> > https://puck.nether.net/mailman/listinfo/voiceops
>
> --
> Jay R. Ashworth Baylink
> jra at baylink.com
> Designer The Things I Think RFC
> 2100
> Ashworth & Associates http://www.bcp38.info 2000 Land
> Rover DII
> St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647
> 1274
> _______________________________________________
> 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
>
Oct. 6, 2023
IPAWS/FEMA National Test - VoWIFI
by nathana@fsr.com
...huh.
https://cacm.acm.org/magazines/2021/10/255719-securing-the-wireless-emergen…
Guess it is delivered over a separate interface to the MME than SMS would be.
Kinda boggles the mind that "WEA over IMS" isn't a thing.
Perhaps it's an issue of scalability? WEA messages over NAS presumably doesn't require that much overhead: MME sends the message out to all eNBs, who in turn I'd guess would just indiscriminately transmit it to all attached UEs. More broadcast-y than unicast-y. Whereas I guess an IMS-based solution would require the CSCF to enumerate all active registrations and then transmit a SIP message individually to each subscriber, one-by-one.
Still, the lack of at least some IP-based way of accomplishing this seems like a huge oversight, especially in an age where it seems like more people (especially in more rural areas) are more reliant on VoWiFi than ever before in order to have any use whatsoever of their mobile voice service while at home.
-- Nathan
-----Original Message-----
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Nathan Anderson via VoiceOps
Sent: Wednesday, October 4, 2023 3:53 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] IPAWS/FEMA National Test - VoWIFI
Darn...it actually had occurred to me to test this very thing by forcing airplane mode and then enabling WiFi, but then spaced it and didn't manage to do that before the broadcast went out!
Assuming I'd actually managed to run the test, I was actually fully prepared to be surprised if I had NOT gotten the test broadcast while exclusively on WiFi Calling. It seems bizarre to me to learn that WEAs are dependent on the same NAS CP messages that non-IP-based SMS over LTE is also dependent on...can this really be true?? This is strange because it would require that all mobile carriers continue to run and maintain a 2G core, since (as far as I know) SMS can only be encapsulated within LTE NAS by way of the SGs interface. (Perhaps there is some separate interface over which WEA payloads specifically are sent to the MME?)
Some months ago -- but well after the 3G UMTS shutdown had taken place -- I found that my ability to use SMS on the AT&T network had suddenly broken in a weird way, and ONLY worked over WiFi. Which was naturally a *wee* bit inconvenient. After digging into it over a few days, I figured out that the SMS over IP (IMS) setting in my (non-5G) handset's baseband was disabled. And apparently this setting is ignored when you are on VoWiFi, since IMS is literally the only way to deliver SMS over ePDG. I enabled it & that fixed my problem with SMS over LTE. I did some back-and-forth testing and every time I re-disabled that baseband setting, SMS over LTE broke again. I took this all as a sign that AT&T was probably looking to retire their entire 2G/3G core, though admittedly I haven't tried forcing the same handset back to SMS-over-SGs since then in order to see if maybe this was just a temporary (yet prolonged) glitch on their side.
-- Nathan
-----Original Message-----
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Jay R. Ashworth via VoiceOps
Sent: Wednesday, October 4, 2023 2:08 PM
To: jra
Cc: VoiceOps
Subject: Re: [VoiceOps] IPAWS/FEMA National Test - VoWIFI
I now have a counter report that the Cellular Control Channel necessary to get
these alerts to a cellphone *is not proxied by carrier WIFI-connect*, by design.
I'm familiar with his credentials, and I'll assume he knows what he's talking about,
cause *I* know what he's talking about, and he sounds like he's talking sense. :-)
Thanks to everyone who responded.
If you *did* get an alert, *and you know you were not in range of ANY cell network*,
only WIFI proxy, that wasn't supposed to be possible and I would still like to hear
about that.
Cheers,
-- jr 'just zis guy, you know?' a
----- Original Message -----
> From: "Jay R. Ashworth via VoiceOps" <voiceops at voiceops.org>
> To: "VoiceOps" <voiceops at voiceops.org>
> Sent: Wednesday, October 4, 2023 3:25:04 PM
> Subject: [VoiceOps] IPAWS/FEMA National Test - VoWIFI
> I have a report from a usually reliable source that he did not receive today's
> IPAWS/CMAS/WEA test message, and he surmises this might be because his phone
> handset is forced to VoWIFI. I have a number of other reports, mostly though
> not all, from the broadcast engineering community; nobody reported expecting
> a CMAS and not getting it, so that's not data here.
>
> Is anyone on the list involved with the FEMA/IPAWS/CMAS link, or knows someone
> who is, and has a channel to clear this query up through?
>
> I could be unsurprised to find that the carrier VoWIFI proxies missed out on
> proxying SMS Cell Broadcast, which I gather provides the underlying PHY for
> CMAS.
>
> Cheers,
> -- jra
>
> --
> Jay R. Ashworth Baylink jra at baylink.com
> Designer The Things I Think RFC 2100
> Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII
> St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
--
Jay R. Ashworth Baylink jra at baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII
St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
_______________________________________________
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
Oct. 4, 2023
IPAWS/FEMA National Test - VoWIFI
by nathana@fsr.com
Darn...it actually had occurred to me to test this very thing by forcing airplane mode and then enabling WiFi, but then spaced it and didn't manage to do that before the broadcast went out!
Assuming I'd actually managed to run the test, I was actually fully prepared to be surprised if I had NOT gotten the test broadcast while exclusively on WiFi Calling. It seems bizarre to me to learn that WEAs are dependent on the same NAS CP messages that non-IP-based SMS over LTE is also dependent on...can this really be true?? This is strange because it would require that all mobile carriers continue to run and maintain a 2G core, since (as far as I know) SMS can only be encapsulated within LTE NAS by way of the SGs interface. (Perhaps there is some separate interface over which WEA payloads specifically are sent to the MME?)
Some months ago -- but well after the 3G UMTS shutdown had taken place -- I found that my ability to use SMS on the AT&T network had suddenly broken in a weird way, and ONLY worked over WiFi. Which was naturally a *wee* bit inconvenient. After digging into it over a few days, I figured out that the SMS over IP (IMS) setting in my (non-5G) handset's baseband was disabled. And apparently this setting is ignored when you are on VoWiFi, since IMS is literally the only way to deliver SMS over ePDG. I enabled it & that fixed my problem with SMS over LTE. I did some back-and-forth testing and every time I re-disabled that baseband setting, SMS over LTE broke again. I took this all as a sign that AT&T was probably looking to retire their entire 2G/3G core, though admittedly I haven't tried forcing the same handset back to SMS-over-SGs since then in order to see if maybe this was just a temporary (yet prolonged) glitch on their side.
-- Nathan
-----Original Message-----
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Jay R. Ashworth via VoiceOps
Sent: Wednesday, October 4, 2023 2:08 PM
To: jra
Cc: VoiceOps
Subject: Re: [VoiceOps] IPAWS/FEMA National Test - VoWIFI
I now have a counter report that the Cellular Control Channel necessary to get
these alerts to a cellphone *is not proxied by carrier WIFI-connect*, by design.
I'm familiar with his credentials, and I'll assume he knows what he's talking about,
cause *I* know what he's talking about, and he sounds like he's talking sense. :-)
Thanks to everyone who responded.
If you *did* get an alert, *and you know you were not in range of ANY cell network*,
only WIFI proxy, that wasn't supposed to be possible and I would still like to hear
about that.
Cheers,
-- jr 'just zis guy, you know?' a
----- Original Message -----
> From: "Jay R. Ashworth via VoiceOps" <voiceops at voiceops.org>
> To: "VoiceOps" <voiceops at voiceops.org>
> Sent: Wednesday, October 4, 2023 3:25:04 PM
> Subject: [VoiceOps] IPAWS/FEMA National Test - VoWIFI
> I have a report from a usually reliable source that he did not receive today's
> IPAWS/CMAS/WEA test message, and he surmises this might be because his phone
> handset is forced to VoWIFI. I have a number of other reports, mostly though
> not all, from the broadcast engineering community; nobody reported expecting
> a CMAS and not getting it, so that's not data here.
>
> Is anyone on the list involved with the FEMA/IPAWS/CMAS link, or knows someone
> who is, and has a channel to clear this query up through?
>
> I could be unsurprised to find that the carrier VoWIFI proxies missed out on
> proxying SMS Cell Broadcast, which I gather provides the underlying PHY for
> CMAS.
>
> Cheers,
> -- jra
>
> --
> Jay R. Ashworth Baylink jra at baylink.com
> Designer The Things I Think RFC 2100
> Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII
> St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
--
Jay R. Ashworth Baylink jra at baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII
St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Oct. 4, 2023