Hello Jijo,
It seems like the decode_mime_type is a somehow broken. The comma is very well
allowed in boundary, as you said. The BNF specified in RFC2046 permits it.
But, the decode_mime_type function ignores everything coming after comma. More
than that, it notifies the function caller that
On Wednesday 17 August 2011, Spencer Thomason wrote:
Can anyone shed some light into the differences between the available LCR
modules? We have migrated our config from OpenSIPS where we used the
drouting module to Kamailio where we are using the lcr module. Our
ruleset is not crazy huge,
Daniel-Constantin Mierla writes:
* this is intended to control the behavior of the tree data and matching
mode. The default one is 0, match longest prefix and the associated data
with the prefix is a string. This is complete implementation.
There is actually a second mode, 1, intended to
Hi Daniel!
Thank You very much!
I tested it, and it seems to be working for me!
Only one typo what i corrected.
You have missed out the beginning from your example.
if(method==ACK) sip_trace();
Thank you again!
By the way two problems with git HEAD.
I checked out the current git HEAD,
Hi Marius,
Thanks for the response.. I checked the other functions, but they don't have
the check for ret !=end, but they check the pointer and if it is comma then
loop through again until it find all the media types.
As per the RFC3261 multiple media-types are not supoorted in the
Content-Type.
Hello
This is how my registrar module is configured, hoping that min-expires set to
30 wont allow registration attempts more often than 30 seconds, but if I
configure a UAC to register every 15 seconds I see that kamailio allows it.
Shouldn't it reply with 422 Session Interval Too Small or
Hi Jijo,
In my opinion, decode_mime_type is broken, and parse_accept_body does not work
as expected.
For example, this is a valid accept header:
accept: text/plain;param=,some value.
but the parse_accept_body will return -1 because the first return value of
decode_mime_type is ,some value\.
