Re: [SR-Users] Diameter AVP handling from kamaiio.cfg

Thank you very much. I opened a feature request: https://github.com/kamailio/kamailio/issues/922 If I will have time, I might try to implement such kind of functionality :) *Cheers,* *Zoltan* On 9 January 2017 at 09:50, Carsten Bock wrote: > Hi Zoltan, > > i've added

Re: [SR-Users] Diameter AVP handling from kamaiio.cfg

Hi Zoltan, that's not a bug, it's a feature request. The value is not available, since you're the first one asking for it. Can you put a Feature-Request on our Tracker (https://github.com/kamailio/kamailio/issues)? We added it to the ims_charging module, because we explicitly needed this

Re: [SR-Users] Diameter AVP handling from kamaiio.cfg

Hi Carsten, Thank you very much for your response! Sadly for the UAR, LIR, SAR are not providing these kind of error codes. As you can see only -1 coming back and not Jan 4 06:17:15 localhost journal: de.fhg.fokus.hss.cx.CxExperimentalResultException: IMS_Diameter_Error_User_Unknown Jan 4

Re: [SR-Users] Diameter AVP handling from kamaiio.cfg

Hi Zoltan, i've added something like this for the IMS-Charging Module in order to retrieve the "full" Charging Response: case -1: #failure xlog("L_ERR", "CCR failure - error response sent from module\n"); switch ($avp(s:cca_result_code)){ case 5030: send_reply("403",

[SR-Users] Diameter AVP handling from kamaiio.cfg

Dear All, I'm wondering is it possible to catch Diameter Messages and their AVP values from kamailio.cfg just like for SIP messages? (Using pseudo variables) I looked into this function from the attached S-CSCF example. route[REG_MAR_REPLY] { #this is async so to know status we have to check