Thanks!
-Original Message-
From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of
Daniel Tryba
Sent: Thursday, November 5, 2015 4:16 AM
To: sr-users@lists.sip-router.org
Subject: Re: [SR-Users] q-value on unsupported clients
> Based on the xlog output,
t: Re: [SR-Users] q-value on unsupported clients
> On 05 Nov 2015, at 10:15, Daniel Tryba wrote:
>
>> Based on the xlog output, the following doesn't appear to be working
>> - remove_hf("Contact");
>> append_hf("Contact: $var(newct)\r\n");
>>
> On 05 Nov 2015, at 10:15, Daniel Tryba wrote:
>
>> Based on the xlog output, the following doesn't appear to be working -
>> remove_hf("Contact");
>> append_hf("Contact: $var(newct)\r\n");
>>
>> I've actually had a similar issue before replacing a hdr so I'm wondering if
>> I'm doing somethin
> Based on the xlog output, the following doesn't appear to be working -
> remove_hf("Contact");
> append_hf("Contact: $var(newct)\r\n");
>
> I've actually had a similar issue before replacing a hdr so I'm wondering if
> I'm doing something wrong?
Header manipulation is doesn't update the already
November 4, 2015 11:04 AM
To: mico...@gmail.com; Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] q-value on unsupported clients
Yes
[dan-signature]
From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of
Daniel-Constantin Mierla
Sent: Wednesday, November 4, 2015 3
Yes
[dan-signature]
From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of
Daniel-Constantin Mierla
Sent: Wednesday, November 4, 2015 3:36 AM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] q-value on unsupported clients
Hello,
do you want to add q value
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 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
