<div dir="ltr">Jessica, et al,<div><br></div><div>A suggested BoF topic for tonight...</div><div><b>Who really should decide whether to permit or deny a call when there is a conflict between the originator and "public opinion"? Should we permit the call, block it, or choose another option? Who should bear the responsibility (burden and cost) for fixing it if the result seems wrong?</b></div><div><br></div><div>Round 1 - Basic Call Scenario...</div><div>A bank sends a call to its originating service provider (OSP). A valid "known customer and known number" was used. The OSP signs the call with Attestation A and routes it to the TSP. (Maybe the TSP is the OSP to keep things simple). The TSP's analytics provider blocks the call due to "reasonable analytics," resulting in a 603+ response. What were the reasonable analytics? Assume the simplest case: the number used is frequently flagged (say 75%) by end users as "decline and report as spam," even though 100% of these calls are being placed to the bank's customers regarding their missed loan payments. The bank is notified via the 603+ response about whom to contact if they want to dispute the call blocking and try to prevent future calls from being blocked. Did the system work correctly? Should such a burden be on the bank?</div><div><br></div><div>It would be interesting if we could have a discussion involving an actual business customer (bank), carriers, and analytics providers. Parties fitting each of the market segments are here... show up and throw down! </div><div><br></div><div>Other variations for discussion if Round 1 doesn't result in mass TKOs...<br>Round 2 - What if the number was also being spoofed (calling people who are not customers of the bank) and that was the reason for "public opinion"? Does that change the answers?</div><div>Round 3 - Does the scenario of the OSP and TSP being the same company versus being different companies make a difference?</div><div><br></div><div>Thanks,<br>Matt </div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, Sep 15, 2026 at 4:26 PM Jessica Willis <<a href="mailto:jessica@theorganizationorganization.co">jessica@theorganizationorganization.co</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hello SIPNOC 2026 attendees!</div><div>Send in your suggestions for BoFs for this evening.</div><div><br></div><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><b>Jessica Willis</b><div><b><a href="tel:(518)%20218-6005" value="+15182186005" target="_blank">518-218-6005</a><br></b><div><b><img width="96" height="31" src="https://ci3.googleusercontent.com/mail-sig/AIorK4xuAcw15Qd4F1KJMCYv4wanSRPZqHFO7mEiTezsbIhugLEUXcT7gaXM6lLIF5OQIDfN28Ja3u1E8cXg"><br></b><div><br></div></div></div></div></div></div></div>
_______________________________________________<br>
Sipnoc26-attendees mailing list<br>
<a href="mailto:Sipnoc26-attendees@sipforum.org" target="_blank">Sipnoc26-attendees@sipforum.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__mail.sipforum.org_mailman_listinfo_sipnoc26-2Dattendees&d=DwICAg&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=24GMt2zYynl90syhEMGevHfGSPx57hGhI0tDcEeNWrA&m=k9fTnIZiyqqF_itkIQg8K4y7DJPSXJhW5q5zYsSN09jmu3vSffjpWTVlZsBMWquJ&s=UZ6Ais3AhQXiMusjYOqd-wBBRSSpcus0uVsrgt40FC0&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.com/v2/url?u=http-3A__mail.sipforum.org_mailman_listinfo_sipnoc26-2Dattendees&d=DwICAg&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=24GMt2zYynl90syhEMGevHfGSPx57hGhI0tDcEeNWrA&m=k9fTnIZiyqqF_itkIQg8K4y7DJPSXJhW5q5zYsSN09jmu3vSffjpWTVlZsBMWquJ&s=UZ6Ais3AhQXiMusjYOqd-wBBRSSpcus0uVsrgt40FC0&e=</a> <br>
</blockquote></div>