summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatt Jordan <mjordan@digium.com>2015-05-07 07:02:49 -0500
committerGerrit Code Review <gerrit2@gerrit.digium.api>2015-05-07 07:02:49 -0500
commit1bf91fbc7325946914e8ab94eedd6849779faff7 (patch)
tree16a5ff7e447fbe396b90a778359e79e15690dc3c
parentfa59e23ddf11a1a1e23471563067c88ca4ad8374 (diff)
parent7103b374ef3712d990fc92dfaaccd0135a1a2b9d (diff)
Merge "chan_dahdi: Improve force_restart_unavailable_chans option description."
-rw-r--r--configs/samples/chan_dahdi.conf.sample10
1 files changed, 6 insertions, 4 deletions
diff --git a/configs/samples/chan_dahdi.conf.sample b/configs/samples/chan_dahdi.conf.sample
index e67574b9b..e0c69ebef 100644
--- a/configs/samples/chan_dahdi.conf.sample
+++ b/configs/samples/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