got some errors after update to astgui 2.2 from SVN

[ronator]

Hello there,

I followed the steps ans everything seemed fine. I could not really test it, beause on sundays all calls are routed away from my server. So, on the next morning i got an error when the system tried to connect the callers to the agent/conference room.

Luckily, my partners were able to "hack" a work-around; they told me, when the system tries to connect, they get an invalid-extension message and in the console the system looks for an extension like 83047777777777. The work-around was to define this extension in vicidial-auto (with ding and hangup).

My logs say this:
[code]May 17 08:00:26 VERBOSE[22137] logger.c: == Starting Local/172*020*001*015*78600052@default-d9aa,1 at vicidial-auto,83047777777777,1 failed so falling back to exten 's'
May 17 08:00:26 VERBOSE[22137] logger.c: == Starting Local/172*020*001*015*78600052@default-d9aa,1 at vicidial-auto,s,1 still failed so falling back to context 'default'
May 17 08:00:26 VERBOSE[22137] logger.c: -- Sent into invalid extension 's' in context 'default' on Local/172*020*001*015*78600052@default-d9aa,1
May 17 08:00:26 VERBOSE[22137] logger.c: -- Executing Playback("Local/172*020*001*015*78600052@default-d9aa,1", "invalid") in new stack
[/code]

I think I know the error: Could it be possible, that the update-script tries to change my AGI-Dial-String ? Especially when it comes to contexts ? Because originally I did not use the default context for incoming calls. Or is the update-script running the update-server-ip-script ?

I don not understand, why it adds 10 times 7 (7777777777) to the known extension 8304 what should just play a ding to my agents. Did this change to 83047777777777 or what's wrong here ?

Thank you for your attention.

Best wishes,
Ron Salvatore

-------------------------
Asterisk 1.2

AST GUI
VERSION: 2.2.1-237
BUILD: 100510-2015

[ronator]

I just read another posting, where someone mentions the agent alert extension wich changed to 83047777777777 with CALLERID(name) or something like that. So am I right, that I just have to modify my old "exten => 8304" just to "exten => 83047777777777" ?

Would this be normally done by the script, when I say YES to generate conf files (what I obviously did not, cause I was a little afraid) ?

Best wishes,
Ron Salvatore

[mflorell]

Did you read all of the UPGRADE doc when you upgraded?

Did you set the servers to rebuild conf files after your upgrade?

[ronator]

