b2b_logic bridge max_duration flag fix #3800
Open
+13
−4
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
The fix for max_duration flag of the b2b_bridge function in the b2b_logic module
Details
The max_duration flag of the b2b_bridge function in the b2b_logic module was not working as expected because the default max_duration setting was overriding the flag value. This issue has been resolved by introducing a new module parameter.
Solution
When b2b_bridge is triggered , the lifetime of the call was set as 5, because max_duration flag is 5:
Oct 2 07:10:35 [19] ERROR:b2b_logic:b2b_script_bridge: params->lifetime: 5 (max_duration)
When the 200 OK reply of initial INTIVE is arrived, the lifetime is updated again with default lifetime value:
Oct 2 07:10:35 [19] ERROR:b2b_logic:b2b_add_dlginfo: max_duration : 43200 tuple->lifetime 43201
The second update is prevented with the new module parameter.
Compatibility
If the new module parameter is set to false, the code behaves as before. The default value is false.
Closing issues
N/A