UAC_REGISTRANT module enhancements #3783
Open
+1,007
−63
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…w instead of waiting for next tick )
|
Any updates here? No progress has been made in the last 30 days, marking as stale. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Add MI commands to operate on the memory of the registrant with no DB interaction
Add event for all states of the registrant
Add new parameter controlling how much sooner the re-register needs to be sent
Details
Sometimes it is useful to use OpenSIPS as a registrant, but without any DB connectivity. 2 new MI commands have been added, reg_upsert and reg_delete, that insert/update the registrant memory contents and delete the registrant.
Added events for all state-machine changes for a registrant entry.
Added a new reregister_expiry_percentage parameter, describing how much sooner a RE-REGISTER needs to be sent based on the Expiry. a 100 value means the RE-REGISTER will be send right on the edge of expiry ( old behavior ), which might lead to registration loss. a 90 value means the RE-REGISTER will be sent sooner , at 90% of the Expiry, etc.