<div dir="ltr">Hi gents,<div><br></div><div>we do not support the preliminary service information. So for now you can only call Rx_AAR when you have SDP in the replies. So for VoLTE (preconditions), for example you can call on 183 SP whilst using plain SIP you will have to call on the first reply you get that has SDP (either 183SP or 200OK).</div><div><br></div><div>HTH</div><div><br></div><div>Cheers</div><div>Jason </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 22, 2016 at 11:11 PM, Ivailo Dobrev <span dir="ltr"><<a href="mailto:ivailod@telera.eu" target="_blank">ivailod@telera.eu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Yes you send both direction media information to the PCRF but when
reply is received in precondition state.<div><div class="h5"><br>
<br>
<div>On 04/23/2016 12:03 AM, José Seabra
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hello Ivailo and <span style="font-size:12.8px">Franz,</span>
<div><span style="font-size:12.8px"><br>
</span></div>
<div><span style="font-size:12.8px">Thank you for your
clarifications.</span></div>
<div><span style="font-size:12.8px"><br>
</span></div>
<div><span style="font-size:12.8px">Well sending an AAR when
receive a reply makes all sense, but ims_qos must send the
SDP information from the Initial Invite and also from 183
ringing or 200Ok, Am I correct?</span></div>
<div><span style="font-size:12.8px"><br>
</span></div>
<div><span style="font-size:12.8px">Because PCRF needs to know
the session parameters from Initial Initial INVITE and the
reply to it.</span></div>
<div><span style="font-size:12.8px"><br>
</span></div>
<div><span style="font-size:12.8px">The PCRF is
a proprietary solution. </span></div>
<div><span style="font-size:12.8px"><br>
</span></div>
<div><span style="font-size:12.8px">Thank you</span></div>
<div><span style="font-size:12.8px">BR</span></div>
<div><span style="font-size:12.8px">José Seabra</span></div>
<div><span style="font-size:12.8px"><br>
</span></div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2016-04-22 21:54 GMT+01:00 Ivailo
Dobrev <span dir="ltr"><<a href="mailto:ivailod@telera.eu" target="_blank">ivailod@telera.eu</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hi Franz,<br>
<br>
There no real OS PCRF. Yota/Telexir use to had some free
VM image that is OK for test. You can search about
FreePCRF. It is a little tricky to configure it but ... I
made for my tests a really dummy one based on
FreeDIAMETER. Generally speaking PCRF is the "brain" of
the network and you should understand and design things
well there. I have experience also w/ commercial PCRFs and
there is no real answer yes this is a right way of making
something.<br>
<br>
Cheers,<br>
<br>
Ivo
<div>
<div><br>
<br>
On 04/22/2016 11:09 PM, Franz Edler wrote:<br>
</div>
</div>
<blockquote type="cite">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="DE">José,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="DE"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US">in principle it is possible to
send an AAR after receiving the request. In
this case the Service-Info-Status AVP is set
to PRELIMINARY SERVICE INFORMATION.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US">More efficient is it to wait
until SDP answer is received and then the
Service-Info-Status AVP is set to
FINAL_SERVICE_INFORMATION.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US">I don’t know if both methods are
covered in ims_qos module.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US">BTW: which PCRF are you using? Is
there some open source PCRF available?</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US">BR </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US">Franz</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US"></span></p>
<p class="MsoNormal"><a name="m_-4830481951054555584_m_5226943923647200882__MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="EN-US"> </span></a></p>
<span></span>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="DE">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif" lang="DE"> sr-users [<a href="mailto:sr-users-bounces@lists.sip-router.org" target="_blank"></a><a href="mailto:sr-users-bounces@lists.sip-router.org" target="_blank">mailto:sr-users-bounces@lists.sip-router.org</a>]
<b>On Behalf Of </b>José Seabra<br>
<b>Sent:</b> Friday, April 22, 2016 3:58
PM<br>
<b>To:</b> Kamailio (SER) - Users
Mailing List <a href="mailto:sr-users@lists.sip-router.org" target="_blank"><sr-users@lists.sip-router.org></a><br>
<b>Subject:</b> [SR-Users] Kamailio
IMS_QOS</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Hello There,<br>
<br>
I'm trying using the ims_qos module
with PCRF for QOS, but I'm facing some
issues.<br>
<br>
When kamailio receives an initial
invite (originator), it will execute
the function -
"Rx_AAR("ORIG_SESSION_AAR","orig","",-1)",
but the PCRF is not contacted and i
see the following messages:<br>
<br>
5(12153) DEBUG: <script>:
Diameter: Orig authorizing media via
Rx<br>
5(12153) DEBUG: ims_qos [mod.c:609]:
w_rx_aar(): Looking for route block
[ORIG_SESSION_AAR]<br>
5(12153) DEBUG: ims_qos [mod.c:621]:
w_rx_aar(): Rx AAR called<br>
5(12153) DEBUG: ims_qos [mod.c:1345]:
create_return_code(): Creating return
code of [-2] for aar_return_code<br>
5(12153) DEBUG: ims_qos [mod.c:1354]:
create_return_code(): created AVP
successfully : [aar_return_code]<br>
5(12153) DEBUG: ims_qos [mod.c:627]:
w_rx_aar(): Can't do AAR for call
session in request.<br>
<br clear="all">
</p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Why
kamailio says that I Can't do AAR for
call session in request? I have looked
into source code and I found that the
condition that is blocking the
communication with PCRF is:<br>
<br>
<br>
<br>
<br>
<br>
//We don't ever do AAR on request for
calling scenario...<br>
if (msg->first_line.type !=
SIP_REPLY) {<br>
LM_DBG("Can't do AAR for call
session in request\n");<br>
return result;<br>
}</p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Anyone can
help me understand why it is happening?
why it can't proceed if isn't a reply?</p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Thank you for
your support</p>
<div>
<p class="MsoNormal">BR</p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">-- </p>
<div>
<div>
<p class="MsoNormal">José Seabra</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<span>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<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>
</pre>
</span></blockquote>
<br>
</div>
<br>
_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" 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>Cumprimentos
<div>José Seabra</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<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>
</pre>
</blockquote>
<br>
</div></div></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" rel="noreferrer" 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 class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><table style="width:450pt" cellpadding="0" cellspacing="0" border="0" width="600"><tbody><tr><td style="padding:0cm" valign="top"><p></p></td></tr></tbody></table><table style="font-family:monospace" cellpadding="0" cellspacing="0" border="0" width="320px"><tbody><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><b>Jason Penton</b></td></tr><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><b>Senior Manager: Applications and Services</b></td></tr><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:15px;padding-top:10px"><b>Smile Communications Pty (Ltd)</b></td></tr><tr><td><table cellpadding="0" cellspacing="0" width="100%"><tbody><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:15px;padding-top:10px" width="27%"><b>Voice:<br><br>Mobile:</b></td><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:10px;padding-top:10px" width="73%"><span>+234 (0) 702 000 000 7</span><br><br>+27 (0) 83 283 7000</td></tr><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:15px;padding-top:10px"><b>Skype:</b></td><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(134,145,154);line-height:18px;padding-left:10px;padding-top:10px">jason.barry.penton</td></tr></tbody></table></td></tr><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><a href="mailto:name.surname@smilecoms.com" style="font-family:Arial;color:rgb(117,179,67);text-decoration:none" target="_blank">jason.penton@smilecoms.com</a></td></tr><tr><td style="font-family:Arial,sans-serif;font-size:16px;color:rgb(117,179,67);line-height:18px;padding-left:15px;padding-top:10px"><a href="http://www.smilecoms.com/" style="font-family:Arial;color:rgb(117,179,67)" target="_blank">www.smilecoms.com</a><br><img src="http://196.33.227.129/~smlcoms/sigs/pty/images/smile_signature_07_09.jpg" height="144" width="420"><br></td></tr></tbody></table></div><br></div></div></div></div></div></div>
</div>
<br>
<span><font color="#888888"><pre>This email is subject to the disclaimer of Smile Communications at <a href="http://www.smilecoms.com/home/email-disclaimer/" target="_blank">http://www.smilecoms.com/home/<WBR>email-disclaimer/</a><a href="http://www.smilecoms.com/disclaimer" target="_blank"></a></pre></font></span>