Next Topic

Previous Topic

Home

Book Contents

Book Index

[Program]

The [program] section contains values that can affect the client, server or both together and are generally values that the way something works rather than specific features or parameters.

ApplicationPath

Used by:

Max length: 128 characters

Example:

ApplicationPath = C:\montel\demo

While not apparently used, this entry is kept in the PABX.INI file as a useful reference mark for the application directory. (This setting was in fact used in Version 2.9.0 up till pre-release 39, to force the PABX.INI file to be read from the specified location. From Pre-release 39 Setup will specify the location of the PABX.INI file in the registry, and MonTel will check that, and then the current path for the PABX.INI file.)

This path name is in the format Drive:\path.

NetworkApplicationPath

Used by: Services

Max length: 254 characters

Example:

NetworkApplicationPath = //MTServer/Apps/Montel

This entry is the UNC path to the MonTel Application folder or directory. This is to allow services to be installed and run over the network from a montel application directory (or folder). The format must the be UNC format in the format //Server/share/path. See also ApplicationPath.

DefaultServiceComputerName

Used by: ServerSV, SerSQLsv, MonexSV, MonimpSV.

Version 2.11.4 onwards

Max length: 30 characters

Example:

DefaultServiceComputerName = PC7

DefaultServiceComputerName is the name of the computer on which the the MonTel Server is running. See also DefaultServiceLoginName.

This field is used as a default. It is overridden by the specific fields in the relevant section for a specific application.

DefaultServiceLoginName

Used by: ServerSV, SerSQLsv, MonexSV, MonimpSV.

Version 2.11.4 onwards

Max length: 30 characters

Example:

DefaultServiceLoginName= FS1\MonTel

DefaultServiceLoginName is the Domain\login name setting for the network account user name for all MonTel Services on a network. Since this account needs to be a network account to access files on the network it requires the domain name as well.

This field is used as a default. It is overridden by the specific fields in the relevant section for a specific application. See also DefaultServiceComputerName.

From version 2.12.11 onwards:

To specify the local system account, use "Local System account". Note that you will need to grant the computer (rather than a user) access permission to the appropriate folders.

DefaultPipeTextOut

Used by: ServerCN, ServerSV, MonImpSV, MonExSv, FaxMonSv SerSqlsv.

Version 2.11.7 onwards.

Example:

DefaultPipeTextOut = 0

When DefaultPipeTextOut= 1 a MonTel Console or Service application will send the screen information by a "named pipe" to the relevant MonTel Service Manager program (usually MTAdmin) which will allow the MonTel supervisor to be able to monitor the service from their local PC. This is the general default setting, which can be over ridden by individual settings specific to each service.

DefaultPipeInstances

Used by: ServerCN, ServerSV, MonImpSV, MonExSv, FaxMonSv SerSqlsv.

Version 2.11.7 onwards.

Example:

DefaultPipeInstances = 5

By default DefaultPipeInstances is set to 5, which is the maximum value. This can be reduced to limit the number of external connections to a Server, or to reduce network traffic down to 1. If it is set to 0 then the Text out pipe is turned off, so this is the equivalent of setting DefaultPipeTextOut= 0.

A pipe instance is one channel between a MonTel service or console application and the Service manager, which is acting as a graphical user interface for the application. One channel or pipe is used for each open Service manager.

The text pipe is screen information sent by a "named pipe" to the relevant MonTel Service manager. This is the default setting, which can be over ridden by settings specific to each service.

DefaultServiceRecoverWaitTimes

Used by: LogSvc (for ServerCN, ServerSV, MonImpSV, MonExSv, FaxMonSv SerSqlsv).

Version 2.11.7 onwards.

Example:

DefaultServiceRecoverWaitTimes = 5,10,82

This setting is a comma delimited list of time in seconds that LogSvc.exe should pause before restarting a service. LogSvc.exe is passed the failure count by the service control system in Windows and chooses the pause in the list in order of the failure count, with the last time being repeated for subsequent failures.

To prevent LogSvc.exe from restarting the service, set the value to a negative number.

By default DefaultServiceRecoverWaitTimes is set to 5, 82.

ShowServiceStoppedOnUnrecoverableError

