Sending CID in e164 format w CID Group

[mhaines]

Hello, I’ve used the forum “a-lot” for most of my set up and troubleshooting and it is a great resource. I’ve also read through the Managers Manual several times ver.2.14-704a but have not found a solution to sending CID Group numbers in e164 format. I am certain I’ve overlooked something easy, but I am struggling to identify the issue. When setting a CID in our dial plan entry, no issue, calls are sent using the CID specified in the e164 format. But when we use AC_CID Group, it sends the CID in SIP format (BELOW DETAIL)
We are trying to minimize our DID’s from being flagged as SPAM Likely and are rotating through our CID Group to help. We’ve verified our DID’s and added them on Shaken / Stir
CID is rotating properly on each call. Before reaching out to the forum, we have spent the last 2 days configuring and troubleshooting our Vicibox AC-CID Group and dialing settings.

We have outbound calls working / processing over twilio elastic SIP trunk but the format on the CID (FROM) is in SIP URI format and not in the needed E164 format. (BELOW vici logs)

In CID Group we added 1NPANXXXXXX only as in the CID Number field it will not accept “+” sign (BELOW)

I am hoping one of you can show me what I’m overlooking here.

Here are my stats:
Version: 2.14b0.5
SVN Version: 3261
DB Schema Version: 1599
DB Schema Update Date: 2021-08-04 06:49:41
Password Encryption: DISABLED - S1 - C1
Auto User-add Value: 101
Recording Prompt Count: 0
Install Date: 2021-08-04

ACCOUNT ENTRY:
[twiliovoip]
disallow=all
dtmfmode=rfc2833
allow=ulaw
allow=alaw
allow=g729
port=5060
username=opsifytwtrunk
secret=AiG4ei2thuN1
host=1840andco.pstn.singapore.twilio.com
insecure=port,invite
canreinvite=no
type=friend
qualify=yes
context=trunkinbound
nat=force,comedia
trustrpid=yes
sendrpid=yes

GLOBAL STRING: TWILIO = SIP/twiliovoip

DIAL PLAN ENTRY:
; TEST DIAL PLAN
exten => _91NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91NXXNXXXXXX,2,Dial(${TWILIO}/+1${EXTEN:2},,tTor)
exten => _91NXXNXXXXXX,3,Hangup


CID GROUP:
# NONE CID NUMBER
1 NONE 14132786776
2 NONE 15706054515
3 NONE 17146274352
4 NONE 19126167236


Vicidial Asterisk logs:

Feb 11 10:33:31] <--- SIP read from UDP:54.169.127.128:5060 --->
[Feb 11 10:33:31] SIP/2.0 183 Session progress
[Feb 11 10:33:31] CSeq: 103 INVITE
[Feb 11 10:33:31] Call-ID: 41c3bd2e1bff96822591e93e1798f154@117.120.1.59:5060
[Feb 11 10:33:31] From: "M2111033260000151716" <sip:14132786776@117.120.1.59>;tag=as6dc8d158
[Feb 11 10:33:31] To: <sip:+18124161934@1840andco.pstn.singapore.twilio.com:5060>;tag=38270690_c3356d0b_b86f24a0-f1ab-4eb6-b6e8-c10ab4828b69
[Feb 11 10:33:31] Via: SIP/2.0/UDP 117.120.1.59:5060;rport=5060;branch=z9hG4bK7e79e68a
[Feb 11 10:33:31] Record-Route: <sip:54.169.127.128;lr>
[Feb 11 10:33:31] Server: Twilio
[Feb 11 10:33:31] Contact: <sip:172.19.74.241:5060>
[Feb 11 10:33:31] Content-Type: application/sdp
[Feb 11 10:33:31] X-Twilio-CallSid: CA79fa71a5a42f7d8265bc26d678b6b779
[Feb 11 10:33:31] Content-Length: 274

[Feb 11 10:34:31] Call-ID: 006655ba161879ea23317ae94a29fcfd@117.120.1.59:5060
[Feb 11 10:34:31] From: "M2111034270000151689" <sip:19126167236@117.120.1.59>;tag=as61915544
[Feb 11 10:34:31] To: <sip:+18124161934@1840andco.pstn.singapore.twilio.com:5060>;tag=63464878_c3356d0b_a25a0129-70e7-40ba-abc1-3a17b037adef
[Feb 11 10:34:31] Via: SIP/2.0/UDP 117.120.1.59:5060;rport=5060;branch=z9hG4bK6b701007
[Feb 11 10:34:31] Record-Route: <sip:54.169.127.128;lr>
[Feb 11 10:34:31] Server: Twilio
[Feb 11 10:34:31] Contact: <sip:172.19.74.241:5060>
[Feb 11 10:34:31] Content-Type: application/sdp
[Feb 11 10:34:31] X-Twilio-CallSid: CA34aff721a61d64175e6aad0e5d70234f
[Feb 11 10:34:31] Content-Length: 273


