asterisk users - Nov 2005 - pstn-destination beeing cut in logs and cdrs

good morning!

last week i've started a disa service with approx. 500 calls/day. it is
used by people with cell phones who dial in to asterisk and get the
second tone to dial international pstn numbers(therefore it's zap
only). since disa is the only application in my asterisk installation
used by so many people i can't tell for sure if the problem i've
experienced is only related to disa or rather a general issue, though
i've only seen it in conjunction with disa yet: when parsing my cdr's
yesterday i realized that there were some calls(about 1 in 100 calls)
were the (pstn-)numbers that had been dialed were very short but the
call didn't fail and billsec were up to 900 secs(allthough it was
obviously impossible to dial those numbers). the recorded dst-field was
e.g. 0049 or 00386 - since i record the verbose log i had a look at it
and the number that had been recorded had also been cut:

Nov 23 12:07:40 VERBOSE[22603] logger.c:     -- Executing
Dial("Zap/2-1", "Zap/G1/0063|120|") in new stack
Nov 23 12:07:40 VERBOSE[22603] logger.c:     -- Requested transfer capability:
0x00 - SPEECH
Nov 23 12:07:40 VERBOSE[22603] logger.c:     -- Called G1/0063
Nov 23 12:07:50 VERBOSE[22603] logger.c:     -- Zap/123-1 is proceeding passing
it to Zap/2-1
Nov 23 12:07:54 VERBOSE[22603] logger.c:     -- Zap/123-1 is ringing
Nov 23 12:08:00 VERBOSE[22603] logger.c:     -- Zap/123-1 answered Zap/2-1
Nov 23 12:08:00 VERBOSE[22603] logger.c:     -- Attempting native bridge of
Zap/2-1 and Zap/123-1
Nov 23 12:17:46 VERBOSE[22603] logger.c:     -- Hungup 'Zap/123-1'
Nov 23 12:17:46 VERBOSE[22603] logger.c:   == Spawn extension (disa2, 0063, 9)
exited non-zero on 'Zap/2-1'
Nov 23 12:17:46 VERBOSE[22603] logger.c:     -- Hungup 'Zap/2-1'

i asked my telco for detailed cdr's and the matching calls they
recorded are, as expected, full international numbers(e.g.
00636442887245). for some reason asterisk seems to output a wrong
dst-value to the cdr's and the logs but dial them correctly(under the
hood).

in the changelogs(2005-11-06) i found the entry: "* apps/app_disa.c
apps/app_forkcdr.c: Fix to use correct arguments to ast_cdr_reset" does
someone know if this is related to what i experience? i also had a look
at mantis but i could not find a bug report with related problems...

i'm currently using 1.2beta2 but look forward to upgrade to 1.2 soon,
hope that fixes it.

regards
christian