System Tuning

Contents

  1. 1 Introduction
  2. 2 Accessing NMS System Parameters
  3. 3 System Parameter Syntax and Description
    1. 3.1 Playback
    2. 3.2 Clean-Up
      1. 3.2.1 Clean-Up Thread
      2. 3.2.2 CDR Clean-Up
      3. 3.2.3 Event Clean-Up
      4. 3.2.4 EMail Clean-Up
      5. 3.2.5 Hunt Group Status Clean-Up
      6. 3.2.6 VMail Clean-Up

Introduction

System Parameters (config_config) are global parameters applied to all domain in each instance of NMS

Accessing NMS System Parameters

Add or modify a system parameter by navigating to System --> Settings --> Advanced --> Properties; as shown below


You will then reach the following screen

 

System Parameter Syntax and Description

Playback

Parameters Values Default Descriptions
MohExitDigit integer 0 DTMF Digit to exit Music On Hold
PlaybackForwardDigit integer 9 DTMF Digit to fast forward by "PlaybackForwardSecond" during playback
PlaybackForwardSecond integer 15 # second to fast forward by each "PlaybackForwardDigit
PlaybackPauseDigit integer 8 DTMF Digit to pause during playback
PlaybackPrevDigit integer 4 DTMF Digit to rewind to previous file during Music On Hold
PlaybackNextDigit integer 6 DTMF Digit to fast forward to next file during Music On Hold
PlaybackRewindDigit integer 7 DTMF Digit to rewind by "PlaybackRewindSecond" during playback
PlaybackRewindSecond integer 15 # second to rewind by each "PlaybackRewindDigit


Clean-Up

The NMS runs a single independent thread to clean up obsoleted :
  • CDR
  • Event
  • VMail
  • EMail
Clean-up occurs only in specified Day-Of-Week and Hour-Of-Day-Window.

Upon the start of a Clean-Up Window, a purge to each object type will be performed before applying their individual In-Between-Purge-Period. Since the purges of all object type are handle by this single Clean-up thread, the purges of the different objects are performed sequentially.

The Clean-Up Thread run at the resolution of the CDR's "CdrPurgePeriod", so any other object with Purge Period less then "CdrPurgePeriod" will run at the same frequency as the purge for the CDR.

Clean-Up Thread

ParametersValuesDefaultDescriptions
CleanUpDayOfWeekstring0123456
i.e. every day		Constraint Clean Up to occur at specific GMT Days of the Week
Match pattern (0..6, Sunday==0, Saturday==6)
CleanUpHourOfDaystringHIJK
i.e. 7:00 to 10:59 GMT		Constraint Clean Up to occur at specific GMT Hour of the Day
Match pattern (A..X, A==00,.. J==9,.. M==12,.. X==23)
CleanUpStartupDelay
integer
300
# Second to delay start of Clean-Up from system start-up to allow everything else to settle down

CDR Clean-Up

CDR Purge size of 100K seem to cause call rate to drop and CDR OOP to increase. Whereas 10K or below seem to have little impact, and 2K or below should be pretty safe.

ParametersValuesDefaultDescriptions
CdrKeepDaysinteger180
days to keep CDR
CdrPurgeSizeinteger1000Cdr Purge Block Size
CdrPurgePeriodinteger10
# Second between Cdr Purges

Event Clean-Up

ParametersValuesDefaultDescriptions
EventKeepDaysinteger10# days to keep Event
EventPurgeSizeinteger1000Event Purge Block Size
EventPurgePeriodinteger10
# Second between Event Purges


EMail Clean-Up

ParametersValuesDefaultDescriptions
EMailPurgePeriod
integer1440
# Minute between E-Mail Purges
EmailSentHoldDay
integer
7
# Days to hold sent E-Mail before purging them

Hunt Group Status Clean-Up

ParametersValuesDefaultDescriptions
HGStatusKeepDaysinteger90
# days to keep Hunt Group Status
HGStatusPurgeSizeinteger10000Hunt Group Status Purge Block Size
HGStatusPurgePeriodinteger10
# Second between Hunt Group Status Purges



VMail Clean-Up

V-Mail purge scans the trash folder of every subscriber, and sleeps for 10ms after each folder to release processing to other tasks. Therefore, it will take some time and hold up the purges for the other objects.

ParametersValuesDefaultDescriptions
TrashHoldDayinteger1# Days to hold deleted items in the trash folder before purging them permanently
VMailPurgePeriod
integer  
1440
# Minute between V-Mail Purges