[SR-Users] q-value on unsupported clients

[Daniel W. Graham]

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

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