Not save register in call_log table

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Not save register in call_log table

Postby dgxa » Mon Jun 06, 2022 4:02 pm

Hello all,

I have a issue with my table call_log in my mariadb, I have some dialplans with a prefix of 5 digits. Results that my phone numer have 9 digits and the total of the are the prefix + my number is 14

The field number_dialed is a varchar(15) but not save nothing in the table. I don´t know what happen, with some prefix of 5 digist work fine and with the others not.

Centos 7 3.10.0-1160.15.2.el7.x86_64 || VERSION: 2.14-772a BUILD: 201004-1045 || mysql Ver 15.1 Distrib 5.5.68-MariaDB
dgxa
 
Posts: 60
Joined: Tue Oct 06, 2020 5:05 pm

Re: Not save register in call_log table

Postby williamconley » Mon Jun 06, 2022 5:05 pm

Instructions for your installation (well, a link to them) would be a Good Idea. Since your installation is obviously not stock. If it was Goautodial, then please post the installer version/full .iso name. Often problems arise directly linked to the installation method.

See if you can find two records in the asterisk logs: One that is proper and one that is not, and compare them.

Note that a missing "h" extension can cause missing data (as the "h" extension initiates the port 4577 agi script that performs cleanup and many log entries).

Also be sure the carrier agi extension occurs, as without that there would be virtually nothing in the logs (vicidial is unaware of the call, just a request to make it).
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 20019
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)

Re: Not save register in call_log table

Postby dgxa » Tue Jun 07, 2022 1:21 pm

williamconley wrote:Instructions for your installation (well, a link to them) would be a Good Idea. Since your installation is obviously not stock. If it was Goautodial, then please post the installer version/full .iso name. Often problems arise directly linked to the installation method.

See if you can find two records in the asterisk logs: One that is proper and one that is not, and compare them.

Note that a missing "h" extension can cause missing data (as the "h" extension initiates the port 4577 agi script that performs cleanup and many log entries).

Also be sure the carrier agi extension occurs, as without that there would be virtually nothing in the logs (vicidial is unaware of the call, just a request to make it).


I validate how your suggestion I found this error

Call with the error
Code: Select all
[Jun  7 13:04:11] WARNING[32662][C-0000e631]: res_agi.c:2039 handle_connection: Connecting to '127.0.0.1:77' failed for url 'agi://127.0.0.1:77/call_log': Connection refused
[Jun  7 13:04:11] WARNING[32662][C-0000e631]: res_agi.c:2099 launch_netscript: Couldn't connect to any host.  FastAGI failed.


Call sucess
Code: Select all
-- Executing [5034999999999@default:1] AGI("SIP/002783281-0000811b", "agi://127.0.0.1:4577/call_log") in new stack
    -- <SIP/002783281-0000811b>AGI Script agi://127.0.0.1:4577/call_log completed, returning 0


Port of the agi was bad. Change from 77 to 4577 in the dial plan was the correction.

Thank you very much williamconley for your help
dgxa
 
Posts: 60
Joined: Tue Oct 06, 2020 5:05 pm

Re: Not save register in call_log table

Postby williamconley » Wed Jun 08, 2022 2:48 pm

excellent detail on the postback

Stick around and help others! 8-)
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 20019
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)


Return to Support

Who is online

Users browsing this forum: Google [Bot] and 60 guests

cron