Page 1 of 1

LIVE AGENTS LOGGED IN: 0

PostPosted: Tue Jul 28, 2020 9:19 am
by liigi
Hi everybody how are you


I have a trouble with a recient vicidial cluster , i have 4 dialers working but one of then have a problem.i do a
Code: Select all
#screen -x ASTVDauto
and this show "LIVE AGENTS LOGGED IN: 0" , the dialer dont do calls but can recive calls trought other dialer ,So the agent can conect ,recive some of calls but trought another conected dialer .In asterisk , #sip show peers show the agents connected

two weeks ago I passed the problem and to solve reinstall but again I have the problem , and dont see any errors



VVersion: 2.14b0.5
SVN Version: 3179
DB Schema Version: 1587 WARNING: Code expects different schema: 1582 (For some reason de database is newer than code, but i have 3 Month working that without problemss )
DB Schema Update Date: 2020-03-11 13:16:35
dialer:
vicibox 9 3179
13.27.1-vici

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Tue Jul 28, 2020 9:30 am
by liigi
thanks in advance

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Tue Jul 28, 2020 9:34 am
by carpenox
Run these commands:

mysql -p -f --database=asterisk < /usr/src/astguiclient/trunk/extras/upgrade_2.14.sql
/usr/src/astguiclient/trunk/install.perl

-Nox

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Tue Jul 28, 2020 9:58 am
by liigi
Thanks brother

This is for updating the code? or to solve the problem of the dialer... That code notice has been like this for several months and it had not affected, I even have several dialers working without problem

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Tue Jul 28, 2020 10:30 am
by carpenox
that updates the db schema which is what puts each field into the correct places and pulls information into the dialer from the vicidial interface...it is very important to make sure that lines up correctly.

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Tue Jul 28, 2020 10:47 am
by liigi
ok i understand

To have a little more information. that database was with vicibox 8 and I already upgraded the schema to 9.so i aready run the upgrade_2.14.sql script .i need only to run the install.pl script , but i dont need to run too a svn up ?

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Tue Jul 28, 2020 10:52 am
by carpenox
if you do a svn upgrade, you then have to do the dbschema run and then perl install.pl

I do a svn every week

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Tue Jul 28, 2020 3:09 pm
by liigi
Ok thanks i will try that

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Tue Jul 28, 2020 10:33 pm
by liigi
it does not work. I do it from svn up, and install but only update the svn to 3270, but the error still shows .the DB Schema is newer than code

but that does not solve the problem I have with the dialer. I honestly dont think this is the problem since I have 6 more dialers and none of these presents problems.

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Tue Jul 28, 2020 10:51 pm
by carpenox
what is the database schema its showing?

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Wed Jul 29, 2020 7:25 pm
by liigi
i do a roll back

Version: 2.14b0.5
SVN Version: 3179
DB Schema Version: 1582

i solve the warning error of version ,doing a downgrade of db schema (manual run of the script)

but the dialer is still with problems

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Wed Jul 29, 2020 11:19 pm
by carpenox
OK lets start over then. What exactly is the problem your having? Can you provide an output from asterisk CLI during the problem?

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Thu Jul 30, 2020 11:15 am
by liigi
the dialer does not make calls but the logged in agents do receive calls through other dialers (through the iax trunks)
when i do a #screen -x ASTVDauto it show "LIVE AGENTS LOGGED IN: 0"

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Thu Jul 30, 2020 11:29 am
by liigi
This is sip peers 2 agents logged in
Name/username Host Dyn Forcerport Comedia ACL Port Status Description
10001/10001 (Unspecified) D Yes Yes 0 UNKNOWN
90089/90089 10.25.30.69 D Yes Yes 51996 UNREACHABLE
90110/90110 10.25.30.68 D Yes Yes 10535 OK (62 ms)
90123/90123 (Unspecified) D Yes Yes 0 UNKNOWN
90128/90128 (Unspecified) D Yes Yes 0 UNKNOWN
TR_PBXIP08_SRVLNXGW02/adm 10.10.10.2 Yes Yes 5060 OK (1 ms)
6 sip peers [Monitored: 2 online, 4 offline Unmonitored: 0 online, 0 offline]
work Trouble; __sip_xmit returns error for pkt data

