Re: [VoiceOps] Outbound Calls being marked as SPAM

2023-04-05 Thread Matthew Crocker via VoiceOps

I just verified the outbound calls are going out with 11 digit To & From 
headers,  11 digit TN in the STI Auth Token,  Attest ‘A’.

Trying to work through out contacts at Comcast to get this resolved.

Thanks again

-Matt


From: Mark R Lindsey 
Date: Wednesday, April 5, 2023 at 4:56 PM
To: Matthew Yaklin 
Cc: Matthew Crocker , voiceops@voiceops.org 

Subject: Re: [VoiceOps] Outbound Calls being marked as SPAM
CAUTION: This email originated from outside of Crocker. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.

Matt, That's really helpful. The ATIS NNI documents functionally set the 
standard for many of these matters, and number formatting ("canonicalization") 
is one of the big ones. You can find some details on the canonicalization 
algorithm in some of their docs:
https://access.atis.org/apps/group_public/download.php/67436/ATIS-174.v003.pdf
https://access.atis.org/apps/group_public/download.php/63572/IPNNI-2022-9R000.docx

The number formatting is summarized several places like this:
...treat the calling TN as if it were an E.164 number; i.e., canonicalize the 
calling TN to remove any leading “+” sign or visual separators (i.e., “.”, “-”, 
“(”, and “)”)

Thus the "orig" value for a STIR/SHAKEN header should be something like 
"12293160013"  (because the country code is 1), and when the UK is sending 
PASSporT's someday, the orig value would be something like "442078702900" 
(because 44 is the UK country code).


Mark R Lindsey | +1-229-316-0013 | m...@ecg.co | Schedule a 
Meeting | 
Newsletter


On Apr 5, 2023, at 16:07, Matthew Yaklin via VoiceOps  
wrote:

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 
mailto:voiceops-boun...@voiceops.org>> On Behalf 
Of Matthew Crocker via VoiceOps
Sent: Wednesday, April 5, 2023 3:59 PM
To: voiceops@voiceops.org
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
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

___
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops


Re: [VoiceOps] Outbound Calls being marked as SPAM

2023-04-05 Thread Mark R Lindsey via VoiceOps
Matt, That's really helpful. The ATIS NNI documents functionally set the 
standard for many of these matters, and number formatting ("canonicalization") 
is one of the big ones. You can find some details on the canonicalization 
algorithm in some of their docs:
https://access.atis.org/apps/group_public/download.php/67436/ATIS-174.v003.pdf
https://access.atis.org/apps/group_public/download.php/63572/IPNNI-2022-9R000.docx

The number formatting is summarized several places like this:
...treat the calling TN as if it were an E.164 number; i.e., canonicalize the 
calling TN to remove any leading “+” sign or visual separators (i.e., “.”, “-”, 
“(”, and “)”)

Thus the "orig" value for a STIR/SHAKEN header should be something like 
"12293160013"  (because the country code is 1), and when the UK is sending 
PASSporT's someday, the orig value would be something like "442078702900" 
(because 44 is the UK country code).


Mark R Lindsey | +1-229-316-0013 | m...@ecg.co | Schedule a Meeting 
 | Newsletter 


> On Apr 5, 2023, at 16:07, Matthew Yaklin via VoiceOps  
> wrote:
> 
> 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  > On Behalf Of Matthew Crocker via 
> VoiceOps
> Sent: Wednesday, April 5, 2023 3:59 PM
> To: voiceops@voiceops.org 
> 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
> VoiceOps@voiceops.org 
> https://puck.nether.net/mailman/listinfo/voiceops

___
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops


Re: [VoiceOps] Outbound Calls being marked as SPAM

2023-04-05 Thread Matthew Yaklin via VoiceOps
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  On Behalf Of Matthew Crocker via 
VoiceOps
Sent: Wednesday, April 5, 2023 3:59 PM
To: voiceops@voiceops.org
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
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops


[VoiceOps] Outbound Calls being marked as SPAM

2023-04-05 Thread Matthew Crocker via VoiceOps

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
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops