"I just met you and I know this is crazy," "but you have their signature so call them maybe?"
I'd avoid assuming hostility, especially this early in the verification game, and if it is hostility or misuse, follow up with the FCC. Maybe their customer is taking advantage of a misconfiguration, maybe they typo-ed something similar and it happens to be your number, maybe you discovered the next unrepentant robocalling company. Paul Timmins Telecommunications Consultant Timmins Technologies, LLC / telcodata.us 248-379-7826 > On Sep 12, 2023, at 11:27 AM, Jeff Anderson via VoiceOps > <[email protected]> wrote: > > In this instance the numbers used for the ANI are not assigned to any of our > customers but they do belong to our company. > > On Tue, Sep 12, 2023 at 10:20 AM Dovid Bender <[email protected] > <mailto:[email protected]>> wrote: >> That in theory can still be valid. What happens if one of your customers is >> using a 3rd party to make calls for them? Are the calls for certain not >> valid or are you assuming so because they are your numbers? >> >> >> On Tue, Sep 12, 2023 at 10:58 AM Jeff Anderson via VoiceOps >> <[email protected] <mailto:[email protected]>> wrote: >>> What is the recommended process to investigate inappropriately stir/shaken >>> signed calls? We have had some calls terminate into our network with our >>> ANI but the call was not signed by us but instead a different provider >>> signing attestation B. >>> >>> Thanks >>> _______________________________________________ >>> VoiceOps mailing list >>> [email protected] <mailto:[email protected]> >>> https://puck.nether.net/mailman/listinfo/voiceops > _______________________________________________ > VoiceOps mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