Used by: Service Applications (for LogSvc ).

Version 2.11.11 onwards.

Example:

ShowServiceStoppedOnUnrecoverableError = 0

When a MonTel Service application has an unrecoverable error, by default (from Version 2.11.11 onwards) it does not alert the service control manager that it has stopped, there by forcing a service failure, which can be used by LogSvc.exe. See How the LogScv (Log Service Failures) application works. When this value is set to 1, an unrecoverable error will send a stop message to the service control manager, so a service failure will not occur. This setting may be useful when not using service recovery, to leave the system in a more predictable state.

By default ShowServiceStoppedOnUnrecoverableError is set to 0.

ClientSetupPathFileName

Used by: Reset32 (MonInst - future versions)

Max length: 128 characters

Example:

ClientSetupPathFileName = F:\Apps\Montel\Setup32\setup.exe

This setting is not required when using the standard location and client set up. In fact, it is better to leave it blank.

It is used when using either a non standard path or sub directory for the client set up files. For example; if the client was to be install locally then the set up path might be: ClientSetupPathFileName = F:\Apps\Montel\Local32\setup.exe.

In some systems the IT manager may want to store the set up files in a different location to the applications files. In this case an example might look like: ClientSetupPathFileName = F:\Setup\Mtclient\setup.exe. In this case, setup.exe will need to know where the MonTel application directory is as it won't be in the parent folder. To do this add a new section [Directory], and entry ApplicationPath = F:\Apps\Montel in the SETUP32.INI file.

LogMessageLevel

Used by: Server, MonexSV, SerSQLsv

Example:

LogMessageLevel=1

Used to determine the type and therefore number of messages place in the log file. Messages displayed in the Status and Errors windows can also be logged to a file in the MAIN data path, the log file for each application being the application name with the extension '.log'.

Log File Message Levels

0
1
2
3
M_LOGGED
M_ERROR
M_DISK_ERROR
M_RUNTIME
M_WARNING
M_STATUS
 
M_PIPE
M_BLANK
M_MESSAGE
 

Settings below 0 are ignored. Therefore messages defined as M_LOGGED, M_ERROR, M_DISK_ERROR and M_RUNTIME are always logged to the log file.
The recommended level is 1. However, for trouble shooting, levels 2 and 3 may be able to give less transitory clues as to what is going on.

PMAFileName

Used by: Client

Max length: 14 characters

Example:

PMASystem = "PMA.INI"

Used to identify the file that hold linking, import, export and configuration information related to the practice management system of the practice or firm. As well as being used to select the type of PMA system to which (the) MonTel (client) exports the disbursement records the entry in the program section also will determined how various fields are displayed in the MonTel client, for example "Matters" in one system will be displayed as "Job Codes" in an other system. The PMA.INI file is also used by MonimpSv and MonexSv using the import and export sections respectively.

By default PMASystem is "PMA.INI" and so is not required. It is really for situations where there are multiple groups, or for testing, where a separate PMA.INI file other than the default may be required. In this case you would expect it to be named something other than PMA.INI.

The PMA.INI file is a conflation of previous INF files, combining what might have been different AuotImportSystem, AutoExportSystem and PMASystem files in to one. To display as one PMA system, while exporting an importing to another (for example using Solution 6 - while importing and exporting to Monitor Business Machines), you may have different settings in the PMA.INI itself. This can be accomplished using EdPma32.exe the ned editor for PMA.INI.

MontelDataRefresh

Used by: Client, Server.

Example:

MontelDataRefresh = 5

The time in seconds between checking for a new Call Record. Not implemented in the DOS utility PABXUSER.EXE (which is fixed at 5 seconds). The range is 1 .. 3660.

This value is also used for checking other elements when a regular heart beat is required. For example, when service control managers such as MtAdmin are checking the status of a service.

NumberOfDataRefreshesToCheckIni

Used by: Client, Server.

Example:

NumberOfDataRefreshesToCheckIni = 6

Default is 6. Don't set 0. Set the number of "MonTelDataRefresh"es to skip before checking the INI file again.

LocalMonTelIniName

Used by: Client, Server.

Max length: 12 characters

Example:

LocalMonTelININame = "MONTEL.INI"

