toggle quoted messageShow quoted text
Just bear in mind that KST2ME does NOT use the telnet interface ... and the protocol is somewhat different.
I've been playing with this recently myself to add a "missed call" feature to my software (ie, if someone messages you while you are not connected, it will store the messages until such time as you do connect.
I am hesitant to criticise the protocol, as I appreciate the time and effort put in by the original author, for the benefit of the community. It is however lacking in some features that I think are needed and some of it is coded in a very odd way, but it is what it is ...
On Mon, 27 Jul 2020 at 12:58, Andy <mm0fmf@...
What are using to view the socket data? I normally rely on Wireshark (Windows and Linux) for this kind of thing.
(the other one)
At least in KST2ME the second type is highlighted, and you can change the .WAV file associated with it to anything you like (even meep.wav if you wanted to) and teh colour of teh highlight.
But Robin and I are still puzzled over the actual coding over air that differentiates a /CQ from the callsign alone
The meep meep is when someone definitely messages you using the /cq. The dind sound is when somebody doesn't use the /cq - in normal use of KST, that message may easily not be seen as it isn't highlighted.
On 27/07/20 12:27, Andy G4JNT wrote:
Main issue solved. I logged into the dreaded ON4KST actual chat facility as G8IMR and into KST2ME with G4JNT
Sent a message prefaced only with the call, no /CQ or anything
Result, a polite dind sound and my filtered message highlighted in magenta
Then in ON4KST typed "/cq G8imr ... etc" and got a loud raucous mepp-meep sound and the message highlighted in orange.
SO that's answered for-sure my original query. Now to find the over-the-air difference between the two messages.
That's going to require a bit of playing around
On Sun, 26 Jul 2020 at 22:21, Robin Szemeti - G1YFG <robin@...
I was unable to work that out either.
If you send /CQ <$callsign> <msg> the KST server will send out the message with the <to> field populated with <$callsign>
In the protocol there is a "highlight" field that can be either 0,1 or 2 ... but I was unable to discover when or why it changed. I ignored it completely and simply looked at the <to> field and triggered the sound with a regex if it matched my call.
No, doesn't help. That sets up the sounds for two apparently different message types. It has two options, CQ sound and Preamble sound
When is a message a CQ and when a preamble? Looking at the raw over-air message contents there seems no obvious difference. Although a few callsigns appear in brackets - is that it ?
I've never used the actual KST web interface, but understand that in there you have to type some daft entity prefaced by "/CQ" i. Is that the difference? In which case I'm going to have to wait for
a quiet period on KST and use the web interface to send some G8IMR <> G4JNT test messages.
Want to know the raw over-air format and its options, coz I have an idea for using KST reporting for something different.
Tools/Setup/Sounds - you will see it all.
Using KST2Me , messages sent to me come up with either an orange or magenta background in the lower window, both accompanied by a sound. Orange a 'meep' sound, magenta
What's the difference between the two colours + sounds?
This email has been scanned by BullGuard antivirus protection.