vicidial_carrier_log contains dial string (channel) which uses a prefix to determine which carrier to use. However: That's not technically "the carrier" which is not logged by name.
- Code: Select all
+---------------+---------------------+---------------+-----------+--------------+------------+---------------------------------------+-----------+---------------+------------------+-------------------+----------------------+
| uniqueid | call_date | server_ip | lead_id | hangup_cause | dialstatus | channel | dial_time | answered_time | sip_hangup_cause | sip_hangup_reason | caller_code |
+---------------+---------------------+---------------+-----------+--------------+------------+---------------------------------------+-----------+---------------+------------------+-------------------+----------------------+
| 1741807971.18 | 2025-03-12 15:32:53 | 192.168.1.249 | 872410813 | 16 | ANSWER | Local/717035550000@default-00000002;2 | 2 | 0 | 0 | | V3121532500872410813 |
+---------------+---------------------+---------------+-----------+--------------+------------+---------------------------------------+-----------+---------------+------------------+-------------------+----------------------+
vicidial_dial_log has "Outbound CID" field which contains the "name" and <number> used (note that the name is actually a code for autodialed calls, which generally contains the Lead ID as the last digits in an otherwise fairly random string). This also still has the "channel" containing the dial prefix which should identify the carrier.
call_log has a "channel" field as well, which has the Account Name of the trunk used on certain types of records (one leg of a call after the call is live).