[SR-Users] Kamailio IMS_QOS

[Franz Edler]

Hi José,

 

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.

More efficient is it to wait until SDP answer is received and then the Service-Info-Status AVP is set to FINAL_SERVICE_INFORMATION.

 

I don’t know if both methods are covered in ims_qos module.

 

BTW: which PCRF are you using? Is there some open source PCRF available?

 

BR 

Franz

 

From: sr-users [mailto:sr-users-bounces at lists.sip-router.org] On Behalf Of José Seabra
Sent: Friday, April 22, 2016 3:58 PM
To: Kamailio (SER) - Users Mailing List <sr-users at lists.sip-router.org>
Subject: [SR-Users] Kamailio IMS_QOS

 

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

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