This should not be changed or used in normal circumstances. It is used by the Demo MonTel, so you can have both a demo and main system on the same lap-top, and for some test systems.

PrivacyOption

Used by: Client, Server.

Example:

PrivacyOption =1

Either 0 or 1. If set to 1, prevents the display of the last two digits in a phone number - when viewing "all calls". The last two digits are replaced by XX.

MonTelOnTop

Used by: Client.

Example:

MonTelOnTop = 1

Either 0 or 1. Displays the Info box pop-up as the topmost Window overlaying other windows until the InfoBox is updated, so as to force users to input data before continuing with other work.

MonTelDefaultClientProgram

Used by: Client, Server.

Max length: 12 characters

Example:

MonTelDefaultClientProgram = "Notify32.exe"

MonTelDefaultClientProgram specifies the program restarted if MonTelAutoRestart had previously been set to 1. See How to make MonTel or Notify automatically restart after an Admin shut down.

MonTelAutoRestart

Used by: Client.

Example:

MonTelAutoRestart = 0

If this is set to 1 before MonTel is started, then the next time that AllowOnlyAdminToUseMontel is set to a non zero value, Montel will close down, and run a very small stand by program, called "restart.exe". This program will periodically check to see if AllowOnlyAdminToUseMontel = 0. When it finds that it is, then it will reload the program specified in MonTelDefaultClientProgram.

See How to make MonTel or Notify automatically restart after an Admin shut down.

AllowOnlyAdminToUseMontel

Used by: Client.

Example:

AllowOnlyAdminToUseMontel = 0

