Avaya Support Forums  

Go Back   Avaya Support Forums > Contact Center Applications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 05-06-2015, 11:15 AM
marzahn's Avatar
marzahn marzahn is offline
Genius
 
Join Date: May 2014
Location: Among the trees in Western RI
Posts: 236
marzahn has 24 reputation pointsmarzahn has 24 reputation points
Question Forcing All CMS Supervisors Closed

First off I realize that I am asking for a technology solution to a staff training issue. However I am at my wits end on this one. I have a large number of call center supervisors who leave their CMS client running for days at a time.
  • This requires me to run the kill command on them when doing full backups and other cmsadm proceedures.
  • It also means that they corrupt their personal CMS cashe from time to time.
I have attempted to modify the behavior of call center manager managers with calls and e-mails. But so far this has not been enough. This an 8 to 5 operation. So staff should be out of the system over night.

Is there a command that I can run from a script that will run the "kill -9" command on everyone on a nightly basis? The only thing I have thought of is too "kill" everyone and issue a shutdown/reboot command from a terminal Emulator session every night before I go to bed. Any ideas out there?
__________________
Thank you,
Bill Marzahn
Telecommunications Administrator
Neighborhood Health Plan of Rhode Island
299 Promenade Street
Providence, RI 02908-5720
401-459-6677 (Direct "Find-me" Line)
Reply With Quote
  #2  
Old 05-07-2015, 12:07 AM
shaikht shaikht is offline
Genius
.
 
Join Date: Feb 2010
Posts: 246
shaikht has 25 to 49 reputation pointsshaikht has 25 to 49 reputation pointsshaikht has 25 to 49 reputation points
Default

Hi Bill,

We have APS solution which will disconnect supervisor session after specific duration.
It will also not allow same id to create new session if one is already running.

Please engage your Account manager so that they can engage APS team for same. Please be notified that APS team works on project basis and will be billable.

On command, you need to create a script which will search for win_io_man process.Supervsior sessions will have win_io_man process associated with it. So once script will be searching all active process and will be killing them.

I hope it helps.
Reply With Quote
  #3  
Old 05-08-2015, 07:05 AM
marzahn's Avatar
marzahn marzahn is offline
Genius
 
Join Date: May 2014
Location: Among the trees in Western RI
Posts: 236
marzahn has 24 reputation pointsmarzahn has 24 reputation points
Solution Confirmed That is Useful

I appreciate that Shaikht. However I would like to learn to do this work myself. I have looked through the help files and it looks as though all the scripts do pretty "plain vanilla stuff" such as reports.

I guess I'm just one of those never satisfied guys. It should not be too hard to set up. I'm going into good practice related to the kill command on the Solaris OS.
__________________
Thank you,
Bill Marzahn
Telecommunications Administrator
Neighborhood Health Plan of Rhode Island
299 Promenade Street
Providence, RI 02908-5720
401-459-6677 (Direct "Find-me" Line)

Last edited by marzahn; 05-15-2015 at 01:52 PM.
Reply With Quote
  #4  
Old 05-20-2015, 12:01 AM
sumit007 sumit007 is offline
Brainiac
 
Join Date: Oct 2013
Posts: 63
sumit007 has 19 reputation pointssumit007 has 19 reputation points
Default Forcing All CMS Supervisors Closed

Hi Bill,
You can involve APS for this for neat and clean work.
But if you dont want then you can follow below procedure.
1. Make a script in which you can have find "win_io_man" and "chip" process
2. Kill them all
3. Make a cronjob entry for this script. before backup schedule means to say that if backup runs at 2:00 everyday in morning then you need to make this script to run at 1:30 everyday.
4. This will kill all Supervisors

Please make a note here that i always recommend to involve APS to get this kind of custom solution to prevent unnecessary problems.

if you are following above steps you must know that what you are doing.
__________________
S.S.
Reply With Quote
  #5  
Old 05-21-2015, 12:25 PM
yadav29 yadav29 is offline
Brainiac
 
Join Date: Jan 2013
Posts: 55
yadav29 has 16 reputation pointsyadav29 has 16 reputation points
Default

You can set a cronjob script for that like you have a office 8*5 so you can schedule in the mid of the night.
in the cronjob script you have to do the scrptig where you will find any session of CMS supervisor it can kill automatically.
yo can check via this command:-
ps -ef |pid (CMS supervisor)
Reply With Quote
  #6  
Old 05-27-2015, 08:42 AM
marzahn's Avatar
marzahn marzahn is offline
Genius
 
Join Date: May 2014
Location: Among the trees in Western RI
Posts: 236
marzahn has 24 reputation pointsmarzahn has 24 reputation points
Solution Confirmed Good One

Quote:
Originally Posted by yadav29 View Post
You can set a cronjob script for that like you have a office 8*5 so you can schedule in the mid of the night.
in the cronjob script you have to do the scrptig where you will find any session of CMS supervisor it can kill automatically.
yo can check via this command:-
ps -ef |pid (CMS supervisor)
I appreciate that. I did some research and it looks pretty straightforward.
__________________
Thank you,
Bill Marzahn
Telecommunications Administrator
Neighborhood Health Plan of Rhode Island
299 Promenade Street
Providence, RI 02908-5720
401-459-6677 (Direct "Find-me" Line)

Last edited by marzahn; 06-04-2015 at 06:12 AM.
Reply With Quote
Reply

Tags
cms, forced closing

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 01:58 PM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.