[Asterisk-Users] Truncated CDR records

[Steve Totaro]

I am pretty sure it will wait if at the beginning of the dialstring like
this:
exten => _.,1,Dial(ZAP/g1,(wwww${EXTEN}))

this amounts to a two second delay, each w = 500ms

Thanks,
Steve

> -----Original Message-----
> From: Innocent Evil [mailto:innocent.evil at inbox.com]
> Sent: Saturday, November 26, 2005 10:45 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [Asterisk-Users] Truncated CDR records
> 
> you can use 'w' option with 'Dial' on 1.2.x
> I don't think w do anything like 'wait', If I am wrong, correct me
someone
> please
> According to app_dial.c
> 
> "    w    - Allow the called party to enable recording of the call by
> sending\n"
> "           the DTMF sequence defined for one-touch recording in
> features.conf.\n"
> "    W    - Allow the calling party to enable recording of the call by
> sending\n"
> "           the DTMF sequence defined for one-touch recording in
> features.conf.\n";
> 
> Thanks,
> 
> 
> --
> You don't have any choice, you already made it before you came here.
> 
> 
> 
> 
> 
> > -----Original Message-----
> > From: a0305292 at unet.univie.ac.at
> > Sent: Fri, 25 Nov 2005 22:04:04 +0100
> > To: asterisk-users at lists.digium.com
> > Subject: Re: [Asterisk-Users] Truncated CDR records
> >
> > fixed by adding a w at the end of the dialstring:
> >
> > "w" would normally indicate a "wait", but putting it at the end of
your
> > dialstring will cause asterisk to assume the number before is
> > "complete".(sic!) ~markster
> >
> > e.g. Dial(Zap/G4/${EXTEN}w)
> >
> > regards
> > chris
> >
> >
> > On Fri, 25 Nov 2005 20:31:41 +0100
> > Christian B <a0305292 at unet.univie.ac.at> wrote:
> >
> >> Hello Group!
> >>
> >> While parsing my cdrs of the last week, i realized that approx. 1
in
> >> 100 _successful_ outbound zap-calls are recorded with a truncated
> >> destination number in the verbose logs and in the cdrs.
> >>
> >> Several digits are simply missing. eg 0049xxxxxxxx is recorded as
> >> 0049. I have received cdrs from the telco, and have verified that
the
> >> "long version" was definitely dialed, and answered.
> >>
> >> Most of my traffic (99%) is via DISA, and so far this behaviour has
> >> only surfaced with outbound DISA calls. I can't be certain that its
a
> >> DISA only problem, though.
> >>
> >> I've added the dialplan that applies to these
calls(dialplan_disa.txt),
> >> the agis
> >> that are beeing executed(disa-usergroup1.sh, disacut.sh), samples
of
> >> verbose
> >> logs for wrong numbers, cdr's and corresponding cdr's from my
> >> telco(examples_cdr_verboselog.txt). I've upgraded to 1.2 final on
> >> 25.11.2000
> >> 03:00am in the hope this would be resolved but also today i have
faulty
> >> records.
> >>
> >> Hope someone can give me information on this issue.
> >>
> >> regards
> >> christian
> >>
> > _______________________________________________
> > --Bandwidth and Colocation sponsored by Easynews.com --
> >
> > Asterisk-Users mailing list
> > Asterisk-Users at lists.digium.com
> > http://lists.digium.com/mailman/listinfo/asterisk-users
> > To UNSUBSCRIBE or update options visit:
> >    http://lists.digium.com/mailman/listinfo/asterisk-
> users_______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> Asterisk-Users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users