vicidial.org

Can someone pls help:
I logged on to the vicidial agent interface got the message that I am the only one logged on to this conference by the softphone. However on opening the agent Interface I got "Your session has been disabled.I have also gone through the managers and agent manuals.
My CLI gave me this
> Channel SIP/204-094d3038 was answered.
-- Executing MeetMe("SIP/204-094d3038", "8600051|F") in new stack
== Parsing '/etc/asterisk/meetme.conf': Found
-- Created MeetMe conference 1023 for conference '8600051'
-- Playing 'conf-onlyperson' (language 'en')
== Manager 'sendcron' logged off from 127.0.0.1
== Refreshing DNS lookups.
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
Thanks for ur help.

a) did you change your IP address? (If so, did you reboot afterwards?)

b) the way you describe it, it sounds almost like you are opening two different interfaces. I'm just making sure: You only log in ONCE, right? (phone login, phone pass, agent login, agent pass ... and you're in ... nothing else, right?)

Thanks for the reply williams.

(a)I cant actually remember the last change i made before i came across dis your session has been disable.But am sure i did not change my IP address after my installation.
(b) I only log in once with phone login,phone pass,user login,user passwd,campaign then my soft phone rang it was picked and i heared you are the only one in this conference.
(c) pls is park and music on hold the same thing.


Thanks.

park and music on hold are not the same thing. but "music on hold" is played for a call that has been "parked", so they can be related.

the music on hold app just plays sound on a channel. (music?)

the park app is storage for a caller (like pushing the Hold button on an older telephone).

How long have you been experiencing "Your session has been disabled"? when did it first occur? how often does it occur? can you reproduce it (make it happen)?

Please help me out, i have working vicidialnow for 5 months. we use vicidialnow as a backup of our main call center suit, i just shutdown the vicidialnow for 2 days now its not allowing anyone to login the agent interface just as anyone login he recieves a call with greetings " your are the only one in this conference but on web it shows your session has been disabled. i dont know whats the problem, i have tried everything but unsuccessful.

sraza wrote:Please help me out, i have working vicidialnow for 5 months. we use vicidialnow as a backup of our main call center suit, i just shutdown the vicidialnow for 2 days now its not allowing anyone to login the agent interface just as anyone login he recieves a call with greetings " your are the only one in this conference but on web it shows your session has been disabled. i dont know whats the problem, i have tried everything but unsuccessful.

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)

its Built version of vicidialnow CE1.3 installed on Pentoum D system with 2 GB RAM and 160 GB HDD, OS offcourse Centos

kernel: [root@vici / ]# uname -a
Linux vici.vicidialnow.org 2.6.18-164.el5.vnow #1 SMP Mon Nov 16 03:11:26 PHT 2009 i686 i686 i386 GNU/Linux

sorry not to mention, i have eyebeam soft phone. i recieve the initial greetings and also the call continues but on screen it shows your session has been disabled.
i tried removing the <span style="position:absolute;left:0px;top:0px;z-index:31;" id="AgenTDisablEBoX">
<table border=1 bgcolor="#FFFFFF" width=<?=$CAwidth ?> height=500><TR><TD align=center>Your session has been disabled<BR><a href="#" onClick="LogouT('DISABLED');return false;">LOGOUT</a><BR><BR><a href="#" onClick="hideDiv('AgenTDisablEBoX');return false;">Go Back</a>
</TD></TR></TABLE>
</span>

in vicidial.php inside /var/www/html/agc2/

then i dont see this message but i dont get inbound call when the above lines are removed.

1) Vicidial X.X.X Build XXXX ?
2) Asterisk X.X.X ?
3) Single Server ?
4) No Digium/Sangoma Hardware ?
5) No Extra Software After Installation ?

Then:

the "agent screen" does not disable the session. It merely informs you that your session is disabled.

without your configuration information it's hard to guess why. i'd like to help.

1) Vicidial X.X.X Build XXXX ?

VicidialNOW CE 1.3

2) Asterisk X.X.X ?

asterisk-1.2.30.2

3) Single Server ?

yes single server

4) No Digium/Sangoma Hardware ?

no hardware

5) No Extra Software After Installation ?

no additional software

sraza wrote:1) Vicidial X.X.X Build XXXX ?

VicidialNOW CE 1.3

That's not the Vicidial version. That's the installation method

VicidialNOW is an .iso installation of CentOS and Vicidial. But you may have any version of Vicidial installed on CentOS.

On each page of the admin screens at the bottom left you will find Vicidial X.X.X Build XXXX. This is the actual Vicidial Version and Build. You could be running 2.0.5, 2.2.0, 2.2.1, 2.4 ...?

