[asterisk-dev] Bounty

[CDR]

The US has hundreds of rural area codes. Some carriers just timeout on those
areas, while working normally with "standard" urban areas. So we need this
timer. The problem is that 1.6 has this bug and for months now nobody has
been able to fix it.
Federico

On Thu, Feb 25, 2010 at 9:09 AM, Benny Amorsen
<benny+usenet at amorsen.dk<benny%2Busenet at amorsen.dk>
> wrote:

> CDR <venefax at gmail.com> writes:
>
> > I need a new Timeout parameter added to the Dial application, for SIP
> > dialing. The new timeout would be "first-ring" timeout, as opposed to
> > timeout for connection. If we don't get a 180 Ringing message before a
> > certain amount of seconds, the call fails. This a needed addition to
> > Asterisk. I need this in version 1.4 and cannot wait the normal time for
> a
> > "new feature" process to complete. The rationale is clear: many carriers
> > will hold the call indefinitely, instead of returning a 503. If the call
> > is ringing, then I don't care if it rings for 60 seconds, but if there is
> > no ringback before 6 seconds, I need yo try another carrier and move on.
>
> Is this something that you experience a lot of carriers doing in normal
> use? It seems rather unusual for a carrier to fail to make a timely
> reply except when the carrier is down completely. If the carrier is down
> completely, you can add qualify for that particular carrier, and your
> calls should fail immediately instead of waiting.
>
>
> /Benny
>
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20100225/9c654968/attachment.htm