Problem with SIP phones being UNREACHEBLE suddenly

We have a couple of installations of FreePbx, 2.9.0.7. We are using Polycom/Kirk phones and all of them is running nearly 100% up, except one.

We suddenly get SIP UNREACHBLE and it seems as the SIP don´t get OK, until we restart the PBX.

It could have been a network problem but we are on a 10Mbit/s fibre between customer site and PBX. We are also using same firewall/nat system as in all other installations.

We get the following in the log:

[2011-10-11 09:03:47] NOTICE[3176] chan_sip.c: Peer ‘105’ is now UNREACHABLE! Last qualify: 0
[2011-10-11 09:03:47] NOTICE[3176] chan_sip.c: Peer ‘106’ is now UNREACHABLE! Last qualify: 0
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 106[ext-local] new state Unavailable for Notify User 111
[2011-10-11 09:03:47] NOTICE[3176] chan_sip.c: Peer ‘107’ is now UNREACHABLE! Last qualify: 0
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 107[ext-local] new state Unavailable for Notify User 111
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 107[ext-local] new state Unavailable for Notify User 103
[2011-10-11 09:03:47] NOTICE[3176] chan_sip.c: Peer ‘204’ is now UNREACHABLE! Last qualify: 0
[2011-10-11 09:03:47] NOTICE[3176] chan_sip.c: Peer ‘203’ is now UNREACHABLE! Last qualify: 0
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 204[ext-local] new state Unavailable for Notify User 304
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 204[ext-local] new state Unavailable for Notify User 101
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 204[ext-local] new state Unavailable for Notify User 108
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 203[ext-local] new state Unavailable for Notify User 111
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 203[ext-local] new state Unavailable for Notify User 104
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 203[ext-local] new state Unavailable for Notify User 103
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 203[ext-local] new state Unavailable for Notify User 108
[2011-10-11 09:03:47] NOTICE[3176] chan_sip.c: Peer ‘201’ is now UNREACHABLE! Last qualify: 0
[2011-10-11 09:03:47] NOTICE[3176] chan_sip.c: Peer ‘208’ is now UNREACHABLE! Last qualify: 0
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 201[ext-local] new state Unavailable for Notify User 101
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 201[ext-local] new state Unavailable for Notify User 104
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 201[ext-local] new state Unavailable for Notify User 103
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 201[ext-local] new state Unavailable for Notify User 111
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 208[ext-local] new state Unavailable for Notify User 101
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 208[ext-local] new state Unavailable for Notify User 104
[2011-10-11 09:03:47] VERBOSE[3013] chan_sip.c: == Extension Changed 208[ext-local] new state Unavailable for Notify User 108

Any idea on how to troubleshoot?

Regards,

Janne

We really need a lot more information to assist you in trouble shooting this problem. What is the network topology? Can you reach any devices at the remote site? From the limited information you have supplied this appears to be a network problem and not a FreePBX issue.

Yes I understand that you need a lot more.

We see no other networking errors, other networking traffic works fine. We see no errors in the firewall. If it only where a network “dip” the handsets should have reregistred again, or? Nothing happens except that all handsets are unavailable, all at the same time. And waiting won’t fix it. The only thing that works is a restart of the PBX.

My question really should be, is someone else is experiencing this? It happens once or twice per/week(now to days in a row). At all other times it is working very well. High quality voice line etc. It looks as follow:
PHONE—FIREWALL–10Mbitfibre—PBX The PBX is located on a public IP address and only one NAT traversal is done. As I say it vorks “most” of the time.

If I start logging more details can that give me more information, I have little knowledge on what logging levels is good for troubleshooting.

Regards,

Janne