<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I don't know if this can help, but I'm getting many messages about
RLS notification failures in the log, like this. Maybe it's not
important, really I don't know, but I don't remember I was getting
these messages before upgrade.<br>
<br>
Jan 3 23:59:14 sipwise /usr/sbin/kamailio[2006]: INFO:
<script>: Handling RLS notification -
R=<a class="moz-txt-link-freetext" href="sip:voip.ibreddigital.net">sip:voip.ibreddigital.net</a> <a class="moz-txt-link-abbreviated" href="mailto:ID=f7a35131-c72a2c49@192.168.1.200">ID=f7a35131-c72a2c49@192.168.1.200</a><br>
Jan 3 23:59:14 sipwise /usr/sbin/kamailio[2006]: ERROR: rls
[resource_notify.c:572]: to tag value not parsed<br>
Jan 3 23:59:14 sipwise /usr/sbin/kamailio[2006]: INFO:
<script>: Failed to handle RLS notification -
R=<a class="moz-txt-link-freetext" href="sip:voip.ibreddigital.net">sip:voip.ibreddigital.net</a> <a class="moz-txt-link-abbreviated" href="mailto:ID=f7a35131-c72a2c49@192.168.1.200">ID=f7a35131-c72a2c49@192.168.1.200</a><br>
Jan 3 23:59:15 sipwise /usr/sbin/kamailio[1998]: INFO:
<script>: New request - M=NOTIFY R=<a class="moz-txt-link-freetext" href="sip:voip.ibreddigital.net">sip:voip.ibreddigital.net</a>
F=<a class="moz-txt-link-freetext" href="sip:n918298593@voip.ibreddigital.net">sip:n918298593@voip.ibreddigital.net</a> T=<a class="moz-txt-link-freetext" href="sip:voip.ibreddigital.net">sip:voip.ibreddigital.net</a>
IP=62.82.222.132:5060 (127.0.0.1:5060)
<a class="moz-txt-link-abbreviated" href="mailto:ID=869a1ae5-e3a0da8f@192.168.0.252">ID=869a1ae5-e3a0da8f@192.168.0.252</a> n 3 23:59:14 sipwise
/usr/sbin/kamailio[2006]: INFO: <script>: Handling RLS
notification - R=<a class="moz-txt-link-freetext" href="sip:voip.ibreddigital.net">sip:voip.ibreddigital.net</a>
<a class="moz-txt-link-abbreviated" href="mailto:ID=f7a35131-c72a2c49@192.168.1.200">ID=f7a35131-c72a2c49@192.168.1.200</a><br>
Jan 3 23:59:14 sipwise /usr/sbin/kamailio[2006]: ERROR: rls
[resource_notify.c:572]: to tag value not parsed<br>
Jan 3 23:59:14 sipwise /usr/sbin/kamailio[2006]: INFO:
<script>: Failed to handle RLS notification -
R=<a class="moz-txt-link-freetext" href="sip:voip.ibreddigital.net">sip:voip.ibreddigital.net</a> <a class="moz-txt-link-abbreviated" href="mailto:ID=f7a35131-c72a2c49@192.168.1.200">ID=f7a35131-c72a2c49@192.168.1.200</a><br>
Jan 3 23:59:15 sipwise /usr/sbin/kamailio[1998]: INFO:
<script>: Handling RLS notification -
R=<a class="moz-txt-link-freetext" href="sip:voip.ibreddigital.net">sip:voip.ibreddigital.net</a> <a class="moz-txt-link-abbreviated" href="mailto:ID=869a1ae5-e3a0da8f@192.168.0.252">ID=869a1ae5-e3a0da8f@192.168.0.252</a><br>
Jan 3 23:59:15 sipwise /usr/sbin/kamailio[1998]: ERROR: rls
[resource_notify.c:572]: to tag value not parsed<br>
<br>
<div class="moz-cite-prefix">El 04/01/2013 2:13, Lorenzo Mangani
escribió:<br>
</div>
<blockquote
cite="mid:CAKN+pHZWcm_+j7DyB3R=3trAF3TgcoZLM0GNag__qU1vyprbCg@mail.gmail.com"
type="cite">Joan,
<div><br>
</div>
<div>The screenshot is suggestive but it tells very little about
your issue. I have a few of those same devices active on my
network and have not noticed anything odd on either SPCE 2.6/2.7</div>
<div>You mention difficulties with this class of devices. What
happens when the ATAs attempts to register after the original
registration expired? </div>
<div>Can you attach a trace displaying an instance for the
supposed misbehavior?</div>
<div><br>
<div
style="color:rgb(119,119,119);font-size:13.200000762939453px;font-family:Arial"><font>Lorenzo
Mangani</font></div>
<div
style="color:rgb(119,119,119);font-size:13.200000762939453px;font-family:Arial"><font>
<div style="font-size:x-small"><br>
</div>
<div style="font-size:x-small">HOMER DEV TEAM</div>
</font></div>
<div
style="color:rgb(119,119,119);font-size:x-small;font-family:Arial"><br>
</div>
<div><font size="1"><br>
</font></div>
<div class="gmail_quote">On Fri, Jan 4, 2013 at 1:54 AM, Joan
Cifre (ibred) <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jcifre@ib-red.com" target="_blank">jcifre@ib-red.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hello all,<br>
we upgrade the server from 2.5 to 2.6 two weeks ago. We've
notes problems with the registration after upgrade,
specially with one ATA model. After many tests, I think the
problem is that after registration expiration (configured to
3600 seconds in the ATA) is very dificult for that phone to
re-register. It fails the registration process many times.
Before the upgrade there were no problems.<br>
As you can see in the registered users graph attached, there
is a very important difference before and after
registration. We have changed the NAT managing of the system
(first managed by routers, now by sip server) and the
problem still remains.<br>
Let me know if you have any ideas about that<br>
The ATA model is Cisco SPA112<br>
Regards,<br>
Joan<br>
<br>
_______________________________________________<br>
Spce-user mailing list<br>
<a moz-do-not-send="true"
href="mailto:Spce-user@lists.sipwise.com" target="_blank">Spce-user@lists.sipwise.com</a><br>
<a moz-do-not-send="true"
href="http://lists.sipwise.com/listinfo/spce-user"
target="_blank">http://lists.sipwise.com/listinfo/spce-user</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<span style="font-size:13px;font-family:arial,sans-serif"><span
style="font-family:Arial">
<div style="color:rgb(119,119,119)">
<font><span
style="font-family:Arial;color:rgb(119,119,119)"><br>
</span></font></div>
<div style="color:rgb(119,119,119)"><font><span
style="font-family:Arial;color:rgb(119,119,119)"><br>
</span></font></div>
<div style="color:rgb(119,119,119)">
<br>
</div>
</span></span>
</div>
</blockquote>
<br>
</body>
</html>