Federico
- Original Message -
From: "Klaus Feichtinger"
To: sr-users@lists.sip-router.org, fsanmar...@telecentro.net.ar
Sent: Thursday, February 26, 2015 5:10:22 PM
Subject: Re: [SR-Users] TEXTOPS parser problem with binary data in MIME body
Hi Frederico,
the only (quick) solu
Hi Frederico,
the only (quick) solution I had found was doing message parsing (MIME
body) in an external PERL script, returning the information that I was
searching for (from that body) to the config script and reducing the
multipart body to a single body. This is (until now) working fine...
Hi Klaus, did you find a solution to this problem? I'm working with SIP-I and
having the same issue with Binary encoding. I need to encode a 0x00 value and
when the config script gets to that point, it breaks. If I encode any other hex
value it's fine. This is the config part I'm using:
route[I
Hello,
most of the functions for pseudo-variables work with string types, that
because a script variable can have only integer or string values. Even
the length can be higher, these functions truncate at first 0. But
internally all should be kept, just not passed to config variables.
Have yo
Hello,
I have an update to the side effects of receiving an INVITE message that
contains a MIME body with binary data:
- pseudo variables are affected, too
- the message buffer ($mb) does not include the whole message; it is
ending with the nul character
- as the message buffer does not include
Hello,
I have a problem with Kamailio version 3.2.4 (tested also with 3.3.5)
regarding "binary data" in message bodies. According RFC3261 it is
explicitly allowed using binary data within MIME bodies:
RFC 3261 section 7.4.1: SIP messages MAY contain binary bodies or body
parts. When no explici
