dev/null for telex

[levend]

As I'm learning my machine, I try to experiment with it a lot. For some of these, it would be beneficial to be able to do a remote connection to a universal sink like /dev/null in Linux.
For example, I want to try out how to send a prepared text, so I would call this remote device, establish a connection, and can then send whatever I need. This way I don't have to "pollute" someones machine with meaningless test messages.
Maybe there is already such a service available?

[FredSonnenrein]

If you dont mind that your messages are recoded, you may use 531099. It's just a electronic recorder on my server pc.

[kerk1v]

Easy enough:

- Install a second instance of PiTelex somewhere, meaning, clone the git repository again in a different directory. It does not need to be on a different raspi or PC, as long as you change the port as shown below, there will be no issues.
- On that second instance, disable all modules except "screen" and "I-Telex" in telex.json. For I-Telex, use a port that is different from your "main" connection
- Populate the last lines of your telex.json of the second instance like follows:

Code: Alles auswählen

  },
  "verbose": true,
  "wru_id": "AN INVENTED NUMBER AND ID HERE",
  "wru_fallback": true,
  "dial_timeout": 0,
  "debug": 3
}

- create a file userlist.csv based on userlist_example.csv file, with an entry for your real machine, the format should be pretty self-explanatory. If you want, do the same on your "real" Pitelex this time pointing to the port of your "fake" or "test" PiTelex so it will work both ways.
- run ./telex.py in the second directory
- Type <esc>AT and type the number used for your "real" PiTelex in the userlist.csv. A communication with your telex machine will be established.
- Happily test away! Note: "@" is WRU and "%" is HEREIS, or the other way around, can't remember now.
- Type <ESC>ST or <ESC>Z to end the connection from within PiTelex, or the "end" key on your T1000S.

Kind regards,

[levend]

Thank you Volker and Fred, I will try it soon.

[levend]

It was unsuccessful to connect to your SW Fred, here is the log from piTelex:

2021-12-16 13:56:17,469 piTelex.txDevITelexClient [INFO]: Get User: '531099'
2021-12-16 13:56:17,748 piTelex.txDevITelexClient [INFO]: Found user in TNS: {'TNum': '531099', 'ENum': None, 'Name': 'Fred, Braunschweig TestSW', 'Type': 'I', 'Host': 'sonnibs.no-ip.org', 'Port': 11134}
2021-12-16 13:56:17,754 piTelex.txDevITelexClient [INFO]: connecting to Fred, Braunschweig TestSW (sonnibs.no-ip.org:11134)
2021-12-16 13:56:17,982 piTelex.txDevITelexCommon [INFO]: Sending direct dial: None
2021-12-16 13:56:17,987 piTelex.txDevITelexClient [INFO]: connected
2021-12-16 13:56:17,992 piTelex.txDevITelexCommon [INFO]: Connection hint: i-Telex connection
2021-12-16 13:56:17,996 piTelex.txDevITelexCommon [INFO]: State transition: 0=>1
2021-12-16 13:56:45,953 piTelex.txDevITelexCommon [INFO]: end connection
2021-12-16 13:56:45,957 piTelex.txDevITelexCommon [INFO]: State transition: 1=>0

[FredSonnenrein]

Strange. Seems to be another incompatability of pi-Telex. Note: The system behind 531099 is a testing system.

[kerk1v]

Strange. Seems to be another incompatability of pi-Telex. Note: The system behind 531099 is a testing system.

I very much agree. PiTelex is a noble quest, but incompatible with original I-Telex in many aspects, and I found out so the hard way, with services that work reliably with the original I-Telex slowing down to a crawl. I know yiu have worked a lot with its developer on the handshakes and the like, but it's still far from perfect.

Fred, maybe you would like to give @levend the link to your repo with the recorder source, so he can run it locally, look at the logs and maybe we figure out what the incompatibility with PiTelex is this time.

Recomendation to @levend: Do the leap, get a proper I-Telex kit from Henning and enjoy a truly well-engineered and reliable connection to the I-Telex net. I know it looks like a sizeable investment at first, but never regretted it and only use Pi-Telex for some testing and playing around, for that it's a fair enough solution, but not for "reliable" use, IMHO.

Regards,

[FredSonnenrein]

Fred, maybe you would like to give @levend the link to your repo with the recorder source, so he can run it locally, look at the logs and maybe we figure out what the incompatibility with PiTelex is this time.

It's a bit more than an alpha version. I would like to spend some work to make it at least "beta".

[kerk1v]

It's a bit more than an alpha version. I would like to spend some work to make it at least "beta".

I compiled it locally, after tinkering with where to find (and put) the libraries, and here it's stable like a rock!

[levend]

I will definitely step forward and purchase a complete i-telex kit in 2022, but right now the budget for my "strange" hobbies have deplepted.