On 8/25/06, Ferguson, Michael <[EMAIL PROTECTED]> wrote:
G'Day All, I am trying to figure out and correct some of the issues showing up in the messages log but, I am still a newbie and thus, somewhat at a loss, so here goes: NUMBER 1 -- This appears continuously in the log REACHABLE and the UNREACHABLE: Aug 25 15:24:18 NOTICE[1867]: Peer '5103' is now REACHABLE! (418ms / 1000ms) Aug 25 15:24:21 NOTICE[1867]: Peer '5107' is now REACHABLE! (448ms / 1000ms) Aug 25 15:24:23 NOTICE[1867]: Peer '5108' is now REACHABLE! (445ms / 1000ms) Aug 25 15:25:22 NOTICE[1867]: Peer '5103' is now UNREACHABLE! Last qualify: 418 Aug 25 15:25:25 NOTICE[1867]: Peer '5107' is now UNREACHABLE! Last qualify: 448 Aug 25 15:25:27 NOTICE[1867]: Peer '5108' is now UNREACHABLE! Last qualify: 445 Aug 25 15:26:14 NOTICE[1867]: Peer '5103' is now REACHABLE! (448ms / 1000ms) Aug 25 15:26:17 NOTICE[1867]: Peer '5107' is now REACHABLE! (449ms / 1000ms) Aug 25 15:26:19 NOTICE[1867]: Peer '5108' is now REACHABLE! (472ms / 1000ms) Aug 25 15:27:18 NOTICE[1867]: Peer '5103' is now UNREACHABLE! Last qualify: 448 Aug 25 15:27:21 NOTICE[1867]: Peer '5107' is now UNREACHABLE! Last qualify: 449 Aug 25 15:27:23 NOTICE[1867]: Peer '5108' is now UNREACHABLE! Last qualify: 472 NUMBER 2 -- Why "cause 3" and "Still have a call" Aug 25 11:08:47 NOTICE[1867]: Peer '5108' is now UNREACHABLE! Last qualify: 460 Aug 25 11:08:51 NOTICE[1867]: Unable to create channel of type 'SIP' (cause 3) Aug 25 11:08:55 NOTICE[1867]: Unable to create channel of type 'SIP' (cause 3) Aug 25 11:09:20 NOTICE[1867]: Unable to create channel of type 'SIP' (cause 3) Aug 25 11:09:28 NOTICE[1867]: Unable to create channel of type 'SIP' (cause 3) Aug 25 11:09:34 NOTICE[1867]: Peer '5103' is now REACHABLE! (457ms / 1000ms) Aug 25 11:09:39 NOTICE[1867]: Peer '5108' is now REACHABLE! (551ms / 1000ms) Aug 25 11:09:56 NOTICE[1867]: Still have a call... Aug 25 11:09:56 NOTICE[1867]: Peer '5001' is now REACHABLE! (83ms / 1000ms) Aug 25 11:40:29 NOTICE[1867]: Unable to create channel of type 'SIP' (cause 3) Aug 25 11:40:30 NOTICE[1867]: Peer '5107' is now REACHABLE! (350ms / 1000ms) Aug 25 11:40:31 NOTICE[1867]: Peer '5108' is now REACHABLE! (355ms / 1000ms) Aug 25 11:49:18 NOTICE[1867]: Peer '5108' is now UNREACHABLE! Last qualify: 449 Aug 25 11:49:42 NOTICE[1867]: Still have a call... Aug 25 11:49:42 NOTICE[1867]: Peer '5003' is now REACHABLE! (26ms / 1000ms) Aug 25 11:57:04 NOTICE[1867]: Unable to create channel of type 'SIP' (cause 3) Aug 25 11:58:14 NOTICE[1867]: Unable to create channel of type 'SIP' (cause 3) NUMBER 3 -- This is also repeated quite a bit. Aug 24 14:36:30 WARNING[8809]: Maximum retries exceeded on call [EMAIL PROTECTED] for seqno 102 (Non-critical Request) Aug 24 14:36:30 WARNING[8809]: Maximum retries exceeded on call [EMAIL PROTECTED] for seqno 102 (Non-critical Request) Aug 24 14:36:30 WARNING[8809]: Maximum retries exceeded on call [EMAIL PROTECTED] for seqno 102 (Non-critical Request) Any pointers, documents, help criticisms welcome..................Thanks...................Mike
You've probably got qualify= on your peers in sip.conf. So Asterisk is sending out a SIP OPTIONS msg to which it's waiting for the peer's reply. If it doesn't respond, it then marks the peer as unreachable, and you then cannot dial out to the peer because it's state is UNREACHABLE which will cause (status 3) messages. You might consider increasing your qualify= time and see if that corrects your problems. If not, you're going to need to start looking at possible firewall/network interruptions between your Asterisk instance and your devices to see if they are knocking down traffic that might be trying to flow between. BJ -- Bird's The Word Technologies, Inc. http://www.btwtech.com/ _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
