Hello Daniel;
3 day ago , i just started to work on rtpproxy. My call flow like UAC1--> Kamailio1---> Kamailio2+RTPPROXY--> UAC2 but it doesnt work because i saw sdp body has missing parameters but rtp flows like UAC1<---->UAC2. And then i removed first kamailio and i saw it worked correctly and there is no mistake on sdpbody. RTP flows like UAC1--->Kamailio2+RTPPROXY---->UAC2 and SIP Flows like UAC1----> Kamailio2+RTTPROXY-->UAC2. i thought it is really weird because how is possible Kamailio1 effect like that. And then i removed nearly all modules and left simple cfg. i realized that appending header effects it. Could you help me about it, please

Thanks

i solved remove_hf function that kamailio removes header field that adds by self , after msg_apply_changes().

i tested UAC1--->Kamailio2---->UAC2 call flow and added 14 header doesnt have any problem.

Thanks.

08.04.2016 12:03 tarihinde Daniel-Constantin Mierla-6 [via SIP Router] yazdı:

Hello,

how did you asserted the fact that the message is truncated? Is the next SIP hop not retrieving it with full content? Or just you looked at some traces on the net, if this one, note that some network sniffing tools are having their limitations in what they display.

Daniel

On 08/04/16 09:30, ycaner wrote:
Hello Daniel;

in request route when invite comes, a header is added like P-SrcUserid. when i added new header , it truncate sdpbody. before t_relay(), i try to remove header, and it didnt. main problem is why truncates sdpbody when i added new header?

Thanks.

Works fine sip messages: http://pastebin.com/t7v9c2vW
removes coming headers cfg,but i couldnt remove P-Provider and P-Uniqueid :http://pastebin.com/9tB7Lx3U

truncateting sip message : http://pastebin.com/DNuuJxhM

removes coming headers cfg,but i couldnt remove P-Provider and P-Uniqueid and added P-SrcUserid : http://pastebin.com/XxhcV55v

08.04.2016 09:22 tarihinde Daniel-Constantin Mierla-6 [via SIP Router] yazdı:

Hello,

On 08/04/16 08:06, ycaner wrote:
> Hello;
> i think i found problem. it is textops module.Appending new header doesnt
> increase content length. in addition , remove_hf doesnt work correctly that
> doesnt remove headers.
>
the value of content lenght is about the body size, it is not affected
by new headers or removing old headers.

What do you mean by remove_hf() is not working? How you try it? Can you
send here how you use remove_hf() in config and the incoming, plus the
outgoing sip message?

Cheers,
Daniel

--
Daniel-Constantin Mierla
http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
[hidden email]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

If you reply to this email, your message will be added to the discussion below:
http://sip-router.1086192.n5.nabble.com/truncating-sip-message-tp147332p147338.html

To unsubscribe from truncating sip message, click here.
NAML

--

View this message in context: Re: truncating sip message
Sent from the Users mailing list archive at Nabble.com.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
[hidden email]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- 
Daniel-Constantin Mierla
http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
[hidden email]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

If you reply to this email, your message will be added to the discussion below:
http://sip-router.1086192.n5.nabble.com/truncating-sip-message-tp147332p147343.html

To unsubscribe from truncating sip message, click here.
NAML

View this message in context: Re: truncating sip message
Sent from the Users mailing list archive at Nabble.com.