[asterisk-bugs] [Asterisk 0016789]: [patch] Overlap receiving timeout, plus dialplan latency, causes network to retry SETUP
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Feb 10 05:41:41 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=16789
======================================================================
Reported By: alecdavis
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16789
Category: Channels/chan_dahdi
Reproducibility: sometimes
Severity: minor
Priority: normal
Status: ready for testing
Asterisk Version: SVN
JIRA: SWP-887
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1
SVN Revision (number only!): 243988
Request Review:
======================================================================
Date Submitted: 2010-02-08 19:57 CST
Last Modified: 2010-02-10 05:41 CST
======================================================================
Summary: [patch] Overlap receiving timeout, plus dialplan
latency, causes network to retry SETUP
Description:
An overlap received call, should have a PROCEEDING sent when asterisk has
deemed that no further digits are coming, IE when asterisk starts executing
the dialplan.
The issue is, ast_waitfordigit in ss_thread waits 'matchdigittimeout'
which set 3 seconds, then there is dialplan delay, which may take a while
to execute PROGRESS(), PROGRESS() or ANSWER(). In our case, database
lookups.
When the network retries the SETUP, with the same channel and call
reference, libpri deems this as a 'Not a new call' and promptly rejects the
call. Now the call is lost!.
Previously it has required the PROCEEDING() to be the the first line of
the dialplan context.
======================================================================
----------------------------------------------------------------------
(0117938) alecdavis (manager) - 2010-02-10 05:41
https://issues.asterisk.org/view.php?id=16789#c117938
----------------------------------------------------------------------
Wimpy:
We see a timeout, which doesn't seem to be configurable on our switch.
The Q.931 standard implies a Proceeding should be sent.
Our Telco send a Proceeding when it's deemed enough digits have been
dialled.
thus: it seems like the right thing to do.
Issue History
Date Modified Username Field Change
======================================================================
2010-02-10 05:41 alecdavis Note Added: 0117938
======================================================================
More information about the asterisk-bugs
mailing list