Logging

If problems occur with the function in ixi-UMS Business, some logs/traces can be created. You can evaluate most of the log files yourself. Only the trace for the communication between the telephone system/router and ixi-UMS Business should be evaluated by a TK technician or sent to UMS support.

 

Trace for fax and voice transmission

This switch activates several trace/logs:

 

Art

file name

Description

Fax/Voice-Data transmission

IFTRCx.txt

CAPI-Trace, Communication with PBX-System

voice transmission

VMLTRCx.txt

Transfer of the voice data to / from the UMS system

SMS

IFXSMS2Soap3.TXT

Communication with SMS provider via HTTP

 

The Fax/Voice-Data transmission trace should only be activated if problems with the ISDN connection and/or on the advice of the company estos GmbH.

This is a trace, which can only be evaluated by specially trained personnel. If the evaluation is carried out by the company estos, a PBX configuration sheet, which has been filled out by the corresponding TK-technician, is absolutely necessary! In addition, only the problem should always be contained in the trace, that is, It should always only one call, fax etc. "getraced".

For VoIP connections please use the XCAPI trace.

 

For each channel, 4 log files are written in the directory ...\ixi-UMS Kernel. The first log file IFTRCx.txt is not overwritten after reaching 10 MB. The IFTRCxa.txt - IFTRCxc.txt files are created.

When all files have reached the 10 MB, the files are overwritten, starting with the IFTRCxa.txt file.

The IFTRCx.txt is retained.

 

Logging

 

In the log for the voice transmission, the operations of the answering machine are logged between the CAPI and the ixi-UMS Business system. This trace is only relevant to estos employees.

The files are created in the ... \ ixi-UMS Kernel directory

 

The connections to the selected SMS provider and any problems that occur are logged in the SMS log.

The log file ist created in the . \ ixi-UMS Kernel directory

 

LDAP Search

This Log is enabled by default.

LDAP queries are logged for the search and the search result for incoming and outgoing messages.

The "Connector.log" file can be opened with Notedpad/Editor in the directory ...\ixi-UMS SMTP Connector.

 

Connection to the mail server (SMTP)

SMTP communication errors between ixi-UMS Business and mailserver are logged.

The "ConnectorSMTP.log" file can be opened with Notedpad/Editor in the directory ...\ixi-UMS SMTP Connector.

 

Voice mailbox and ixi-UMS voice mailbox configuration

This log should only be activated in the event of an error.

In the log file "IXI-UMS Mobile WebMod.log" for the voice mailbox, all LDAP processes and user inputs as well as scripts are logged.

 

The "MobileHomepage.log" for the ixi-UMS voice mailbox configuration logs all read and write accesses to the LDAP database when the user performs changes in the browser-based ixi-UMS voice mailbox configuration and the logon processes.

 

The log for the "Voice mailbox: Invalid PIN entered" is always written if an incorrect PIN is entered or the mailbox is blocked.

 

All log files for the voice mailbox are stored in the directory ...\IXI-Framework \ Logs.

 

Notification (MWI)

The creation and dispatch of MWI messages is divided into 3 steps.

1.LDAP search for receiver settings:
IXI-UMS Mobile Notifier Express.log in the directory .. \ IXI-Framework \ Logs

2.Creation of the file:
ModMWI.log in the ixi-UMS Business \ ixi-UMS Kernel \ RConn \ logs directory

3.Send the MWI (through the ixi-UMS Business server service):
Displayed in the journal

 

Version 6