Skip to content

Conversation

@Schlepptop
Copy link
Contributor

Do not use FROM header to find response target address

Fixes #33

Do not use FROM header as response target address
@jaminh
Copy link
Collaborator

jaminh commented Jun 16, 2025

You are absolutely right about the FROM header in the RFC, so this definitely needs updating. I do think it is still valid, and helpful, to use the FROM header URI to identify the endpoint however. I think it would be better to leave the caller_endpoint logic as is and add a separate field to expose the contact header value specifically. I think that should allow us to avoid some migration issues with the HA integration, but still put us in compliance with the spec, and hopefully work for the implementation you are using as well.

@phavel
Copy link

phavel commented Jul 21, 2025

Yes! Please approve, solves my problem where I am forced to use the default port 5060 instead of my own port.
home-assistant/core#148578

@jaminh
Copy link
Collaborator

jaminh commented Jul 23, 2025

@Schlepptop @phavel Would it be possible for you to test with the changes in #40 to see if that solves your issue?

@jaminh
Copy link
Collaborator

jaminh commented Jul 29, 2025

Addressed in #40

@jaminh jaminh closed this Jul 29, 2025
@phavel
Copy link

phavel commented Jul 29, 2025

@jaminh Thank you for the edit! I will be able to test it in about a month.

@phavel
Copy link

phavel commented Oct 6, 2025

Tested and works, fixed, great and thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Response Host and Port should not be parsed from "FROM" field

3 participants