AWS Chime Clip No Screening Support

[0xnullcats]

On the website Chime is listed as supporting clip no screening, is this still true? I am unable to change the outbound caller ID to any of my numbers.

The numbers are properly formatted, I've censored them but the only thing I've changed is the values.

3CX Log: Call or Registration to +11235551234@(Ln.10000@Amazon Chime Voice Connector) has failed. sip:12.34.56.78:5060;transport=TCP;lr replied: Forbidden (403)

Chime Log:
"sip_message":"SIP/2.0 403 Caller Id +10005551234 (Properly formatted number) is not valid
Via: SIP/2.0/TCP 123.45.67.89:5060;received=1.23.45.678;branch=z9hG4bK-524287-1---d2b02f20dd774b20;rport=48519
From: "+10005551234"<sip:+10005551234@chime_termination_id.voiceconnector.chime.aws;transport=TCP>;tag=e7a14355


I can't seem to find any information on clip no screening, as to what that actually means, if it's not simply using a custom caller ID.

I understand the FCC is becoming more strict on caller IDs, if AWS doesn't support this feature anymore, are there any providers that will allow me to do this without messing with the number?

 

[TheodorosG_3CX]

Amazon Chime does support Clip No Screening:


Have you also checked documentations here and here?

 

[0xnullcats]

Amazon Chime does support Clip No Screening:
View attachment 41304

Have you also checked documentations here and here?

Yes. I have followed the configuration guide closely, as well as the guides linked in that article. I am using Chime because it is more accessible to me. I already use AWS for most of my work. From what I've found, the partnered services require sensitive documents I'm not totally willing to present online.

I understand completely if there is simply no way to achieve what I want, how I want.

Thank you for your time.

 

[TheodorosG_3CX]

Where do you set the caller id?

 

[0xnullcats]

Where do you set the caller id?

I tried multiple places and methods in the 3cx UI:
- Within the trunk settings, Under Options > Caller ID Control
- Under Outbound Rules > Outbound Caller ID

(Please note I tried multiple combinations of settings, different numbers both real and 555, and I have censored the area code with 201, the area code I used is the one in which my real numbers use.)

I tried within AWS but you can only set CNAME, which doesn't allow numbers and takes like a week to update.

 

[TheodorosG_3CX]

Please check this guideline here in order to see how the PBX is handling the outbound caller id.
Then you need to make some test calls with captures. If the PBX does sent the information to the provider but this does not passthrough then you need to contact the provider for further clarification.

 

[0xnullcats]

Within AWS cloudwatch, there are logs showing the set outbound caller ID, so I think the PBX is sending it correctly but AWS does not support it anymore, which is why I asked.

Thank you for your time, I appreciate the effort

 

[TheodorosG_3CX]

You are welcome