[Spce-user] registration problems after upgrade to 2.6

[Joan Cifre (ibred)]

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.

Jan  3 23:59:14 sipwise /usr/sbin/kamailio[2006]: INFO: <script>: 
Handling RLS notification  - R=sip:voip.ibreddigital.net 
ID=f7a35131-c72a2c49 at 192.168.1.200
Jan  3 23:59:14 sipwise /usr/sbin/kamailio[2006]: ERROR: rls 
[resource_notify.c:572]: to tag value not parsed
Jan  3 23:59:14 sipwise /usr/sbin/kamailio[2006]: INFO: <script>: Failed 
to handle RLS notification - R=sip:voip.ibreddigital.net 
ID=f7a35131-c72a2c49 at 192.168.1.200
Jan  3 23:59:15 sipwise /usr/sbin/kamailio[1998]: INFO: <script>: New 
request - M=NOTIFY R=sip:voip.ibreddigital.net 
F=sip:n918298593 at voip.ibreddigital.net T=sip:voip.ibreddigital.net 
IP=62.82.222.132:5060 (127.0.0.1:5060) 
ID=869a1ae5-e3a0da8f at 192.168.0.252 n  3 23:59:14 sipwise 
/usr/sbin/kamailio[2006]: INFO: <script>: Handling RLS notification  - 
R=sip:voip.ibreddigital.net ID=f7a35131-c72a2c49 at 192.168.1.200
Jan  3 23:59:14 sipwise /usr/sbin/kamailio[2006]: ERROR: rls 
[resource_notify.c:572]: to tag value not parsed
Jan  3 23:59:14 sipwise /usr/sbin/kamailio[2006]: INFO: <script>: Failed 
to handle RLS notification - R=sip:voip.ibreddigital.net 
ID=f7a35131-c72a2c49 at 192.168.1.200
Jan  3 23:59:15 sipwise /usr/sbin/kamailio[1998]: INFO: <script>: 
Handling RLS notification  - R=sip:voip.ibreddigital.net 
ID=869a1ae5-e3a0da8f at 192.168.0.252
Jan  3 23:59:15 sipwise /usr/sbin/kamailio[1998]: ERROR: rls 
[resource_notify.c:572]: to tag value not parsed

El 04/01/2013 2:13, Lorenzo Mangani escribió:
> Joan,
>
> 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
> You mention difficulties with this class of devices. What happens when 
> the ATAs attempts to register after the original registration expired?
> Can you attach a trace displaying an instance for the supposed 
> misbehavior?
>
> Lorenzo Mangani
>
> HOMER DEV TEAM
>
>
> On Fri, Jan 4, 2013 at 1:54 AM, Joan Cifre (ibred) <jcifre at ib-red.com 
> <mailto:jcifre at ib-red.com>> wrote:
>
>     Hello all,
>     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.
>     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.
>     Let me know if you have any ideas about that
>     The ATA model is Cisco SPA112
>     Regards,
>     Joan
>
>     _______________________________________________
>     Spce-user mailing list
>     Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>     http://lists.sipwise.com/listinfo/spce-user
>
>
>
>
> -- 
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130104/dd29941c/attachment-0001.html>