[SR-Users] Warnings at apply_changes()

Diego Nadares dnadares at gmail.com
Mon Apr 24 20:11:15 CEST 2017


Hi list,

I'm converting body message to multipart. Calls establishes ok and Kamailio
it's not logging errors but I'm seeing some info and warnings that I don't
know it they are correct.

Maybe you could tell me if it's normal or if I'm doing something wrong in
my script.

kamailio[13428]: INFO: <script>: Original content type is application/sdp
kamailio[13428]: INFO: <core> [msg_translator.c:1693]: get_boundary():
Content-Type hdr has no params <application/sdp>
kamailio[13428]: WARNING: <core> [msg_translator.c:1959]:
build_req_buf_from_sip_req(): check_boundaries error
kamailio[13428]: INFO: <script>: Appending GTD to body


I use the following sintax:

route{
          ...
          route(MANAGE_MULTIPART);
          ...
}
route[MANAGE_MULTIPART]{
    ....
    if (is_method("INVITE") && !has_totag() && has_body()){
     ...
      xlog("L_INFO", "Original content type is $cT");
      set_body_multipart();
      *msg_apply_changes();*
      xlog("L_INFO", "Appending GTD to body");

      ...
   }
    ...
}

Invite example:

INVITE sip:222222222 at 172.16.205.122:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.213.21:5060;branch=z9hG4bK-28085-1-0
From: "111111111" <sip:1111111111 at 172.16.213.21:5060;user=phone>;tag=1
To: <sip:2222222222 at 172.16.205.122:5060>
Call-ID: 1-28085 at 172.16.213.21
CSeq: 1 INVITE
Contact: "1111111111" <sip:111111111 at 172.16.213.21:5060>
Max-Forwards: 70
Subject: Performance Test
Content-Type: application/sdp
Content-Length:   137

v=0
o=user1 53655765 2353687637 IN IP4 172.16.213.21
s=-
c=IN IP4 172.16.213.21
t=0 0
m=audio 6000 RTP/AVP 8
a=rtpmap:8 PCMA/8000

As you can see the log says that "Content-Type hdr has no params
<application/sdp>" but in the line before says "Original content type is
application/sdp".

I'm running kamailio 4.4 by the way.

Thanks in advance.

Diego.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20170424/d4c79da2/attachment.html>


More information about the sr-users mailing list