From: "Barman, Sibon B \(Sibon\)" <[EMAIL PROTECTED]> When a user agent sends a REGISTER request with private address in the Contact header, the session border element sends a response with the UA's public IP address in the contact header as well as in the Via header's rport and received parameters. Is that correct spec-wise --- should the UA be able to handle this registration response and treat it as its own contact? Or does the 3261 spec dictate that the response should contain the same contact address as the request?
Assuming that the session border element is "transparent", it must make the UA think it is talking to an RFC 3261 registrar, and the registrar think it is talking to an RFC 3261 UA. So when the UA sends REGISTER to the SBE, the SBE replaces the contact A with the contact A' (which is routable in the registrar's network). The registrar's response lists contact A'. But the response that arrives at the UA must contain the contact A, because that's how a 3261 registrar would have responded to it. So the SBE has to replace A' in the response with A. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
