I was talking with a comcast guy a while back when we had a SBC incorrectly set. Here is what he said. By any chance are you sending a 10 digit in the to or from? Comcast wants 11 digits for both with no exceptions. We simply logged into the Neustar portal and made a small adjustment on that side as it was easier then tweaking the acme sbc.
"Hello. My name is XXX XXX; I am an Engineer in Comcast's Voice Communications Engineering organization. I obtained your contact information from the Robocall Mitigation Database. Below is an example call and Identity header that fails Comcast's STIR-SHAKEN verification service. You are signing the call using only a 10 digit TO and FROM number. All TO and FROM numbers need to be 11 digits. Almost all 8M Comcast residential voice customers have Xfinity Voice Spam Blocker enabled with the default settings. Failed STIR-SHAKEN calls are sent directly to voicemail and do not ring my customer's phone." matt From: VoiceOps <[email protected]> On Behalf Of Matthew Crocker via VoiceOps Sent: Wednesday, April 5, 2023 3:59 PM To: [email protected] Subject: [VoiceOps] Outbound Calls being marked as SPAM We have a customer whos outbound calls are being marked as SPAM by the terminating carrier. We are sending the calls out fully signed (STIR/SHAKEN) with attest 'A' and all of the propery identity headers. The terminating carrier is Comcast from what we can tell, does anyone have any tricks we can use or something we may have missed to help get the calls marked correctly? Thanks -Matt
_______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
