Hey,
Maybe someone from the list can share some information about the path module. Why can the path module only add either the received parameter to path or the flow token with the ob parameter, but not both.
Does the RFC mandates it? I didn't find anything like that and was wondering because the source calculates max length of the parameters with following:
/* maximum possible length of suffix */ suffix_len =
strlen(";lr;received=sip::12345%3Btransport%3Dsctp;ob;>\r\n") + IP_ADDR_MAX_STR_SIZE + 2 + (add_params ? add_params->len : 0) + 1;
This looks like it can be possible to have both.
Best regards Rick
Hello,
On 03.10.17 00:46, Rick Barenthin wrote:
Hey,
Maybe someone from the list can share some information about the path module. Why can the path module only add either the received parameter to path or the flow token with the ob parameter, but not both.
Does the RFC mandates it? I didn't find anything like that and was wondering because the source calculates max length of the parameters with following:
/* maximum possible length of suffix */ suffix_len =
strlen(";lr;received=sip::12345%3Btransport%3Dsctp;ob;>\r\n") + IP_ADDR_MAX_STR_SIZE + 2 + (add_params ? add_params->len : 0) + 1;
This looks like it can be possible to have both.
I am not aware of such restrictions from specs -- the received is kind of own extension.
Anyhow, there was a pull request done by you which was already merged, I guess it added what you needed.
Cheers, Daniel
-
Daniel-Constantin Mierla -
Rick Barenthin