Hi!
catalina oancea schrieb:
Then it is standard conform. If the request is received from a different address then advertised, this parameter must be added.
This is because SIP requires to send the response to the IP address from which the request was received.
regards klaus
Catalina,
Klaus is right. See RFC 3261 18.2.1 ("Receiving Requests"):
When the server transport receives a request over any transport, it MUST examine the value of the "sent-by" parameter in the top Via header field value. If the host portion of the "sent-by" parameter contains a domain name, or if it contains an IP address that differs from the packet source address, the server MUST add a "received" parameter to that Via header field value. This parameter MUST contain the source address from which the packet was received. This is to assist the server transport layer in sending the response, since it must be sent to the source IP address from which the request came.
-- Alex
Ok if it's according to the rfc I guess I must accept it.
Thanks Catalina
2009/7/17 Alex Balashov abalashov@evaristesys.com:
catalina oancea schrieb:
Ok if it's according to the rfc I guess I must accept it.
of course you could hack the source code - should be rather easy to not add the parameter. Nevertheless I never heard of any issues due to this parameter.
regards klaus
On 17.07.2009 16:19 Uhr, Klaus Darilion wrote:
just in case this "personalization" is really needed for someone, the place to look at is msg_translator.c in core, function received_test().
Cheers, Daniel