< Previous by Date Date Index Next by Date >
  Thread Index Next in Thread >

[reSIProcate-users] text parameter collision?


Title: text parameter collision?

Hello,

I have a problem parsing this embedded Reason header:
Reason=sip%3btext%3d%22Moved%20Temporarily%22%3bcause%3d302

The problem is that the stack does not seem to be able to find the 'cause' parameter.

As this one works fine:
Reason=sip%3bcause%3d302%3btext%3d%22Moved%20Temporarily%22

I *think* the problem is that there is a 'text' parameter defined, but as an ExistsParameter, according to ParameterTypes.hxx from RFC 3840. It seems that the parser is then confused when a 'text' parameter has a value.

The Reason header is defined in RFC 3326.

What would be the best way to handle this collision?

(Reasonably there should be no difference if it was a plain header and not embedded, but if there really is a difference I decided to show my real problem.)

Rgds,
Mats