Skip to main content

Vicidial showing UID as CID - Loopback Dialplan to remove UID

 

Vicidial showing UID as CID - Loopback Dialplan to remove UID


Topic: Vicidial showing UID instead of CID and Loopback Dialplan

    In vicidial while dialing out you may notice the UID as Caller ID or Caller Name, both in manual dial as well auto dial. Too remove this UID you have to use vicidial loopback Dialplan or your trunk provider should trim the UID from the SIP header.

    By default vicidial sets the campaign caller ID as Caller ID and UID as the Caller ID name, if your voip trunk provider not trimming the callerid name sent from vicidial, the customers will see the UID as the caller ID.



How to remove vicidial UID - CID?

    In Vicidial the UID which is showing caller ID can be removed by three ways , particularly for CANDADA dialing you have to remove the UID in From SIP Header.

Vicidial Loopback Dialplan
Another Asterisk server as Trunk or SBC
Trunk provider to Trim discard UID

Vicidial Loopback Dialplan

    Vicidial by default have the option called loopback trunk ,using the loopback trunk you can remove the UID added in Caller ID name before dialing out via Carrier

note: But using the loopback trunk dialing will increase the load on the system.

Steps to create loopback Dialplan.

    For vicidial loopback Dialplan you need to add the carrier with loopback Dialplan in vicidial admin portal and edit the extensions.conf in console for carrier Dialplan .

Step 1: Create Carrier with Loopback Dialplan entry

    Under vicidial carrier settings, add your carrier details with the below dial plan entry,

Consider your trunk name in account enry is [siptrunk1] and dial prfix used in campaign is 9988 and dialing to US numbers, if you are dialing other countries modify the dialplan , for more details on dialplan check my tutorial on dialplan entry

Dialplan entry

exten => _99881NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _99881NXXNXXXXXX,n,NoOp(MY CALLERD !!!! ${CALLERID(all)})
exten => _99881NXXNXXXXXX,n,Set(_CALLERID(num)=${CALLERID(num)})
exten => _99881NXXNXXXXXX,n,Dial(${TRUNKloop}/999${EXTEN:4},55,Tto)
exten => _99881NXXNXXXXXX,n,Hangup()
exten => _9991NXXNXXXXXX,1,Goto(loopback-no-log,9${EXTEN:3},1)
exten => _9991NXXNXXXXXX,n,Hangup()

Step 2: Extension.conf for carrier dialplan

    Now you need to login the console either ssh to the server using putty or direct console access.
using nano or vi editor open the file extensions.conf

nano  /etc/asterisk/extensions.conf

now under the loopback-no-log context add the below Dialplan, which actually dials through your carrier

[loopback-no-log]
exten => _91NXXNXXXXXX,1,Set(CALLERID(name)=${CALLERID(num)})
exten => _91NXXNXXXXXX,n,Dial(SIP/siptrunk1/${EXTEN:1},,Tto)
exten => _91NXXNXXXXXX,n,Hangup()

save the file and reload the asterisk once

asterisk -rx "reload"

Solution 2: other SIP server as trunk

    You can use another SIP server like asterisk, open sips and create a trunk between the vicidial and the other SIP server, the Other SIP will be configured with the actual carrier sip settings to dialout, the vicidial will be registering to the other SIP server either via SIP trunk or IAX trunk.

Solution 3: Trim the Caller ID Name

    you may request your Trunk provider to trim the caller ID name sent by the vicidial, which is the easiest way, but few of the vendors wont supports this, is this case either use solution 1 or solution 2 mentioned in this article.

Comments

Popular posts from this blog

Install OpenVPN 2.4 and 2.6 on Alma / Rocky Linux

 To install OpenVPN on AlmaLinux 9.5, you can follow these steps: 1. Update the System : Before installing any software, it's a good idea to update your system: sudo dnf update -y 2. Install EPEL Repository : OpenVPN is available in the EPEL (Extra Packages for Enterprise Linux) repository. First, install the EPEL repository: sudo dnf install epel-release -y 3. Install OpenVPN : After enabling the EPEL repository, install OpenVPN: sudo dnf install openvpn -y 4. Install NetworkManager (Optional) : If you are using NetworkManager for managing network connections, you can install the OpenVPN plugin for NetworkManager: sudo dnf install NetworkManager-openvpn -y 5. Configure OpenVPN : Once installed, you need to configure OpenVPN by copying your .ovpn configuration file to the /etc/openvpn/ directory: sudo cp /path/to/your/config.ovpn /etc/openvpn/ 6. Start OpenVPN : You can start OpenVPN by specifying the configuration file directly: sudo openvpn --config /etc...

Vicidial Scratch installation Alma -9/10

Step 1 – Download the dependencies   hostnamectl set-hostname xxxxxx.xxxxx.xxx ### Use YOUR SubDomain vi /etc/hosts ##Change domain name for actual server ip (xxx.xxx.xxx.xxx   complete domain name    subdomain only) timedatectl set-timezone Asia/Kolkata yum check-update yum update -y yum -y install epel-release yum update -y yum install git -y yum install -y kernel* sudo dnf install kernel-devel-$(uname -r) -y # Install english language pack dnf install -y glibc-langpack-en # Configure new locale. This basically just edits /etc/locale.conf localectl set-locale en_US.UTF-8 #Disable SELINUX sed -i 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/selinux/config     reboot Step 2 – Run the Script cd /usr/src/ git clone https://github.com/manish23k/vicidial-install-scripts cd vicidial-install-scripts ####For PHP 7.4 use this script. chmod +x alma-rocky9-ast16.sh ./alma-rocky9-ast16.sh Or the Asterisk 18 version: chmod +x alma-rocky9-ast18.sh ./alma-rock...

How to Format and Mount a New 1TB HDD

🖥 How to Format and Mount a New 1TB HDD to /var/www/recordings on Linux If you’ve added a new HDD to your Linux server and want to use it as a dedicated storage location — for example, to store Asterisk or web server recordings — you’ll need to partition, format, mount, and configure it to auto-mount at boot . In this guide, we’ll walk through the process of wiping the drive (careful — data will be lost!), creating a single ext4 partition , and mounting it permanently. Step 1: Identify Your New Disk Run: lsblk Example output: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8 : 0 0 931.5 G 0 disk ├─sda1 8 : 1 0 50 M 0 part ├─sda2 8 : 2 0 540.8 G 0 part └─sda3 8 : 3 0 390.6 G 0 part In our case, /dev/sda is the new 1TB disk. ⚠ Warning: Double-check you’ve picked the right disk! Formatting the wrong one will destroy data. Step 2: Unmount Any Mounted Partitions sudo umount /dev/sda* 2>/dev/null Step 3: Wipe Old Partitions and Create One ...