Galaxy Alarm Reporting over Ethernet

I have a Galaxy 500 (firmware 4.39) with Ethernet and Telecomms. I have the telecomms reporting via SMS paging which works okay but is expensive as I have groups enabled (2 groups) so each time someone locks/unlocks the house I get two SMS paging messages

I have a local area network (Ethernet) and servers (computers) - what I want to do is have the Ethernet module in the Galaxy report to a program on the PC and have it "filter" messages and send a subset of the 'interesting' ones out via internet SMS paging to my mobile, rather than the telecom module sending everything blindly and filling up my phone... for example I don't want SMS paging when user 001 sets/unsets the system as its me!

Does anyone on here know how the Microtech protocol works over Ethernet?

I've configured the Ethernet module with its TCP/IP settings and can access it with Galaxy Gold 6.80 okay, so I know it's on the LAN and working, however I have written a dumb TCP/IP listener program that sits on a server listening to port 10002 and I've programmed the Galaxy to call it... what happens is the Galaxy makes the TCP/IP connetion hangs for a few seconds, disconnects, then tries again... this appears to go on for ever...

I have the Galaxy panel programmed to report in Microtech protocol (not SIA). Are there any TCP/IP networking aware readers on here?

What I see on my 'dumb' program is the Galaxy starts a connection and then waits, then disconnects... so it looks like the panel is expecting some greeting/protocol/handshake from the PC/application -- like Alarm Monitoring... does anyone know how this works? On receipt of a connection from the Galaxy what do I need to send to get it to tell me stuff?

Mike