nope, i did not. which document :D ? I just did, what`s said on the maim-page, nothing else. nope, i did not, because i had no backup and didn't want to mess around with (potentionally) crapped conf files ...

Did you set the servers to rebuild conf files after your upgrade?

do you mean rebuild from the upgrade-script or within the web-interface in the server settings ? furthermore I cannot find any document what says something about changes in "agent alert"; i looked in /usr/share/astguiclient and /usr/src/astguiclient. could you please you give me a link or path to this document ?

well, is there any problem in re-running the perl script ? without updating mysql again ? I'll have a look at the UPGRADE docs, if I find 'em ^^

thank you very much.
best wishes

[ronator]

well, also the reports-agent-stats have been raped !
goddamnit, i have to re-run this script ! or else switch back to the old system.

Can you say something about the posibillities that a re-run could make things worse ? I mean the system is still running, but as an example, i can neither see PAUSE-stats nor PAUSED agents (not READY).

re-run ? maybe with --test :D ????

best wishes

[mflorell]

re-run which script?

The install.pl script can be run multiple times without issues.

Same with the upgrade_sql file, you should be able to run it with no problems.

What system settings DB Schema Version are you upgrading from?

[ronator]

Well, since I am no real DB admin, i can not really answer this question, what's somehow embarressing for me :/ where can I find this information ? I can only say we use mysql 5.0.77 with MyISAM and utf8_unicode_ci but you should already know this, because it's just installed from iso. I mean, vicidialnow-1.3 from cd and then upgrade astgui per svn.

I'll try re-running the script this night and then report here, so all press thumbs, please :D

best wishes
Ron Salvatore

[gardo]

You need to rebuild the Asterisk conf files as instructed by Matt. Here's a snapshot on where you can do it (Admin -> Servers -> Vicidial):



This will rebuild the Asterisk conf files to match the data on Mysql.

[ronator]

hey folks,

thank you very much for updating the upgrade-howto. Finally, I made a backup of /etc/asterisk and /var/www/html (just to be sure) and after re-reading the howto I just rebuild the conf files per web interface. In fact, I recognized the difference of extensions-vicidial.conf (e.g. the former, missed 83047777777777-extension), but one big problem still remained; Agents, who are in PAUSE are not displayed anymore. This is kinda anoying, because I upgraded only because the Agents Stats were wrong concerning the times (one hour to early), and now the times are fine, but PAUSED Agents aren't visible anymore. Only Agents with stats INCALL or READY are visible o_O

So, I decided to re-run install.pl in case something was missing. After that I rebuild conf per web interface, re-ran mysql-update, restarted all related services (mysql,httpd,asterisk) ... and in the end the problem remained.

In fact, I have no clue, what's going wrong there, I did not even check anything (logs/errors) because the system IS running fine but the presentation of data is somehow damaged. I just hoped anyone may have an idea, what's going on there, because it might be a "known problem".

The only thing I changed was modifying vicidial.php (some phrases translated into german) and therefore I renamed it (to something like vicidial-0.20.php, on which the "agent login"-link is pointing on). That's the only thing I changed (not considering any campaigns) in relation to the standard installation and still calls are going in and out with no problem: except the presentation / agent stats ...

If you need more information concerning my setup, please let me know. I think you have a better overview of the whole system, so I don't have to poke in the dark and accidently screw it up more than it is right now!

Maybe someone else had some similiar experiences ?!?!? Let us know !

Best wishes,
Ron Salvatore[/img]

[gardo]

How long has the agent been in PAUSE status? Normally if they have been in PAUSE for more than 30 or 60 mins they disappear from the realtime monitor page. You might also need to check on the date/time on their workstations. This needs to be synchronized with the VicidialNOW server. A screenshot of the monitor page can help us see what's happening.

[williamconley]

when you post, please post your entire configuration including (but not limited to) your installation method, vicidial version and build, asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box.

Similar to This:
Vicibox X.X from .iso | Vicidial X.X.X Build XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

(Just in case there is something unusual about your setup, or if this turns out to be a bug in need of tracking!!)

when you ran the install script, did you tell it to copy the sample configuration files? (If you had edited, and forgot, the original .conf files the fresh ones could resolve your issue).

[ronator]

thank you for creating this example! I think on the weekend I'll got enough time to provide you with the needed information.

best wishes
Ron Salvatore

[ronator]

These should be te requested information you needed:

Installation from cd, phones used (without any problems) Aastra 6753i, no cluster ...
ViciDial 1.3 | astgui 2.2 [ VERSION: 2.2.1-237, BUILD: 100510-2015 ] |
Asterisk 1.2.30.2 | single server | no digium | No extra software

Here is what I did: _Exactly_ what's written in your howto. Correct me if I am wrong, but I was the one who asked for adding the "rebuild conf files" to the upgrade-howto. One week later it was ... so i did that, too. It brought in and rebuilded the conf files but the live stats still didn't look correct. In the end I got back the agent-alert on 83047777777777 and the agent stats were correct in time (GMT+2).

The live stats are broken and transfer is also working another way, so i had to disable it, cause it uses "another string" than before the upgrade.

Except modifying /etc/asterisk/*.conf the only thing I can imagine could be related to the problem, is that I changed vicidial.php to vicidial-0.8.php. Might this create the error ?

still so thankful,
best wishes,
Ron Salvatore

[williamconley]

i did not mean "rebuild the conf files" in the GUI, i meant re-copy the conf files during the installation. this re-creates the STATIC conf files.

[gardo]

I just followed the upgrade instructions I posted on a fresh VicidialNOW install. Everything is working as it should. No manual editing of conf files necessary.

[dimorry]

I posted this in another thread, but after some more searching, this actually seems to be the same problem i'm having after updating to 2.2 svn.

I have two vicidialnow install servers one using BD and WEB and the other vicidial.

VICIDIAL VERSION: 2.2.1-237
BUILD: 100510-2015

My report was only showing the agents INCALL. It wasn't showing the paused agents and the other statuses (DISPO, DEAD...). To see if i could get a bit more information, i commented out the lines (for the PAUSED status)
if ($call_time_S >= 21600)
// {$j++; continue;}
//else
of the php report page and it is now showing only the paused agents call TIME with thousands. (which is why the other statuses weren't appearing before)

I have already checked the time and time zone in both the client and the servers and they are the same.

Here is a plot of the report with both INCALL and PAUSED statuses:

| SIP/3103 | SIRLEY + | 8600080 | INCALL | 0:47 | 1001 | 77 |
| SIP/3116 | IRENI + | 8600078 | PAUSED | 21275853:26 | 1001 | 38 |

I did check the root mail and found these two issues (it was an suggestion on the other thread)
on the DB/Web server - 192.168.200.3:
AST_vm_update.pl - unknown remote host line 174
AST_conf_update.pl - unknown remote host line 239

And on the Vicidial/Asterisk (192.168.200.6) I have a few:

DBI connect('asterisk:192.168.200.3:3306','cron',...) failed: Can't connect to MySQL server on '192.168.200.3' (110) at /usr/share/astguiclient/AST_manager_kill_hung_congested.pl line 116
Couldn't connect to database: Can't connect to MySQL server on '192.168.200.3' (110) at /usr/share/astguiclient/AST_manager_kill_hung_congested.pl line 116.

and basically the same error in these other scripts
ADMIN_keepalive_ALL.pl
AST_vm_update.pl
AST_CRON_audio_1_move_mix.pl
AST_VDhopper.pl -q
AST_conf_update.pl

I can remotely access mysql server from mysql prompt with without a problem. It seems to be a problem for perl to access the mysql server.
And besides these status in the report, everything seems to be working fine.

Is the status problem related to these script errors?
How can I fix these errors?

Thanks a lot,

Mauricio

[williamconley]

I can remotely access mysql server

are you remotely accessing as the cron user with the same password being used by perl with the same port?

[dimorry]

Yep.
Here is how i tested it from my vicidial server

[root@pabxsrv1 ~]# mysql -h 192.168.200.3 -p -u cron
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 8419860
Server version: 5.0.77 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql>

[dimorry]

Just to make sure, specifiying the database and the port also worked fine,
And acctually, the vicidial server does access the database server, since I am using vicidial with manual dialing. The cron password is the default (1234).

~]# mysql -h 192.168.200.3 -p asterisk -u cron --port=3306
Enter password:
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 8456367
Server version: 5.0.77 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql>

[williamconley]

try running the scripts in debug / debugX mode

[dimorry]

williamconley, my fault. The scripts are running fine. The mail file was quite large and I only looked at the first lines. When the errors were logged i was still configuring the servers.
This still leaves me with the wrong timing for other statuses except INCALL.
Any idea of what might be happening?

Thanks for the help

[dimorry]

Just figured out what the problem is.
I use a portuguese-brazil(agc_br) translation in the clients and that interface was not updated.
Thanks for the help though.

[williamconley]

thanks for posting the flaw!

update your language file and post it for others to use on the issue tracker!

[dimorry]

I downloaded the updated version from http://sourceforge.net/projects/astguiclient/

[ronator]

ok, this is somehow calming me that I wasn't the only one facing these cruel problems with agents not being displayed when in pause ...
I tried to follow dimorry, but hence I didn't get it all. I translated the vicidial.php manually (and only partially) into German. I did not understand if I can solve my problem the way dimorry did.
Furthermore I wonder why I have to re-copy anything ?

i did not mean "rebuild the conf files" in the GUI, i meant re-copy the conf files during the installation. this re-creates the STATIC conf files.

As mentioned, I did what was written in the SVN howto and there was nothing mentioned about re-copying anything ... since the system is still running, i somehow ignorred the problem the last weeks, so I have to think about, where I backed up the conf files before upgrade :/ So you mean to re-copy _my_ conf files should help me out ?

best wishes ...

[mflorell]

Did you read the UPGRADE document?

[dimorry]

ronator,

for testing, just have your clients log on the original /agc/vicidial.php, then check the paused statuses

[williamconley]

when you "upgrade" vicidial, one of the steps is to "install". this is done via the install.pl script.

during the "question and answer" of the install.pl script, one of the questions is whether to Copy sample configuration files. If you say "YES", it will use the configuration files which are specific to this version (thus if any changes are necessary to the configuration files, they are already made). All the other changes (database, php, etc.) are covered in other steps of the upgrade. But this one ... can be easily overlooked.

major progress in VICIdial was made in 2.0.5 and since then to make it possible to make all necessary changes without editing the configuration files directly. this means that "custom" configuration files should not be necessary any more. So copying the NEW configuration files each time you install or update is now possible without blowing away any custom changes (since you should not have any).

unless you have custom configuration files, always say yes to this option so you get the benefit of the wisdom and experience of the team building the software. they put those configuration files there with those entries because they work. the old ones ... may not.

[ronator]

why do I feel offended ?

hey, folks, please correct me if I am wrong, but when you change the tutorial from time to time cause of some users having little difficulties, why then pointig at me, asking if I have read the UPGRADE document?
You should better ask if I have re-read the tutorial, and yes, that bold line

Don't forget to answer "Y" when asked "Copy sample configuration files to /etc/asterisk/?"

wasn't there before I (and maybe others) reported their problems.

Moreover it was my suggestion to give a hint to the user, that he/she should rebuild conf files over web-interface .One week later the "Additional steps" were added ... To put it in a nutshell: I asked before doing it, if there are any known problems and the answer was: stick to the tut and everything is fine ... well it did not for me, so that's why I am here again. When I start an update-script and nothing special is mentioned, I suppose the default setting should work. Since the sentence "copy sample conf files to foobar" defaults to "no", I was fine doing so, cause I was afraid it could overwrite my original conf files ...

I know it is not easy to write a how-to everybody could follow; but don't blame me for this, I asked more than once !!! And yes, on the weekend I will re-try it and I think the day will come when I enter here again happilly telling everybody that it works fine again and that vicidialnow is the best opensource voip-server that ever has been outta there ;)

thx to williamconley for his unreached patience and competencies !!!

But this one ... can be easily overlooked.

Quite fair statement ... and thx for the little insight you gave with your previous posting ...

best wishes to all,
Ron Salvatore

P.S.: Press thumbs that I won't crash my whole system *g

[ronator]

ronator,

for testing, just have your clients log on the original /agc/vicidial.php, then check the paused statuses

oh my god, that idea was so close to my nose, that I couldn't smell nor see it.
*head --> table*

THX a lot ! I'll report when I got the time !!!!

[ronator]

ronator,

for testing, just have your clients log on the original /agc/vicidial.php, then check the paused statuses

Awesome, dimorry ! The pause status works ... But actually, I wonder why ? doesn't that mean, that the conf files are fine but my web-files are somehow "misconfigured" ??
Does someone know a fast way how I can get "agc2" to work properly again (with the information at hand, that "agc" just still works ...) ???

just re-running install.pl saying "yes" to "copy files to foobar" ???

Best wishes,
Ron Salvatore

[dimorry]

Ron,

if i'm not mistaken there is a problem with the agc2 interface and the svn 2.2.
I think i've read it somewhere in the forum.

[mflorell]

The white agc2 interface does not work with 2.2, only the default gray agent interface.

[gardo]

Yes. The modified agent interface only works for the older 2.0.5.X versions. We're currently porting it to 2.2.X. Hopefully we get to have it released by mid or end of July included with the next major release of the VicidialNOW project. Watch out for it.

Some or the changes are:

Updated base to CentOS 5.5
Astguiclient/Vici 2.2.X
Asterisk 1.4.X
Totally web based system

Everything is web based including systems and network configuration. Kinda like Elastix and Trixbox. No need to dive to the linux console.

[ronator]

Thank You all for joining this thread!
Now that is really a clear answer and now it makes sense to me, what has gone wrong. Although, since agc2 is the standard web-app with vicidial-1.3 (isn't it ?), I wonder why there is no WARNING that it might not work with agc2 ... The point is, that agc2 just looks fresher and more modern than the old one and since I saw the new client-interface, I strongly wanted to offer this to my agents instead of they dusty, grey-green interface with boring images.

Mabe I should have asked if it is possible with agc2 but, honestly, I didn't have it in mind ...

Best wishes to one of the greatest communities ....

thx a lot, my headache disappears ...

I'll report when I get it done (and explained to my agents: sorry, you gotta use the old interface :-( )

[ronator]

somehow offtopic, but nevertheless ...

Some or the changes are:

Updated base to CentOS 5.5
Astguiclient/Vici 2.2.X
Asterisk 1.4.X
Totally web based system

Everything is web based including systems and network configuration. Kinda like Elastix and Trixbox. No need to dive to the linux console. 8)

I hope it's clear to you, that I can't wait to install and work with the new major release :) Moreover, I think it's just about the time to use asterisk 1.4 and this will be a big milestone for this project. If I can help in testing anything, e.g. bug-reporting, it would be a pleasure for me to become a beta-tester ...

best wishes,
Ron Salvatore

[gardo]

Hey Ron,

We definitely need more testers. Hit me up with an email (demian.biscocho @ gmail.com) and let's talk off the board.

[ronator]

just to inform everybody: got all my agents switched back to agc-1 and everything seems to work fine (except some facts that I'll discuss in another thread ;). I even successfully begged my executives to get both of your manuals bought *proud*

so, right now I got a new "holy bible" (no one feel offended, plz), dispatching every page. Hope I will be through after the weekend and maybe there will be some threads never opened by myself cause I might already will have found the answer on myself ... i hope that was correct english (future II) :D

best wishes
Ron Salvatore


thread might be closed

[ronator]

wrote you an email