Status: Accepted
Owner: jean.deruelle
Labels: Type-Defect Priority-Medium Component-Sip-Servlets MSS-2.0.0.FINAL
Roadmap-Fix TelScale-6.1.2.GA
New issue 156 by jean.deruelle: MSS overwrites host part of Contact Header
in REGISTER requests
http://code.google.com/p/sipservlets/issues/detail?id=156
As per JSR 289 Section 4.1.3, this seems wrong :
"The other use of Contact is in REGISTER requests and responses, as well as
3xx and 485 responses. The value of Contact header fields in these messages
specify alternate addresses for a user, and there may be more than one.
These are the uses where SIP servlets may legitimately set Contact
addresses."
It may stem from confusion later in the same section saying :
" The host component of the URI and URI Scheme are irrelevant and cannot be
trusted to reflect the actual values that the container will be using when
inserting a Contact header into Request or Response. The container MUST
ignore or overwrite any host/port set on the Contact URI accessed as above.
This is because the container is responsible for managing the actual
network listen points and uses these to create Contact headers' host/port."
I think the former section is still prevalent as those can be alternates
addresses so not necessarily the container's IP addresses.
