CMS Time Notes

CMS affectively has two times start time which is the acd default time and start time +utc which is the timezone handled by TZ. (TZ updater is used to update timezone information)

The time zone is handled by the variable TZ. For global configuration edit the “/etc/default/init” file and alter the TZ line for example:

TZ=GMT if you want to set it to GMT.

To change date from CLI

date -s “30 october 2016 08:41”

to view from CLI



CMS Symon Wallboard check feed

Checking the wallboard using rt socket as to provide the feed. From the CMS command line type;


It will ask you confirm the socket number usually the default 1 so click enter.

You will now see the feed to the wallboard

configuration is in the rta.conf file in the same directory.

CMS Power Down & Reboot

On the CLI at ROOT

Shutdown CMS
/usr/bin/shutdown -y -g0 -i0

Reboot CMS
/usr/bin/shutdown -y -g0 -i6

Power Up CMS
Push the button and wait. Once the CMS is up from the CLI

tail /cms/pbx/acd1/spi.err

You will see a number of messages PUMP-UP but you are waiting for the DATAX with the number of calls beside it which means you are seeing data from the switch.


**Notes added by Giel**

It worth noting that these commands are used on Avaya CMS running on the Solaris operating system.

/usr/bin/shutdown -y -g0 -i0 will take you to the OK boot prompt, which means it will shut the software but still allow you to run diagnostics on the hardware. This run level can also be reached by pressing the STOP + A keys on the Sun Keyboard.

Init 0= OK boot prompt (i0)
Init 3 = Normal running level (i3)
Init 5 =Shutdown and power off (i5)
Init 6=Reboot (i6)

The “g0” refers to the grace period before shutdown

Listing CMS Users

Telnet to CMS and login as root.

root#. /opt/informix/bin/setenv >dbaccess cms@cms_ol - <<! >select l_name, f_name, room, telephone from users >!

CMS Supervisor Error 429

Resolving CMS Supervisor Error 429 issue.

Error 429 typically occurs when code tries to instantiate an object. This error can be caused in many ways. The following list includes some of the most common scenarios that could cause this error:

  • License information for a particular component is not present.
  • A component is missing or is not registered.
  • A DCOM issue exists.
  • A Packaging and Deployment Wizard (PDW) issue exists.

1. Clear the log under CMS directory
2. User ID has insufficient right to access the directory
3. Goto Services->Telephone, set it to automatic

Another solution but not tested
1. create on your desktop a text file “test.txt”
2. Rename it to “test.avsup”
3. if Avaya supervisor is installed properly, you can double-click on this file and CMS with prompt you to enter your credentials.


From the CentreVu “readme” file:

If an “Error 48” or “Error 429” message is displayed the first time you
run Avaya CMS Supervisor, or if a component fails to start, it may be a
result of some elements not being properly entered into the Windows
registry. To fix this problem, complete the following steps:

1) Navigate to the CMS Supervisor installation directory.
(by default,the installation directory is C:\Program Files\Avaya\CMS Supervisor R16)

2) Run the RegistryDefaults.bat file.

CentreVu/Supervisor/CentreVu Supervisor/CMS Supervisor, all same thing.

CMS Reset User Passwords

From the CMS Main Menu, highlight the Commands (F3).
CMS displays the Commands menu.

2. Select UNIX (r) system.
The screen clears and a $ prompt is displayed.

3. Enter the following command:

4. At the Password: prompt, enter the root password.
The # prompt is displayed.

5. Enter the following command:
passwd <userid>
(Where <userid> is the ID of the user who needs a new password)
Solaris displays a prompt for the new password.

6. Enter a new password for the user.
Solaris displays the # prompt.

7. Enter the following command:
passwd -f <userid>
(Where <userid> is the ID of the user with a new password.)
Solaris displays the # prompt.

The passwd –f command will force the user to change their password the next time they log in to CMS.

CMS ADM Backup

ADM = performed every 30 days login as root and type “cmsadm”

Insert new tape into the CMS Backup tape drive
Log in using cms login
Terminal type is 615 [enter]
$ su root [enter] [enter in root password, enter]
# cmsadm [enter]
Select “3” for Backup [enter]
Press “Enter” when ready
Follow CMS routine, selecting enter to defaults, when complete, label the tape with the date as well as the information displayed by CMS as instructed & store in fire proof safe.
Return the appropriate incremental tape back into the tape drive.

To check the back up has been done

find /cms/ -name backup.success -ls

To make the system think it has been done you can use the command just to stop the users getting the error message. The backup will still need to be performed.
touch /cms -name/install/logdir/backup.success -ls


cd / /cms/install/logdir

touch backup.success