(Summary: 0 for all users, 1 to allow only MonTel Administrators to use client programs, 2 to allow MonTel Administrators to use only the Administrative programs such as EdIni and MtAdmin. A setting of 3 will exit all programs.

Set to zero for normal use. If set to 1, all MonTel client applications that are open will be shut down (taking about 15-30 seconds) except for those users with Admin privileges. Useful for updates, to ensure all users are logged out, or to force new settings.

MonTel has several security or privilege levels. Normal users have level 0. MonTel Administrators running the normal client programs such as Notify32, MonTel32 or SerMon have level 1 in those programs, and level 2 when in administrator programs such as EdIni and MtAdmin. A MonTel Administrator has AdministratorOn in their entry in the [users] section of PABX.INI.

For Versions up to 2.11.24 : (Summary: 0 for all users, 1 for Admin only or 2 for no users.)

Set to zero for normal use. If set to 1, all MonTel (for windows ) clients open will be shut down (taking about 15-30 seconds) except for those users with Admin privileges. A setting of 2 will shut down all users. Useful for updates, to ensure all users are logged out.

DontStartMonTelClient

Used by: Client.

Example:

DontStartMonTelClient = 0

0 by default - If set to 1, no MonTel (for windows ) clients will be able to open. (Note - It will not shut down already open programs). This prevents even the splash screen from displaying.

This setting is useful to stop users trying to start MonTel during an update. It may also be useful if there were major systemic problems where you might not want MonTel or Notify to auto start in widows when a user first logs on.

AllowReEntrant

Used by: Client.

Example:

AllowReEntrant = 1

This option is set to 1 by default, so this value need not be supplied. With Version 2.9 the Pop up Message Boxes have been changed to allow background processes to continue. This is to allow MonTel to exit gracefully even is a message box is being displayed, if AllowOnlyAdminToUseMontel = 1. (See How to make MonTel or Notify automatically restart after an Admin shut down.) This means that more than one message box may be generated as the the code is reentrant. Since this may result in unexpected situations where message boxes are continually been creating in some regular error scenario, provision has been made to revert to the "old style" message boxes, where all processing would stop.

To enable the "old style" message boxes set AllowReEntrant = 0.

"New style" message boxes are generally thinner and taller and the "old style" message boxes.

MonTelExitMessage

Used by: Client.

Max length: 80 characters

Example:

MonTelExitMessage = "This will just be a quick fix!"

You can change this to whatever you want - just before you change AllowOnlyAdminToUseMontel. For example "Please try again later". or "This will be a quick fix, try again in
3 minutes".

AlwaysUseDefaults

Used by: Client, Server.

Example:

AlwaysUseDefaults = 0

If this is set to 1, then the MonTel Client (the popup) will read DEFAULTS.INI from the same directory as PABX.INI and not MONTEL.INI the Windows directory. Setting this variable forces uses to have only the one set defaults parameters specified by the administrator. A DEFAULTS.INI file in the same directory as PABX.INI (the application directory) with be used as a non-enforceable default if this setting is 0.

The best way to set this up is to copy an ideal MONTEL.INI to DEFAULTS.INI in the MonTel Application directory. (Note the file name IS defaults.INI not default.INI)

For more information see: How to set or force local default or background options in the MonTel Client.

FirmSecurityAndPrivacy

Server Version 1.2.159 onwards

Used by: Server.

Example:

FirmSecurityAndPrivacy = 1

The default is 0.

This setting is used so that if multiple groups are being used SerSqlsv the default Main Call record database will not be placed in an SQL server database (only the group items).

An unknown extension, is an extension that is not specified in at least one user entry in the PABX.INI file.

From 2.11.32: In addition the MonTel Server was changed in this version so that a license slot was no longer wasted (or needed) to specify NONE. All unknown extensions will be saved in OFMAIN.DAT or OFINT.DAT in the MonTel Data Directory under Main (where the master call record database is stored), unless SaveOverFlowCalls =0 or IgnoreExtNotInIniFileError =1. See SaveOverFlowCalls and also IgnoreExtNotInIniFileError.

If IgnoreExtNotInIniFileError is set, then if both IgnoreExtNotInIniFileError = 1 and FirmSecurityAndPrivacy = 1 then the call will be thrown away and not recorded. If SaveOverFlowCalls =0 the call will also be ignored (though later in the processing).

From 2.9.38 to 2.11.31: If set to 1 then the MonTel server will not place calls by unknown extensions in the "All Calls" Main Call Record Database. The other features above from 2.11.32 were not included.

MonitorUpdateUsers

Used by: EdIni and Edmon.

Example:

MonitorUpdateUsers = 0

If set to 1 then EdIni will save a 1009 format user file as well as writing to the PABX.INI file. The setting Monitor1009File specifies the full path and file name.

Version 2.11.6 on wards: If set to 2, then EdIni will save a Type 31 format user file. MonitorUserUpdateFilePath is now used to specified the full path and file name. Monitor1009File is not used.

MonitorUseEmployeeCode

Used by: EdIni and Edmon.

Example:

MonitorUseEmployeeCode = 0

The table below shows the changes to the format of the monitor Type 32 user report generated by saving EdIni data to the PABX.INI file.

Value

result

0
Default value. The Primary number will be the Employee code.
1
Primary number will be the User's PIN number.
2
Primary number will be the User's Login name.
3
Primary number will be the User's primary extension.
4
 
5
Primary number will be the Employee code.

If 32 is added to the value, then the PIN field will be blank.

MonitorUserUpdateCommand

Used by: EdIni and Edmon.

Max length: 140 characters

Example:

MonitorUserUpdateCommand = ""

This specifies the full path and file name to be used as a command (generally an executable) or alternatively a bat file to activate the Monitor Business Machine side of the import. As there is no specific option available for this from Monitor yet, it is more likely that this field is not used, and that importing into monitor will take place overnight as part of their usual activities.

MonitorUserUpdateFilePath

Used by: EdIni and Edmon.

Max length: 140 characters

Example:

MonitorUserUpdateFilePath= ""

The file and complete path name of the file to be created by EdIni32 in the appropriate Monitor report format specified in MonitorUpdateUsers, to be used by Monitor from Monitor Business Machines to import users in to their system.

This field replaces Monitor1009File.

CheckINIfileforAmoreRecentSave

Used by: Ini Editors.

Version 2.9.0 Pre-release 47 onwards

Range: 0 - 1.

Example:

CheckINIfileforAmoreRecentSave = 0

Previously the INI editors (meaning EdINi32, EdDef32 and EdSet32) checked to see if the date had been changed on the file and prompted the user to re-load, since another user may have updated the PABX.INI file. However, since this was been triggered more often than not by the clocks bet out slightly between PC and Server, the default is now not to check (0), and this setting is provided to re-enable the check.

AlwaysShowEmployeeLogin

Used by: Client.

Version 2.9.0 Pre-release 49 onwards

Range: 0 - 1.

Example:

AlwaysShowEmployeeLogin = 0

Setting this option to one will cause the Employee Login form to always be displayed on start. This may be useful in an environment when multiple shift workers share a Workstation.

PinNumberSameAsEmployeeCode

Used by: Client.

Version 2.9.50 Pre-release onwards

Range: 0 - 1.

Example:

PinNumberSameAsEmployeeCode = 0

Setting this option to one will set the Pin number to the same value as the employee code on the Employee Login form only. This might be useful in scenarios where AlwaysShowEmployeeLogin = 1.

DontNeedToRegisterPinNumber

Topic creation date: 2008-07-03

Used by: Client.

Version 2.12.4 onwards

0 or 1

Example:

DontNeedToRegisterPinNumber = 1

DontNeedToRegisterPinNumber is by default set to 0. If a pin number has not been specified in the PABX.INI file for each user then the user will be prompted to add their pin number each time they start the MonTel client. In the case where a Pin number is not used to identify the user, the login box pop-up can be disabled for cases where a pin number is not supplied when DontNeedToRegisterPinNumber =1.

SpecificVersionParameters

Used by: Any.

Version 2.11.23 release onwards

Range: 16bit bit field (0 -65536).

Example:

SpecificVersionParameters = 0

This option is unspecified, and may/will change from version to version. Only use if directed by netwiz support staff. See the change log for details. This item should only be used for testing and debugging.

The value is actually a bit field, which means that various settings can be used together by adding up the various settings. The various settings are powers of two, that is 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048 etc. Each setting is either on (the power of two number) or off (meaning 0). To have a combination of values simply ad the numbers together. When they are all off, as they should be then the value is 0 (or blank since 0 is the default).

The following will vary over time an may be out of date.

Version 2.11.26:

Settings affecting only the message displayed when exiting the client for any reason.

  • 8 = Show a message about where the exit occurred for MonTel Administrators only, except if the exit was a clean exit from an existing deliberate cause.
  • 16 = Show a message about where the exit occurred for all users, except if the exit was a clean exit from an existing deliberate cause. Don't use this one unless you are really sure you need to do so.
  • 32 = Show a messages even if the exit was a clean exit from an existing deliberate cause. Use this in combination with one of the above, that is 40 or 48.

This was used in Version 2.11.26 to track down a problem on one site that was experiencing the very occasional disappearance of the MonTel client. At the time this text was written the most likely cause was a MonTel (miss) configuration in the DEFAULT.INI or PABI.INI perhaps in conjunction with occasional network problems. The code was added since the problem was too intermittent to be able to replicate.

Version 2.11.23:

Values affecting the display and type of message box:

  • 1 = Old Client MessageBox, but only if the Old client message box was used previously.
  • 2 = Standard Modal Windows MessageBox.

Version 2.11.23 introduced a new MessageBox to replace mostly the message box used in the client applications. This old message box will be called Old Client Message Box. The Old Client Message Box code was left intact so if there were any issues with the new message box, the old one can be used immediately after a restart by changing this parameter.

The Standard Modal Windows MessageBox will not allow MonTel to be automatically exited by the AllowOnlyAdminToUseMonTel setting, and so should be used only as a last desperate measure.

The new message box is superior to the old client message box because is more accuractly simulates the Standard Windows Modal MessageBox, including features such as allowing to Ctrl-C copying to the clipboard of error messages.

EdIniVersion

Used by: EdIni,Instmon.

Range: x.x.x.x.

Example:

EdIniVersion = 3.4.4850

This option is not user-configurable. It is set by EdIni32.exe when updating the PABX.INI file. It is used as a check so that an older version of EdIni is not used to modify a more recent version of the PABX.INI file (thus deleting settings).

ClientVersion

Used by: EdIni,Instmon.

Range: x.x.x.x.

Example:

ClientVersion = 2.9.55

This option is not user-configurable. It is set by EdIni32.exe when updating the PABX.INI file. It is used as a check by Instmon as one of several methods to determine any modification of settings in the PABX.INI file when updating versions of MonTel.

------------------------------