From: Richard Mudgett <rmudgett@digium.com>
Date: Wed, 6 May 2015 21:00:40 +0000 (-0500)
Subject: chan_dahdi: Improve force_restart_unavailable_chans option description.
X-Git-Tag: 11.18.0-rc1~21
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d5db20302479f7f2c83c92def57196ab53b1ed5b;p=thirdparty%2Fasterisk.git

chan_dahdi: Improve force_restart_unavailable_chans option description.

ASTERISK-25034
Reported by: Richard Mudgett

Change-Id: I1ff8f02124d2f4abd632a050da52c64285bb7f30
---

diff --git a/configs/chan_dahdi.conf.sample b/configs/chan_dahdi.conf.sample
index 584be46cb2..51f6daf16d 100644
--- a/configs/chan_dahdi.conf.sample
+++ b/configs/chan_dahdi.conf.sample
@@ -196,10 +196,12 @@ context=public
 ;
 ;resetinterval = 3600
 ;
-; Enable per span to force a RESTART on a channel that returns a cause
-; code of PRI_CAUSE_REQUESTED_CHAN_UNAVAIL(44).  If the cause is because
-; of a stuck channel on the peer and the channel is always the next
-; channel we pick for an outgoing call then this might help.
+; Enable per ISDN span to force a RESTART on a channel that returns a cause
+; code of PRI_CAUSE_REQUESTED_CHAN_UNAVAIL(44).  If this option is enabled
+; and the reason the peer rejected the call with cause 44 was that the
+; channel is stuck in an unavailable state on the peer, then this might
+; help release the channel.  It is worth noting that the next outgoing call
+; Asterisk makes will likely try the same channel again.
 ;
 ; NOTE: Sending a RESTART in response to a cause 44 is not required
 ; (nor prohibited) by the standards and is likely a primitive chan_dahdi