Twilio CDR

Call SID and Date Status Direction From To Call Type Duration STIR Status
CAefbdb7b8d8e0e13f0f4ea569df58fbf6
15:38:14 UTC 2022-02-11 No Answer Trunking Terminating sip:14132786776@117.120.1.59 +18124161934 sip-pstn 0 sec B
CAf56300eb718d4d962c2a69ffe37e104f
15:37:18 UTC 2022-02-11 No Answer Trunking Terminating sip:15706054515@117.120.1.59 +18124161934 sip-pstn 0 sec —
CA185b90d767acee2d97e41c245be59daa
15:35:24 UTC 2022-02-11 No Answer Trunking Terminating sip:17146274352@117.120.1.59 +18124161934 sip-pstn 0 sec B
CA34aff721a61d64175e6aad0e5d70234f
15:34:28 UTC 2022-02-11 No Answer Trunking Terminating sip:19126167236@117.120.1.59 +18124161934 sip-pstn 0 sec B
CA79fa71a5a42f7d8265bc26d678b6b779
15:33:28 UTC 2022-02-11 No Answer Trunking Terminating sip:14132786776@117.120.1.59 +18124161934 sip-pstn 0 sec B
CA4b6246ae2cc4147a17c621dca78f4f84
15:31:55 UTC 2022-02-11 No Answer Trunking Terminating sip:15706054515@117.120.1.59 +18124161934 sip-pstn 0 sec B
CA863de313e3628b92c11854d11a8db2fb
15:30:36 UTC 2022-02-11 No Answer Trunking Terminating sip:17146274352@117.120.1.59 +19132133240 sip-pstn 0 sec B
CAea831bccd6040ab1a29fb73697f4e522
15:27:47 UTC 2022-02-11 No Answer Trunking Terminating sip:19126167236@117.120.1.59 +17147236910 sip-pstn 0 sec B


Thank you,

[mflorell]

We've never had a client request the ability to include the plus sign '+' with CIDnumber, so it's something we've never even tested before.

[mhaines]

Thank you Matt, I appreciate your time. Yeah, twilio tends to be a bit finicky and we are constantly referred to the need to use E164 format to avoid being flagged. Thanks again,

[striker]

use the dialplan to set +(plus) for the callerid set by AC_CID group.

exten => _91NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91NXXNXXXXXX,n,NoOp(CALLERID SET BY AC CID IS ${CALLERD(num)})
exten => _91NXXNXXXXXX,n,Set(newcid=${CALLERID(num)})
exten => _91NXXNXXXXXX,n,Set(CALLERID(num)=+${newcid})
exten => _91NXXNXXXXXX,n,NoOp(My current callerid ${CALLERID(num)})
exten => _91NXXNXXXXXX,n,Dial(${TWILIO}/+1${EXTEN:2},,tTor)
exten => _91NXXNXXXXXX,n,Hangup()

[carpenox]

Thank you Matt, I appreciate your time. Yeah, twilio tends to be a bit finicky and we are constantly referred to the need to use E164 format to avoid being flagged. Thanks again,

yea their shaken token identifier is crap. who requires a + other than them? their lookup method is total bs. ive had the same issues with certain clients that use them, then i show them other options which are better such as tiltx

[OGZROC24]

use the dialplan to set +(plus) for the callerid set by AC_CID group.

exten => _91NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91NXXNXXXXXX,n,NoOp(CALLERID SET BY AC CID IS ${CALLERD(num)})
exten => _91NXXNXXXXXX,n,Set(newcid=${CALLERID(num)})
exten => _91NXXNXXXXXX,n,Set(CALLERID(num)=+${newcid})
exten => _91NXXNXXXXXX,n,NoOp(My current callerid ${CALLERID(num)})
exten => _91NXXNXXXXXX,n,Dial(${TWILIO}/+1${EXTEN:2},,tTor)
exten => _91NXXNXXXXXX,n,Hangup()

On behalf of mhaines and our team, THANK YOU SO MUCH for your help. This dial plan entry really solved our issue with sending E164 format. Kuddos!

[atkins513]

We've never had a client request the ability to include the plus sign '+' with CIDnumber, so it's something we've never even tested before.

I'm having similar problems with getting the caller ID's to fully display, and being marked as spam.
Would this "plus" solution help in my case?

My Dial plan is

exten => _5.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _5.,2,Dial(${NESIDTTRUNK}/99904${EXTEN:2},,To)
exten => _5.,3,Hangup()



VERSION: 2.14-634c BUILD: 210421-2110