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
-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
-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
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
