Audix Web Page Java Fail

I know most of these have gone now but there are still a few out there happily churning away.

If when you web browse to the Audix 10.x.x.x and go to messaging administration but the java bit fails then leave it open in that state. Open up putty in SUNT to the local CM system and then ssh username@10.x.x.x and enter the password and it will get you on the system

Ideally you would want to resolve the java / browser issue but in the scenario in which you don’t have administrative permissions to resolve it this will get you by.


Intuity Audix LX MT VOLT

Added because it is was a nightmare to find any documentation regarding the alarm or the solution on the Avaya support site.

Intuity LX version 2.0
MT VOLT 7 2 MAJ alarm on the sever but voice mail in service and taking calls. Power Supply was replaced but the alarm is still there which proves that the problem related to the motherboard or it’s voltage sensor.
Maintenance logs:
Problem Resource Msg Reporting Resource
Type Inst Location Typ Type Inst Source
7 ERR VOLT logsend.c 92
App: MT EventID:VOLT004 Date/Time Rec:10/18/11 00:02:01 Cnt: 1
Add to Voltage leaky bucket
7 ERR VOLT logsend.c 92
App: MT EventID:VOLT004 Date/Time Rec:10/18/11 00:05:01 Cnt: 1
Add to Voltage leaky bucket
Problem related to the motherboard and voltage sensor.
The whole chassis must be replaced. The Comcode of chassis is :700395874
Audix will be down during this procedure.

Modular Messaging FEDB Resync

*** Warning this will take the appropriate MAS out of service while it carries out the FEDB sync ***

You may want to make a backup copy of the fedb.mdb file which can be found in \\Avaya Modular Messaging\Vserver

If your MAS and Messaging Store databases get out of kilter with each other, then you may need to run an FEDB resync, the easiest way is to download the FEDB Resync tool to C://Avaya_Support/Tools and run it

Alternatively to run the it manually as it were navigate to the appropriate Regedit settings;

Exchange Messaging Store

  • Navigate to the HKLM\Software\Octel\Geneva\Vups_UserProfileServiceMgr
  • Edit the Value Peer Directory Servers
  • For example:  If the value is set as
  • CAQ010AVDC1::48e33c0200000000
  • Change 48e33c0200000000 back to all zeros.

MSS Messaging Store

  • Navigate to the key HKLM\Software\Octel\Geneva\Vups_UserProfileServiceMgr
  • Edit the Value NodeSeqTable
  • In the Data Value, enter 0,0;
  • Edit the Value CosSeqNo
  • In the Data Value, enter 0

Then stop and start the services in the event log you should see event 1030 indicating a full FEDB synchronisation has started. When the synchronisation has completed a 1027 event will be raised showing how many entries were created, updated etc.

Modular Messaging Stop & Start Services

If you come across problems with Modular Messaging and the service appears down, it may be worth stopping and starting the MM services in the first instances to insure they are all running correctly. To stop them go to  C:\Avaya_Support\Tools\ServiceControl (run StopMMServices.exe) when this is finished go to C:\Avaya_Support\Scripts (run serverrecovery.vbs). The MM will take a while to start up properly, to check you can go into the application event logs and wait until 1241 event appears this would confirm the MM services should be up and working.

In the event you wish to stop & start the services manually they should be done in the following order;


1) Call Me Server
2) Message Waiting Indicator Server
3) Event Monitor Server
4) Process Monitor Server
5) Performance Monitor Server
6) Tracing Server
7) Alarming Server
8) Mailbox Monitor Server
9) Messaging Application Server


1) Messaging Application Server
2) Mailbox Monitor Server
3) Alarming Server
4) Tracing Server
5) Performance Monitor Server
6) Process Monitor Server
7) Event Monitor Server
8) Call Me Server
9) Message Waiting Indicator Server

Audix LX/MSS Rebuilding Poet Database

This is originally for MSS but works on Audix LX as well, you will require the TSC password (for MM3.0 + su sroot).

stop_vs 0,
cd /vm/audix/sd/mail
rm -rf mb dr node xmq
cd ../sdata
rm -rf extr
repair_poet_databases -r -v
su – vexvm
audit -i2 -a rebuild -T trace 2>&1
cd /ldap/home/ol/bin

Now start_vs or reboot the system.

%d bloggers like this: