#261 MD reply/add listener does not use send parameters

[Bryce Jensen]

While tlm_reply does pass in send parameters, within that function it sets newSession to FALSE. This results in the call to trdp_mdConnectSocket effectively doing nothing, leaving the parameters (TTL, QoS) unused. While this makes some sense I theorized that perhaps the parameters are set up in the call to tlm_addListener, however that only uses default MD parameters. This means that there if you desire MD with differing QoS or TTL you will be unable to do so.

[Bernd Löhr]

The standard leaves this open, in a way. In the XML configuration, each telegram (comId) has communication parameters on its own, which could be used for the reply. Or, the recived request's values should be read out (of the header) and will be used for the reply.
We postpone this a bit, because the changes will be quite large for a bug-fix release...

[Armin-Hagen Weiss]

Postponed until standard has a clear definition. Now the default settings used for creating the receive socket are used sincs this one is also used for sending the reply.

[Armin-Hagen Weiss]

Setting MD telegram specific communication parameters is not foreseen in version 2 of 2-3, so the pSendParam parameter shall be removed from tlm_notify, tlm_reply, tlm_request, tlm_confirm and tlm_replyQuery.

[Armin-Hagen Weiss]

Send params removed from tlm_addListener/reply/replyQuery/confirm/notify() since useless. In tlm_request() send params are replaced by retries to define the maximum number of retries of a request in case there is no reply/replyQuery().