Mapped sequence count is not zeroed when IO connection stops/times out

The host application has the possibility to map the sequence count into the DPM's input data area (see EIP_AS_OPTION_MAP_SEQCOUNT for service EIP_OBJECT_AS_REGISTER_REQ).

Typically, the sequence count starts at 0 and increments as the connection is running.
In case the connection stops (actively closed by the originator or times out) the sequence count is supposed to be set back to value 0.

This is currently not the case. The sequence count stops at its last value and stays there until a new connection is established.