<div dir="ltr">Hi guys, sorry for bothering you with silly questions.<div>I am working on school project and I'd like to process the RTP in Kamailio directly. I have manage to use subst_body() and fix_nated_sdp() to force RTP to be sent to my Kamailio (ip and port of my Kamailio server). I have recompiled Kamailio module topoh to print incomming and outgoing messages but I don't see any RTP messages. I also set sanity_checks to 0 so I can see raw data but no success there.</div>
<div><br></div><div>Can you please point me what module is processing the message first. I hoped that it would be topoh module but clearly I was wrong. I would like to get to this packet as soon as it arieves to Kamailio so I can work with it.</div>
<div><br></div><div>Is this even possible or the core of the Kamailio rejects the message before it is sent to any module? Is there any way to register to the first callback of the core so i can get unfiltered network traffic?</div>
<div><br></div><div>Thanks in advance</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 26, 2014 at 3:18 PM, Alex Balashov <span dir="ltr"><<a href="mailto:abalashov@evaristesys.com" target="_blank">abalashov@evaristesys.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>No. You can't route the RTP and RTCP traffic to Kamailio, by definition. <br>
<br>
You keep asking questions that betray a lack of basic understanding of SIP network elements. I think you should take Olle's suggestion and learn how it works. <br><div><div class="h5">
<br><br><div class="gmail_quote">On 26 March 2014 04:21:08 GMT-04:00, Cock Ootec <<a href="mailto:cockootec@gmail.com" target="_blank">cockootec@gmail.com</a>> wrote:<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">Ok so if I explicitly route all my VoIP traffic (SIP, RTP, RTCP) to Kamailio I can distinguish the streams (parse packets, edit packets) and for example forward these streams to different ports? Thats perfect. Thanks for all your responses they helped much.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 26, 2014 at 8:56 AM, Olle E. Johansson <span dir="ltr"><<a href="mailto:oej@edvina.net" target="_blank">oej@edvina.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><br><div><div><div>On 26 Mar 2014, at 08:44, Cock Ootec <<a href="mailto:cockootec@gmail.com" target="_blank">cockootec@gmail.com</a>> wrote:</div><br><blockquote type="cite">
<div dir="ltr">Thanks for your quick reply. So, Kamailio does nothing with RTP/RTCP packets? I think I understand (now when I think about it) - Kamailio only handles SIP messages by which in nested SDP two endpoints negotiate the stream where media will go through? </div>
</blockquote></div>Yes, that is how the SIP protocol works. Please update yourself on the protocol which Kamailio is built around.</div><div><div><br><blockquote type="cite"><div dir="ltr">So RTP/RTCP media stream flow directly between two UA endpoints and Kamailio has nothing to do with handling of these packets. Could you, please confirm my thoughts?</div>
</blockquote></div>Yes.<div><br><blockquote type="cite"><div dir="ltr"><div>
<br></div><div>All right but what if for example we have special UA that sends to Kamailio specially modified packet (non standard SIP). In my extension of topoh module I have sanity_checks disabled so will Kamailio check this packet before my module and drops it or I can receive, modify and forward this packet? I mean modify this packet to standard SIP packet and forward it to another UA. I am just asking theoretically because in the moment I cant try this.</div>
</div></blockquote></div>You can modify as much as you want.</div><span><font color="#888888"></font><div><font color="#888888"><br></font></div></span><div><span><font color="#888888">/O</font></span><div><br><blockquote type="cite">
<div dir="ltr">
<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 26, 2014 at 7:41 AM, Olle E. Johansson <span dir="ltr"><<a href="mailto:oej@edvina.net" target="_blank">oej@edvina.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div><div>On 26 Mar 2014, at 01:06, Cock Ootec <<a href="mailto:cockootec@gmail.com" target="_blank">cockootec@gmail.com</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr">Hi,<div>I'd like to develop module for Kamailio which will be working with RTP/RTCP packets. Is there any way to capture and edit RTP packet in module of Kamailio for example in module extended from <b>topoh</b>?</div>
<div><br></div></div></blockquote></div><div>Kamailio in itself is a SIP server, often acting as a SIP proxy. The SIP protocol doesn't handle media, it facilitates setup and management of a media session. Adding a module for handling media in Kamailio doesn't really make any sense.</div>
<div><br></div><div>We do have modules that talk to external media servers. Look into those - like rtpproxy. The Kamailio module itself does not handle media, but communicates with the other server that in fact manages media relaying.</div>
<div><br></div><div>Before you modify software, you need to understand the architecture :-)</div><div><br></div><div>/O</div><div><br></div><br><blockquote type="cite"><div><div dir="ltr"><div>In topoh there are two events <span style="color:rgb(51,51,51);font-family:Consolas,'Liberation Mono',Courier,monospace;font-size:12px;line-height:18px;white-space:pre-wrap">SREV_NET_DATA_IN and </span><span style="color:rgb(51,51,51);font-family:Consolas,'Liberation Mono',Courier,monospace;font-size:12px;line-height:18px;white-space:pre-wrap">SREV_NET_DATA_OUT </span>but I didn't be able to capture any RTP packets by them.</div>
<div><br></div><div>Thanks in advance for any help or useful information.</div></div></div>
_______________________________________________<br>sr-dev mailing list<br><a href="mailto:sr-dev@lists.sip-router.org" target="_blank">sr-dev@lists.sip-router.org</a><br><a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
</blockquote></div><br></div><br>_______________________________________________<br>
sr-dev mailing list<br>
<a href="mailto:sr-dev@lists.sip-router.org" target="_blank">sr-dev@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>sr-dev mailing list<br><a href="mailto:sr-dev@lists.sip-router.org" target="_blank">sr-dev@lists.sip-router.org</a><br><a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
</blockquote></div></div><br></div><br>_______________________________________________<br>
sr-dev mailing list<br>
<a href="mailto:sr-dev@lists.sip-router.org" target="_blank">sr-dev@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
<br></blockquote></div><br></div>
<p style="margin-top:2.5em;margin-bottom:1em;border-bottom:1px solid #000"></p><pre><hr><br>sr-dev mailing list<br><a href="mailto:sr-dev@lists.sip-router.org" target="_blank">sr-dev@lists.sip-router.org</a><br><a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
</pre></blockquote></div><br></div></div>
--<br>
Sent from my mobile, and thus lacking in the refinement one might expect from a fully fledged keyboard. <br><div class="">
<br>
Alex Balashov - Principal <br>
Evariste Systems LLC<br>
235 E Ponce de Leon Ave<br>
Suite 106<br>
Decatur, GA 30030<br>
United States<br></div>
Tel: <a href="tel:%2B1-678-954-0671" value="+16789540671" target="_blank">+1-678-954-0671</a><br>
Web: <a href="http://www.evaristesys.com" target="_blank">http://www.evaristesys.com</a>/, <a href="http://www.alexbalashov.com" target="_blank">http://www.alexbalashov.com</a></div><br>_______________________________________________<br>
sr-dev mailing list<br>
<a href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
<br></blockquote></div><br></div>