There is no way to prevent that a SIP client sends you a request at any
time.
The standard defined behavior for setting REGISTER interval is by
setting the expires header.
Of course you could block which does not use the provided expires
header, but then it may increase load on your support team
I think that can easily become a problem if all the users decide to send
registrations as they please. I tried looking into ratelimit and pike and it
wont solve my problem.
What is the extent of the setting min_expires on this module? Will it create a
423 reply to the user or is not the intende
0
Cflag:: 0
Socket:: udp:192.168.1.194:5060
Methods:: 4767
[root@mia-sbc-registrar1 sbin]# ./kamctl ul show
Date: Fri, 19 Aug 2011 13:04:29 +0200
From: mico...@gmail.com
To: sr-users@lists.sip-router.org
CC: fbo..
Hello,
On 8/18/11 6:20 PM, Fabian Borot wrote:
Hello
This is how my registrar module is configured, hoping that min-expires
set to 30 wont allow registration attempts more often than 30 seconds,
but if I configure a UAC to register every 15 seconds I see that
kamailio allows it. Shouldn't it
Hello
This is how my registrar module is configured, hoping that min-expires set to
30 wont allow registration attempts more often than 30 seconds, but if I
configure a UAC to register every 15 seconds I see that kamailio allows it.
Shouldn't it reply with "422 Session Interval Too Small" or "
