Freeswitch send 423 (Interval Too Brief)
Hi all, is there a way to make freeswitch send a 423 (Interval Too Brief) during a SIP REGISTER request? I want to prevent clients to (re)register with a low expire-time and thus spam our network. The "sip-force-expires"-variable would work but don't seem to be SIP-compliant to me.
From RFC 3261:
10.3 Processing REGISTER Requests When receiving a REGISTER request, a registrar follows these steps: (...) 7. The registrar now processes each contact address in the Contact header field in turn. For each address, it determines the expiration interval as follows: - If the field value has an "expires" parameter, that value MUST be taken as the requested expiration. - If there is no such parameter, but the request has an Expires header field, that value MUST be taken as the requested expiration. - If there is neither, a locally-configured default value MUST be taken as the requested expiration. The registrar MAY choose an expiration less than the requested expiration interval. If and only if the requested expiration interval is greater than zero AND smaller than one hour AND less than a registrar-configured minimum, the registrar MAY reject the registration with a response of 423 (Interval Too Brief). This response MUST contain a Min-Expires header field that states the minimum expiration interval the registrar is willing to honor. It then skips the remaining steps. Thanks in Advance, Adam
On Tue, Jun 5, 2012 at 8:51 AM, Lappe, Adam <Adam.Lappe@qsc.de> wrote:
is there a way to make freeswitch send a 423 (Interval Too Brief) during a SIP REGISTER request?
I want to prevent clients to (re)register with a low expire-time and thus spam our network.
Have you greped the code for it? Seems like it's be easy to spot. If not, open a ticket. Or, better yet, submit a patch :)
The “sip-force-expires”-variable would work but don’t seem to be SIP-compliant to me.
Have you followed the SIP traces to see exactly how this works? I haven't, but perhaps it really does work how you'd hope (I don't know, I've never used it). Best, Gabe
This means the invite contains a session timer that is lower than the allow minimum per the RFC, it's asterisk? if so it just might be sending -1 as the min se. Sent from my iPad On Jun 8, 2012, at 9:15 PM, Gabriel Gunderson <gabe@gundy.org> wrote:
On Tue, Jun 5, 2012 at 8:51 AM, Lappe, Adam <Adam.Lappe@qsc.de> wrote:
is there a way to make freeswitch send a 423 (Interval Too Brief) during a SIP REGISTER request?
I want to prevent clients to (re)register with a low expire-time and thus spam our network.
Have you greped the code for it? Seems like it's be easy to spot. If not, open a ticket. Or, better yet, submit a patch :)
The �gsip-force-expires�h-variable would work but don�ft seem to be SIP-compliant to me.
Have you followed the SIP traces to see exactly how this works? I haven't, but perhaps it really does work how you'd hope (I don't know, I've never used it).
Best, Gabe
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
Join Us At ClueCon - Aug 7-9, 2012
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (3)
-
Brian West
-
Gabriel Gunderson
-
Lappe, Adam