<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello all,<br>
I think it's SOLVED! You can see attached the graph of registered
devices in the last minutes, how it grows.<br>
Now I've disabled the banning in the server and we will disable the
keep alive message in the ATAs.<br>
One question, was the banning process changed from 2.5 to 2.6? In
2.5 users were not banned!<br>
<br>
Thanks to all specially Lorenzo and Jon for the great support<br>
Joan<br>
<br>
<br>
<div class="moz-cite-prefix">El 05/01/2013 10:30, Jon Bonilla
(Manwe) escribió:<br>
</div>
<blockquote cite="mid:20130105103042.389c51e8@quenya" type="cite">
<pre wrap="">El Sat, 5 Jan 2013 10:21:17 +0100
Lorenzo Mangani <a class="moz-txt-link-rfc2396E" href="mailto:lorenzo.mangani@gmail.com"><lorenzo.mangani@gmail.com></a> escribió:
</pre>
<blockquote type="cite">
<pre wrap="">Joan,
If this is the case as Jon seems to also suggest and the ban is caused by
the NOTIFY messages getting rejected, try to switch off you ATA
"keep-alive" behavior or alternatively, change it from $NOTIFY to $REGISTER
and it should have better luck,
</pre>
</blockquote>
<pre wrap="">
Disabling the keepalive could also be a good idea. No need to send NOTIFY or
REGISTER as the spce takes care of sending keepalives every 30 seconds to all
nated registered devices.
This interval can be changed in config.yml:
kamailio_proxy_natping_interval
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Spce-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>
<a class="moz-txt-link-freetext" href="http://lists.sipwise.com/listinfo/spce-user">http://lists.sipwise.com/listinfo/spce-user</a>
</pre>
</blockquote>
<br>
</body>
</html>