If simringer receives a 180 on a branch then propagate 180 back out of simringer #13
Conversation
This file contains 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
Otherwise I think caller hears silence until someone answers (except if someone in between is doing comfort ring)
Forward first 180 received from a branch back to caller
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Only does so for the first branch to send back a 180.
Didn't deal with other 1xxs, especially 183. But using simringer to call a bunch of endpoint devices must be a common case and most will send 180 and not 183.
Wanted this since at the moment if a call is being processed through simringer there is no progress (180 Ringing) and that creates uncomfortable dead air for the call who is likely to conclude that the call failed.