<div dir="ltr"><div>There are two standards based options for MSRP. Peer-to-peer between clients (RFC 4975) with no servers involved and traffic between clients relayed through a server (RFC 4976). RFC 4976 is used for NAT traversal and policy (security/logging/etc) enforcement. The relay option requires the MSRP client to support additional MSRP request types, procedures, and SDP elements - essentially use of a relay requires the client to support this and be configured for it.</div>
<div><br></div><div>There is a third option which is not standards based, that is B2BUA'ing MSRP where a server pretends to be a pair of clients back-to-back. This is what a lot of SBCs do.<br></div><div><br></div><div>
As a server that is not a B2BUA Kamailio supports MSRP relay as per RFC 4976. However, your MSRP client needs to support RFC 4976 (and be correctly configured) to make use of the relay.</div><div><br></div><div>Regards,</div>
<div><br></div><div>Peter</div><div><div><br></div><div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 29 July 2013 11:20, Rajkumar Kanniappan <span dir="ltr"><<a href="mailto:rajkumar.kanniappan@sasken.com" target="_blank">rajkumar.kanniappan@sasken.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal">Hi,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Is it possible to make MSRP to pass through kamailio instead of peer to peer?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">For me, my sip client registers with kamailio without any problem and able to chat with other sip client as well.
<u></u><u></u></p>
<p class="MsoNormal">But the chat communication using MSRP is always peer to peer, because of the SDP negotiation. But I need make the msrp messages to pass through the kamailio server.<u></u><u></u></p>
<p class="MsoNormal">Please help me in configuring the kamailio.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks<u></u><u></u></p>
</div>
<br>
<hr>
<font face="Arial" color="Black">SASKEN BUSINESS DISCLAIMER: This message may contain confidential, proprietary or legally privileged information. In case you are not the original intended Recipient of the message, you must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message and you are requested to delete it and inform the sender. Any views expressed in this message are those of the individual sender unless otherwise stated. Nothing contained in this message shall
be construed as an offer or acceptance of any offer by Sasken Communication Technologies Limited ("Sasken") unless sent with that express intent and with due authority of Sasken. Sasken has taken enough precautions to prevent the spread of viruses. However
the company accepts no liability for any damage caused by any virus transmitted by this email.<br>
Read Disclaimer at <a href="http://www.sasken.com/extras/mail_disclaimer.html" target="_blank">http://www.sasken.com/extras/mail_disclaimer.html</a><br>
</font>
</div>
<br>_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div><font face="courier new, monospace">Peter Dunkley</font></div><div><font face="courier new, monospace">Technical Director</font></div><div>
<font face="courier new, monospace">Crocodile RCS Ltd</font></div></div>
</div>