{"ct_name":"Richard Gaustad","ct_title":"Manager","ct_dept":"Administration","ct_address":"263 Country Club Drive | Stansbury Park UT 84074 | n","ct_tel":"4358400000","ct_email":"rich@rtechvoip.com","bz_address":"263 Country Club Drive | Suite 105 | Stansbury Park UT 84074","country":"United States of America","declare":"2024-04-07","last_seen":"2024-05-02","sys_id":"2f430f711b41f41002beea82f54bcb87","is_new":0,"gw_prov":"false","gw_prov_choice":"No","combined_gw":"false","ipr_imported":"false","voice_choice":"No","intermed_choice":"Yes","investigated":"No","intermed_exempt_rule":"See Page 9, footnote 67 of https:\/\/docs.fcc.gov\/public\/attachments\/FCC-23-18A1.pdf, which further cites 47 CFR ? 64.6304(b) (SPC token access extension.) This footnotes specifically states: \"(excluding from a STIR\/SHAKEN implementation obligation those providers that lack control over the necessary network infrastructure)\"\n\nWe are a reseller that lacks direct control over the switch carrying our customers' traffic. As such, we have no access to the switch to enable us to implement STIR\/SHAKEN procedures. However, we take specific reasonable steps to control and mitigate illegal robocalls, such as the \"know your customer\" and \"know your upstream provider\" procedures, These steps are listed in our Robocall Mitigation Plan as updated from time to time. The rules I found that exempt our STIR\/Shaken implementation include non-gateway intermediate providers like us who \"lack control over the facilities necessary to implement STIR\/SHAKEN.\"","gw_exempt_rule":"","voice_exempt_rule":"","investigate_descript":""}