<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18882"></HEAD>
<BODY>
<DIV><FONT size=2 face=Arial>Overlap receiving timeout, plus dialplan latency,
causes network to retry SETUP </FONT></DIV>
<DIV><FONT size=2 face=Arial><A
href="https://issues.asterisk.org/view.php?id=16789">https://issues.asterisk.org/view.php?id=16789</A></FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><SPAN class=653182117-09022010><FONT size=2 face=Arial>This patch removes
the requirement that some may have found that you need to insert a Proceeding()
statement very early in your dialplan, otherwise an inbound overlap call
may retry and fail.</FONT></SPAN></DIV>
<DIV><SPAN class=653182117-09022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=653182117-09022010><FONT size=2 face=Arial>Our experience was
from a PRI connected PABX, if we took too long doing database lookups, the
PABX would resend the SETUP, asterisk doesn't handle these yet,
treats as not newcall and rejects it.</FONT></SPAN></DIV>
<DIV><SPAN class=653182117-09022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=653182117-09022010><FONT size=2 face=Arial>Please feedback to
the bug.</FONT></SPAN></DIV>
<DIV><SPAN class=653182117-09022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=653182117-09022010><FONT size=2 face=Arial>Currently the patch
is for Asterisk 1.6.1, but the issue applies to all.</FONT></SPAN></DIV>
<DIV><SPAN class=653182117-09022010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=653182117-09022010><FONT size=2 face=Arial>Alec
Davis</FONT> </SPAN></DIV></BODY></HTML>