Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
introduce new monitoring mode that keeps sipsak running until
failureThis new -X mode keeps sending messages until a failure occurs. A
negative answer is not considered a failure. This is helpful when you
want to monitor a SIP device and do not want to restart sipsak all over
again — it keeps running until the device fails. In this mode, the
RFC3261 retransmission timers are ignored — they are constant.
Use it like this: keep trying every 1/4 sec and return with a failure
if 5 retries are not sufficient:
sipsak -s sip:[email protected] -X -Z 250 -D 5
I know it is not a best practice but I did several unnecessary changes
too — the code was simply too widely nested and I had a too narrow
monitor — I hope that’s fine. If not I can submit just the minimum
necessary changes instead.