I'm not familiar with the old configurator, but the new one shows the parameter's IDs when you hover over them. I assume DIN 2-4 are in the range 2010-2014, 2020-2024 and 2030-2034. At least in the newer version getparam format is getparam ID (or getparam ID1;ID2;...;IDn) and setparam ID:value (or setparam ID:value;ID2:value2;...)
Answering your second question:
According to wiki, Codec14 is supported in firmware FMB.Ver.03.25.04.Rev.00 and up. Since this device will be EOL soon, I'm not sure if it's supported.
For tracking device connections consider using TCP instead (Yes, there are drawbacks). In order to implement proper messaging over UDP (With Codec12) you could implement queues that send one message at a time (for messages that provide response) and give enough time for the device to process the message in case the message should not return response. For messages that could change AVL data, you could configure the AVL element to be sent "on change", and wait for the change to come over Codec8.
edit: actually try sending two commands in one udp packet, and the second one could contain something identifiable - getinfo, getver or getimsi. Might work this way.
(disclaimer: I'm more familiar with FMB1xx range of devices and recent 3.x firmwares and this answer might not be entirely correct)