[SR-Users] Does kamailio has some headers optimizing mechanism ?

[Daniel-Constantin Mierla]

Hello,

On 7/16/12 8:19 PM, Konstantin M. wrote:
> Hello,
>
> I have a following part of code:
>
>
>     if (route(Test_TO_Dialer))
>     {
>         append_hf("P-hint: Loose Routing. Re-INVITE Detected: Uplink 
> --> Originator.\r\n");
>         xlog("********** loose_route(): Detected Re-INVITE from 
> Uplink! **********\n");
>
>         setflag(1); # do accounting
>
>         append_hf("P-hint: SDP was mangled\r\n");
>         python_exec("ParseSDP", $mb);
>
>         fix_nated_contact();
>         setbflag(6);    # Mark as NATed
>
>         rtpproxy_manage();
>         dlg_manage();
>     }
>
> But in a logs I see:
>
> P-hint: Loose Routing. Re-INVITE Detected: Uplink --> Originator., SDP 
> was mangled
>
> but it should be like this:
> P-hint: Loose Routing. Re-INVITE Detected: Uplink --> Originator.
> P-hint: SDP was mangled
>
> Does kamailio has some headers optimizing mechanism ?
>
> # ./kamailio -V
> version: kamailio 3.2.3 (x86_64/linux)
> flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, 
> USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 
> SHM_MMAP, PKG_MALLOC, DBG_QM_MALLOC, USE_FUTEX, 
> FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, 
> USE_DST_BLACKLIST, HAVE_RESOLV_RES
> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, 
> MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
> id: unknown
> compiled on 15:37:11 Jun  9 2012 with gcc 4.4.3
>
>
there is no such mechanism to join headers with same name added by 
append_hf(). Can you provide a ngrep trace of such situation?

Cheers,
Daniel

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw