Re: [Asterisk-Users] Repeated Notice: (UN/REACHABLE)
Should this actually attempt more than a single ping before claiming the remote is unreachable? ie, one packet (out of the two - one request + one reply) might be lost or intermittent congestion might be involved. Perhaps a config option for setting number of consecutive ping requests are un-responsive. Also, subsequent requests might be sooner than otherwise queued. ie, successfully answered probes are re-sent every 60 seconds, while after an un-successful probe, we re-send the next probe in 10 seconds Just my 0.02c worth On Wed, 2004-04-21 at 15:03, Robert Hajime Lanning wrote: When you have qualify=yes or some number, then asterisk will poke at the peer, to measure latency. If the peer does not reply or the reply takes to long, you get the UNREACHABLE message, and you will not be able to send/receive calls to/from that channel. When the peer starts replying within the latency threshold, you will get the REACHABLE message, and you will be able to send/receive calls to/from that channel. I get it alot from FWD. Usualy means the peer is to busy (FWD) or something between you and the peer is unstable or over utilized. quote who=Barton Fisher I see repeated over and over the following messages: NOTICE[1142106560]: chan_sip.c:4988 handle_response: Peer '1001' is now REACHABLE then 5 minutes later: NOTICE[1142106560]: chan_sip.c:5958 sip_poke_noanswer: Peer '1001' is now UNREACHABLE both messages repeated over and over Any clue what I can do to fix this? Is there any where I can look up these Notices to find meaning? Thanks Bart ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Repeated Notice: (UN/REACHABLE)
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Adam Goryachev Sent: Wednesday, April 21, 2004 2:29 AM To: [EMAIL PROTECTED] Subject: Re: [Asterisk-Users] Repeated Notice: (UN/REACHABLE) Should this actually attempt more than a single ping before claiming the remote is unreachable? ie, one packet (out of the two - one request + one reply) might be lost or intermittent congestion might be involved. Perhaps a config option for setting number of consecutive ping requests are un-responsive. Also, subsequent requests might be sooner than otherwise queued. ie, successfully answered probes are re-sent every 60 seconds, while after an un-successful probe, we re-send the next probe in 10 seconds Just my 0.02c worth On a somewhat related note. I was experiencing some random SIP UN/REACHABLE messages during random points during the day. This would also come hand-in-hand with poor SIP call quality (jitters, stutters, etc). Yesterday I was tryint to debug a choppy SIP phone and it just so happened that I was in my lab , and noticed that we were using Ghostcast server over multicast to send images to some new PCs. On a whim, I cancelled the ghostcast session and the problem immediatly vanished. Must be a misconfig on the switch (Cisco Cat 4500 with all copper 10/100/1000 ports ) cause the switch load was minimal, but somehow the multicast traffic was screwing with the SIP transmission over the wire. Just something for other people to look for. -sb ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] Repeated Notice: (UN/REACHABLE)
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Adam Goryachev Sent: Wednesday, April 21, 2004 2:29 AM To: [EMAIL PROTECTED] Subject: Re: [Asterisk-Users] Repeated Notice: (UN/REACHABLE) Should this actually attempt more than a single ping before claiming the remote is unreachable? ie, one packet (out of the two - one request + one reply) might be lost or intermittent congestion might be involved. Perhaps a config option for setting number of consecutive ping requests are un-responsive. Also, subsequent requests might be sooner than otherwise queued. ie, successfully answered probes are re-sent every 60 seconds, while after an un-successful probe, we re-send the next probe in 10 seconds Just my 0.02c worth That would be more robust/quicker to recover. You do have to remember that the RTP session (when you make a call) does not try to recover. So, usually when the SIP poke fails, the RTP would be of bad quality. quote who=Bisker, Scott (7805) On a somewhat related note. I was experiencing some random SIP UN/REACHABLE messages during random points during the day. This would also come hand-in-hand with poor SIP call quality (jitters, stutters, etc). Yesterday I was tryint to debug a choppy SIP phone and it just so happened that I was in my lab , and noticed that we were using Ghostcast server over multicast to send images to some new PCs. On a whim, I cancelled the ghostcast session and the problem immediatly vanished. Must be a misconfig on the switch (Cisco Cat 4500 with all copper 10/100/1000 ports ) cause the switch load was minimal, but somehow the multicast traffic was screwing with the SIP transmission over the wire. Just something for other people to look for. You would need to configure the switch for IGMP snooping and the ghost clients need to send multicast group membership requests, that the switch will be able to snoop. Otherwise multicast traffic is broadcast to every active port. So, it is not the switch that is being overrun, it is your SIP endpoints, that are flooded with the ghost traffic. -- END OF LINE -MCP ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Repeated Notice: (UN/REACHABLE)
When you have qualify=yes or some number, then asterisk will poke at the peer, to measure latency. If the peer does not reply or the reply takes to long, you get the UNREACHABLE message, and you will not be able to send/receive calls to/from that channel. When the peer starts replying within the latency threshold, you will get the REACHABLE message, and you will be able to send/receive calls to/from that channel. I get it alot from FWD. Usualy means the peer is to busy (FWD) or something between you and the peer is unstable or over utilized. quote who=Barton Fisher I see repeated over and over the following messages: NOTICE[1142106560]: chan_sip.c:4988 handle_response: Peer '1001' is now REACHABLE then 5 minutes later: NOTICE[1142106560]: chan_sip.c:5958 sip_poke_noanswer: Peer '1001' is now UNREACHABLE both messages repeated over and over Any clue what I can do to fix this? Is there any where I can look up these Notices to find meaning? Thanks Bart -- END OF LINE -MCP ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
