Any luck with getting m1xep to send out the http request?
I am getting a similiar result. I have the text string defined in Elk that I want, which in my case is 00AP1admin?profile=1^M^J
Using the M1XEP Diagnostic tool, I see the string in the trace window when I cause the Elk to be triggered to send the text:
14:34:40 TCP SendUnkPkt 19KC01150000000000000000011
14:34:40 TCP SendUnkPkt 17IC000000000000203010076
14:34:40 TCP SendUnkPkt 00AP1admin?profile=1
14:34:40 TCP SendUnkPkt 0ATC010000D7
But there is no http command being sent by the elk. I am running wireshark, and the only data on the network that has the string is the italk UDP message that is sent from the M1XEP to the M1XEP Diagnostic Tool.
I have tried removing the CRLF (^M^J) from the text definition, and that had no effect.
The only other thing I wonder about is that my IP address is username
assword@numericip , I wonder if elk could be unhappy with that? In any case I haven't been able to find any other form of passing the username and password that the target server (Blue Iris) is happy with, so I don't have anything else to try.