Revision as of 00:14, August 31, 2016 by Sschlich (talk | contribs)
Jump to: navigation, search

Check and Refresh Mailbox Counters

Feature Server release 8.1.201.80 includes these two python scripts:

  • refreshMailboxCounters.py — Renews or resets mailbox counters.
  • getAllMailboxCountersInfo.py — Checks mailbox counters.

Now the procedure looks like following (Check and Refresh Mailbox Counters)

  1. Run getAllMailboxCountersInfo.py to identify mailboxes having invalid counters.
    a.These mailboxes will be marked with !!! in script output log, e.g. (SIPVM-3970)
    Mailbox: 86025: Read value: '-1/0 (0/0)'; Calculated value: '0/0 (0/0)';  !!!
  2. Create the input file listing all mailboxes having invalid counters.
  3. Run refreshMailboxCounters.py using input file created. Feature Server release 8.1.201.64 includes these two python scripts:
    • renewMailboxcountersColumnFamily.py — Renews or resets mailbox counters.
    • getAllMailboxCountersInfo.py — Checks mailbox counters.
    You can run python scripts, on the master Feature Server instance, to:
    • correct an error that caused Feature Server to display incorrect totals for the number of messages in a mailbox.
    • check the mailbox counters.
    Feature Server release 8.1.201.64 includes these two python scripts:
    • renewMailboxcountersColumnFamily.py — Renews or resets mailbox counters.
    • getAllMailboxCountersInfo.py — Checks mailbox counters.

    Deploy the python scripts

    1. On the master Feature Server instance, copy the jython-2.7b1.jar file...
      from FS installation path\work\jetty-x.x.x.x-pppp-fs.war-_fs-any-\webapp\WEB-INF\lib
      to FS installation path\python\util
    2. Open the console and navigate to FS installation path\python\util, which contains the scripts.
    3. Enter the appropriate command to set the JYTHONPATH...
      Windows
      set JYTHONPATH=FS installation path\python
      Linux
      export JYTHONPATH=FS installation path/python

    Run the python scripts

    The following python scripts save data, such as User roles, User Voicemail Profiles assignments, and User Group Voicemail Profiles assignments, that are not related to or synchronized with Configuration Server.

    Each script creates a csv file that you can analyze, edit as needed, and use as the input data for the scripts restoring the data not contained in Configuration Server.

    Use this command line format to run each script:

    java -jar jython-2.7b1.jar scriptname.py script input parameters
    

    Check and Refresh Mailbox Counters

    1. Run getAllMailboxCountersInfo.py to identify mailboxes having invalid counters.
      These mailboxes will be marked with !!! in script output log, e.g. (SIPVM-3970)
      Mailbox: 86025: Read value: '-1/0 (0/0)'; Calculated value: '0/0 (0/0)';  !!!
    2. Create the input file listing all mailboxes having invalid counters.
    3. Run refreshMailboxCounters.py using input file created.

    Refresh Mailbox Counters

    1. Verify that:
      • Your Cassandra database is backed up. See [Documentation:FS:Admin:cassback Backing Up and Restoring Cassandra Data].
      • All Feature Servers are up and running.
      • There is no voicemail activity (no one can deposit, read, or listen to voicemail).
    2. Create a .csv file which has the list of mailboxes that needs to be refreshed.
    3. Run the Python script refreshMailboxcounters.py.

    The content of the file mailboxeIdsInput.csv should be in this format:

    4909045
    4909185
    4909005
    4909889
    

    Sample Command Line

    java -jar jython-2.7b1.jar refreshMailboxCounters.py -H localhost -p 9160 -i ./mailboxeIdsInput.csv -o ./refreshMailboxCounters.log
    

    Check Mailbox Counters

    1. Verify that:
      • All Feature Servers are up and running.
      • There is no voicemail activity (no one can deposit, read, or listen to voicemail).
    2. Run getAllMailboxCountersInfo.py.

    Sample Command Line

    java -jar jython-2.7b1.jar getAllMailboxCountersInfo.py -H localhost -p 9160 -o ./getAllMailboxCountersInfo.log
    
Comments or questions about this documentation? Contact us for support!