but de vicidial service show 0 agente log in ,that's why an automatic dialer call is not generated

2020-07-30 12:21:07|| updating server parameters 100|8365|-4.00|default||
TIME DEBUG: -4.00|-4.00|0| GMT: 16:21
checking to see if listener is dead |1|
TIME DEBUG: -4.00|-4.00|0| GMT: 16:21
2020-07-30 12:21:10|SERVER CALLS PER SECOND MAXIMUM SET TO: 4 |250||
2020-07-30 12:21:10|LIVE AGENTS LOGGED IN: 0 ACTIVE CALLS: 0|
2020-07-30 12:21:10| : agents: 0 (READY: 0) dial_level: 0 (||) |
2020-07-30 12:21:10| : Calls to place: 0 (0 - 0 [0 + 0|0|0|0]) 0 |
2020-07-30 12:21:10|CAMPAIGN DIFFERENTIAL: 0 0 (0 - 0)|
2020-07-30 12:21:10|LOCAL TRUNK SHORTAGE: 0|0 (0 - 100)|
2020-07-30 12:21:10| : CALLING|
TIME DEBUG: -4.00|-4.00|0| GMT: 16:21
TIME DEBUG: -4.00|-4.00|0| GMT: 16:21

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Thu Jul 30, 2020 11:32 am
by carpenox
Ok anything in asterisk cli when they try to login?

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Thu Jul 30, 2020 2:31 pm
by liigi
Any erros,

this is a incominga call ,through the iax

ul 30 15:27:25] -- Accepting AUTHENTICATED call from 10.10.10.7:4569:
[Jul 30 15:27:25] -- > requested format = ulaw,
[Jul 30 15:27:25] -- > requested prefs = (ulaw|gsm),
[Jul 30 15:27:25] -- > actual format = ulaw,
[Jul 30 15:27:25] -- > host prefs = (ulaw),
[Jul 30 15:27:25] -- > priority = mine
[Jul 30 15:27:25] -- Executing [8600054@default:1] MeetMe("IAX2/virtualpx7-6721", "8600054,F") in new stack
[Jul 30 15:27:27] == Manager 'sendcron' logged on from 127.0.0.1
[Jul 30 15:27:27] -- Called 58600054@default
[Jul 30 15:27:27] -- Executing [58600054@default:1] MeetMe("Local/58600054@default-00000001;2", "8600054,Fmq") in new stack
[Jul 30 15:27:27] -- Local/58600054@default-00000001;1 answered
[Jul 30 15:27:27] -- Executing [8309@default:1] Answer("Local/58600054@defau lt-00000001;1", "") in new stack
[Jul 30 15:27:27] -- Executing [8309@default:2] Monitor("Local/58600054@default-00000001;1", "wav,20200730-152709_8123685395_luissanchez_2023") in new stack
[Jul 30 15:27:27] -- Executing [8309@default:3] Wait("Local/58600054@default-00000001;1", "3600") in new stack
[Jul 30 15:27:28] == Manager 'sendcron' logged off from 127.0.0.1

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Thu Jul 30, 2020 4:21 pm
by carpenox
ok and the dialer that isnt making calls, whats the CLI for that box? are you sure the dialplan is setup correctly for it?

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Fri Jul 31, 2020 7:58 am
by liigi
YEs sure , i can make manual dials , yes that is the dialer cli

yesterday i reainstall the dialer , butr still have the problem .What is the vicidial script, responsible for recognizing the connected agents to perform automatic dialing?

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Sun Aug 02, 2020 5:22 pm
by carpenox
here is what mine shows:

