You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Path header value is not a sip parameters string (which is name1=value1;name2=value2; ...), but a name-address. You are using the wrong approach by doing only param transformation. Sometimes you may get the right value (eg., in this case, when there is another parameter after received), but that's because of a pure string delimiter parsing.
So, you have to combine {tobody.uri} and {param.value,received}
Description
Given the following Path header:
When logging with the following log line
I am seeing the following being logged in the logs:
Notice the trailing angle bracket (>).
I would have expected it to return something like the following:
Am I using this transformation correctly, or is this indeed a small bug?
Possible Solutions
Unknown
Additional Information
kamailio -v
The text was updated successfully, but these errors were encountered: