Polycom 3725-70003-009F 사용자 설명서
ReadiVoice Administration & Maintenance Guide
112
Proprietary & Confidential
It’s best to stop and restart ReadiVoice processes only when there are no active
conferences. In an emergency, however, you may have to do this while
conferences are running. If so, keep the following in mind:
• Anyone using the Operator or Moderator interface is isolated from the
conferences. In an emergency, however, you may have to do this while
conferences are running. If so, keep the following in mind:
• Anyone using the Operator or Moderator interface is isolated from the
conferencing system for the time it takes to stop and restart (about one
minute).
minute).
• New calls can’t be handled until the core processes have restarted.
Depending on your system configuration, callers hear either a busy signal
or a message stating that the system isn’t available and asking them to call
or a message stating that the system isn’t available and asking them to call
back.
• Existing conferences continue to operate normally. The participants are
unaffected unless they request an operator or try to use the Moderator
interface during the stop/restart operation.
interface during the stop/restart operation.
To stop and restart the ReadiVoice processes:
1
Open a Telnet session to the CACS as user cnow and switch user to root
(or log into the CACS as root and use an XTerm window).
(or log into the CACS as root and use an XTerm window).
2
Change directories to /rahome.
3
Enter ./rastop. If the prompt doesn’t reappear, press
ENTER
.
4
Enter ./rastart. If the prompt doesn’t reappear, press
ENTER
.
5
To verify that the required processes are running, enter ./racheck.
Rebooting the Sun Server
Under certain circumstances, you should reboot the server. These include:
• If you change the date and time on the Sun server.
• If the system exhibits erratic or unpredictable behavior.
• If you change the date and time on the Sun server.
• If the system exhibits erratic or unpredictable behavior.
Naturally, rebooting the server also includes stopping and restarting the
ReadiVoice processes. If conferences are running, the same considerations
apply. But, the entire process takes longer, perhaps five to ten minutes. In
addition, the bridges don’t have access to files on the server during the reboot.
apply. But, the entire process takes longer, perhaps five to ten minutes. In
addition, the bridges don’t have access to files on the server during the reboot.
This may affect existing conferences if, for example, sound files not already
cached on the bridge are needed.
Caution!
Stopping and restarting the ReadiVoice processes affects current users as
described below.
described below.
Caution!
Rebooting the Sun server affects current ReadiVoice users as described in the
previous section and below.
previous section and below.