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
August 2019
- 16 participants
- 36 messages
CLEC - STIR/SHAKEN
by calvin.ellison@voxox.com
An update on this topic:
https://sites.atis.org/insights/sti-ga-executes-iconectiv-contract-as-secur…
The STI-GA Board determined that an entity must meet the following criteria
to access STI certificates:
1. Have a current FCC Form 499A on file with the FCC (filed by all
intrastate, interstate, and international providers of telecommunications
(including VoIP providers) within the United States, with limited
exceptions)
2. Have an Operating Company Number (OCN)
3. Have direct access to telephone numbers from the North American
Number Plan Administrator (NANPA) and National Pooling Administrator (NPA)
[1
<https://sites.atis.org/insights/sti-ga-executes-iconectiv-contract-as-secur…>
]
1. While the access limitation is reasonable, signing a given call
should not be limited to only the pool of numbers available to the provider
via direct access. In other words, per ATIS-100074, 5.2.3, under correct
conditions a qualified service provider (SP) must be allowed to sign leased
numbers as well as other numbers belonging to an OCN not assigned to that
qualified SP insofar as the SP can properly verify the customer?s
authorized use of that number.
Regards,
*Calvin Ellison*
Senior Voice Operations Engineer
calvin.ellison at voxox.com
+1 (213) 285-0555
-----------------------------------------------
*voxox.com <http://www.voxox.com/> *
5825 Oberlin Drive, Suite 5
San Diego, CA 92121
[image: Voxox]
Aug. 27, 2019
CLEC - STIR/SHAKEN
by calvine@gmail.com
I spoke with NECA on the phone today and they confirmed IPES OCN can be
issued with only the documents I quoted from their website. They said some
VoIP companies who don't have their own numbering resources still get an
OCN because the partners they are connected to want them to have one. I'm
hoping this might be a solution for wholesale providers and international
gateways who want to sign calls at Attestation Level B or C. Certificate
Delegation doesn't address this.
Full Attestation (A) ? The service provider has authenticated the calling
party and they are authorized to use the calling number. An example of this
case is a subscriber registered with the originating telephone service
provider?s softswitch.
Partial Attestation (B) ? The service provider has authenticated the call
origination, but cannot verify the call source is authorized to use the
calling number. An example of this use case is a telephone number behind an
enterprise PBX.
Gateway Attestation (C) ? The service provider has authenticated from where
it received the call, but cannot authenticate the call source. An example
of this case would be a call received from an international gateway.
https://transnexus.com/whitepapers/understanding-stir-shaken/
On Wed, Aug 21, 2019 at 7:57 AM Mary Lou Carey <marylou at backuptelecom.com>
wrote:
> My understanding is that the only VOIP carriers that can get an IPES OCN
> are Interconnected VOIP carriers. You have to get a certification from
> the FCC to become an Interconnected VOIP carrier because the
> Interconnected VOIP status allows you to order and manager your own
> NXXs.
>
> The main network difference between a CLEC and an Interconnected VOIP
> carrier is that the CLEC has a direct connection to the PSTN via their
> own SS7 links and direct trunks to the ILEC. The Interconnected VOIP
> carrier gets their connection to the PSTN through a third party carrier
> that manages the SS7 links and direct trunks to the ILEC.
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
> On 2019-08-20 07:51 PM, Calvin Ellison wrote:
> > Glen,
> >
> > What are we to do for our clients who have DID/TFN from 3rd paries? We
> > won't have any relationship with their DID provider to request a
> > delegated certificate, and wouldn't have one of our own to sign those
> > calls, even as Attestation level B or C. Does the client need to
> > request a delegated cert and provide it to each termination carrier
> > they want to use?
> >
> > I had a call with Bandwidth today was told the delegated certificates
> > would need to contain (or refer via URL) a list of which numbers are
> > permitted to be signed by that cert. I hope they've considered the
> > potential information leak here and use hashes of the permitted
> > numbers, not the numbers in cleartext.
> >
> > For what it's worth, I received confirmation from NECA that an IPES
> > OCN can be issued without an FCC waiver. This would at least let us
> > sign with level B or C.
> >
> > Query to NECA and their reply:
> >
> > Assuming I will need an OCN, I have been told that VoIP carriers that
> > are not certified by
> > the FCC as Interconnected VoIP carriers cannot be assigned an OCN.
> > This doesn't jive with the lingo on your website:
> >
> >> IPES service: Proof of service and customers, e.g., interconnection
> >> agreement (or evidence of an interconnection order pursuant to an
> >> approved tariff) and contractual agreements with end-user customers.
> >> Or, regulatory administration approval, if applicable.
> >
> > We definitely have contracted customers and definitely have
> > interconnections with DID/TFN origination carriers and termination
> > carriers. If we have no intention to obtain numbering resources
> > directly, can we still obtain an OCN?
> >
> > YES, YOU CAN STILL OBTAIN AN OCN.
> >
> > Regards,
> >
> > CALVIN ELLISON
> > Senior Voice Operations Engineer
> > calvin.ellison at voxox.com
> > +1 (213) 285-0555
> >
> > -----------------------------------------------
> > VOXOX.COM [2]
> > 5825 Oberlin Drive, Suite 5
> > San Diego, CA 92121
> >
> > On Tue, Aug 20, 2019 at 9:17 AM Glen Gerhard <glen at cognexus.net>
> > wrote:
> >
> >> Yes, I believe that is the case today. In the new "delegated
> >> certificate" model the VoIP provider (or CPaaS provider) will be
> >> provided a certificate from the OCN that is used for the ANI. This
> >> delegated certificate will give the downstream carriers A level
> >> Attestation for the calls regardless of where the outbound calls are
> >> originated.
> >>
> >> Ultimately it is the originating Enterprise that needs to be
> >> traceable from the terminating carrier. Once this relationship chain
> >> has been vetted the certificates can be delegated and used at call
> >> set up time. NetNumber has a service for brokering the Certificates
> >> but the spec is not fully adopted to my knowledge.
> >>
> >> Another proposal at ATIS is to have the sending CNAM (and expanded
> >> eCNAM) validated with a similar vetted relationship and certificate
> >> chain. Ultimately this may be more useful for both the Enterprise
> >> and the Callee than just the ANI.
> >>
> >> ~Glen
> >>
> >> On 8/16/2019 11:40, Mary Lou Carey wrote:
> >> So it sounds to me like you just have to be a certified carrier to
> >> get a STIR/SHAKEN certificate. That means either a CLEC, Wireless,
> >> or Interconnected VOIP Carrier. The VOIP carriers that are not
> >> certified by the FCC as Interconnected VOIP carriers cannot be
> >> assigned an OCN.
> >>
> >> MARY LOU CAREY
> >> BackUP Telecom Consulting
> >> Office: 615-791-9969
> >> Cell: 615-796-1111
> >>
> >> On 2019-08-16 01:32 PM, Calvin Ellison wrote:
> >> As explained to me by TransNexus, the Certificate Authorities will
> >> most likely require an OCN. VoIP carriers with their own numbering
> >> resources already have their IPES category OCN. It's also possible
> >> they might only require a SPID.
> >>
> >> Regards,
> >>
> >> CALVIN ELLISON
> >> Senior Voice Operations Engineer
> >> calvin.ellison at voxox.com
> >> +1 (213) 285-0555
> >>
> >> -----------------------------------------------
> >> VOXOX.COM [1] [1]
> >> 5825 Oberlin Drive, Suite 5
> >> San Diego, CA 92121
> >>
> >> On Fri, Aug 16, 2019 at 8:02 AM Dovid Bender <dovid at telecurve.com>
> >> wrote:
> >>
> >> Alex,
> >>
> >> You would think so. From what I understand you will need to be a LEC
> >>
> >> to get a cert.
> >>
> >> On Fri, Aug 16, 2019 at 10:33 AM Alex Balashov
> >> <abalashov at evaristesys.com> wrote:
> >>
> >> If non-LEC VoIP providers can direct own numbering resources now,
> >> it follows that they should be able to partake of STIR/SHAKEN.
> >>
> >> ?
> >> Sent from mobile, with due apologies for brevity and errors.
> >>
> >> On Aug 16, 2019, at 9:16 AM, Dovid Bender <dovid at telecurve.com>
> >> wrote:
> >>
> >> As I understand it if one wants to get a cert for STIR shaken
> >> you need to become a CLEC. Anyone have a how to/contacts for
> >> companies that make this effortless and easy?
> >>
> >> _______________________________________________
> >> 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
> >
> > Links:
> > ------
> > [1] http://www.voxox.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
> >
> > --
> > Glen Gerhard
> > glen at cognexus.net
> > 858.324.4536
> >
> > Cognexus, LLC
> > 7891 Avenida Kirjah
> > San Diego, CA 92037
> >
> > _______________________________________________
> > VoiceOps mailing list
> > VoiceOps at voiceops.org
> > https://puck.nether.net/mailman/listinfo/voiceops
> >
> >
> > Links:
> > ------
> > [1] http://VOXOX.COM
> > [2] http://www.voxox.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
>
Aug. 22, 2019
Who do we call - 3rd plus party carrier issues affecting local customers
by marylou@backuptelecom.com
I would try calling AT&T's NOC and asking them if they can tell what
trunk group they're receiving the call from. That might allow you to
keep tracing the call back to the previous carrier until you find the
culprit. I can send you their number privately.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2019-08-21 07:50 AM, Mark Timm wrote:
> Always perform a LNP query on the originating number to determine the
> originating company and start with them, realizing they may not
> provide the LD, doesn?t matter they have to work with you.
>
> You say CenturyLink was removed from route by Inteliquent and it
> cleared T-Mobile so this wouldn?t seem to be a facilities issue but
> have you examined the TCIC?s the calls come in on from ATT, are they
> confined to a range?
>
> There are a number of ways to get in touch with ATT but they will say
> they are passing what they receive. The best be is to start with the
> originating company.
>
> At this point who would you file a FCC complaint against?
>
> [2]
>
> Mark Timm?
>
> Switch Engineer
>
> Aureon Technology
>
> 7760 Office Plaza Drive South
>
> West Des Moines
>
> ,
>
> IA
>
> 50266
>
> MARK.TIMM at AUREON.COM
>
> 515-830-0478 [3]
>
> [4]
>
> WWW.AUREON.COM [4]
>
> [5]
>
> [6]
>
> [7]
>
> [8]
>
> [9]
>
> This message contains confidential information and is intended only
> for the intended recipients. If you are not an intended recipient you
> should not disseminate, distribute or copy this e-mail. Please notify
> the sender immediately by e-mail if you have received this e-mail by
> mistake and delete this e-mail from your system. E-mail transmission
> cannot be guaranteed to be secure or error-free as information could
> be intercepted, corrupted, lost, destroyed, arrive late or incomplete,
> or contain viruses. The sender therefore does not accept liability for
> any errors or omissions in the contents of this message, which arise
> as a result of e-mail transmission. If verification is required please
> request a hard-copy version.
>
> FROM: VoiceOps <voiceops-bounces at voiceops.org> ON BEHALF OF Brandon
> Svec
> SENT: Tuesday, August 20, 2019 10:58 PM
> TO: Jamie Montgomery <Jamie.Montgomery at comporium.com>
> CC: voiceops at voiceops.org
> SUBJECT: Re: [VoiceOps] Who do we call - 3rd plus party carrier issues
> affecting local customers
>
> [EXTERNAL EMAIL] THIS MESSAGE WAS SENT FROM OUTSIDE THE COMPANY WITH A
> URL. PLEASE DO NOT CLICK LINKS UNLESS YOU RECOGNIZE THE SOURCE OF THIS
> EMAIL AND KNOW THE CONTENT IS SAFE.
>
> It sounds like you have done more than half the troubleshooting
> already.
>
> I would continue to work the AT&T escalation angle as it sounds they
> should be the ones in a position to identify the trouble route and
> resolve it.
>
> Maybe through out the idea of a potential FCC complaint by someone in
> your organization it could help move things along.
>
> Good luck
>
> On Tue, Aug 20, 2019 at 7:45 PM Jamie Montgomery
> <Jamie.Montgomery at comporium.com> wrote:
>
>> Greetings..
>>
>> Looking for the proper way to identify a third party carrier..
>>
>> We have had a monthlong ongoing issue with external calls into our
>> switch with terrible quality. It?s random, but it?s calls to
>> ported numbers into one of our CLEC areas. When an affected call
>> comes in, it is reported as static or delay. We have obtained an
>> audio capture of a couple of these calls from the ingress point of
>> our TDM network, and the audio is severely delayed and choppy as if
>> it was delayed within an IP network. We?re assuming the call has
>> been routed through an IP low-cost carrier somewhere. (Working with
>> T-Mobile below, we found that their switches would route calls that
>> originates and terminates locally in South Carolina through
>> Washington state carriers.)
>>
>> All of the calls with an issue come into us from a legacy ATT
>> tandem, but not all of the calls from the ATT tandem are affected.
>> We?ve been trying to get in touch with ATT for a month, and have
>> recently spoken to some people with no resolution. We continue to
>> call them daily. We worked with T-Mobile on issues with their
>> wireless customers calling our CLEC customers experiencing this
>> problem. The guys at T-Mobile were excellent to work with. (They
>> reached out to their 3rd party carrier Inteloquent who had rerouted
>> calls away from CenturyLink, which resolved calls from T-Mobile
>> devices.) We?re getting dozens of trouble calls a day from several
>> of our CLEC customers on calls originating from many other sources
>> (Verizon, local ILEC landlines, etc.). We?ve explained to our
>> customer that the trouble is not ours, that we?re doing our best
>> to track down the problem carrier, but we?re been notified by our
>> customers that we?re going to lose them, regardless.
>>
>> Our last idea is to file a complaint with the FCC, but that?s
>> leaving issues unresolved. My questions to the community are:
>>
>> * What?s the most effective way to zero in on the problem
>> carrier to troubleshoot the issue?
>> * What legal means do we have to empower somebody to support us in
>> finding the issue?
>> * What would you do if your hands were tied like ours seem to be?
>> * (What other questions should I be asking the community that come
>> to mind?)
>>
>> My background is switching and some at work experience of the SS7
>> network. I?m of the opinion that I?m not the most qualified in
>> our organization to engage the FCC or twist ATT?s arm to work with
>> us.. but no one else beside the on-point technician is making any
>> effort. Internal responsibilities aside: How do we make the extra
>> effort to keep our customers?
>>
>> I appreciate the time you took from your day reading this.
>>
>> JAMIE MONTGOMERY | COMPORIUM
>>
>> Network Facilities Engineering | Voice Network Engineering Associate
>>
>>
>> www.comporium.com [1]
>>
>> jamie.montgomery at comporium.com
>>
>> _The information contained in this e-mail message and any
>> attachments thereto are confidential, privileged, or otherwise
>> protected from disclosure, and are intended for the use of the
>> individual or entity named above. Dissemination, distribution or
>> copying of this message and any attachments by anyone other than the
>> intended recipient, or an employee or agent responsible for
>> delivering the message to the intended recipient, is prohibited. If
>> you have received this communication in error, please immediately
>> notify the sender by telephone or e-mail and destroy the original
>> message, attachments, and all copies._
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>
> --
>
> Brandon Svec
> 15106862204 voice | fax | sms
>
> teamonesolutions.com [10]
> 14729 Catalina St. San Leandro, CA 94577
>
> .?l?.?l?. Cisco Meraki CMNA
>
> Links:
> ------
> [1] http://www.comporium.com
> [2] https://www.aureon.com/
> [3] tel:515-830-0478
> [4] http://www.aureon.com/
> [5] https://www.facebook.com/aureon
> [6] https://www.linkedin.com/company/aureon
> [7] https://www.twitter.com/aureon
> [8] https://www.youtube.com/channel/UCv6xwRKJCouZM6FPQEJ6CMA
> [9] https://www.instagram.com/aureon_/
> [10] http://teamonesolutions.com
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Aug. 21, 2019
CLEC - STIR/SHAKEN
by marylou@backuptelecom.com
My understanding is that the only VOIP carriers that can get an IPES OCN
are Interconnected VOIP carriers. You have to get a certification from
the FCC to become an Interconnected VOIP carrier because the
Interconnected VOIP status allows you to order and manager your own
NXXs.
The main network difference between a CLEC and an Interconnected VOIP
carrier is that the CLEC has a direct connection to the PSTN via their
own SS7 links and direct trunks to the ILEC. The Interconnected VOIP
carrier gets their connection to the PSTN through a third party carrier
that manages the SS7 links and direct trunks to the ILEC.
MARY LOU CAREY
BackUP Telecom Consulting
Office: 615-791-9969
Cell: 615-796-1111
On 2019-08-20 07:51 PM, Calvin Ellison wrote:
> Glen,
>
> What are we to do for our clients who have DID/TFN from 3rd paries? We
> won't have any relationship with their DID provider to request a
> delegated certificate, and wouldn't have one of our own to sign those
> calls, even as Attestation level B or C. Does the client need to
> request a delegated cert and provide it to each termination carrier
> they want to use?
>
> I had a call with Bandwidth today was told the delegated certificates
> would need to contain (or refer via URL) a list of which numbers are
> permitted to be signed by that cert. I hope they've considered the
> potential information leak here and use hashes of the permitted
> numbers, not the numbers in cleartext.
>
> For what it's worth, I received confirmation from NECA that an IPES
> OCN can be issued without an FCC waiver. This would at least let us
> sign with level B or C.
>
> Query to NECA and their reply:
>
> Assuming I will need an OCN, I have been told that VoIP carriers that
> are not certified by
> the FCC as Interconnected VoIP carriers cannot be assigned an OCN.
> This doesn't jive with the lingo on your website:
>
>> IPES service: Proof of service and customers, e.g., interconnection
>> agreement (or evidence of an interconnection order pursuant to an
>> approved tariff) and contractual agreements with end-user customers.
>> Or, regulatory administration approval, if applicable.
>
> We definitely have contracted customers and definitely have
> interconnections with DID/TFN origination carriers and termination
> carriers. If we have no intention to obtain numbering resources
> directly, can we still obtain an OCN?
>
> YES, YOU CAN STILL OBTAIN AN OCN.
>
> Regards,
>
> CALVIN ELLISON
> Senior Voice Operations Engineer
> calvin.ellison at voxox.com
> +1 (213) 285-0555
>
> -----------------------------------------------
> VOXOX.COM [2]
> 5825 Oberlin Drive, Suite 5
> San Diego, CA 92121
>
> On Tue, Aug 20, 2019 at 9:17 AM Glen Gerhard <glen at cognexus.net>
> wrote:
>
>> Yes, I believe that is the case today. In the new "delegated
>> certificate" model the VoIP provider (or CPaaS provider) will be
>> provided a certificate from the OCN that is used for the ANI. This
>> delegated certificate will give the downstream carriers A level
>> Attestation for the calls regardless of where the outbound calls are
>> originated.
>>
>> Ultimately it is the originating Enterprise that needs to be
>> traceable from the terminating carrier. Once this relationship chain
>> has been vetted the certificates can be delegated and used at call
>> set up time. NetNumber has a service for brokering the Certificates
>> but the spec is not fully adopted to my knowledge.
>>
>> Another proposal at ATIS is to have the sending CNAM (and expanded
>> eCNAM) validated with a similar vetted relationship and certificate
>> chain. Ultimately this may be more useful for both the Enterprise
>> and the Callee than just the ANI.
>>
>> ~Glen
>>
>> On 8/16/2019 11:40, Mary Lou Carey wrote:
>> So it sounds to me like you just have to be a certified carrier to
>> get a STIR/SHAKEN certificate. That means either a CLEC, Wireless,
>> or Interconnected VOIP Carrier. The VOIP carriers that are not
>> certified by the FCC as Interconnected VOIP carriers cannot be
>> assigned an OCN.
>>
>> MARY LOU CAREY
>> BackUP Telecom Consulting
>> Office: 615-791-9969
>> Cell: 615-796-1111
>>
>> On 2019-08-16 01:32 PM, Calvin Ellison wrote:
>> As explained to me by TransNexus, the Certificate Authorities will
>> most likely require an OCN. VoIP carriers with their own numbering
>> resources already have their IPES category OCN. It's also possible
>> they might only require a SPID.
>>
>> Regards,
>>
>> CALVIN ELLISON
>> Senior Voice Operations Engineer
>> calvin.ellison at voxox.com
>> +1 (213) 285-0555
>>
>> -----------------------------------------------
>> VOXOX.COM [1] [1]
>> 5825 Oberlin Drive, Suite 5
>> San Diego, CA 92121
>>
>> On Fri, Aug 16, 2019 at 8:02 AM Dovid Bender <dovid at telecurve.com>
>> wrote:
>>
>> Alex,
>>
>> You would think so. From what I understand you will need to be a LEC
>>
>> to get a cert.
>>
>> On Fri, Aug 16, 2019 at 10:33 AM Alex Balashov
>> <abalashov at evaristesys.com> wrote:
>>
>> If non-LEC VoIP providers can direct own numbering resources now,
>> it follows that they should be able to partake of STIR/SHAKEN.
>>
>> ?
>> Sent from mobile, with due apologies for brevity and errors.
>>
>> On Aug 16, 2019, at 9:16 AM, Dovid Bender <dovid at telecurve.com>
>> wrote:
>>
>> As I understand it if one wants to get a cert for STIR shaken
>> you need to become a CLEC. Anyone have a how to/contacts for
>> companies that make this effortless and easy?
>>
>> _______________________________________________
>> 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
>
> Links:
> ------
> [1] http://www.voxox.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
>
> --
> Glen Gerhard
> glen at cognexus.net
> 858.324.4536
>
> Cognexus, LLC
> 7891 Avenida Kirjah
> San Diego, CA 92037
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
> Links:
> ------
> [1] http://VOXOX.COM
> [2] http://www.voxox.com/
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Aug. 21, 2019
Who do we call - 3rd plus party carrier issues affecting local customers
by Mark.Timm@aureon.com
Always perform a LNP query on the originating number to determine the originating company and start with them, realizing they may not provide the LD, doesn?t matter they have to work with you.
You say CenturyLink was removed from route by Inteliquent and it cleared T-Mobile so this wouldn?t seem to be a facilities issue but have you examined the TCIC?s the calls come in on from ATT, are they confined to a range?
There are a number of ways to get in touch with ATT but they will say they are passing what they receive. The best be is to start with the originating company.
At this point who would you file a FCC complaint against?
Mark Timm
Switch Engineer
Aureon Technology
7760 Office Plaza Drive South
West Des Moines
, IA
50266
Mark.Timm at aureon.com
515-830-0478
www.aureon.com
This message contains confidential information and is intended only for the intended recipients. If you are not an intended recipient you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Brandon Svec
Sent: Tuesday, August 20, 2019 10:58 PM
To: Jamie Montgomery <Jamie.Montgomery at comporium.com>
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] Who do we call - 3rd plus party carrier issues affecting local customers
[External Email] This message was sent from outside the company with a URL. Please do not click links unless you recognize the source of this email and know the content is safe.
It sounds like you have done more than half the troubleshooting already.
I would continue to work the AT&T escalation angle as it sounds they should be the ones in a position to identify the trouble route and resolve it.
Maybe through out the idea of a potential FCC complaint by someone in your organization it could help move things along.
Good luck
On Tue, Aug 20, 2019 at 7:45 PM Jamie Montgomery <Jamie.Montgomery at comporium.com<mailto:Jamie.Montgomery at comporium.com>> wrote:
Greetings..
Looking for the proper way to identify a third party carrier..
We have had a monthlong ongoing issue with external calls into our switch with terrible quality. It?s random, but it?s calls to ported numbers into one of our CLEC areas. When an affected call comes in, it is reported as static or delay. We have obtained an audio capture of a couple of these calls from the ingress point of our TDM network, and the audio is severely delayed and choppy as if it was delayed within an IP network. We?re assuming the call has been routed through an IP low-cost carrier somewhere. (Working with T-Mobile below, we found that their switches would route calls that originates and terminates locally in South Carolina through Washington state carriers.)
All of the calls with an issue come into us from a legacy ATT tandem, but not all of the calls from the ATT tandem are affected. We?ve been trying to get in touch with ATT for a month, and have recently spoken to some people with no resolution. We continue to call them daily. We worked with T-Mobile on issues with their wireless customers calling our CLEC customers experiencing this problem. The guys at T-Mobile were excellent to work with. (They reached out to their 3rd party carrier Inteloquent who had rerouted calls away from CenturyLink, which resolved calls from T-Mobile devices.) We?re getting dozens of trouble calls a day from several of our CLEC customers on calls originating from many other sources (Verizon, local ILEC landlines, etc.). We?ve explained to our customer that the trouble is not ours, that we?re doing our best to track down the problem carrier, but we?re been notified by our customers that we?re going to lose them, regardless.
Our last idea is to file a complaint with the FCC, but that?s leaving issues unresolved. My questions to the community are:
* What?s the most effective way to zero in on the problem carrier to troubleshoot the issue?
* What legal means do we have to empower somebody to support us in finding the issue?
* What would you do if your hands were tied like ours seem to be?
* (What other questions should I be asking the community that come to mind?)
My background is switching and some at work experience of the SS7 network. I?m of the opinion that I?m not the most qualified in our organization to engage the FCC or twist ATT?s arm to work with us.. but no one else beside the on-point technician is making any effort. Internal responsibilities aside: How do we make the extra effort to keep our customers?
I appreciate the time you took from your day reading this.
Jamie Montgomery | Comporium
Network Facilities Engineering | Voice Network Engineering Associate
www.comporium.com<http://www.comporium.com>
jamie.montgomery at comporium.com<mailto:jamie.montgomery at comporium.com>
The information contained in this e-mail message and any attachments thereto are confidential, privileged, or otherwise protected from disclosure, and are intended for the use of the individual or entity named above. Dissemination, distribution or copying of this message and any attachments by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you have received this communication in error, please immediately notify the sender by telephone or e-mail and destroy the original message, attachments, and all copies.
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
--
Brandon Svec
15106862204 voice | fax | sms
teamonesolutions.com<http://teamonesolutions.com>
14729 Catalina St. San Leandro, CA 94577
.?l?.?l?. Cisco Meraki CMNA
Aug. 21, 2019
Who do we call - 3rd plus party carrier issues affecting local customers
by bsvec@teamonesolutions.com
It sounds like you have done more than half the troubleshooting already.
I would continue to work the AT&T escalation angle as it sounds they should
be the ones in a position to identify the trouble route and resolve it.
Maybe through out the idea of a potential FCC complaint by someone in your
organization it could help move things along.
Good luck
On Tue, Aug 20, 2019 at 7:45 PM Jamie Montgomery <
Jamie.Montgomery at comporium.com> wrote:
> Greetings..
>
>
>
> Looking for the proper way to identify a third party carrier..
>
>
>
> We have had a monthlong ongoing issue with external calls into our switch
> with terrible quality. It?s random, but it?s calls to ported numbers into
> one of our CLEC areas. When an affected call comes in, it is reported as
> static or delay. We have obtained an audio capture of a couple of these
> calls from the ingress point of our TDM network, and the audio is severely
> delayed and choppy as if it was delayed within an IP network. We?re
> assuming the call has been routed through an IP low-cost carrier somewhere.
> (Working with T-Mobile below, we found that their switches would route
> calls that originates and terminates locally in South Carolina through
> Washington state carriers.)
>
>
>
> All of the calls with an issue come into us from a legacy ATT tandem, but
> not all of the calls from the ATT tandem are affected. We?ve been trying to
> get in touch with ATT for a month, and have recently spoken to some people
> with no resolution. We continue to call them daily. We worked with T-Mobile
> on issues with their wireless customers calling our CLEC customers
> experiencing this problem. The guys at T-Mobile were excellent to work
> with. (They reached out to their 3rd party carrier Inteloquent who had
> rerouted calls away from CenturyLink, which resolved calls from T-Mobile
> devices.) We?re getting dozens of trouble calls a day from several of our
> CLEC customers on calls originating from many other sources (Verizon, local
> ILEC landlines, etc.). We?ve explained to our customer that the trouble is
> not ours, that we?re doing our best to track down the problem carrier, but
> we?re been notified by our customers that we?re going to lose them,
> regardless.
>
>
>
> Our last idea is to file a complaint with the FCC, but that?s leaving
> issues unresolved. My questions to the community are:
>
> - What?s the most effective way to zero in on the problem carrier to
> troubleshoot the issue?
> - What legal means do we have to empower somebody to support us in
> finding the issue?
> - What would you do if your hands were tied like ours seem to be?
> - (What other questions should I be asking the community that come to
> mind?)
>
>
>
> My background is switching and some at work experience of the SS7 network.
> I?m of the opinion that I?m not the most qualified in our organization to
> engage the FCC or twist ATT?s arm to work with us.. but no one else beside
> the on-point technician is making any effort. Internal responsibilities
> aside: How do we make the extra effort to keep our customers?
>
>
>
> I appreciate the time you took from your day reading this.
>
>
>
> *Jamie Montgomery | Comporium*
>
> Network Facilities Engineering | Voice Network Engineering Associate
>
> www.comporium.com
>
> jamie.montgomery at comporium.com
>
>
> *The information contained in this e-mail message and any attachments
> thereto are confidential, privileged, or otherwise protected from
> disclosure, and are intended for the use of the individual or entity named
> above. Dissemination, distribution or copying of this message and any
> attachments by anyone other than the intended recipient, or an employee or
> agent responsible for delivering the message to the intended recipient, is
> prohibited. If you have received this communication in error, please
> immediately notify the sender by telephone or e-mail and destroy the
> original message, attachments, and all copies.*
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
--
Brandon Svec
15106862204 voice | fax | sms
teamonesolutions.com
14729 Catalina St. San Leandro, CA 94577
.?l?.?l?. Cisco Meraki CMNA
Aug. 21, 2019
Who do we call - 3rd plus party carrier issues affecting local customers
by ross@tajvar.io
In my experience, filing an FCC complaint does a lot to motivate someone
(usually someone with some away) from the carrier in question to speak to
you.
On Tue, Aug 20, 2019, 10:45 PM Jamie Montgomery <
Jamie.Montgomery at comporium.com> wrote:
> Greetings..
>
>
>
> Looking for the proper way to identify a third party carrier..
>
>
>
> We have had a monthlong ongoing issue with external calls into our switch
> with terrible quality. It?s random, but it?s calls to ported numbers into
> one of our CLEC areas. When an affected call comes in, it is reported as
> static or delay. We have obtained an audio capture of a couple of these
> calls from the ingress point of our TDM network, and the audio is severely
> delayed and choppy as if it was delayed within an IP network. We?re
> assuming the call has been routed through an IP low-cost carrier somewhere.
> (Working with T-Mobile below, we found that their switches would route
> calls that originates and terminates locally in South Carolina through
> Washington state carriers.)
>
>
>
> All of the calls with an issue come into us from a legacy ATT tandem, but
> not all of the calls from the ATT tandem are affected. We?ve been trying to
> get in touch with ATT for a month, and have recently spoken to some people
> with no resolution. We continue to call them daily. We worked with T-Mobile
> on issues with their wireless customers calling our CLEC customers
> experiencing this problem. The guys at T-Mobile were excellent to work
> with. (They reached out to their 3rd party carrier Inteloquent who had
> rerouted calls away from CenturyLink, which resolved calls from T-Mobile
> devices.) We?re getting dozens of trouble calls a day from several of our
> CLEC customers on calls originating from many other sources (Verizon, local
> ILEC landlines, etc.). We?ve explained to our customer that the trouble is
> not ours, that we?re doing our best to track down the problem carrier, but
> we?re been notified by our customers that we?re going to lose them,
> regardless.
>
>
>
> Our last idea is to file a complaint with the FCC, but that?s leaving
> issues unresolved. My questions to the community are:
>
> - What?s the most effective way to zero in on the problem carrier to
> troubleshoot the issue?
> - What legal means do we have to empower somebody to support us in
> finding the issue?
> - What would you do if your hands were tied like ours seem to be?
> - (What other questions should I be asking the community that come to
> mind?)
>
>
>
> My background is switching and some at work experience of the SS7 network.
> I?m of the opinion that I?m not the most qualified in our organization to
> engage the FCC or twist ATT?s arm to work with us.. but no one else beside
> the on-point technician is making any effort. Internal responsibilities
> aside: How do we make the extra effort to keep our customers?
>
>
>
> I appreciate the time you took from your day reading this.
>
>
>
> *Jamie Montgomery | Comporium*
>
> Network Facilities Engineering | Voice Network Engineering Associate
>
> www.comporium.com
>
> jamie.montgomery at comporium.com
>
>
> *The information contained in this e-mail message and any attachments
> thereto are confidential, privileged, or otherwise protected from
> disclosure, and are intended for the use of the individual or entity named
> above. Dissemination, distribution or copying of this message and any
> attachments by anyone other than the intended recipient, or an employee or
> agent responsible for delivering the message to the intended recipient, is
> prohibited. If you have received this communication in error, please
> immediately notify the sender by telephone or e-mail and destroy the
> original message, attachments, and all copies.*
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
Aug. 21, 2019
Who do we call - 3rd plus party carrier issues affecting local customers
by Jamie.Montgomery@comporium.com
Greetings..
Looking for the proper way to identify a third party carrier..
We have had a monthlong ongoing issue with external calls into our switch with terrible quality. It's random, but it's calls to ported numbers into one of our CLEC areas. When an affected call comes in, it is reported as static or delay. We have obtained an audio capture of a couple of these calls from the ingress point of our TDM network, and the audio is severely delayed and choppy as if it was delayed within an IP network. We're assuming the call has been routed through an IP low-cost carrier somewhere. (Working with T-Mobile below, we found that their switches would route calls that originates and terminates locally in South Carolina through Washington state carriers.)
All of the calls with an issue come into us from a legacy ATT tandem, but not all of the calls from the ATT tandem are affected. We've been trying to get in touch with ATT for a month, and have recently spoken to some people with no resolution. We continue to call them daily. We worked with T-Mobile on issues with their wireless customers calling our CLEC customers experiencing this problem. The guys at T-Mobile were excellent to work with. (They reached out to their 3rd party carrier Inteloquent who had rerouted calls away from CenturyLink, which resolved calls from T-Mobile devices.) We're getting dozens of trouble calls a day from several of our CLEC customers on calls originating from many other sources (Verizon, local ILEC landlines, etc.). We've explained to our customer that the trouble is not ours, that we're doing our best to track down the problem carrier, but we're been notified by our customers that we're going to lose them, regardless.
Our last idea is to file a complaint with the FCC, but that's leaving issues unresolved. My questions to the community are:
* What's the most effective way to zero in on the problem carrier to troubleshoot the issue?
* What legal means do we have to empower somebody to support us in finding the issue?
* What would you do if your hands were tied like ours seem to be?
* (What other questions should I be asking the community that come to mind?)
My background is switching and some at work experience of the SS7 network. I'm of the opinion that I'm not the most qualified in our organization to engage the FCC or twist ATT's arm to work with us.. but no one else beside the on-point technician is making any effort. Internal responsibilities aside: How do we make the extra effort to keep our customers?
I appreciate the time you took from your day reading this.
Jamie Montgomery | Comporium
Network Facilities Engineering | Voice Network Engineering Associate
www.comporium.com
jamie.montgomery at comporium.com
The information contained in this e-mail message and any attachments thereto are confidential, privileged, or otherwise protected from disclosure, and are intended for the use of the individual or entity named above. Dissemination, distribution or copying of this message and any attachments by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you have received this communication in error, please immediately notify the sender by telephone or e-mail and destroy the original message, attachments, and all copies.
Aug. 21, 2019
CLEC - STIR/SHAKEN
by calvin.ellison@voxox.com
Glen,
What are we to do for our clients who have DID/TFN from 3rd paries? We
won't have any relationship with their DID provider to request a delegated
certificate, and wouldn't have one of our own to sign those calls, even as
Attestation level B or C. Does the client need to request a delegated cert
and provide it to each termination carrier they want to use?
I had a call with Bandwidth today was told the delegated certificates would
need to contain (or refer via URL) a list of which numbers are permitted to
be signed by that cert. I hope they've considered the potential information
leak here and use hashes of the permitted numbers, not the numbers in
cleartext.
For what it's worth, I received confirmation from NECA that an IPES OCN can
be issued without an FCC waiver. This would at least let us sign with level
B or C.
Query to NECA and their reply:
Assuming I will need an OCN, I have been told that VoIP carriers that are
not certified by
the FCC as Interconnected VoIP carriers cannot be assigned an OCN. This
doesn't jive with the lingo on your website:
IPES service: Proof of service and customers, e.g., interconnection
agreement (or evidence of an interconnection order pursuant to an approved
tariff) and contractual agreements with end-user customers. Or, regulatory
administration approval, if applicable.
We definitely have contracted customers and definitely have
interconnections with DID/TFN origination carriers and termination
carriers. If we have no intention to obtain numbering resources directly,
can we still obtain an OCN?
*Yes, you can still obtain an OCN.*
Regards,
*Calvin Ellison*
Senior Voice Operations Engineer
calvin.ellison at voxox.com
+1 (213) 285-0555
-----------------------------------------------
*voxox.com <http://www.voxox.com/> *
5825 Oberlin Drive, Suite 5
San Diego, CA 92121
[image: Voxox]
On Tue, Aug 20, 2019 at 9:17 AM Glen Gerhard <glen at cognexus.net> wrote:
> Yes, I believe that is the case today. In the new "delegated certificate"
> model the VoIP provider (or CPaaS provider) will be provided a certificate
> from the OCN that is used for the ANI. This delegated certificate will give
> the downstream carriers A level Attestation for the calls regardless of
> where the outbound calls are originated.
>
> Ultimately it is the originating Enterprise that needs to be traceable
> from the terminating carrier. Once this relationship chain has been vetted
> the certificates can be delegated and used at call set up time. NetNumber
> has a service for brokering the Certificates but the spec is not fully
> adopted to my knowledge.
>
> Another proposal at ATIS is to have the sending CNAM (and expanded eCNAM)
> validated with a similar vetted relationship and certificate chain.
> Ultimately this may be more useful for both the Enterprise and the Callee
> than just the ANI.
>
> ~Glen
>
>
> On 8/16/2019 11:40, Mary Lou Carey wrote:
>
> So it sounds to me like you just have to be a certified carrier to get a
> STIR/SHAKEN certificate. That means either a CLEC, Wireless, or
> Interconnected VOIP Carrier. The VOIP carriers that are not certified by
> the FCC as Interconnected VOIP carriers cannot be assigned an OCN.
>
> MARY LOU CAREY
> BackUP Telecom Consulting
> Office: 615-791-9969
> Cell: 615-796-1111
>
> On 2019-08-16 01:32 PM, Calvin Ellison wrote:
>
> As explained to me by TransNexus, the Certificate Authorities will
> most likely require an OCN. VoIP carriers with their own numbering
> resources already have their IPES category OCN. It's also possible
> they might only require a SPID.
>
> Regards,
>
> CALVIN ELLISON
> Senior Voice Operations Engineer
> calvin.ellison at voxox.com
> +1 (213) 285-0555
>
> -----------------------------------------------
> VOXOX.COM [1]
> 5825 Oberlin Drive, Suite 5
> San Diego, CA 92121
>
> On Fri, Aug 16, 2019 at 8:02 AM Dovid Bender <dovid at telecurve.com>
> <dovid at telecurve.com>
> wrote:
>
> Alex,
>
> You would think so. From what I understand you will need to be a LEC
> to get a cert.
>
> On Fri, Aug 16, 2019 at 10:33 AM Alex Balashov
> <abalashov at evaristesys.com> <abalashov at evaristesys.com> wrote:
>
> If non-LEC VoIP providers can direct own numbering resources now,
> it follows that they should be able to partake of STIR/SHAKEN.
>
> ?
> Sent from mobile, with due apologies for brevity and errors.
>
> On Aug 16, 2019, at 9:16 AM, Dovid Bender <dovid at telecurve.com>
> <dovid at telecurve.com>
>
> wrote:
>
>
> As I understand it if one wants to get a cert for STIR shaken
>
> you need to become a CLEC. Anyone have a how to/contacts for
> companies that make this effortless and easy?
>
>
>
> _______________________________________________
> 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
>
>
>
> Links:
> ------
> [1] http://www.voxox.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
>
>
> --
> Glen Gerhardglen at cognexus.net
> 858.324.4536
>
> Cognexus, LLC
> 7891 Avenida Kirjah
> San Diego, CA 92037
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
Aug. 21, 2019
Ringing problems
by abalashov@evaristesys.com
This could also be due to serial forking by a proxy upstream, leading to
a conflicting blizzard of different progress indications from various
gateways.
If you can get a capture of such a scenario and indeed find a 183 ->
180 dynamic, I'd be curious to take a look at it.
Of course, there's no reason a lightweight pass-thru B2BUA in an SBC
couldn't behave in a way that leads to the same result.
-- Alex
On Tue, Aug 20, 2019 at 12:37:19PM -0400, Pete Eisengrein wrote:
> We have recently gotten several complaints about not getting, or severely
> abbreviated ringback. The first few examples we were able to trace back to
> a carrier and believe it is because the call sets up with 183 Session
> Progress w/SDP and <1 second later get a 180 Ringing and the audible
> ringing stops.
>
> We heard a similar complaint in Europe last with an EU carrier. And again
> today with yet another US (global) provider.
>
> So, my questions are:
>
> 1- Anyone else seeing this? If so, what's your workaround/fix?
> 2- Since this is not contained to a single carrier, anyone aware of an SBC
> or softswitch maker recently released code that might be causing?
>
> Thanks,
> Pete
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Aug. 20, 2019