Re: Answer()ing a local Originate takes 500ms!?

"Joshua C. Colp" <[email protected]>
Newsgroups gmane.comp.telephony.pbx.asterisk.user
Message-ID <CAM0A2Z2Z-28xrsW-fzdaTanDEiVgjnmmrK1byVNeerLnjZ=A5g@mail.gmail.com>
On Fri, Nov 11, 2022 at 12:09 PM Antony Stone <
[email protected]> wrote:

> Hi.
>
> Asterisk 16.2.1
>
> I have a dialplan where one context (named "inbound") performs:
>
> Originate(Local/${Target}@inOrig,exten,inbound,${EXTEN},208)
>
> The idea is that this command will spawn a "call" to the context "inOrig"
> on
> the same machine, and then return to the "inbound" context at priority 208.
>
> Priority 208 is simply a NoOp(Returned from inOrig)
>
> The "inOrig" context does:
>
> NoOp(Answering inbound call)
> Answer()
> NoOp(Returned to inbound context)
> Originate(Local/${EXTEN}@dialout,exten,BridgIt,${EXTEN},1)
>
> It's all doing what I want / expect, but I am seeing, completely
> consistently,
> a 500ms delay in the Answer() application.
>
> So, I get the following sequence of timings:
>
> 08:41:49.514918 inbound:201 Originate(.....)
> 08:41:49.516459 inOrig:1 NoOp(Answering inbound call)
> 08:41:49.517016 inOrig:2 Answer()
> 08:41:49.517489 inbound:208 NoOp(Returned from inOrig)
> 08:41:50.017454 inOrig:3 NoOp(Returned to inbound context)
>
> I have analysed dozens of calls and there is always a ~500ms delay between
> when the Answer() has clearly completed (because control returns to
> priority
> 208 of the "inbound" context), and when the inOrig context continues with
> the
> following NoOp.
>
> https://wiki.asterisk.org/wiki/display/AST/Application_Answer tells me
> that
> the Answer() application takes an optional parameter which causes Asterisk
> to
> wait that number of milliseconds before returning to the dialplan after
> answering the call.
>
> Does this undocumentedly default to 500?
>
> Are the results I'm seeing expected, is there something wrong with my
> dialplans, is there some way to eliminate this delay?
>

There is a hard coded minimum of 500 milliseconds for media to flow. You'd
have to modify the code to remove it.

-- 
Joshua C. Colp
Asterisk Project Lead
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org

-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

Check out the new Asterisk community forum at: https://community.asterisk.org/

New to Asterisk? Start here:
      https://wiki.asterisk.org/wiki/display/AST/Getting+Started

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.