Use header values for response host and port #40
Merged
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
This was referenced Jul 23, 2025
Closed
Use the values from the Via header for determining the host and port to send responses to. If the Via header can not be used fall back to the Contact header. If both the Via header and Contact header can not be used fall back to the peer host and port from the transport the message was received on.
jaminh
force-pushed
the
response-host-port
branch
from
895e4cb to
dfc18e6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Use the values from the Via header for determining the host and port to send responses to. If the Via header can not be used fall back to the Contact header. If both the Via header and Contact header can not be used fall back to the peer host and port from the transport the message was received on.
The Contact header value is also being added to the CallInfo object. This should allow Home Assistant to save the associated URI to use for making outgoing calls, per https://datatracker.ietf.org/doc/html/rfc3261#section-8.1.1.8.