Blocked outbound calls


New member
Recently we have run into a large number of outbound calls that cannot be completed and an audio message plays informing that the caller ID is blocked. I sent the following relative events from sip debug log to my carrier.

(I replaced the phones numbers and IP's with examples - the 555 area code is my cellphone, toll-free number is our main number, is my PBX, is my carrier)

From: "M8261430450002079298" <sip:18005551212@>;tag=as677b9662
To: <sip:+15556661212@>
Contact: <sip:18005551212@>
Call-ID: 4f9a41965a101ee52843a2606d491219@

The carrier support agent replied:
Certain carriers will participate and not block the calls, but some will restrict these from completing. This is due to :
--We would need valid FROM number built in the North American Numbering Plan. The FCC recently adopted new rules allowing carriers to "proactively block illegal calls." This rule includes automatic blocking of calls with Caller ID numbers which use unassigned area codes, numbers which do not have the correct number of digits, and unassigned repeating numbers like 000-000-0000 or 555-555-5555.
So it is now upon the downstream carrier to choose to participate or not.

Please adjust the From: "M8261430450002079298" to something more common.

I am looking for a solution to send only our e.164 Toll-Free number as our outbound caller ID as it is set in the Campaign Detail.

Campaign CallerID (our 11 digit Toll-Free #)
Custom CallerID: N
CID Group: Disabled

I am not sure where it is acceptable to make a change to the CALLERID to correct this problem. Any input is appreciated!
Thank you!


VERSION: 2.14-694a
BUILD: 181005-1738

Cluster 1 core + 2 dialers
SuperMicro board and chassis

Core DB+HTTP Server:
openSUSE Leap 42.3
Intel Xeon CPU E5-2620 v4 @ 2.10GHz - 8 core 16 thread

openSUSE Leap 42.3
Asterisk 13.21.1-vici
Intel Xeon CPU E3-1220 v3 @ 3.10GHz - 4 core 4 thread

openSUSE Leap 42.3
Asterisk 13.21.1-vici
Intel Xeon CPU E3-1220 v3 @ 3.10GHz - 4 core 4 thread


New member
Looks like you carrier is setting the caller id based on the FROM header, but add this setting to your carrier sendrpid = yes, if they accept to set the Caller id using the remote-party-id header it will work for you,