* Protect against CALL_SUCCESS being sent twice for each call
* Do ZMQ publishing in a dedicated thread, as sockets aren't thread-safe
* When the rate changes, the call opening task should calculate its expected amount of calls based on the time since the last rate change, not the start - otherwise it sddenly decides that it should have been producing an extra 50 calls/sec for several minutes and works too hard to catch up