Extension loses registration on a daily basis

UPDATE

Checking on system log on a daily basis, I could realize one of my extensions stops registering every day (usually circa 18:00h) and starts registering again in the following day at 02:00 am (all times considering America/Sao Paulo timezone, on www4).

Is there any server or configuration reset taking place at this time?

Any help is appreciated.

===========================================

Hello,

I am having some issues with one of my extensions. Sometimes, in the middle of the day, it refuses to re-register. It is apparently working, but calls cannot be completed - inbound or outbound.

Checking on the system log, I found the following message:

VERBOSE[115047] logger.c: -- Got SIP response 482 "Loop Detected"

I don't know what could have caused it. All of my extensions are in separate offices (one per office), all of them are working fine - except for this one.

Any ideas?

Thanks

Update: the Loop Detected message is not actually affecting any functionality, as far as I know. Despite this message, calls are completed normally.

This post has been edited 1 time(s), it was last edited by cac on 03.05.2011 at 01:28.

RE: SIP response 482 "Loop Detected"

If this is an ongoing issue, I would try connecting that SIP UA via another broadband connection, to verify whether you get the "482 Loop Detected" message.

RE: SIP response 482 "Loop Detected"

Hello Diafora,

as I wrote on the update, the Loop Detected happens in 3 extensions, each of them in a separate location. They have, though, the same ISP, what may be causing the message. However, I realized it is not affecting my service.

The real problem, as I later verified, is that one extension (ext. 102) stops registering during the day and becomes unavailable for all calls, inbound, outbound or internal.

At 2 am (everyday) it starts registering again. Magically. Or else, if the phone is cold booted (pull the power plug) it also goes back to work.

The ISP committed to make some investigation, but I have no idea where the real problem is. I'll try to change the IP phone as well, to be sure it is not some device bug.

Thanks for your help!

RE: SIP response 482 "Loop Detected"

Well I am not sure at all, what the issue is with the extension that stops registering at a certain time interval every day. But I will ask a few questions trying to narrow it down:

• Behind what kind of router is this SIP UA connecting to the Internet?
• What kind of SIP User Agent is this extension using? (i.e. IP-phone, ATA, soft-phone)
• What other network elements are connecting to the Internet via the same broadband connection? (PCs, NAS, IPTV STBs, SIP UAs)

The sure-fire way to troubleshoot this, is to disconnect everything else from the LAN and verify whether the SIP UA looses its' registration at the specified time. If it does, then you should connect it via a hub, along with a single PC to capture a packet trace.

Let me know if that is feasible.

RE: SIP response 482 "Loop Detected"

The current topology is:

Internet
ISP Firewall/NAT
our Internet link
Linksys 524 wifi router
computer 1|| computer 2 || IP cameras || IP Phone

All devices are wired to the router. IP cameras connect to the computer 2, which also has an always-active LogMeIn account (for remote control).

Computer 1 is only used for registering sales.
The IP Phone (Intelbras TIP 100) is connected to the router.
There are no ATAs or softphones in this network.

We are behind 2 NAT, the ISP's and ours. However, STUN is dealing fine with them.

We'll shut them all down during the weekend to test.

Thank you again.

RE: SIP response 482 "Loop Detected"

Do yourself a favor and place the IP-phone on the DMZ of the Linksys so it can avoid one NAT. Let me know if the issue persists.

RE: SIP response 482 "Loop Detected"

Before opening this thread I have made a few tests, including different stun servers and placing the phone at the DMZ.

Since the last post, the service has become more stable - what made troubleshooting even worse. It used to go down every day around a certain time and go up precisely 02:00am. Since May 6th, I have noticed only these flaws:

May 7 17:59:14 (last registration of the day)
May 8 02:01:46 (first registration of the day)

May 11 02:05:13 (this was a completely atypical day)
May 11 07:46:41

May 11 18:57:03
May 12 02:02:43

May 13 19:20:15
May 14 02:01:07

These were the only interruptions from May 6 to May 15. As they appear in random days, I couldn't isolate a root cause - be it the IP cameras, the desktop monitoring application or the ISP. Taking a shot at the SIP now, waiting for them to reply my trouble ticket.

Any updates will be shared with you.

Regards