loop counter: |5693805|
TIME DEBUG: -5.00|-4|1| GMT: 22:22
2020-08-02 18:22:18|SERVER CALLS PER SECOND MAXIMUM SET TO: 5 |200||
2020-08-02 18:22:18|LIVE AGENTS LOGGED IN: 0 ACTIVE CALLS: 1|
2020-08-02 18:22:18| : agents: 0 (READY: 0) dial_level: 0 (||) |
2020-08-02 18:22:18| : Calls to place: -1 (0 - 0 [0 + 0|0|0|0]) 1 OTHER LIMIT override: 0|
2020-08-02 18:22:18|CAMPAIGN DIFFERENTIAL: 0 0 (0 - 0)|
2020-08-02 18:22:18|LOCAL TRUNK SHORTAGE: 0|0 (0 - 23)|
2020-08-02 18:22:18| : CALLING|
TIME DEBUG: -5.00|-4|1| GMT: 22:22
2020-08-02 18:22:18|| dead call vac XFERd do nothing|373082|9549477572|XFER||
TIME DEBUG: -5.00|-4|1| GMT: 22:22
2020-08-02 18:22:18| NO-ANSWER log check: Y, active, checking unprocessed calls...|
2020-08-02 18:22:18| NO-ANSWER log vle records count: 0|0|

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Mon Aug 03, 2020 1:58 pm
by williamconley
1) your db schema and your vicidial scripts Must Match.

2) to test this, you check the svn folder's highest version .sql script. The last line of that file will include a db schema value "update" request. That value must match the value in admin->system settings to prove that the scripts in the svn folder match the db schema. Note that this was about the scripts in the svn folder, not "in use presently". That would require running perl install.pl which propagates the svn folder files to the "in use" areas. And a reboot in case any of those screens or background processes were affected.

3) When you say "no errors" ... where are you looking? Apache logs? have you checked all the screens and/or astguiclieng logs?

4) Do not update/upgrade your Vicidial server (OS or Vicidial scripts) randomly. There's no purpose in this any more than you need to change the oil in your car weekly. In fact, it's much more likely that you'll eventually screw it up the more often you upgrade.

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Fri Aug 07, 2020 3:09 pm
by liigi
Hi

u say the /usr/src/astguiclient/trunk/extras sql scripts ?? the last line is "1587" but system settings show ( SVN Version:3179 , DB Schema Version: 1582) .So i need to run perl install.pl ? ,Only in the Database or all servers ?


I had only verified the asterisk logs in the dialer, because i have 6 dialers , all was install with the same dvd ,same realese 3179 , but only 1, the most newly instaled have this problem . Recently I put a new dialer and it worked fine until today that I restart the database services and now that dialer does not want make calls. I am thinking that the problem could be in the Database


in the database which logs can help me diagnose the problem ?¡

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Fri Aug 07, 2020 3:36 pm
by williamconley
liigi wrote:Hi

u say the /usr/src/astguiclient/trunk/extras sql scripts ?? the last line is "1587" but system settings show ( SVN Version:3179 , DB Schema Version: 1582) .So i need to run perl install.pl ? ,Only in the Database or all servers ?


I had only verified the asterisk logs in the dialer, because i have 6 dialers , all was install with the same dvd ,same realese 3179 , but only 1, the most newly instaled have this problem . Recently I put a new dialer and it worked fine until today that I restart the database services and now that dialer does not want make calls. I am thinking that the problem could be in the Database


in the database which logs can help me diagnose the problem ?¡


Your database in system settings is 5 versions behind the code. If you've installed from this code already (as it sounds like you have), then the code is more recent than the database and does not match. Reinstalling the code will not make it match the database.

Either downgrade the svn revision level until the last line is "1582" and then install that version of Vicidial with "perl install.pl", or upgrade the database using the sql file. I recommend deleting all the entries presently in the sql file before "1582" as they have already run and may not want to run again without crashing (ie: if the script tries to create an index or field that already exists, the command will fail, and the script will stop right there ... and NOT run the five entries you specifically need to run ... so just run those five instead and you're good!).

Also note that any time you run perl install.pl, you should include the "sample-conf-files" option. Sometimes there are changes to the conf files that are integral to Vicidial's functionality (not merely preferences). If you don't include the sample conf files, eratic failures can occur. But if you always include them, you're good to go ... assuming of course you have not customized them! Any customizations need to be re-edited after the upgrade. This includes (specifically) the "externip" value of sip.conf since that's almost always edited.

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Fri Aug 07, 2020 4:08 pm
by liigi
ok Thanks

i will do that , edit the script and run the last 5 lines,

Re: LIVE AGENTS LOGGED IN: 0

PostPosted: Fri Aug 07, 2020 4:26 pm
by williamconley
Note that there is a value in the astguiclient.conf:

Code: Select all
ExpectedDBSchema => 1540


If your upgrade works, update that value to avoid a warning in Admin->System Settings