Next Topic

Previous Topic

Home

Book Contents

Book Index

[Export]

The [export] section deals with exporting disbursement data from MonTel to the PMA system.

ExportFilterName

Used by: MonexSv, ParsOut.

V2.12.0 Onwards

Max length: 128 characters

Example:

ExportFilterName = "monitor.mef"

ExportFilterName specified the name of the MonTel Export Filter (MEF or .mef) file. This allows MonTel to have a different typed of exports from the import or the display type of pma system. The file specified must be the name of the appropriate MEF file in the MonTel application folder. The path is not included.

.

ExportReportFormat

Used by: MonexSv, ParsOut.

V2.12.0 Onwards

Single number as a bit field.

Example:

ExportReportFormat = ""

ExportReportFormat is used to supply specific formatting instructions to a filter which is useful when there might be a number of alternative export formats. For example Monitor installation may use it to choose between using the P1051 format or the new ATI export format. This setting will be different and used differently for each type of import filer.

For details see Export Format settings table. See also ServerAutoExportFormat.

ExportCommandInfo

Used by: MonexSv, ParsOut.

V2.12.0 Onwards

Single number as a bit field.

Example:

ExportCommandInfo = 9

ExportCommandInfo provides general commands about how to process the import. The items specified here concern the way and order in which items are open and closed, the use of resources and speed of import. Often these items are a trade off against each other and against available system resources.

The default is 1. (See the table below).

ExportCommandInfo is broken down into bit fields, express as adding (or subtracting) a number that is a power of two. Set the ExportCommandInfo value with the (cumulative) addition of one or more of the values from below.

Value

Options

0

FILTERCOMMAND_NONE
The default options are:
  • Open for each record and close each record (or line) in an imported text file.
  • Load the PMA.INI file when loading the PABX.INI file.
  • Load the .MEF (.DLL) when loading the PABX.INI file.

1

FILTERCOMMAND_KEEPOPEN
Open the export text file for batch processing, that is open the file at the start write all the records and then close the file.

2

FILTERCOMMAND_DEMANDLOADPMA
Load PMA.INI only when about to export and unload when exported.
 

4

FILTERCOMMAND_DEMANDLOADFILTER
Load .MEF (.DLL) only when about to export and close again when exported.

16

FILTERCOMMAND_LOCKFILE
(monitor.mef only)
The file being written to is locked when writing to the file.

 

 

 

 

Since ImportCommandInfo defaults to 17. This process the file in batch mode and for monitor exports also locks the file while weirring the record. To force monimpsv to open and close a file handle for every record or line imported you would need to set ImportCommandInfo=0 (if it has not previously been set at all).

Commands specific to certain filters (.mif) or PMA systems will be included in ImportReportFormat.

ExportDSN

Topic creation date: 2009-09-25

Used by: monexsv.

Version 2.12.23 onwards

Max length: 128 characters

Example:

ExportDSN = ""

When using an ODBC (or SQL effectively) Export, the ExportDSN is a windows system or other DSN name to be used. The DSN is used directly and should contain all the relevant information to make the connection. The same information might also be contained in AutoExportFilePathName from the PABX.INI and ExportFileDSN below.

For relevant filters the precedence ExportFileDSN is will be read ahead of the AutoExportFilePathName from the PABX.INI which in turn is ahead of the ExportDSN from the PMA.INI. Some filters may need to have a specific one of the settings specified. Most filterers will not use an SQL export.

ExportFileDSN

Topic creation date: 2009-09-25

Used by: monexsv

V2.12.23 Onwards

Max length: 128 characters

Example:

ExportFileDSN= "\\DM14\MT_PARS\sup5.dsn"

ExportFileDSN is the full path and file name of a file based DSN. For example the file 'sample.dsn' that might be located in the MonTel application folder (and therefore would not require a path) for a Monitor Supervisor 5 Export might contain:

[ODBC]
DRIVER=SQL Server
UID=sa
PWD=MonTelSys
DATABASE=SupervisorNet
WSID=VC134
APP=ParsOut
SERVER=VC134\SQLEXPRESS
Description=SupervisorNet
Trusted_connection=no
Description=sup5

This file will be read and processed and an ODBC connection created from the contents rather than directly called. For relevant filters the precedence ExportFileDSN is will be read ahead of the AutoExportFilePathName from the PABX.INI which in turn is ahead of the ExportDSN from the PMA.INI. Most filterers will not use an SQL export.

ExportIncudeNonChargeable

Topic creation date: yyyy-mm-dd

Used by: MonexSv, ParsOut.

Version 2.12.11 onwards

0 or 1

Example:

ExportIncudeNonChargeable = 1

By default this ExportIncudeNonChargeable is set to 0. If set to 1 then non chargeable calls are also exported. This is so a PMA system or cost recovery system can perform additional processing or reporting on these records.

ExportIgnoredCodeList

Used by: monexsv

V2.12.0 Onwards

Max length: 128 characters

Example:

ExportIgnoredCodeList = ""

ExportIgnoredCodeList is currently not used.

ExportAsSummaryOnly

Topic creation date: 2009-04-11

Used by: MonexSv, ParsOut.

Version 2.12.20 onwards

Value: 0 or 1

Example:

ExportAsSummaryOnly = 1

By default this value is set to 0. When set to 0 export records are processed and exported line-by-line to the PMA system, usually this means a line-by-line set of records in a text file.

When set to 1, instead of line-by-line, the records are grouped, first by client and then by disbursement for each client, before being exported as a summary.

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