From: sr-users [mailto:sr-users-bounces@lists.sip-router.org]
On Behalf Of Daniel-Constantin Mierla
Sent: Wednesday, November 4, 2015 3:36 AM
To: Kamailio (SER) - Users Mailing List <sr-users@lists.sip-router.org>
Subject: Re: [SR-Users] q-value on unsupported clients
Hello,
do you want to add q value to Contact header on incoming REGISTER requests?
Cheers,
Daniel
On 04/11/15 08:06, Daniel W. Graham wrote:
I have a need to use q-value for serial forking but my clients don’t support it. I need to specify unique q-value on all ports on the client device.
I explored using the User-Agent header and appending q-value, but this wouldn’t help on multi-port clients.
Some things I have been thinking about are ‘abusing’ the authorization user or from user to somehow append q-value but this opens the door to other issues, and a database trigger however there would be no way to match this up to a record in another table as the usernames would be the same.
Any thoughts/ideas or methods others have used in situations like this?
-Dan
_______________________________________________SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced Training, Nov 30-Dec 2, Berlin - http://asipto.com/kat