looks like register module does not provide means to override q value given in contact uri when save is done.
any thoughts if it would make sense to add such a capability? save already has optional params, so perhaps the implementation should use an avp to store the q value.
-- juha
Hello,
On 12/12/14 09:45, Juha Heinanen wrote:
looks like register module does not provide means to override q value given in contact uri when save is done.
any thoughts if it would make sense to add such a capability? save already has optional params, so perhaps the implementation should use an avp to store the q value.
It can be added as an inner attribute to xavp_cfg: - http://www.kamailio.org/docs/modules/stable/modules/registrar.html#registrar...
Cheers, Daniel
Daniel-Constantin Mierla writes:
It can be added as an inner attribute to xavp_cfg:
http://www.kamailio.org/docs/modules/stable/modules/registrar.html#registrar...
ok, so you suggest that a new valid inner xavp name 'q' is added?
-- juha
On 12/12/14 10:01, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
It can be added as an inner attribute to xavp_cfg:
http://www.kamailio.org/docs/modules/stable/modules/registrar.html#registrar...
ok, so you suggest that a new valid inner xavp name 'q' is added?
Yes, that xavp is supposed to collect details for processing current register, overwriting some attributes -- for now it does with socket -- if exists, it's taken from there instead from local socket that received the packet.
Cheers, Daniel
Hi, I added an internal function 'set_q_override' to registrar last year to do that. I only needed to access it from another module through the C API, so it doesn't have an exported function yet. It would be simple to add.
Hugh
-----Original Message----- From: sr-dev-bounces@lists.sip-router.org [mailto:sr-dev-bounces@lists.sip-router.org] On Behalf Of Juha Heinanen Sent: 12 December 2014 08:45 To: sr-dev@lists.sip-router.org Subject: [sr-dev] overriding q value
looks like register module does not provide means to override q value given in contact uri when save is done.
any thoughts if it would make sense to add such a capability? save already has optional params, so perhaps the implementation should use an avp to store the q value.
-- juha
_______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev ________________________________ This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.
Ummm ... what I do it's just mangling the contact before calling save, so I could overwrite the q value easly.
We do this for allowing subscribers to register various SIP endpoints that don't allow them to specify the q value ... so we use a trick, and assign the q value based on the last digit of the expire value, that it's the only thing they could modify on their SIP endpoints.
----- Mensaje original ----- De: "Juha Heinanen" jh@tutpro.com Para: sr-dev@lists.sip-router.org Enviados: Viernes, 12 de Diciembre 2014 8:45:22 Asunto: [sr-dev] overriding q value
looks like register module does not provide means to override q value given in contact uri when save is done.
any thoughts if it would make sense to add such a capability? save already has optional params, so perhaps the implementation should use an avp to store the q value.
-- juha
_______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-
Daniel-Constantin Mierla -
Juha Heinanen -
Raúl Alexis Betancor Santana -
Waite, Hugh