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
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 < voiceops at voiceops.org> 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 VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
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 <dovid at telecurve.com> 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 < voiceops at voiceops.org> 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 VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/voiceops/attachments/20230912/0fa4f117/att...>
An HTML attachment was scrubbed... URL: <https://puck.nether.net/pipermail/voiceops/attachments/20230912/9e14fdf9/att...>
"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 <voiceops at voiceops.org> 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 <dovid at telecurve.com <mailto:dovid at telecurve.com>> 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 <voiceops at voiceops.org <mailto:voiceops at voiceops.org>> 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 VoiceOps at voiceops.org <mailto: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
Are you suggesting using the contact information found here when you say go to them directly based on the signature? https://authenticateapp.iconectiv.com/splist How are you turning a signature into a contact point? On Tue, Sep 12, 2023 at 11:05?AM Paul Timmins <paul at timmins.net> wrote:
"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 < voiceops at voiceops.org> 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 <dovid at telecurve.com> 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 < voiceops at voiceops.org> 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 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
I haven't found a signature in 2 years I couldn't find a contact for by simply taking the name in the certificate, going to the robocall mitigation database, and then contacting that person. It's been incredibly fruitful for me. At worst it might take a light googling, but RMD is mandatory, and if they have taken the time to get a cert, they're also gonna be in the RMD. YMMV, of course.
On Sep 12, 2023, at 12:14 PM, Jeff Anderson <ciscoplumber at gmail.com> wrote:
Are you suggesting using the contact information found here when you say go to them directly based on the signature? https://authenticateapp.iconectiv.com/splist
How are you turning a signature into a contact point?
On Tue, Sep 12, 2023 at 11:05?AM Paul Timmins <paul at timmins.net <mailto:paul at timmins.net>> wrote:
"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 <http://telcodata.us/> 248-379-7826
On Sep 12, 2023, at 11:27 AM, Jeff Anderson via VoiceOps <voiceops at voiceops.org <mailto:voiceops at voiceops.org>> 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 <dovid at telecurve.com <mailto:dovid at telecurve.com>> 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 <voiceops at voiceops.org <mailto:voiceops at voiceops.org>> 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 VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
VoiceOps mailing list VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
participants (4)
-
ciscoplumber＠gmail.com -
dfrigen＠wabash.net -
dovid＠telecurve.com -
paul＠timmins.net