Hello @JamesC,
Yes I did read the specification before, implementing but some documents are difficult to get if you don't know how they are called, in any case thanks for pointing me out to that document, it has clarified some points from from the gateway towards the customer server, however, it has blurried also others like for instance, how a downlink request should be, LoRa inter-server interface definition.pdf attached by @w4e states on section 8.3.5 the sort of message to be used. This is contradictory what I heard from Kerlink, since they were claiming that I should I use
{{"tx": {"moteeui":"2010103","txmsgid": "1","trycount":5,"txsynch": "false","ackreq":"true","userdata":"port":1,"payload":"aGk="}}}}
whereas that section states
{{"txpk": {"moteeui":"2010103","txmsgid": "1","trycount":5,"txsynch":
"false","ackreq":"true","userdata":"port":1,"payload":"aGk="}}}}
So now I have doubts of what to use actually, because I don't know whether they are using some parsing in between or what...
Another question that I have now, it's that I according to LoRa specs the received data from mac rx should be encrypted, however if I send something from Kerlink website, it is not, I mean the payload that I set there is flatly HEX data and I receive it as it is without encrypting it, nevertheless when using the UDP interface seems to be following the standard...