UM services
Errors during fax or SMS transmission as well as fax or voicemail reception are written to the UM log files. The logging for UM is activated by default with the level error search under System settings > Logging > UM services > Logging.
This logging window has a Download log files button. Clicking this button archives the data in a ZIP file which can be sent product support together with an exact description of the procedure.
Hint
Log files which are more than five days old are automatically deleted.
Logging
Here logging can be activated and the degree of detail (Detailed debug notifications, Only warnings, Only errors) can be specified.
The log files are saved in the directory:
<XPhone Connect Server Installationsverzeichnis>\\UMS\Log
Hint
If you have activated the highest logging level for troubleshooting, remember to reset the level once the problem has been rectified to Warning or Only errors. Forgetting to perform a reset diminishes system performance and increases hard disk use.
The following log files are of relevance for the individual services:
- Voicemail player
If an employee listens to his voicemail messages via the end device by clicking the “Play” button in the voicemail form in XPhone Connect Client or Microsoft Outlook and is then automatically called, this is handled by the Voicemail player service. All other voicemail processes are written in the Voicemail log.
- Voicemail
The Voicemail service is responsible when a voicemail is recorded for a user or the user checks his voicemail inbox by calling the voicemail number. Processes such as Transferring callers via a voicemail greeting and all Auto Attendant processes are recorded in this log. Messages left for users are passed on to the SMTP relay service and then passed on to the internal or external e-mail server’s inbox.
- Receiving faxes (Fax2Mail)
Fax messages received are initially received by the Receiving faxes (Fax2Mail) service. Once the corresponding user has been found in XPhone Connect Server, the fax is relayed to the SMTP Sender service which sends the fax to the internal or external e-mail server’s inbox, e.g. Exchange, via the SMTP relay service. Please also note the log files for SMTP Sender and SMTP Relay.
- Fax messages (Mail2Fax)
Fax messages sent by the XPhone Connect Client, Microsoft Outlook or other e-mail clients are initially processed by the Inbound SMTP service (smtpCmds), followed by the SMTP Receiver service which then passes them on to the Fax dispatch service (Mail2Fax). If no entries can be found on fax dispatch in the logs referred to above, the fax may be stuck in the e-mail server, e.g. Exchange. Check the e-mail server used.
- Text message dispatch (Mail2SMS)
Text messages sent from XPhone Connect Client are initially processed by the Inbound SMTP service (smtpCmds), followed by the SMTP receiver (SMTP Receiver) which then passes them on to the Text message dispatch service (Mail2SMS). Check the log files referred to; if nothing is logged here, the text message is stuck in the e-mail server, e.g. Exchange. If necessary, check the e-mail server used.
- SMTP dispatch (SMTP Sender)
Inbound fax messages or voicemails are relayed to this service by the Inbound fax service (Fax2Mail) or voicemail in order to supply them to the user via the SMTP relay service in the user’s inbox or on the internal or external e-mail server.
- Fax printer (Fax2Print)
This service logs all incoming fax messages which are automatically printed on a printer.
- SMTP receipt (SMTP Receiver)
This service receives faxes or text messages to be sent from the SMTP Inbound service (smtpCmds) in order to relay them to the Fax dispatch service (Mail2Fax) or the Text message dispatch service (Mail2SMS).
Internal e-mail server log:
- IMAP (imapCmds)
This service logs queries of the XPhone Connect Client for new UM elements (faxes, voicemails, text messages) from the XPhone Connect Server. It also logs when a user wishes to listen to his voicemails by remote access in the internal e-mail server.
- SMTP input (smtpCmds)
This service logs fax and text message dispatch by the XPhone Connect Client, or via Outlook or other e-mail clients. The receipt of fax messages and voicemails is also logged as well as the fax and text message delivery reports (DRs, NDRs).
- SMTP relay service
If the SMTP input service (SmtpCmds) establishes that the incoming e-mail (fax, voicemail or text message) is not intended for a certain internal inbox, this element is relayed to the e-mail server installed under System settings > E-Mail Gateway. This communication between the internal e-mail server and the external e-mail server (e.g. Microsoft Exchange or Domino Server) is logged here.
Administrator alert
This is where you specify an email address to be used for alarm messages. The administrator alarm is activated when the check box is ticked.
Recording of connection data
It is possible to generate a connection data file about all sent and received fax documents. This is created in .CDR format in the directory <XPhone Connect Server installation directory>\UMS\CDR.
Activate the creation of a connection data file here and specify the time for daily creation. Choose a time outside of the normal working hours. In general, the default setting can be kept.
Format of the connection data file
Connection data are recorded in text files, which you can find the cdr sub-directory. The connection data are recorded separately for sending and receiving.
Sending data are saved in files with the name template
M2Fyyyymmdd.cdr.Receive data is stored under
F2Myyymmdd.cdr. yyymmdd stands for year, month and day of recording.
Each connection consists of a data set with several fields separated by a TAB (ASCII 09hex). The data sets are separated by carriage return / line feed (ASCII 0D0Ahex).
A data set in the file for receiving faxes consists of the following fields:
Designation |
Meaning |
|---|---|
JobID |
Unique identifier of data record |
Calling party number |
Sender phone number |
Calling party Station ID Fax ID (CSID) |
Sender fax ID |
Called party number |
Recipient’s fax number |
Called party e-mail address |
Recipient mailbox number |
Start time of the transmission |
Start time of transmission: day, month, year, hour, minutes, seconds (dd.mm.yyyy hh:mm:ss) |
Stop time of the transmission |
Stop time of transmission: day, month, year, hour, minutes, seconds (dd.mm.yyyy hh:mm:ss) |
Duration Stop time – start time |
Duration |
Send time of the e-mail dd.mm.yyyy hh:mm:ss |
Time entered in message store: day, month, year, hour, minutes, seconds (dd.mm.yyyy hh:mm:ss) |
Type of charge |
Type of charge information UNITS = charges are sent as units NATIONAL = charges are sent in national currency NOTAVAILABLE = no charge information available |
Total charges |
Sum of all charges as per unit ID |
Number of pages |
Number of pages |
Resolution |
Resolution |
Format OK? OK, PARTLY RESTORED, RESTORED, CORRUPT |
Error ID |
Disconnect reason |
Disconnect reason |
A data set in the file for sending faxes consists of the following fields:
Designation |
Meaning |
|---|---|
JobID |
Unique identifier of data record |
Calling party e-mail address |
Calling party email address |
Calling party number |
Sender phone number |
Called party number |
Sender phone number |
Receive time of the e-mail dd.mm.yyyy hh:mm:ss |
Transmission time from central message store (outbox) to sender service, day, month, year, hour, minutes, seconds (dd.mm.yyyy hh:mm:ss). |
Start time of the transmission dd.mm.yyyy hh:mm:ss |
Start of transmission: day, month, year, hour, minutes, seconds (dd.mm.yyyy hh:mm:ss). |
Stop time of the transmission dd.mm.yyyy hh:mm:ss |
End of transmission: Day, month, year, hour, minutes, seconds (dd.mm.yyyy hh:mm:ss). |
Duration Stop time – start time |
Duration of transmission |
Type of charge |
Type of charge information UNITS = charges are sent as units NATIONAL = charges are sent in national currency NOTAVAILABLE = no charge information available |
Total charges |
Sum of all charges as per unit ID |
Number of pages |
Number of pages |
Resolution |
Vertical resolution (98 or 196) |
Number of dial attempts |
Number of times a dial was attempted |
Disconnect reason |
Disconnect reason |
Status SENT or FAILED |
Transmission status |
Subject |
Subject line of the sent fax |
ISDN Error Codes:
Code |
Meaning |
Description |
|---|---|---|
0000 |
Normal call clearing |
|
3301 |
Protocol error layer 1 |
Connection interrupted or B-channel closed by control protocol. The cable may not be connected properly. |
3302 |
Protocol error layer 2 |
|
3303 |
Protocol error layer 3 |
|
3304 |
Another application got that call |
Another application was faster in accepting the call |
3311 |
Connection failed |
Remote station is not a fax machine |
3312 |
Connection failed |
(training error) |
3313 |
Disconnected before transfer |
Remote station does not support transfer mode Resolution may be incorrect for instance |
3314 |
Disconnected during transfer |
Remote abort |
3315 |
Disconnected during transfer |
Remote procedure error |
3316 |
Disconnected during transfer |
Local tx data underrun |
3317 |
Disconnected during transfer |
Local rx data overflow |
3318 |
Disconnected during transfer |
Local abort |
3319 |
Illegal parameter coding |
e.g. SFF file error |
3400 |
No ISDN connection. |
|
3481 |
Unallocated number |
This error normally occurs if the fax service has not been configured in the telephone system |
3482 |
No route to specified transit network |
|
3483 |
No route to destination |
|
3486 |
Channel unacceptable |
|
3487 |
Call accepted and forwarded to existing connection |
|
3490 |
Normal call clearing |
|
3491 |
User busy |
|
3492 |
No user responding |
There is probably no terminal device connected to the number you are calling |
3493 |
No answer from user (user alerted) |
The remote station is ringing but nobody is answering The fax device may need to be turned on manually. |
3495 |
Call rejected |
|
3496 |
Number changed |
|
349a |
Non-selected user clearing |
|
349b |
Destination out of order |
|
349c |
Invalid number format |
The party you are calling could not be reached because the number you called is in the wrong format or incomplete. |
349d |
Facility rejected |
|
349e |
Reply to status query |
|
349f |
No ISDN connection Reason unknown |
This error code is only logged if no other code from the “normal” class applies. |
34a2 |
No channel available |
All ISDN channel occupied. If this error occurs frequently, it may mean that additional ISDN channels need to be opened |
34a6 |
Network out of order |
|
34a9 |
Temporary failure |
|
34aa |
Switching equipment congestion |
The sending switch is currently overloaded. |
34ab |
Access information discarded |
|
34ac |
Requested channel not available |
|
34af |
Resources unavailable, unspecified |
|
34b1 |
Service not available |
|
34b2 |
Requested facility not subscribed |
|
34b9 |
|
|
34ba |
Bearer capability not presently available |
|
34bf |
Service or option not available, unspecified |
|
34c1 |
|
|
34c2 |
Channel type not implemented |
|
34c5 |
Requested facility not implemented |
|
34c6 |
Only restricted digital information bearer capability is available |
|
34cf |
Service or option not implemented, unspecified |
|
34d1 |
Invalid value of the call reference |
|
34d2 |
Specified channel does not exist |
|
34d3 |
An suspended call exists but this call identity does not |
|
34d4 |
Call identity in use |
|
34d5 |
No call suspended |
|
34d6 |
Call having the requested call identity has been cleared |
|
34d8 |
Remote station is not compatible |
The sending unit that protocols this error received the request to establish a connection with the protocol being to low or too high. This error often occurs if the fax service was not configured correctly in the telephone system. |
34db |
Invalid transit network selection |
|
34df |
Invalid message, unspecified |
|
34e0 |
Mandatory information element is missing |
|
34e1 |
Information element non-existent or not implemented |
|
34e2 |
Message not compatible with call state or message type non-existent or not implemented |
|
34e3 |
Information element non-existent or not implemented |
|
34e4 |
Invalid information element contents |
|
34e5 |
Message not compatible with call state |
|
34e6 |
Recovery on timer expiry |
|
34ef |
Protocol error |
|
34ff |
Interworking, unspecified |
|
fffe |
Timeout |
A timeout occurs mainly when a connection is set up There are different reasons for this error code: The remote station is not a fax device, or it is a fax device, but needs to be manually set to receive faxes. |
Have you found a mistake on this page?
Or is something not formulated well or too vague? Then we look forward to receiving an e-mail, preferably with a suggestion for improvement, to doku@c4b.de. Thank you very much!