[SR-Users] Kamailio IMS_QOS

[Ivailo Dobrev]

Hi Jose,

AAR is made no the reply. Reply is the place in that both media streams 
in SDP are available and known. Default IMS config should be changed a 
little Rx to start work. This also reminds me that you will probably 
face another problem if your PCRF does not have integration w/ HSS.

P.S.
Good luck w/ PCRF battle. It is a great fun to make it work ;)

Cheers,

Ivo

On 04/22/2016 04:58 PM, José Seabra wrote:
> Hello There,
>
> I'm trying using the ims_qos module with PCRF for QOS, but I'm facing 
> some issues.
>
> 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:
>
>  5(12153) DEBUG: <script>: Diameter: Orig authorizing media via Rx
>  5(12153) DEBUG: ims_qos [mod.c:609]: w_rx_aar(): Looking for route 
> block [ORIG_SESSION_AAR]
>  5(12153) DEBUG: ims_qos [mod.c:621]: w_rx_aar(): Rx AAR called
>  5(12153) DEBUG: ims_qos [mod.c:1345]: create_return_code(): Creating 
> return code of [-2] for aar_return_code
>  5(12153) DEBUG: ims_qos [mod.c:1354]: create_return_code(): created 
> AVP successfully : [aar_return_code]
>  5(12153) DEBUG: ims_qos [mod.c:627]: w_rx_aar(): Can't do AAR for 
> call session in request.
>
> 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:
>
>
>
>
>
> //We don't ever do AAR on request for calling scenario...
>     if (msg->first_line.type != SIP_REPLY) {
>         LM_DBG("Can't do AAR for call session in request\n");
>         return result;
>     }
>
> Anyone can help me understand why it is happening? why it can't 
> proceed if isn't a reply?
>
> Thank you for your support
>
> BR
> -- 
> José Seabra
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20160422/e124feab/attachment.html>