yes thanks brother here is the vicidial build version

VERSION: 2.0.5-174
BUILD: 90522-0506

ok! ignition!

you have a fairly old (just became old, really, so it's not that bad ) version.

consider upgrading to 2.2.1 (it's very easy, only takes a few command, less than 10)

has this installation been in service for a while and this just happened or is it a fresh install?

have you changed the IP address or anything in the code?

what is the load on the server when this happens?

When you have your session has been disabled, you can try to resolve the the issue by typing asterisk -r and see the errors.

However, one of the major cause of this is the softphone. Please make sure your softphone is synch'ed with asterisk.

Thanks

No i have not changed the ip address of the Server, this server is in production for 5-6 months but suddenly after shutting down for two days (saturday and sunday) it started this error, i have no clue what to do. the system load is 2-3 percent and sufficient amount of ram is free (more than 85% is free)

watch the "live agents" table, see if the random number field changes every second (as it should)

we used to work with default phoen logins (cc100/test) and some agent, i see registered soft phone and also the greeting call came in saying you are the only person in this conference blah blah blah, but on screen it shows your session has been disabled. but before i used to work with hard phone using meda pack, but at that time also i have work with eyebeam, ekiga etc now i get this error using all of these things

williamconley wrote:watch the "live agents" table, see if the random number field changes every second (as it should)

this is where the hunt begins

where is the random agent table?

are you familiar with phpmyadmin? (or just plain mysql?)

asterisk database

vicidial_live_agents table

random_id field

each time you "view" random_id should always be different (unless you manage to view twice in the same second)

yes im fimiliar with phpmyadmin, but not too much, can i have a mysql query to see those

LOL

use asterisk;

select * from vicidial_live_agents;

what the hell is this
ERROR 144 (HY000): Table './asterisk/vicidial_live_agents' is marked as crashed and last (automatic?) repair failed

Thanks brother alotttttttt, i put this command and everythings seems fine now, thanks alot ur great!
[edited to draw this solution out]

Code: Select all

 mysqlcheck -u cron -p -A --auto-repair

Enter password:
asterisk.call_log OK
asterisk.conferences OK
asterisk.groups_alias OK
asterisk.inbound_numbers OK
asterisk.live_channels
note : The storage engine for the table doesn't support check
asterisk.live_inbound OK
asterisk.live_inbound_log OK
asterisk.live_sip_channels
note : The storage engine for the table doesn't support check
asterisk.park_log OK
asterisk.parked_channels
note : The storage engine for the table doesn't support check
asterisk.phone_favorites OK
asterisk.phones
warning : 3 clients are using or haven't closed the table properly
status : OK
asterisk.phones_alias OK
asterisk.recording_log
warning : 9 clients are using or haven't closed the table properly
status : OK
asterisk.server_performance
warning : 24 clients are using or haven't closed the table properly
status : OK
asterisk.server_updater
note : The storage engine for the table doesn't support check
asterisk.servers OK
asterisk.system_settings
warning : 16 clients are using or haven't closed the table properly
status : OK
asterisk.user_call_log
warning : 6 clients are using or haven't closed the table properly
status : OK
asterisk.vicidial_admin_log
warning : 6 clients are using or haven't closed the table properly
status : OK
asterisk.vicidial_agent_log OK
asterisk.vicidial_agent_sph OK
asterisk.vicidial_api_log OK
asterisk.vicidial_auto_calls OK
asterisk.vicidial_call_times OK
asterisk.vicidial_callbacks OK
asterisk.vicidial_campaign_agents OK
asterisk.vicidial_campaign_dnc OK
asterisk.vicidial_campaign_hotkeys OK
asterisk.vicidial_campaign_server_stats
note : The storage engine for the table doesn't support check
asterisk.vicidial_campaign_stats OK
asterisk.vicidial_campaign_statuses OK
asterisk.vicidial_campaigns
warning : 22 clients are using or haven't closed the table properly
status : OK
asterisk.vicidial_campaigns_list_mix OK
asterisk.vicidial_closer_log OK
asterisk.vicidial_conf_templates OK
asterisk.vicidial_conferences OK
asterisk.vicidial_cpd_log OK
asterisk.vicidial_did_log
warning : 5 clients are using or haven't closed the table properly
status : OK
asterisk.vicidial_dnc OK
asterisk.vicidial_hopper OK
asterisk.vicidial_inbound_dids
warning : 1 client is using or hasn't closed the table properly
status : OK
asterisk.vicidial_inbound_group_agents OK
asterisk.vicidial_inbound_groups
warning : 1 client is using or hasn't closed the table properly
status : OK
asterisk.vicidial_ivr OK
asterisk.vicidial_lead_filters OK
asterisk.vicidial_lead_recycle OK
asterisk.vicidial_list OK
asterisk.vicidial_list_alt_phones OK
asterisk.vicidial_list_pins OK
asterisk.vicidial_lists
warning : 8 clients are using or haven't closed the table properly
status : OK
asterisk.vicidial_live_agents
warning : Table is marked as crashed and last repair failed
warning : 1 client is using or hasn't closed the table properly
error : Found 3 keys of 4
error : Corrupt
asterisk.vicidial_live_inbound_agents OK
asterisk.vicidial_log OK
asterisk.vicidial_manager OK
asterisk.vicidial_nanpa_prefix_codes OK
asterisk.vicidial_pause_codes OK
asterisk.vicidial_phone_codes OK
asterisk.vicidial_postal_codes OK
asterisk.vicidial_qc_codes OK
asterisk.vicidial_remote_agents OK
asterisk.vicidial_scripts OK
asterisk.vicidial_server_carriers
warning : 1 client is using or hasn't closed the table properly
status : OK
asterisk.vicidial_server_trunks OK
asterisk.vicidial_shifts OK
asterisk.vicidial_state_call_times OK
asterisk.vicidial_stations OK
asterisk.vicidial_status_categories OK
asterisk.vicidial_statuses OK
asterisk.vicidial_timeclock_audit_log
warning : 1 client is using or hasn't closed the table properly
status : OK
asterisk.vicidial_timeclock_log OK
asterisk.vicidial_timeclock_status OK
asterisk.vicidial_user_closer_log
warning : 12 clients are using or haven't closed the table properly
status : OK
asterisk.vicidial_user_groups OK
asterisk.vicidial_user_log
warning : 14 clients are using or haven't closed the table properly
status : OK
asterisk.vicidial_users
warning : 13 clients are using or haven't closed the table properly
status : OK
asterisk.vicidial_xfer_log OK
asterisk.web_client_sessions
note : The storage engine for the table doesn't support check

Repairing tables
asterisk.vicidial_live_agents OK

thank you for posting your resolution. good habit. and the next user now will be able to follow the progress and solve their problem without an issue.

if you just did that, and solved your problem, you should thank him! even if it's next year.

Thanks williams thanks alot.

I have to say that I had the same problem. My system had a power outage and users were still logged in. I am so appreciative to VICIDIAL, you guys ROCK.

Thank you again.

Really, thank you, I had forgotten that after a crash the tables had to be repaired. I owe you one.

Ah, thank you so much.. I am having this problem as well TY TY will report in the morning as to the progress made.

Awesome, this just solved the same problem for us today! Would anyone advise against using a mysqlcheck cronjob every night?

There is a twist to this one. The mysqlcheck sorts out the "your session has been disabled" problem but if you use the timeclock feature the "you cannot log in within 30 seconds" remains. Days later that problem still remains and we cannot use the timeclock.

Any ideas how to clear this up?

This is awesome! experienced an issue with this today. and this is a lifesaver!

THANK YOU!

Still wondering how we can get rid of the timeclock error. It is now completely unusable.

Hello everyone.
I want to configure my campaign to run automatically throughout the week.
I set the Call Times 9am until 19h. Shifts and 24hours.
every morning I find the message "your session has been disabled"
Can someone explain to me? thank you

GoAutoDial CE 2.1
VICIDIAL (v: 2.4-309a)

hamzakh wrote:Hello everyone.
I want to configure my campaign to run automatically throughout the week.
I set the Call Times 9am until 19h. Shifts and 24hours.
every morning I find the message "your session has been disabled"
Can someone explain to me? thank you

GoAutoDial CE 2.1
VICIDIAL (v: 2.4-309a)

This would be because the server essentially "crashes" the agent during overnight mysql routines (around 1AM usually). Use a remote agent instead of a live agent. They are very useful for automated campaigns.

Live agent screens require constant contact with the DB. Eventually the server will perform a maintenance function that will break that link (just for a minute ...) and the Live Agents will all be logged out. You can alter the timing of those routines to a moment when you can be there to resolve it ... or just switch to remote agents with no such requirement. After all, Live Agents by definition are expected to be staring at that screen. LOL

You can set a script to activate/deactivate the remote agent at the times you like. And another script to check at reboot to see if the agent should be on or off (in case a reboot coincides with a changeover time and the change is missed ... having a check on reboot resolves that issue). Another method is to have a script run every 30 minutes to check if the remote agent should be on or off, which is even safer.

thank you very much, I used remote agent