Telexforum.de

wyssby hat geschrieben: ↑Mo 5. Sep 2022, 21:36 Hi Andy,
you wrote about two serial ports. I assume one is that on the Ethernet card of i-telex and the other one is the serial port which is part of a combined TW39 - Serial card.
Logging for anything related to the connection via Internet is done on the first of those COM port. This depends on the logging level set in the webbased configuration menu. But this will not include the full messages text afaik.
Logging of events on any other port i.e. telex machines is defined with another entry in the configuration menu.

Details about the configuration and the logging levels are available from the related section of the i-Telex Wiki

You could setup the answering machine which is part of the serial port on the combined card so that any message arriving while the telex machine is unavailable will be stored there and can be retrieved later, either from a telex machine or via serial port.

Regards
B@ from Switzerland

FredSonnenrein hat geschrieben: ↑Di 6. Sep 2022, 07:51 Hello Andy,
There is no function for "logging" is you might expect.
The serial port of the ethernet PCB provides only "logging" for debugging purposes. There is no "human readable" information in.
The serial port of the "combined" (TW39 and RS232) has a built-in "call recorder".
So any communication reaching this port (so it must be called) is output to the RS232-port AND simultaneously recorded in an EEPROM.
This recording can be replayed either by using the RS232 or by calling the interface by telex and following a special procedure.

To archive that incoming calls are redirected to the "serial port with logging" you have to do:
- enable the option "Forward calls to alternative teleprinter if called is busy:" to "also for direct calls".
- put the "regular" printer port to "busy" by either:
- pressing the button related to this port, that the blue LED goes on OR
- setting up a "block time" in the configuration of the TW39 port
it is not sufficient to just switch off the printer, as this is not recognized by the hardware.

Best regards,

Fred

FredSonnenrein hat geschrieben: ↑Sa 10. Sep 2022, 11:39 Unfortunately there is no simple way to record all the communication.
I think about a possibility to use the serial port of the ethernet board to log all texting (instead of debugging log), but this would need an 7/24 running pc or similar to store the log.