[Asterisk-Users] Repeated Notice: (UN/REACHABLE)

[Adam Goryachev]

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