[asterisk-r2] Fwd: Delay - Outgoing calls

[Aleks Honma]

Moises you probably already know that, but man you rock!

Timer is gone and I get connected 3s earlier, so from 8s in my test we have
gone done to 5s.

Now the issue seems that it is taking way too much time between sending out
digits for ANI and DNIS. On my test above I was dialing just 5 digits
(10315) that that is why it was taking 8s. For regular phone number where I
dial 021ZZ XXXX-XXXX it takes about 15 seconds or more.

Is there any option to tweak this ?

Thanks again in advance for your time,
Aleks

On Thu, May 26, 2016 at 11:23 AM, Moises Silva <moises.silva at gmail.com>
wrote:

> You can try setting this parameter in the advanced protocol file:
>
> mf_g1_tones.no_more_dnis_available=F
>
> This will force openr2 to send an F when there are no more DNIS available.
> The Brazilian variant by default is using the timeout mechanism, but your
> telco may accept the F.
>
>
> -
>
> Moy
>
> On Wed, May 25, 2016 at 7:34 AM, Aleks Honma <aleks.honma at gmail.com>
> wrote:
>
>> Hello R2 Specialists,
>>
>>  I have been struggling for some time trying to find the source for the
>> delay in initiating an OUTBOUND call.
>>
>>  The first question is what is a reasonable (normal) wait time between
>> the last digit dialed and the first ring in Asterisk with an E1 setup for
>> an outbound call?
>>
>>  My call takes beyond 8 seconds to connect. Just for ref. same link with
>> old legacy Siemens PBX was almost instant.
>>
>> My setup:
>> - Country: Brazil
>> - Telco: Embratel
>> - Link type: E1 R2 (CAS)
>> - Freepbx 13, Asterisk 13.8.2
>>
>> Implementation scenario:
>> Embratel E1 <-> Freepbx (Digium TE235 -2 span E1)
>>
>>  I "see" time counting at this stage below, here alone we have about 5
>> seconds of wait time.
>>
>> [2016-05-20 13:06:01] DEBUG[22751][C-0000005b]: chan_dahdi.c:3892
>> dahdi_r2_write_log: Chan 23 - Sending DNIS digit 5
>> [2016-05-20 13:06:01] DEBUG[22751][C-0000005b]: chan_dahdi.c:3892
>> dahdi_r2_write_log: Chan 23 - Group A DNIS request handled
>> [2016-05-20 13:06:01] DEBUG[22751][C-0000005b]: chan_dahdi.c:3892
>> dahdi_r2_write_log: Chan 23 - No more DNIS. Doing nothing, waiting for
>> timeout.
>> [2016-05-20 13:06:01] DEBUG[22751][C-0000005b]: chan_dahdi.c:3892
>> dahdi_r2_write_log: Chan 23 - Group A DNIS request handled
>> [2016-05-20 13:06:04] DEBUG[22751][C-0000005b]: chan_dahdi.c:3892
>> dahdi_r2_write_log: Chan 23 - Sending category National Subscriber
>> [2016-05-20 13:06:05] DEBUG[22751][C-0000005b]: chan_dahdi.c:4648
>> dahdi_ec_enable: Enabled echo cancellation on channel 23
>> MFC/R2 call has been accepted on forward channel 23
>>     -- DAHDI/23-1 is ringing
>> [2016-05-20 13:06:05] DEBUG[1968]: devicestate.c:474 do_state_change:
>> Changing state for DAHDI/23 - state 6 (Ringing)
>> [2016-05-20 13:06:05] DEBUG[1968]: devicestate.c:474 do_state_change:
>> Changing state for PJSIP/820 - state 2 (In use)
>>
>>  I understand that people usually have delays with broken dialplans, but
>> in this case it seems that we have gone by all that pretty fast and the
>> trouble as above is from the trunk forward.
>>
>>  Any one could share a tip for me to follow?
>>
>> Many thanks in advance,
>> Aleks Honma
>>
>>
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>
>> asterisk-r2 mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-r2
>>
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-r2
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-r2/attachments/20160526/451ee83c/attachment.html>