NumAnaLocalCallTable

Container for NumAnaLocalCallType

This MO is created by the system.

Actions
`boolean`	`numAnaLocalCallTableCommitAction ( );` <p>This action must be triggered to commit any of the NUMANA OAM Table changes. <br>This action is allowed only when numAnaLocalCallTableSyncState is "Editing"<br>On success this action returns TRUE, changes the numAnaLocalCallTableSyncState to either of below<br>"Syncing": If syncing is in progress.<br>"Active" : If syncing is completed. </p>
`boolean`	`numAnaLocalCallTableEditAction ( );` <p>This action must be triggered before updating any of the NUMANA OAM Tables.<br>This action is allowed only when numAnaLocalCallTableSyncState is "Active"<br>On success this action returns TRUE, changes the NumAnaLocalCallTableSyncState to "Editing"<br></p>

Attributes
`uint32[0..1] noNotification`	`groupId = 0` Relevant only in TSP. Independently from the permissions, this attribute can always be modified by the MO owner and by the Super Administrator.
`integerKeyString key mandatory noNotification restricted`	`numAnaLocalCallTableEntry` Key attribute to NumAnaLocalCallTable MO.
`NumAnaRatingCenterAdjacent`	`NumAnaLocalCallTableRatingCenterAdjacentKey = CALLEDPARTY` This key defines which rating center adjacent list to be used when determing the local call subtype
`boolean`	`numAnaLocalCallTableSynchronization = false` After any Configuration of NumAnaLocalCallTable, the NumAnaLocalCallTableSynchronization is set to TRUE. This means the Number Analysis application will be notified that new configuration has been made and it starts reading the new data in to its cache table. The Number Analysis application sets the NumAnaLocalCallTableSynchronization to FALSE when it is ready. When NumAnaLocalCallTableSynchronization is TRUE no new configuration can be made in NumAnaLocalCallTable until the flag is set to FALSE again. Deprecated:
`string readOnly`	`numAnaLocalCallTableSyncState` <p>This value will replicate the Manager Sync State<br>Allowed values are<br>Initial : Initial value on maiden-installation / new deployment<br>Editing : The operator has triggered Edit action. This is only state in which configuration can change and commit action is allowed<br>Syncing : The operator has triggered the commit action, OR one or more processors has recently scaled out<br>Active : The system is stable, and all traffic are using current configuration. This is only state in which Edit is allowed<br><br></p>
`uint32[0..1] noNotification`	`ownerId = 0` Relevant only in TSP. Independently from the permissions, this attribute can always be modified by the MO owner and by the Super Administrator.
`integer[0..1] noNotification`	`permissions = 9` Relevant only in TSP. The operations allowed for the group members and for other administrators are represented as a bitmap: groupRead(1), groupUpdate(2), groupManage(4), otherRead(8), otherUpdate(16), otherManage(32). Read permission means to read the MO attributes and to see the children of the MO; write permission allows to modify the MO attributes and manage permission allows to create and delete children of the MO. The owner of the MO has all the permissions. The attribute can only be modified by the owner of the MO or by the Super Administrator. By default, the MO is created with the permissions determined by the defaultPermissions attribute of the owner administrator.
`DN[0..1] noNotification`	`shareTree = nodeName=jambala` Relevant only in TSP. This attribute refers to a container object and implies that all administrators defined under this shareTree value have the privileges set as share permissions over the container and its leaf object. Obsolete, must not be used.

class NumAnaLocalCallTable