Reset conference on login

[ekaftan]

I have a set of 40 agents using Nortel Meridian phones. Those phones dont really want to hangup sometimes, so in some shift changes an agent will login to a busy tone instead of 'your are the only person on this conference'.

Is there a way to patch vicidial to reset a conference when an agent logs in? (ie, kick/hangup another agent if its still there?)

thanks,

[mflorell]

Yes, this is actually default in SVN trunk and SVN branches/agc_2.0.4

The next release will have this feature as default as well.

[ekaftan]

Yes, this is actually default in SVN trunk and SVN branches/agc_2.0.4

The next release will have this feature as default as well.

Thanks. I am kind of desperate.... can you point to me to a way to backport it to 2.0.4?

thanks.

[mflorell]

It is already ported to 2.0.4 in the branches/agc_2.0.4 section of SVN

Just go and check it out and move over the www/agc folder that is inside there.

Here is a howto for SVN.

http://www.eflo.net/VICIDIALwiki/index.php/SVN:howto

[ekaftan]

It is already ported to 2.0.4 in the branches/agc_2.0.4 section of SVN

Just go and check it out and move over the www/agc folder that is inside there.

Here is a howto for SVN.

http://www.eflo.net/VICIDIALwiki/index.php/SVN:howto

Just did it today and no joy...

[root@orsus03 ~]# asterisk -rx 'meetme list 8603004'
User #: 02 4037 <no name> Channel: Zap/84-1 (unmonitored)
User #: 03 4037 <no name> Channel: Zap/71-1 (unmonitored)
User #: 04 4026 <no name> Channel: Zap/63-1 (unmonitored)
User #: 05 4026 <no name> Channel: Zap/68-1 (unmonitored)
User #: 06 4031 <no name> Channel: Zap/82-1 (unmonitored)
User #: 07 4031 <no name> Channel: Zap/87-1 (unmonitored)
User #: 08 4037 <no name> Channel: Zap/88-1 (unmonitored)
User #: 09 4507 <no name> Channel: Zap/86-1 (unmonitored)
8 users in that conference.
Verbosity is at least 3

[mflorell]

Is this line in your vicidial.php script towards the top?

$LogouTKicKAlL = '1'; # set to 1 to hangup all calls in session upon agent logout



Can you post the Asterisk CLI output when an agent clicks LOGOUT?

[ekaftan]

Is this line in your vicidial.php script towards the top?

$LogouTKicKAlL = '1'; # set to 1 to hangup all calls in session upon agent logout



Can you post the Asterisk CLI output when an agent clicks LOGOUT?

After banging myself abit with the wall today, I realized that the kick is when logging out! (I had assumed the kick would happen on login).

So far, no problems the rest of the day, so It seems to be working! I am happy.

Tomorrow at 8am we'll have the really good test though Most mornings staff spend an hour resetting conferences until everybody is properly logged in.

[mflorell]

Let us know how it all goes tomorrow. This is one of the big improvements in what will be the 2.0.4.1 release.

[ekaftan]

Let us know how it all goes tomorrow. This is one of the big improvements in what will be the 2.0.4.1 release.

Yesterday we did have problems, I think because I made the runing change during the day and not all agents were using the new code when they went home.

Today it looks like it did work:

[root@orsus03 ~]# asterisk -rx 'meetme '
No active MeetMe conferences.
Verbosity is at least 3

I still think a check on login makes more sense than one on logout, but it looks like its working.

Thanks!

[mflorell]

I actually tried to get the kick-all working for login, but the problem was that had to add a delay of several seconds to the login procedure so that the kick-all process could run. If I did not add this delay then sometimes the agent would be kicked out within a couple seconds of logging in.

Doing the Kick-all on logout works much better with no added delay to logins.

[gardo]

Having the kick-all on login makes more sense to me Matt. How about showing a message on the agent's screen telling them that they are being logged-in and so on and so forth for the delay not to get noticed?

[mflorell]

At this point the feature is not even in release yet. Let's see if it works in wide release first.

I agree that doing it on login makes more sense, but the reality is on loaded systems the delay could cause all sorts of problems, and with doing it on logout there are no problems and no additional agent-notification is necessary.