Hello, I am using ims qos module to send Rx_AAR for dedicated bearer via Diameter RX interface. Kamailio PCSCF is configured with #!define WITH_RX_CALL. It is working as expected but I have an issue with the release of the bearer after the call is disconnected. There is no function available to release the bearer. As I saw the only way to do this is via the rx_auth_expiry which is static:
modparam("ims_qos", "rx_auth_expiry", 120)
Is this something that is planned to be developed in the future or there is something I am missing?
Thanks in advance! Regards, Pavel
Hi Pavel,
you find all open feature request in our github tracker, so you can have a look there to see if somebody else already got the same idea.
If you need that functionality, you could also have a look to the code, extend the module and create a pull request.
Cheers,
Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.comhttps://gilawa.com/
From: sr-dev sr-dev-bounces@lists.kamailio.org On Behalf Of Pafel Sent: Wednesday, February 12, 2020 1:15 PM To: sr-dev@lists.kamailio.org Subject: [sr-dev] ims_qos module - dedicated bearer release after call end
Hello, I am using ims qos module to send Rx_AAR for dedicated bearer via Diameter RX interface. Kamailio PCSCF is configured with #!define WITH_RX_CALL. It is working as expected but I have an issue with the release of the bearer after the call is disconnected. There is no function available to release the bearer. As I saw the only way to do this is via the rx_auth_expiry which is static:
modparam("ims_qos", "rx_auth_expiry", 120)
Is this something that is planned to be developed in the future or there is something I am missing?
Thanks in advance! Regards, Pavel
Hi Henning,
Looking at the code last week we found that bearer release (RX STR) is present functionality but you must have enabled dialog in pcscf : #!define FLT_DIALOG 2
I think there is not enough information in module documentation. What is the way to contribute to the documentation?
Cheers, Pavel
На пн, 17.02.2020 г. в 15:57 Henning Westerholt hw@skalatan.de написа:
Hi Pavel,
you find all open feature request in our github tracker, so you can have a look there to see if somebody else already got the same idea.
If you need that functionality, you could also have a look to the code, extend the module and create a pull request.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
*From:* sr-dev sr-dev-bounces@lists.kamailio.org *On Behalf Of *Pafel *Sent:* Wednesday, February 12, 2020 1:15 PM *To:* sr-dev@lists.kamailio.org *Subject:* [sr-dev] ims_qos module - dedicated bearer release after call end
Hello, I am using ims qos module to send Rx_AAR for dedicated bearer via Diameter RX interface. Kamailio PCSCF is configured with #!define WITH_RX_CALL. It is working as expected but I have an issue with the release of the bearer after the call is disconnected. There is no function available to release the bearer. As I saw the only way to do this is via the rx_auth_expiry which is static:
modparam("ims_qos", "rx_auth_expiry", 120)
Is this something that is planned to be developed in the future or there is something I am missing?
Thanks in advance! Regards, Pavel
Hello Pafel,
just create a pull request in github if you want to contribute a change to docs or code. You find our contributing guide here: https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
If you haven’t worked with github much before, have a look to their comprehensive documentation.
Somebody from the developer team will then review and integrate it to the git master branch, docs extensions and bugfixes also to the stable release branches.
Cheers,
Henning
-- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.comhttps://gilawa.com/
From: Pafel pafels@gmail.com Sent: Thursday, February 20, 2020 3:59 PM To: Henning Westerholt hw@skalatan.de Cc: Kamailio (SER) - Development Mailing List sr-dev@lists.kamailio.org Subject: Re: [sr-dev] ims_qos module - dedicated bearer release after call end
Hi Henning,
Looking at the code last week we found that bearer release (RX STR) is present functionality but you must have enabled dialog in pcscf : #!define FLT_DIALOG 2
I think there is not enough information in module documentation. What is the way to contribute to the documentation?
Cheers, Pavel
На пн, 17.02.2020 г. в 15:57 Henning Westerholt <hw@skalatan.demailto:hw@skalatan.de> написа: Hi Pavel,
you find all open feature request in our github tracker, so you can have a look there to see if somebody else already got the same idea.
If you need that functionality, you could also have a look to the code, extend the module and create a pull request.
Cheers,
Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.comhttps://gilawa.com/
From: sr-dev <sr-dev-bounces@lists.kamailio.orgmailto:sr-dev-bounces@lists.kamailio.org> On Behalf Of Pafel Sent: Wednesday, February 12, 2020 1:15 PM To: sr-dev@lists.kamailio.orgmailto:sr-dev@lists.kamailio.org Subject: [sr-dev] ims_qos module - dedicated bearer release after call end
Hello, I am using ims qos module to send Rx_AAR for dedicated bearer via Diameter RX interface. Kamailio PCSCF is configured with #!define WITH_RX_CALL. It is working as expected but I have an issue with the release of the bearer after the call is disconnected. There is no function available to release the bearer. As I saw the only way to do this is via the rx_auth_expiry which is static:
modparam("ims_qos", "rx_auth_expiry", 120)
Is this something that is planned to be developed in the future or there is something I am missing?
Thanks in advance! Regards, Pavel