Provider certification record
Lovo Systems LLC
Listed- RMD number
- RMD0011900
- FRN
- 0032704553
- OCN
Identity
- Legal business name
- Lovo Systems LLC
- Doing-business-as
- Foreign Voice Service Provider
- No
- Business address
- 7315 12th ave, brooklyn NY 11228
- Filing contact
- William Shashaty
Owner · Admin
billy@lovosystemsny.com
(347) 461-8300
7315 12th ave brooklyn NY 11228
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- William J Shashaty
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider None Overall None - Exemption rules
- Rule: 47 CFR § 64.6305(c) LOVO SYSTEMS LLC does not directly implement STIR/SHAKEN on its own network. Instead, it relies on Bandwidth which is the upstream provider that does implement STIR/SHAKEN. My authentication is by IP only. All endpoints are authenticated by IP only and not credentials. It is not possible for any other endpoint to authenticate that is not allowed. We has very few end users and little termination traffic. Filer has well under 100,000 users; Rule: 47 CFR § 64.6305(c) LOVO SYSTEMS LLC does not directly implement STIR/SHAKEN on its own network. Instead, it relies on Bandwidth which is the upstream provider that does implement STIR/SHAKEN. I personally provide VOIP service and PBX/Gateway service to my customers and I administer all said systems and do not spoof or allow caller ID or robocall phone calls as I am the only person that can change any settings on the said systems. I manage all endpoints and credentials. There is no possible way for any of my customers to obtain any credentials for any endpoints to make phone calls from other than a VOIP deskphone. Endpoints/phones are password protected. There is absolutely no way anyone of my customers can spoof their caller ID or use ANY kind of robocall equipment. I also do not have any customers that would need to implement a robocall system. If I was asked to implement such a system I would decline. If I was to receive notice that a spoof or robocall was made with one of my customers/systems, I would immediately investigate and suspend any outbound traffic from that customer/system until I found the issue and fixed it. I would also terminate the relationship with the customer if it was to happen a 2nd time. I know it is impossible because I administer all systems and endpoints for all my customers.
Prior investigations / actions
- Description
- I had a deficient Robocall Mitigation Database certification or mitigation program because I did not see any emails from the FCC about new requirements and deadlines. I have whitelisted any emails from FCC.GOV in my spamfilter and I will check my emails more often on a daily basis
Robocall mitigation plan
Declaration
- By
- William J Shashaty
- Date
- 2025-08-28No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2025-09-02 | New | Initial certification filed and added to database. |