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 <[EMAIL PROTECTED]> 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
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
