C++/VB - can not use atsp32 with dialer.exe

Hi!

I am playing around with atsp32 sample. Building, installing and
configuration works fine. When I start dialer.exe, I can see the lines
offered by atsp32. But when I choose a line and press OK, dialer.exe
does not accept it, because next time when I enter the configuration the
line for phone calls is switched back to <automatic selection>.

Further, if I just try to dial, dialer.exe does not try to dial via the
atsp32 lines. So, what must a TSP support to get used by dialer.exe? I
saw that atsp32 sets numPhones=0 during TSPI_providerEnumDevices - might
that be the cause of the problem?

Thanks
Klaus

  Klaus Darilion replied to Klaus Darilion

Klaus Darilion schrieb:

Just answering myself: dwPermanentLineID must be set in
TSPI_lineGetDevCaps().

regards
klaus

Query regarding to permanent line ID C++ / VB hello friends, Can any one brief the dwPermanentLineID parameter in LINEDEVCAPS structure. An example will be more helpful. Actually I want to know device ID and their significance. Thanks, Mohit Win32 TAPI Discussions LINEDEVCAPS.dwPermananetLineID (1) TAPIaroundTheWorld (1) DwPermanentLineID (1) LineGetDevCaps (1) DwDeviceID (1) LineOpen (1) Windows (1) ReplySo (1) Mohit, dwDeviceID range from 0 to num_devices - 1. It is assigned by TAPISRV. It is used to specify devices at lineOpen(), lineGetDevCaps() etc. LINEDEVCAPS.dwPermananetLineID should be unique (regarding the PC) for all devices. It is created your reply So, does TAPI or TAPI Application make any mapaping between the dwDeviceID and dwPermanentLineID? For an example, initially a TSP detects 5 line device then it will provide the reflected or used in TAPI? Thnaks, Mohit Mohit, you are welcome. TAPISRV just passes he dwPermanentLineID from the TSP to the TAPI app for a requested dwDeviceID via lineGetDevCaps(). It is up to the TAPI app to do any mapping it requires. Yes, that TAPISRV may re-use the dwDeviceID and re-assign the same - TSP may assign new dwPermanentLineID if it get un-installed and re- installed Think of the following scenario. A user

fundamental question. The call to lineInitializeEx() finds two devices in my computer. When I call lineGetDevCaps() for each of the two devices, I can see no difference between the two devices other than the dwPermanentLineID. How do I know which is the telephone and which is the telephone line? I Win32 TAPI Discussions TAPIaroundTheWorld (1) DwRedirectionIDFlags (1) DwRemoveFromConfCaps (1) DwRedirectingIDFlags (1) DwMaxNumActiveCalls (1) DwConnectedIDFlags (1) DwPermanentLineID (1) DwCalledIDFlags (1) Dan, please post a TAPI Browser TB20.log for lineGetDevCaps() and lineGetAddressCaps() for both dwDeviceIDs. What telephony devices do you have? See my TAPI and hInstance = x1000000 lpfnCallback = x1004105 lpszAppName = x10121a0 lpdwNumDevs = x62f3b4 lineInitialize returned SUCCESS num line devs = 2 lineGetDevCaps params: hLineApp = x402d30 dwDeviceID = x0 APIVersion = x10004 dwExtVersion = x0 lpLineDevCaps = x400078 lineGetDevCaps returned SUCCESS LINEDEVCAPS dwTotalSize = x1000 dwNeededSize = x239 dwUsedSize = x239 dwProviderInfoSize = x3e dwProviderInfoOffset = x1bd 646e6957 2073776f Service Provid 66207265 5520726f 6576696e 6c617372 er for Universal 646f4d20 44206d65 65766972 xxxx0072 Modem Driver. dwPermanentLineID = x18dae dwLineNameSize = x1c dwLineNameOffset = x185 2e532e55 626f5220 6369746f 36352073 U.S. Robotics 56 6f56204b 20656369 fundamental question. The call to lineInitializeEx() finds two devices in my computer. When I call lineGetDevCaps() for each o

I look in the LINECALLINFO struct for dwAddressID on an active call I get 0xFFFFFFFF. lineGetDevCaps on the line using TB2.0: lineGetDevCaps returned SUCCESS LINEDEVCAPS dwTotalSize = x1000 dwNeededSize = x168 dwUsedSize = x168 dwProviderInfoSize = x11 dwProviderInfoOffset = x124 6972654d 6e616964 xxxxxxxx xxxxxxxx . dwSwitchInfoSize = x3 dwSwitchInfoOffset = x146 xxxx3532 xxxxxxxx xxxxxxxx xxxxxxxx 25 xxxxxx00 xxxxxxxx xxxxxxxx xxxxxxxx . dwPermanentLineID = x70040 dwLineNameSize = xe dwLineNameOffset = x14c 656e694c 2e353220 2e302e30 xxxx0031 Line 25.0.0.1. dwStringFormat CCT version 5. Angus Win32 TAPI Discussions DwDigitDuration (1) DwMaxNumActiveCalls (1) DwDialSpeed (1) DwProviderInfoOffset (1) LineGetDevCaps (1) DwNumAddresses (1) DwSwitchInfoOffset (1) DefDialParams (1) That sounds like a bug. Did you check I look in the LINECALLINFO struct for dwAddressID on an active call I get 0xFFFFFFFF. lineGetDevCaps on the li

About .dwPermanentLineID in multiline device C++ / VB Is .dwPermanentLineID identifier for each line or for the whole device? I am testing now 4 line device (Hi-Phone Maestro) but each of 4 lines has the same .dwPermanentLineID. Is that normal? Your comments please, Fred Win32 TAPI Discussions TAPIaroundTheWorld (1 DwPermanentLineID (1) DwPermanentLineID (1) DwPermenentLineID (1) Maestro (1) Windows (1) Frappr (1) Toto® (1) Fred schrieb: as the says - for the line. no regards klaus Fred, I regard this a TSP bug. The dwPermanentLineID should be unique in the system (PC or mobile phone). - - Best Regards Andreas Marschall Microsoft might be a case of rather than answering the question asking WHY Fred needs the dwPermanentLineID. Perhaps he really wants something else like the device name or device ID. dwPermenentLineID may to both of us more advantageous (?) if we start communicating directly, Fred. Fred keywords: About, .dwPermanentLineID, in, multiline, device description: Is .dwPermanentLineID identifier for each line or for the whole device