Re: Strange digits "invented" by dialer.exe

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi,

You may want to try lineTranslateAddress() with exactly the same number.
Can you reproduce the issue with TAPI Browser TB20 ?
Please post a TB20.log and enable Options/LogParameters and /ShowTimeStamps in
TB20.

I have som trouble to use the TB20, cause I dont know how to add a
Address (Phonenumber) to Translate. I managed it to initialize and
open a line, but when it comes to TranslateAddress() I am totaly
overwhelmed. (I have no TAPI Programming Skills). When I doubleclick
on LineTranslateAddress() there are 7 Parameters to choose from:
hLineApp, dwDeviceID, APIVersion, IpszAddressIn, dwCard,
dwTranslateOptions, lpTranslateOutput. Each of them has different
values to set (all in hex) and then a field with Bit flags options....
What to do ?

I think some options can be configured with "options > Default values"
But there I don't know what to fill in there...

Any suggestions what I have to do next ?

-- trace of TB20
14:40.52.54 : Calling lineInitialize
lphLineApp=x329550
hInstance=x7cd0000
lpfnCallback=x7ce0891
lpszAppName=x12f3c0
lpdwNumDevs=x12f49c
14:40.52.69 : lineInitialize returned SUCCESS
num line devs = 7
14:40.57.633 : Calling lineOpen
hLineApp=x80000300
dwDeviceID=x0
lphLine=x329ac8
APIVersion=x10003
dwExtVersion=x0
dwCallbackInstance=x0
dwPrivileges=x1
dwMediaModes=x10
lpCallParams=x0
14:40.57.633 : lineOpen returned SUCCESS
14:41.3.822 : Calling lineTranslateAddress
hLineApp=x80000300
dwDeviceID=x0
APIVersion=x20000
lpszAddressIn=x12e338
dwCard=x0
dwTranslateOptions=x1
lpTranslateOutput=x3239d8
14:41.3.822 : lineTranslateAddress returned SUCCESS
LINETRANSLATEOUTPUT
dwTotalSize=x1000
dwNeededSize=x45
dwUsedSize=x45
dwDialableStringSize=x7
dwDialableStringOffset=x28
35353554 xx003535 xxxxxxxx xxxxxxxx T55555.
dwDisplayableStringSize=x6
dwDisplayableStringOffset=x36
xxxx3535 xxxxxxxx xxxxxxxx xxxxxxxx 55
00353535 xxxxxxxx xxxxxxxx xxxxxxxx 555.
dwCurrentCountry=x1
dwDestCountry=x0
dwTranslateResults=x0,
--- end log --
.

Relevant Pages

  • Re: lineOpen fails with LINEERR_OPERATIONFAILED
    ... "Grant Schenck" wrote: ... I have used TB20 to provide additional trace. ... Calling lineInitialize ... lineInitialize returned SUCCESS ...
    (microsoft.public.win32.programmer.tapi)
  • problems with message order and GetCallInfo
    ... the messages received from TAPI are in another order as shown in TB20 ... Calling lineInitializeEx ... lineInitializeEx returned SUCCESS ... lineGetCallStatus returned SUCCESS ...
    (microsoft.public.win32.programmer.tapi)
  • Re: lineOpen fails with LINEERR_OPERATIONFAILED
    ... I have used TB20 to provide additional trace. ... Calling lineInitialize ... lineInitialize returned SUCCESS ...
    (microsoft.public.win32.programmer.tapi)
  • Re: How can TAPI listen twice ?
    ... I have tried to reproduce the issure using TB20. ... - checked options\auto-deallocate idle monitored calls ... 9:16.59.453: lineInitialize returned SUCCESS ... > Can you reproduce the issue with TAPI Browser TB20? ...
    (microsoft.public.win32.programmer.tapi)
  • Re: lineOpen fails with LINEERR_OPERATIONFAILED
    ... I do not see these events when my application successfully uses TAPI to ... I have used TB20 to provide additional trace. ... Calling lineInitialize ... lineInitialize returned SUCCESS ...
    (microsoft.public.win32.programmer.tapi)