Hi Victor, Many thanks for your reply. Here is what happens if I amend msg_apply_changes(): /usr/sbin/kamailio[1705]: ERROR: textops [textops.c:1854]: append_multibody_helper(): Cannot get boundary. Is body multipart? /usr/sbin/kamailio[1705]: INFO: <script>: ISUP Changes Applied Succesfully /usr/sbin/kamailio[1705]: ERROR: <core> [msg_translator.c:1664]: get_boundary(): Content-Type hdr has no params /usr/sbin/kamailio[1705]: WARNING: <core> [msg_translator.c:1927]: build_req_buf_from_sip_req(): check_boundaries error and the SIP message appears as MALFORMED. If I do msg_apply_changes() in the end, then: /usr/sbin/kamailio[2274]: ERROR: textops [textops.c:1854]: append_multibody_helper(): Cannot get boundary. Is body multipart? /usr/sbin/kamailio[2274]: INFO: <script>: ISUP Changes Applied Succesfully /usr/sbin/kamailio[2274]: ERROR: <core> [msg_translator.c:1664]: get_boundary(): Content-Type hdr has no params /usr/sbin/kamailio[2274]: WARNING: <core> [msg_translator.c:1927]: build_req_buf_from_sip_req(): check_boundaries error I also got same result with kamailio 4.2. Thanks,Andrei
On Tuesday, July 7, 2015 8:24 PM, Victor Seva linuxmaniac@torreviejawireless.org wrote:
On 07/07/2015 04:07 PM, andre second wrote:
Hi,
I am using Kamailio version: kamailio 4.3.0 (x86_64/linux) c6aa95 on CentOS 6
I am trying to encapsulate ISUP in the INVITE:
... if(has_body("application/sdp")) { set_body_multipart(); if(msg_apply_changes()) { $var(acm) = "7e Od 04 55 75 69 20 4d 61 6b 65 43 61 6c 6c"; append_body_part("$var(acm)","application/isup; version=itu-t92+","signal; handling=optional"); xlog("L_INFO", "ISUP Changes Applied Succesfully"); } } ... And getting the following error:
I would say if you don't have modified the message already:
if(has_body("application/sdp")) { set_body_multipart(); $var(acm) = "7e Od 04 55 75 69 20 4d 61 6b 65 43 61 6c 6c";
append_body_part("$var(acm)","application/isup;version=itu-t92+","signal; handling=optional"); xlog("L_INFO", "ISUP Changes Applied Succesfully"); }
and only call msg_apply_changes() if you need to modify the message later
Anyhow, can you please create an issue at github with a minimal kamailio.cfg that crash and a backtrace? We should not crash.
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users