Support #623

Updated by Madars about 3 years ago

Currently tpridge exchanges monotonic clock values when connection is established between nodes. This value is used for detection of expired in progress messages, and if they are expired, message is dropped automatically when call reaches server process. If the clocks on servers over the time drift away (thus the difference after some 15 days, is not more X seconds, stored in bridge, but Y seconds), and if this difference is higher than NDRX_TOUT setting, then it is possible that messages received from other server node are never processed and dropped immediately. Thus to cope with this situation:
- Periodic exchange of monotonic server clock value shall be implemented.
- Only if the exchange time is less than certain time, the new calculated difference should be used.
- Also when messages are dropped for this reason, they should go to ULOG and in process log logged with error level 2 (i.e. ndrx topic/facility shall be at-least set to ndrx=2 to see this message. In ULOG it is written unconditionally). 2.

Back