[OpenSIPS-Devel] [ opensips-Feature Requests-3561032 ] configure REGISTER exipres based on protocol from script
SourceForge.net
noreply at sourceforge.net
Fri Aug 24 13:29:14 CEST 2012
Feature Requests item #3561032, was opened at 2012-08-23 08:29
Message generated for change (Comment added) made by bogdan_iancu
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1086413&aid=3561032&group_id=232389
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: None
>Status: Closed
Priority: 5
Private: No
Submitted By: Robert Smith (denodaeus)
>Assigned to: Bogdan-Andrei Iancu (bogdan_iancu)
Summary: configure REGISTER exipres based on protocol from script
Initial Comment:
Greetings list,
We would like to be able to set the REGISTER expires value on a response from opensips (and thus a save() in registrar/usrloc) to be different from a scripting context. A good example of this: we would like the expires value to be different based on protocol, where UDP gets a much shorter value than TCP (NAT, we prefer to keep the UDP value pretty low).
Currently this is only globaly configurable, which is a problem because many clients by default are provisioned for 1 hour or even 1 day times.
Thanks very much!
----------------------------------------------------------------------
>Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2012-08-24 04:29
Message:
Closing as the corresponding patch was uploaded.
----------------------------------------------------------------------
Comment By: Nick Altmann (nikbyte)
Date: 2012-08-23 09:45
Message:
You can use my patch
(https://sourceforge.net/tracker/?func=detail&aid=3556883&group_id=232389&atid=1086412)
this way:
save("e60E60") for 60 seconds.
or interval from 60 to 120 seconds:
save("e60E120")
----------------------------------------------------------------------
Comment By: Robert Smith (denodaeus)
Date: 2012-08-23 08:38
Message:
Seems like there's a patch for this here that hasn't been approved yet:
https://sourceforge.net/tracker/?func=detail&aid=3556883&group_id=232389&atid=1086412
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1086413&aid=3561032&group_id=232389
More information about the Devel
mailing list