Your consultant should be able to help with that. More than likely you just need to write down some policies you probably already have on the books. A big part of this is being able to make a statement similar to this:
We follow the best practices for vetting caller identity described by the NANC Call Authentication Trust Anchor Working Group. (https://docs.fcc.gov/public/attachments/DOC-367133A1.pdf) We use TransNexus ClearIP which basically just required us to turn on some reporting to be compliant - https://transnexus.com/clearip/ There are two examples at the bottom of that page how it can work with Metaswitch The extension gives you until 2023 to implement STIR/SHAKEN. photograph Daniel White Co-Founder phone: +1 (702) 470-2770 direct:+1 (702) 470-2766 > Mike Hammett <mailto:[email protected]> > June 23, 2021 at 13:15 > We have a consultant filing our mitigation plan (June 30 deadline) and > are working with Metaswitch\TNS on the technical aspects (seems like > we have until 2022 to do that). > > From some webinars I got the impression that we needed a variety of > policy and procedure changes to be compliant. Where is a good resource > to figure those out? > > Yes, I am working a variety of things in parallel in this project. > > > > ----- > Mike Hammett > Intelligent Computing Solutions <http://www.ics-il.com/> > <https://www.facebook.com/ICSIL><https://plus.google.com/+IntelligentComputingSolutionsDeKalb><https://www.linkedin.com/company/intelligent-computing-solutions><https://twitter.com/ICSIL> > Midwest Internet Exchange <http://www.midwest-ix.com/> > <https://www.facebook.com/mdwestix><https://www.linkedin.com/company/midwest-internet-exchange><https://twitter.com/mdwestix> > The Brothers WISP <http://www.thebrotherswisp.com/> > <https://www.facebook.com/thebrotherswisp> > > > <https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg> > >
-- AF mailing list [email protected] http://af.afmug.com/mailman/listinfo/af_af.afmug.com
