Blocked outbound calls

[ryanhs]

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, 10.10.10.10 is my PBX, 10.10.10.20 is my carrier)

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

-----
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!

-Ryan

------------------------------
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
16GB RAM
SSD RAID

Dialer1:
openSUSE Leap 42.3
Asterisk 13.21.1-vici
Intel Xeon CPU E3-1220 v3 @ 3.10GHz - 4 core 4 thread
8GB RAM
HDD RAID

Dialer2:
openSUSE Leap 42.3
Asterisk 13.21.1-vici
Intel Xeon CPU E3-1220 v3 @ 3.10GHz - 4 core 4 thread
8GB RAM
HDD RAID

[ambiorixg12]

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,

[ryanhs]

Thank you very much ambiorixg12!

[ryanhs]

We have had less problems with our calls being blocked dialing out since adding sendrpid = yes however it is still not correct. Our Caller ID now shows up as 10 digits instead of 11 even though I have 11 digits entered in the Campaign Caller ID Field.

[Sep 13 08:21:25] -- Executing [51801xxxxxxx@default:1] AGI("Local/8600064@default-0000006f;1", "agi://127.0.0.1:4577/call_log") in new stack
[Sep 13 08:21:25] -- AGI Script Executing Application: (EXEC) Options: (Set(_CAMPCUST=TEST1))
[Sep 13 08:21:25] -- <Local/8600064@default-0000006f;1>AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
[Sep 13 08:21:25] -- Executing [51801xxxxxxx@default:2] Dial("Local/8600064@default-0000006f;1", "SIP/bandwidth/+1801xxxxxxx,,tTo") in new stack
[Sep 13 08:21:25] == Using SIP RTP CoS mark 5
[Sep 13 08:21:25] Audio is at 17122
[Sep 13 08:21:25] Adding codec ulaw to SDP
[Sep 13 08:21:25] Adding non-codec 0x1 (telephone-event) to SDP
[Sep 13 08:21:25] Reliably Transmitting (no NAT) to xx.xx.xx.xx:5060:
[Sep 13 08:21:25] INVITE sip:+1801xxxxxxx@xx.xx.xx.xx:5060 SIP/2.0
[Sep 13 08:21:25] Via: SIP/2.0/UDP xx.xx.xx.xx:5060;branch=z9hG4bK2ad6c1bf
[Sep 13 08:21:25] Max-Forwards: 70
[Sep 13 08:21:25] From: "M9130821250002084220" <sip:1800xxxxxxx@xx.xx.xx.xx>;tag=as35aef776
[Sep 13 08:21:25] To: <sip:+1801xxxxxxx@xx.xx.xx.xx:5060>
[Sep 13 08:21:25] Contact: <sip:1800xxxxxxx@xx.xx.xx.xx:5060>
[Sep 13 08:21:25] Call-ID: 61d001fa1ea0253a77aa4b7578046f17@xx.xx.xx.xx:5060
[Sep 13 08:21:25] CSeq: 102 INVITE
[Sep 13 08:21:25] User-Agent: Asterisk PBX 13.21.1-vici
[Sep 13 08:21:25] Date: Fri, 13 Sep 2019 14:21:25 GMT
[Sep 13 08:21:25] Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
[Sep 13 08:21:25] Supported: replaces, timer
[Sep 13 08:21:25] Remote-Party-ID: "M9130821250002084220" <sip:1800xxxxxxx@xx.xx.xx.xx>;party=calling;privacy=off;screen=no
[Sep 13 08:21:25] Content-Type: application/sdp
[Sep 13 08:21:25] Content-Length: 259
[Sep 13 08:21:25]
[Sep 13 08:21:25] v=0
[Sep 13 08:21:25] o=root 1486936172 1486936172 IN IP4 xx.xx.xx.xx
[Sep 13 08:21:25] s=Asterisk PBX 13.21.1-vici
[Sep 13 08:21:25] c=IN IP4 xx.xx.xx.xx
[Sep 13 08:21:25] t=0 0
[Sep 13 08:21:25] m=audio 17122 RTP/AVP 0 101
[Sep 13 08:21:25] a=rtpmap:0 PCMU/8000
[Sep 13 08:21:25] a=rtpmap:101 telephone-event/8000
[Sep 13 08:21:25] a=fmtp:101 0-16
[Sep 13 08:21:25] a=ptime:20
[Sep 13 08:21:25] a=maxptime:150
[Sep 13 08:21:25] a=sendrecv
[Sep 13 08:21:25]
[Sep 13 08:21:25] ---
[Sep 13 08:21:25] -- Called SIP/bandwidth/+1801xxxxxxx
[Sep 13 08:21:25]
[Sep 13 08:21:25] <--- SIP read from UDP:xx.xx.xx.xx:5060 --->
[Sep 13 08:21:25] SIP/2.0 100 Giving a try
[Sep 13 08:21:25] Via: SIP/2.0/UDP xx.xx.xx.xx:5060;branch=z9hG4bK2ad6c1bf
[Sep 13 08:21:25] From: "M9130821250002084220" <sip:1800xxxxxxx@xx.xx.xx.xx>;tag=as35aef776
[Sep 13 08:21:25] To: <sip:+1801xxxxxxx@xx.xx.xx.xx:5060>
[Sep 13 08:21:25] Call-ID: 61d001fa1ea0253a77aa4b7578xxxxx@xx.xx.xx.xx:5060
[Sep 13 08:21:25] CSeq: 102 INVITE
[Sep 13 08:21:25] Server: Bandwidth.com TRM (bw7.gold.13)
[Sep 13 08:21:25] Content-Length: 0

[ryanhs]

The carrier verified that they sent all the digits downstream that I sent for Caller ID and are not yet sure why that is getting stripped. They also expect "From:" to be the actual Caller ID. Is there any way to change that in VICIdial?

[williamconley]

10 v 11 digits is often set by the receiving carrier as a matter of technical correctness.

If you are calling FROM the US to and TO the US, 10 digit dialing is the rule and a 10 digit caller ID is preferred by many in this scenario. In fact, there are many carriers where the recipient can set this in their preferences (include or exclude the country code).

While you could consider adding the + in front of your 11 digits, it may simply be out of the control of any carrier except the recipients ... and you can't fix that.

[ambiorixg12]

They also expect "From:" to be the actual Caller ID. Is there any way to change that in VICIdial?

On your carrier setting you need to set this parameter fromuser=XXXXX where XXXX is the CID number expected by your carrier on the FROM header

[ryanhs]

We have different DID's for each campaign so I need to send the respective Caller ID's. To get around that I will setup multiple carriers with different dial prefixes and use "fromuser=" in the carrier.

Thank you!