[Serusers] Changing 'expires' value in response to REGISTER
Kanakatti Mahesh Subramanya
mahesh at aptela.com
Fri Aug 5 00:35:59 CEST 2005
This works successfully with the Snoms.
However, it also successfully breaks Sipuras (of which we have quite a
few too)
And, rfc3261 never actually sez. that teh UAC must accept the value I
send back (weird...)
Any other ideas??
cheers
Andres wrote:
> Kanakatti Mahesh Subramanya wrote:
>
>> And the beat goes on...
>>
>> I 've got a bunch of Snom's that have a minimum register interval of
>> 1 minute.
>>
>> I *know* that I can get them to register every 30 seconds if I set
>> the 'expires' value in the Contact header of the '200 OK' response to
>> the REGISTER request appropriately (whew)
>> e.g., instead of returning
>> Contact: <sip:jake.foobaz at 1.2.3.4:49154>;expires=60
>> I return
>> Contact: <sip:jake.foobaz at 1.2.3.4:49154>;expires=30
>>
>> The question is - how do I change the 'expires' value?
>
>
> How about using a global parameter like:
>
> 1.3.3. max_expires (integer)
>
> The maximum expires value of a Contact, values higher than
> this maximum will be automatically set to the maximum. Value 0
> disables the checking.
>
> Default value is 0.
>
> Example 1-3. Set max_expires parameter
> ...
> modparam("registrar", "max_expires", 120)
>
>
>>
>> append_to_reply() isn't relevant - i don't want another header
>> subst() on the request's 'Expires' header isn't useful since
>> build_contact() seems to extract it's values from the original
>> request. Any changes I made to it seem to be ignored
>>
>> Any ideas?
>>
>> cheers
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Serusers mailing list
>> serusers at lists.iptel.org
>> http://lists.iptel.org/mailman/listinfo/serusers
>>
>>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mahesh.vcf
Type: text/x-vcard
Size: 332 bytes
Desc: not available
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20050804/5e8b3e04/attachment.vcf>
More information about the sr-users
mailing list