<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
Hello,<br><br>Thank you for your reply. Can you please elaborate more on
this patch? In my case, the caller won't process any authentication
info, OpenSIPS will handle all of this on his behalf. What I'm actually
seeking is a function similar to "Surrogate registration".<br><br>Thanks,<br>Marwan<br><br><div><div id="SkyDrivePlaceholder"></div><hr id="stopSpelling">From: marwan_sadek@hotmail.com<br>To: users@lists.opensips.org<br>Subject: B2B/Proxy Authentication<br>Date: Wed, 23 May 2012 15:27:13 +0300<br><br>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<style><!--
.ExternalClass .ecxhmmessage P
{padding:0px;}
.ExternalClass body.ecxhmmessage
{font-size:10pt;font-family:Tahoma;}
--></style>
<div dir="ltr">Hello,<br><br>I'm trying to implement the following scenario (Attached REGISTER.TXT) using OpenSIPS. The UA needs to register with the core IMS and wait for a 200OK, it cannot respond to the 401 sent from the server. Therefore, I want to put OpenSIPS in the middle to handle the authentication part with the core IMS and once this is done, it will respond back to the UA. What is the best approach to do this? knowing that OpenSIPS needs to :<br><br>1) Add some P-Headers to the original REGISTER sent by UA.<br>2) Relay back to the UA some P-Headers received in the 200OK of the IMS server.<br>3) Further messages can be sent from UA to IMS and vice versa for the same dialog, e.g starting some services, etc.<br><br>Should OpenSIPS be configured as a B2B? Proxy? or a combination of the two?<br><br>Thank you in advance for your answers.<br><br><font color="#333399" face="Courier New, Courier, Monospace" size="3"></font></div>
</div>
</div>
</div></div> </div></body>
</html>